From: John Devereux <john@devereux.me.uk>
To: ntg-context@ntg.nl
Subject: Design for Translation
Date: Wed, 11 Mar 2009 19:44:24 +0000 [thread overview]
Message-ID: <877i2vg7zb.fsf@cordelia.devereux.me.uk> (raw)
Hi,
I am wondering how best to go about creating an evolving document that
will need translation.
This is a manual that will probably need to be produced - and
maintained - in around 6 languages.
For what it is worth, I have come up with two approaches, which
follow.
But I would really appreciate any insights anyone may have.
...
1) Just translate the file
--------------------------
- Obey formatting rules in document tex file so as to most easily
visually separate commands from text.
- Distribute the files for translation with instructions.
This will work until we need to modify the file, then how to
communicate the modifications? An english diff?
I think this may be the best solution, but there is also
2) Using blocks
---------------
The "excursion" manual briefly describes an alternative (which I
think may be too cumbersome). The idea would be to totally separate
the text from any tex commands (except for a single type of begin/end
sequence). Conceptually :-
manual-env.tex:
\defineblock[EN,de,it]
\setupblock[EN][file=EN]
\setupblock[DE][file=DE]
\setupblock[IT][file=IT]
\doifmode[EN]{\def\lang{EN}}
\doifmode[DE]{\def\lang{DE}}
\doifmode[IT]{\def\lang{IT}}
manual.tex:
\environment manual-env.tex
\useblocks[\lang][installation-1]
\useblocks[\lang][installation-2]
EN.tex:
\beginEN[installation-1]
This is how to install the product type 1
\endEN
\beginEN[installation-2]
This is how to install the product type 2
\endEN
DE.tex:
\beginDE[installation-1]
(german text here)
\endDE
\beginDE[installation-2]
(german text here)
\endDE
IT.tex:
\beginIT[installation-1]
(italian text here)
\endIT
\beginIT[installation-2]
(italian text here)
\endIT
--
John Devereux
___________________________________________________________________________________
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:[~2009-03-11 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 19:44 John Devereux [this message]
2009-03-11 21:39 ` Mari Voipio
2009-03-12 5:04 ` Marcin Borkowski
2009-03-12 8:22 ` Mari Voipio
2009-03-12 9:17 ` John Devereux
2009-03-12 10:18 ` Mari Voipio
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=877i2vg7zb.fsf@cordelia.devereux.me.uk \
--to=john@devereux.me.uk \
--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).