From: Asmus Freytag [mailto:[EMAIL PROTECTED]]
Sent: Sunday, September 23, 2001 02:24 AM
The typical situation involves cases where large data sets
are cached in
memory, for immediate access. Going to UTF-32 reduces the
cache effectively
by a factor of two, with no comparable
γῆν —
Ἀρχιμήδης
[http://www.macchiato.com]
- Original Message -
From: Ayers, Mike [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 24, 2001 9:23 AM
Subject: RE: UTF-8 UCS-2/UTF-16 conversion for library use
From: Asmus Freytag [mailto:[EMAIL PROTECTED]]
Sent: Sunday
Mike,
The typical situation involves cases where large data sets
are cached in
memory, for immediate access. Going to UTF-32 reduces the
cache effectively
by a factor of two, with no comparable increase in processing
efficiency to
balance out the extra cache misses. This is because
If you think you have the answer to all the problems, then you
don't know all the problems.
I tried to make a point, and apparently made it poorly. I will try
again. It seems that some people are arguing that UTF-16 is the ideal
solution for all computing, and that UTF-8 and
At 13:59 -0500 2001-09-24, Ayers, Mike wrote:
It seems that some people are arguing that UTF-16 is the ideal
solution for all computing, and that UTF-8 and UTF-32 exist only for
network transport.
I tend to think that because I have to make web pages using UTF-8, I
wish that I had better
From: Ayers, Mike [EMAIL PROTECTED]
Analyze problem. Pick solution. In that order.
Wiser advise was ne'er spoken, on *this* topic at least.
I wonder is there is some way that a policy decision can be made to declare
a moratorium on the whole *My* UTF is better than *your* UTF for a while?
Mike,
If you think you have the answer to all the problems, then you
don't know all the problems.
I tried to make a point, and apparently made it poorly. I will try
again. It seems that some people are arguing that UTF-16 is the ideal
solution for all computing, and that
At 10:21 AM 9/21/01 -0700, Kenneth Whistler wrote:
It is my impression, however, that most significant applications
tend, these days, to be I/O bound and/or network
transport bound, rather than compute bound.
...
We don't hear
much, anymore, about how wasteful Unicode is in its storage
of
Tree said:
While the conversion between UTF-8 and UTF-16/UCS-2 is algorithmic and
very fast, we need to remember that a buffer needs to be allocated to
hold the converted result, and the data needs to be copied as things
go in and out of the library.
Well, of course. But then I am mostly a
While the conversion between UTF-8 and UTF-16/UCS-2 is algorithmic and
very fast, we need to remember that a buffer needs to be allocated to
hold the converted result, and the data needs to be copied as things
go in and out of the library.
What is the real impact of this? I don't know: I haven't
10 matches
Mail list logo
