From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Foreign Languages / interface translation
Date: Tue, 12 Sep 2000 22:38:44 +0200 [thread overview]
Message-ID: <3.0.6.32.20000912223844.008a7b10@pop.wxs.nl> (raw)
In-Reply-To: <000b01c01cce$7fcf32e0$66470e97@nuovo>
At 05:30 PM 9/12/00 +0200, you wrote:
>definitions, and to correct some typos. I'd also like to know if the
>headtexts left empty are to be left that way, or the correct name is to be
>inserted.
It depends. I think you can add the labels after % so that users who want
them, can take their pick. I'm thinking of an option to set them as well as
turn them on and off. So, even if not normally used, just add them.
>> (1) mult-com.tex
>
>How do I change this files? The format is somewhat strange, and for some
>of them I don't know the correct translation, or it's quite longish. Does
>this pose any problem?
Do not change the files yet. Just prepare a list first or make sure that we
can use a perl script to merge the files. We must not get out of tune.
There is no problem in the length, but keep an eye on what users want. If
you don't know the translation yet, keep it english for the moment.
>> (2) mult-con.tex
>
>For this one, some other problems arise: names can depend on the gender of
>the next word, or even on the starting letter: one is "uno" (the number, or
>reffering to a male, and with the next word beggining with two consonants),
>"un" is male, with next word beginning with simple consonant or with vowel,
>and "una" is female; which should I put?
Czech also has that problem. The 'one' is used as a stand alone number, in
mult-con there are only keywords and values. Although we may some day
consider a gender specific label prefix mechanism (when needed).
>For both the previous files, is it possible to do something in such a way
>that italian keys are defined, e.g., like english?
yes:
dutch: dutchkey englishkey
germankey czechkey
italiankey
>> (3) grep on \startmessages
>
>I translated them. This was the easy part :-)
All of them? That's fast! You can test that with the file cont-it.tex i'll
send you.
texexec --make --alone it
will generate you a version with an english interface and italian messages.
>Does this mean that all I have to do is add the italian translation and then
>send you the appropriate files?
messages : isolate them in one file
keys/values : add a header 'italian' and add keywords, use - for unknown
entries
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2000-09-12 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-11 19:13 Foreign Languages Giuseppe Bilotta (Oblomov)
2000-09-12 10:04 ` Hans Hagen
2000-09-12 11:02 ` Ansuman Lahiri
2000-09-12 11:09 ` Hans Hagen
2000-09-12 13:39 ` Robert F. Beeger
2000-09-12 15:30 ` Giuseppe Bilotta (Oblomov)
2000-09-12 20:38 ` Hans Hagen [this message]
2000-09-12 22:31 ` Foreign Languages / interface translation Giuseppe Bilotta (Oblomov)
2000-09-13 17:02 ` 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=3.0.6.32.20000912223844.008a7b10@pop.wxs.nl \
--to=pragma@wxs.nl \
--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).