Oh, I also forgot to mention, I am also using boost::filesystem::path. I
guess this means I need to use wchar_t everywhere (std::wstring,
boost::filesystem::wpath, etc) and just let wxWidgets do the
encoding/decoding? If I don't have to do any encoding/decoding myself, then
there really is no need for a special object. But just in case I would like
to have the encoding/decoding abilities.
On Sun, Jun 14, 2009 at 12:27 PM, Robert Dailey
Hi everyone, I did a bit of googling to see if Boost 1.39 as any portable support for UTF-16 encoded strings, but I did not find any. I'm currently using wxWidgets in my application, and I need a decent string object to use. I know that wxWidgets has UTF-16 string support through wxString, however I do not want to expose this object in my interfaces. I want to remain as abstracted away from wxWidgets as possible. Having said that, if someone could tell me if there is any existing UTF-16 string support in Boost, I'd appreciate it. I did not find anything in the vault, sandbox, or trunk in Boost.
If boost has no such string object, could someone give me a head start on where to look? Thanks.