From: Tobias Burnus <burnus@gmx.de>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: Italic languages
Date: Mon, 09 Oct 2000 10:56:57 +0200 [thread overview]
Message-ID: <39E18859.890F04FA@gmx.de> (raw)
In-Reply-To: <000301c03166$d7bd3360$3b400e97@nuovo>
Hi,
> Ok, \SP expand to \language [\s!sp ] so I guess that's it; now, I wonder:
> shouldn't the spanish tag have been "es" rather than "sp"?
http://lcweb.loc.gov/standards/iso639-2/englangn.html
shows:
----
Language Name (English) Language Name (French) 639-2/B 639-2/T 639-1
Spanish espagnol spa spa es
ISO 639-2/B is the bibliographic code and ISO 639-2/T is the terminology
code. ISO 639-1 is the Alpha-2 code.
----
So: Yes, "es" would be the right one. (sp could be an alias as du is for
de).
Tobias
next prev parent reply other threads:[~2000-10-09 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-07 14:36 Giuseppe Bilotta
2000-10-07 16:38 ` Tobias Burnus
2000-10-07 18:15 ` Hans Hagen
2000-10-08 13:56 ` Giuseppe Bilotta
2000-10-08 22:27 ` Hans Hagen
2000-10-09 8:56 ` Tobias Burnus [this message]
2000-10-09 10:54 ` Hans Hagen
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=39E18859.890F04FA@gmx.de \
--to=burnus@gmx.de \
--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).