Re: [libxml++] Glib::ustring, lBoost Lib, and libstdc++
- From: "Trappel Martin" <martin trappel ksengineers at>
- To: Loïc Joly <Loic Joly reportive com>
- Cc: libxmlplusplus-general lists sourceforge net
- Subject: Re: [libxml++] Glib::ustring, lBoost Lib, and libstdc++
- Date: Wed, 29 Aug 2007 07:43:08 +0200
> -----Original Message-----
> From: libxmlplusplus-general-bounces lists sourceforge net
> [mailto:libxmlplusplus-general-bounces lists sourceforge net]
> On Behalf Of Loïc Joly
> Sent: Tuesday, August 28, 2007 6:14 PM
> To: libxmlplusplus-general lists sourceforge net
> Subject: Re: [libxml++] Glib::ustring, lBoost Lib, and libstdc++
> > De la part de Tom Browder
> > A couple of years ago I participated in a thread here discussing
> > decoupling libxml++'s dependency on the whole of Glib and friends.
> > Among other things discussed was possible substitutes for ustring.
> > Now I've come back to ask if there has been any thought to
> > that ustring be made a member of the Boost library (for possible
> > future incorporation into the C++ standard library).
> UTF8 string are certainly considered for the C++ standard.
> They would probably not look like Glib::ustring, however, but
> like an instanciation of basic_string with a specific
> char_trait. Here are last versions of the standard evolution
> papers about UTF8 support in the standard:
html (UTF8 litteral) http://www.open-> std.org/jtc1/sc22/wg21/docs/papers/2007/n2149.html (UTF8
html (UTF8 in the SL)
Pfff ... Too me it seems it specifically hasn't been addressed:
(...) items are conspicuously missing from this paper: UTF-8 support, (...)
(...) One way to provide UTF-8 support would be a new string class whose interface is very different from basic_string, (...)
(...) Some form of UTF-8 support is important because there's an awful lot of real-world code that uses UTF-8 even internally, and programmers certainly need UTF-8 to interface with third-party libraries like libxml2. (...)
best regards / mit freundlichen Grüßen,
] [Thread Prev