From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: cont-fr interface ?
Date: Sun, 18 Dec 2005 19:08:51 +0100 [thread overview]
Message-ID: <43A5A5B3.9010405@elvenkind.com> (raw)
In-Reply-To: <43A5A03D.5070504@boede.nl>
Willi Egger wrote:
> Hi Renaud,
>
> ASFAIK the interface is defined in a file called mult-com.tex. Adding a
> new interface would mean to place translations of the defined items into
> this file.
There are two big jobs to be done, one of which is optional:
1) add translations to mult-com.tex and mult-con.tex, like so:
\startcommands dutch english
german czech
italian romanian
french
language: taal language
sprache jazyk
lingua limba
langue
...
\stopcommands
Note: your translations have to be 7-bit clean. This is required
because otherwise mayhem results when e.g. the french interface is
used to typeset documents in italian or czech.
Each time, you add 'french' to the language list at the top, then
add a new translation for each keyword.
You *cannot* skip a translation within a command list (the number
of translated items has to match up), but you *can* skip an entire
command block (\startcommands ... \stopcommands).
2) (optionally) translate the message libraries to french. Search
for \startmessages in the source files. There are a lot of them,
but you do not have to translate all (they will default to english).
About the only other thing is to create a cont-fr.tex that begins
with \def\defaultinterface{french}, and switches to french.
Taco
next prev parent reply other threads:[~2005-12-18 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 17:15 Renaud AUBIN
2005-12-18 17:45 ` Willi Egger
2005-12-18 17:51 ` Renaud AUBIN
2005-12-18 17:58 ` Willi Egger
2005-12-18 18:11 ` Taco Hoekwater
2005-12-18 20:01 ` Hans Hagen
2005-12-18 20:54 ` Renaud AUBIN
2005-12-18 21:02 ` Hans Hagen
2005-12-18 18:08 ` Taco Hoekwater [this message]
2005-12-18 20:11 ` 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=43A5A5B3.9010405@elvenkind.com \
--to=taco@elvenkind.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).