On Tue, Apr 28, 2009 at 4:39 PM, Greg Spencer <gspen...@google.com> wrote:
> 1) I'd like to add some explicit routines for converting to/from UTF8 and
> UTF16. While it's nice (and important) that FilePath uses the platform's
> native string, we've found that many third party libraries have made other
> assumptions, where they always expect UTF8 (char) or UTF16 (wchar_t) paths
> regardless of platform, and converting a FilePath to and from those forms is
> a platform-dependent exercise which should be centralized into the class
> (i.e. adding "ToUTF8" and "ToWide" functions to the class, and explicit
> constructors that take each type).
One thing many of us have found, across multiple projects, is that
wchar_t is fraught with complication as soon as more than one platform
is involved. "wchar_t == UTF16" is a Windowsism (gcc defaults to 4
bytes, for example, and L"mumble" gets stored in UCS-4, not UTF-16).
Chrome started with more or less what you are suggesting, and we moved
off of it after much pain.
--Amanda
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
