Hey Evan,
I apologize for missing this discussion, I'm sure that I'm not seeing
the entire picture and the pros of this argument. I mentioned before
that I'm in support of utf-8 everywhere we can get it.
We are obviously going to have platform specific code for the UI
(win32 /
On Wed, Feb 4, 2009 at 6:53 AM, Dean McNamee de...@chromium.org wrote:
I apologize for missing this discussion, I'm sure that I'm not seeing
the entire picture and the pros of this argument. I mentioned before
that I'm in support of utf-8 everywhere we can get it.
I lost this argument, so I
The proposal was to search-n-replace std::wstring to string16. We would
have to invent a macro to replace L usage. Most usages of string literals
are in unit tests, so it doesn't seem to matter if there is cost associated
with the macro.
My belief is that there isn't much fruit to be had by
On Wed, Feb 4, 2009 at 6:11 PM, Darin Fisher da...@chromium.org wrote:
The proposal was to search-n-replace std::wstring to string16. We would
have to invent a macro to replace L usage. Most usages of string literals
are in unit tests, so it doesn't seem to matter if there is cost associated
Trying to remember what came up along the discussion.
UTF16 is what Mac/win use, so there we can avoid a batch of conversions on
those two platforms. (Mac can take UTF8, but the system would still be
doing conversions to get things into a form it prefers)
Didn't someone say ICU needs things in
On Wed, Feb 4, 2009 at 9:35 AM, Dean McNamee de...@chromium.org wrote:
On Wed, Feb 4, 2009 at 6:11 PM, Darin Fisher da...@chromium.org wrote:
The proposal was to search-n-replace std::wstring to string16. We would
have to invent a macro to replace L usage. Most usages of string
literals
The big string area is webkit, of course. If webkit were 100% UTF-8
already, we might take a different stance on this issue as well.
If it is our goal to get to UTF-8 everywhere, then laying the plumbing for
utf8 strings rather than string16 strings seems like the right thing to do.
Mike
On
+1 to string16
I can't make performance or memory saving claims with a straight face
for any. We just don't process enough strings for us to matter.
On Feb 4, 9:57 am, Mike Belshe mbel...@google.com wrote:
The big string area is webkit, of course. If webkit were 100% UTF-8
already, we might
An angel loses its wings for each 00 byte in UTF-16. Is 'host'
measured in base-2 or base-10?
Linus
On Tue, Feb 3, 2009 at 6:11 PM, Evan Martin e...@chromium.org wrote:
[A bunch of the team met up today to hammer out some decisions.]
In brief: for strings that are known to be Unicode (that
