Re: AfxMessageBox?

Mihai N. wrote:

Maybe because many Unix systems had the good sense to go with UTF-8.

This is very debatable. I don't see it as good sense, but as laziness.
I can tell you that in the Unicode world (UTC and such) UTF-16 is regarded
as the better option for processing, and utf-8 better for transfer/storage.


Hi Mihai:

We have discussed this before. And I'm sure we will again...

I would agree with you, except that unfortunately there are now surrogate pairs in UTF-16. This means that any program that does string manipulation assuming each wchar_t is a single character is technically incorrect, and could fail. Microsoft 16-bit "Unicode" no longer has the advantage that motivated its creation.

I confess that one reason I like UTF-8 is that is backward compatible with code that assumed all ASCII characters. Is this what you mean by lazy?

David Wilkinson
.

Relevant Pages

  • Re: Unicode string libraries
    ... encoding negotiation. ... old languages which have adopted Unicode without much pain. ... compatibility with too many old programs; but char as a holder for UTF-8 ... The limitations of UTF-16 ...
    (comp.programming)
  • Re: Case-sensitivity as option?
    ... Code points beyond 0x10FFFF cannot be encoded with UTF-16, ... it is unlikely that Unicode will ... Windows to UTF-8. ... encode them with normal surrogates. ...
    (comp.lang.forth)
  • Re: unicode in ruby
    ... doesn't support unicode strings natively? ... put on Unix ages ago. ... (When Unix filesystems can write UTF-16 as ... translate to UTF-8 and/or follow the nonsensical POSIX rules for native ...
    (comp.lang.ruby)
  • Re: Unicode Delphi Win32 - which approach
    ... I like the backwards compatibility aspects of UTF-8 vs UTF-16. ... UTF-8 encoding is different from ANSI, at least it's still byte oriented ... encoding, programmers will be forced to "think" Unicode, and not ...
    (borland.public.delphi.non-technical)
  • Re: Unicode Delphi Win32 - which approach
    ... I like the backwards compatibility aspects of UTF-8 vs UTF-16. ... The first 256 Unicode characters map to the ANSI character set. ... entire stream> but calling an API 100 times in a loop I can imagine. ... and explicitly contextualise every string. ...
    (borland.public.delphi.non-technical)
Loading