Subject: Re: [boost] [nowide] Request for interest (nowide unicode support for windows)
From: Artyom (artyomtnk_at_[hidden])
Date: 2010-06-17 09:06:03
> > I was talking about v3
> v3 makes it even easier. Internally it always calls
> RemoveFileW on Windows
> regardless is whether the path was created from a narrow or
> wide string.
> > Windows had never supported, does not support
> according to Lars Viklund
> > links it seems like it will never be supported.
> I think you misunderstood me. I meant
> Boost.Filesystem could interpret
> narrow strings as UTF-8 by default on Windows.
This would be really great.
> > So the only way to do the thing right is **always**
> > Wide API on windows and convert normal strings to wide
> one just before
> > calling appropriate API functions.
> Yes. Except that Filesystem handles this by
> converting immediately. It
> makes little difference.
If so this is the way to go. Having boost::filesystem::v3
treating path as UTF-8 on windows would solve lots of issues.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk