I did a little homework on this topic and made some discoveries.
First, a colleague of mine at work checked with his friend, the ANSI
representative to ISO TC212, who claimed that all references to ISO
standards in standards-track documents are to the most current version
of that standard. I
Or, alternately, that takes a charset value and returns a
codepage?
try TranslateCharsetInfo()
Bob
You can convert UTF8 characters to UNICODE using
MultiByteToWideChar(CP_UTF8,1,utf8string,-1,unicodestring,size_of_string);
The UTF-8 codepage will be passed to the fucntion.
Antoine Leca [EMAIL PROTECTED] wrote:
This means that some major, significant languages like Turkish and
Yoruba will never get two-letter codes, which seems odd somehow.
Turkish is tr, and Yoruba is yo, since the beginning. What is the
point?
They are not listed in the HTML page on
wParam of WM_INPUTLANGCHANGE *is* the codepage ID (that you can pass
to MultiByteToWideChar(), for example).
I believe wParam gives a charset id, not a codepage id. There's a
difference. I wasn't sure how one gets codepage from charset (short of
maintaining a table).
Unfortunately, the MSDN
On 08/11/2000 08:13:54 AM Doug Ewell wrote:
They are not listed in the HTML page on Michael Everson's site, which
claims to be "complete and up-to-date as of 2000-02-19." But they are
listed in a text file, "Technical contents of ISO 639:1988," originally
typed by Keld Simonsen, wich I had
Hello,
I proposed SCSU (as described in UTR 6) for registration as a charset with IANA (as
"SCSU" with no aliases).
Good news: it was approved on 2000-jul-19.
Bad news: The publication of IANA registrations is currently being redesigned and
re-staffed, therefore nothing has been and will be
On 08/11/2000 10:48:55 AM Mark Leisher wrote:
In the case of Tonga, there may perhaps be a legitimate doubt
whether
to equate
the "to" (Tonga) code with "tog" (Tonga (Nyasa)) or with "ton"
(Tonga
(Tonga Islands)), or with both.
Peter This relates to one of the problems
Peter I don't agree that there isn't a problem: the idea that's applied
Peter in RFC1766 (at least, in the draft for the next version) is that
Peter (a) precedence is given first to ISO 639-1 then to ISO 639-2, and
Peter (b) you use the most specific tag that is appropriate to
First ICU Developer Workshop Meeting
September 11-12, 2000
IBM Emerging Technology Center
Cupertino, California, USA
**
Unicode
10 matches
Mail list logo
