Leuven, E. wrote: >> edwin leuven wrote: >> >> fyi, i am not proposing to put the tabular stuff in. so i don't see why i >> couldn't tinker a bit with that... >> >>Of course you can, but if you don't want to put it in what is the purpose >> on working on it? > > life after 1.5 ?
Then I'd suggest to start working on that after 1.5. My experience is that it takes too much time to keep half finished patches in a working state. > i think everybody is waiting for alpha2 (with binaries) to get some > serious feedback, people need to start using 1.5 While that is certainly needed we know a lot of bugs already. Apart from Status.15x there is also bugzilla. And I have something for the windows users: One of the next steps in making non-ascii filenames work will be to actually implement FileName::toFilesystemEncoding(). I know what to do on linux, but not on windows, so it would be nice if somebody could find out the following: What encoding is used for filenames on windows? I know that boost::filesystem has wstring support for filenames on windows, and that probably uses ucs2/utf16. What I do want to know is whether it is also possible to use non-ascii filenames with the std::fstream and narrow strings, or do we need to use the streams of boost::filesystem? Any pointers to some documentation are welcome. Georg
