From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with encoding
Date: Tue, 21 Dec 2010 11:11:33 +0100 [thread overview]
Message-ID: <20101221101133.GJ29474@phare.normalesup.org> (raw)
In-Reply-To: <op.vn14z7m8tpjj8f@lpr>
> BTW: What is the difference what the COUNTRY code and the LANGUAGE code affects?
In your case, you should use a language code since you want to set a
language. ConTeXt has used different sets of codes in the past, but we
now try to follow IETF recommendation "Tag for Identifying Languages"
(http://tools.ietf.org/html/bcp47), because it's the only one that can
be precise enough for our needs (at least among the tagging systems I
know of). For example, you can distinguish between British English and
American English by appending a country code to the language code (hence
"en-gb" and "en-us", respectively). Using a country code to identify a
language is generally a bad idea and should be discouraged, since that's
not what they're meant for, and it can lead to confusion: for example,
you could use the code "uk" to identify English as spoken in the United
Kingdom, but that's actually the language code for Ukrainian, which has
been an actual problem for ConTeXt in the post (in addition to that,
"uk" is not even the proper language code for the United Kingdom: it's
"gb", as written above; the reason why "uk" is used as a DNS top-level
domain is not clear and has lead, alas, to even more confusion).
The authorities that decide upon language and country codes are
different committees of the ISO; the ISO standard for language codes is
ISO 639 (with different parts), and the one for country codes is ISO 3166
(again, with different parts; the two-letter codes of ISO 3166-1 are
generally rather well-known because they're the ones being used for DNS
top-level domains -- with some exceptions, see above).
Arthur
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-12-21 10:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 8:34 Procházka Lukáš Ing. - Pontex s. r. o.
2010-12-21 9:29 ` Mojca Miklavec
2010-12-21 9:37 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-12-21 10:05 ` Hans Hagen
2010-12-21 10:11 ` Arthur Reutenauer [this message]
2010-12-21 10:17 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-12-21 11:19 ` Philipp Gesang
2010-12-21 11:21 ` Philipp Gesang
2010-12-21 11:44 ` Thomas Schmitz
2010-12-21 12:23 ` Arthur Reutenauer
2010-12-21 12:35 ` Hans Hagen
2010-12-21 12:17 ` Arthur Reutenauer
2010-12-21 12:37 ` Hans Hagen
2010-12-21 10:14 ` Mojca Miklavec
2010-12-21 10:35 ` Arthur Reutenauer
2010-12-21 9:43 ` Arthur Reutenauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101221101133.GJ29474@phare.normalesup.org \
--to=arthur.reutenauer@normalesup.org \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).