Re: [Boost-bugs] [Boost C++ Libraries] #4581: Filesystem V3 should not require wstring support

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4581: Filesystem V3 should not require wstring support
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-03-24 08:56:18

#4581: Filesystem V3 should not require wstring support
------------------------------------------------+---------------------------
  Reporter:  Steve Soule <sts11dbxr@…>          |       Owner:  bemandawes
      Type:  Bugs                               |      Status:  closed    
 Milestone:  To Be Determined                   |   Component:  filesystem
   Version:  Boost 1.44.0                       |    Severity:  Problem   
Resolution:  wontfix                            |    Keywords:            
------------------------------------------------+---------------------------

Comment (by wim@…):

 I'd also appreciate if this gets fixed. Reasons:
 1. even though it's a pragmatic approach that works in many cases,
 std::wstring is not a nicely portable solution for internationalized
 strings anyway (2 bytes per char on windows, 4 bytes per char on unix, and
 uses in general still an unspecified encoding). It's use should not be
 encouraged. You seem to realise this too, since you provide separate
 unicode methods (u16string, u32string).
 2. many embedded systems don't support wstring. For example: Android,
 uclibc, ...

 I'd be much more interested in a method that is actually generally usable,
 such as a u8string() method that returns UTF8 path info.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/4581#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.