From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Greek: GR or EL? Czech: CZ or CS? UK: Ukrainian or ...
Date: Wed, 5 Dec 2007 02:40:39 +0100 [thread overview]
Message-ID: <6faad9f00712041740k7c485079y88171590235accf4@mail.gmail.com> (raw)
Hello,
I have noticed that ConTeXt uses "gr" for Greek, but the ISO code
seems to be "el". Less problematic: should agr be grc instead?
(OpenType uses PGR, but I'm not sure if that's the same thing.)
What do the Greek experts say?
Well, English is a story on its own. "us" and "uk" don't have their
own codes as a separate language, and even worse: uk should stand for
Ukrainian!!!
"Norwegian" (which is not a language at all) should be patched
(according to an old user request) once.
A similar problem exists with:
- Chinese (cn instead of zn)
- Czech (cz instead of cs)
- Vietnamese (vn instead of vi)
- Ukrainian (ua instead of uk!!!)
A case where I have no opinion:
- deo
Some languages have already changed their codes in the past:
- Spanish: sp -> es
- German: du -> de
- Slovenian: si -> sl (no trace left, I hope :)
My proposal would be to change:
- gr -> el
- agr -> grc
- cz -> cs
- vn -> vi
- deo -> ? (if at all)
gmh - German, Middle High (ca.1050-1500)
goh - German, Old High (ca.750-1050)
- cn -> zn (with *lots of care*)
And to keep all the needed synonyms. (Besides that: to issue a warning
if possible.)
I have no idea what to do with Ukrainian and UK though.
-------------
Another issue: some languages need some little modifications or alternatives:
1.) In German, Slovenian, Croatian, (maybe in other languages as well)
... one can use two types of quotes:
- „" U+201E/U+201C & ‚' U+201A/U+2018 (sorry, a bug in gmail reencodes them)
- »« U+00BB/U+00AB & ›‹ U+203A/U+2039
It might make sense to be able to say something similar to
\mainlanguage
[german]
[quotes | quotationmarks | quotationstyle =
guillemots | guillemets or comma | ninesix]
2.) I could imagine a Serbian user to request being able to typeset in
two scritpts (Latin or Cyrillic). That means:
- different labels
- loading different hyphenation patterns (even though transcription in
either direction can be made on the fly - I can confirm that a user
has already asked me if I know how to input text in cyrillic and get
output in latin - as he wasn't fluent in reading Cyrillic, he wanted
to misuse ConTeXt to help him read texts from web)
So I could imagine making Cyrillic the default script, but still
letting one to use
\mainlanguage
[serbian]
[script=latin,
% or even (if any user would be enthusiastic enough to provide code)
transliteration=on]
and get latin labels and hyphenation patterns.
3.) Solve the problem with English in a more elegant way:
\mainlanguage
[english]
[alternative=us]
or
\mainlanguage[en][US] % as in "en_US.UTF-8"
\mainlanguage[en][GB]
\mainlanguage[en][AU]
\mainlanguage[de][AT] % if one ever figures out that "German from
Germany" isn't good enough
Then, [us] should be kept as a synonym for \mainlanguage[en][US].
(The examples above could also be called via
\mainlanguage[de][alternative=guillemets] or
\mainlanguage[sr][alternative=latin].)
4.) deo
\mainlanguage[de][alternative=old] ??? (no idea what that is about)
Note that 1.) could be combined (should be "combinable") with this one.
Any thoughts?
Mojca
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2007-12-05 1:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 1:40 Mojca Miklavec [this message]
2007-12-05 7:43 ` Thomas A. Schmitz
2007-12-05 8:20 ` Arthur Reutenauer
2007-12-05 8:33 ` Thomas A. Schmitz
2007-12-05 10:38 ` Hans Hagen
2007-12-05 8:42 ` Wolfgang Schuster
2007-12-05 9:55 ` Henning Hraban Ramm
2007-12-05 10:45 ` Arthur Reutenauer
2007-12-05 11:16 ` Henning Hraban Ramm
2007-12-05 11:22 ` Hans Hagen
2007-12-05 20:29 ` Arthur Reutenauer
2007-12-05 21:18 ` Mojca Miklavec
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=6faad9f00712041740k7c485079y88171590235accf4@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).