Re: Code Page problem in SetWindowText

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Tom Serface" <tom.nospam@xxxxxxxxxxxxx> ha scritto nel messaggio
news:Oxv$i6J8HHA.4584@xxxxxxxxxxxxxxxxxxxxxxx

but it's difficult to quantify the difference and I suspect it is
negligible so Unicode seems a better way to go in my opinion.

Hi Tom,

I agree with you.

And maybe if memory space saving is the main target, UTF-8 could be used as
the encoding for Unicode, instead of UTF-16.
But maybe for historical reasons, it seems that internal Windows format for
Unicode is UTF-16 :(
On the other side, IIRC Mac OS X and Linux tend to use UTF-8, but I may be
in mistake...


If you really need to minimize memory space (like you're trying to run an
MFC application on your watch or something) then perhaps, but ...

IIRC, Windows CE (which should be suited to embedded platforms and platforms
with memory limits, not like the "huge" 1-2 GB of RAMs in current desktop
PCs) uses Unicode (UTF-16) and not ANSI :)

Giovanni



.

Relevant Pages

  • 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. ... 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)
  • Re: Unicode string libraries
    ... UTF-8 is the encoding that must be used ... I initially thought that the variable-length characters ... but also that UTF-8 didn't break when Unicode got extended ...
    (comp.programming)
  • Re: AfxMessageBox?
    ... 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, ... 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. ...
    (microsoft.public.vc.mfc)