On Wed, Jan 14, 2009 at 11:40 AM, Emil Dotchevski <emildotchevski@gmail.com> wrote:
On Wed, Jan 14, 2009 at 5:56 AM, Beman Dawes <bdawes@acm.org> wrote:
On Tue, Jan 13, 2009 at 1:17 PM, Emil Dotchevski
Is it true that had the interface of boost::filesystem been defined in terms of utf8, then the only platform on which wchar_t support would have been instrumental is Windows, and we wouldn't have had problems with Cygwin?
The problem isn't so much the interface as the internals. Windows' native character type for file names is wchar_t.
I was thinking that had the boost::filesystem interface been defined in terms of UTF-8, then on Cygwin, Unicode file names would have passed through boost::filesystem flawlessly, only to fail at Cygwin level due to lack of UTF-8 support (in Cygwin.)
But that would have been their problem, not ours, and we wouldn't be talking about dropping (all) Cygwin support.
I
Sorry hit Send prematurely :) I wanted to say "I'm probably missing something but I can't see it." Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode