<meta http-equiv="Content-Type" content="text/plain; charset=utf-8">

Wis: How to add translations to an MLHT page
Uad: In order to add more languages to a multilingual hypertext document, you needn't know anything about MLHT programming.  You just fetch the translatable text source, replace line by line with your language and mail it back to the MLHT author.  Some examples and answers to frequently asked questions are given here.
Wee: How does the author use my translation
Wih: What can the translator do wrong
Dui: The author uses the MLHT command %1 for placing your translation into the MLHT structure.  This command inserts your lines in those places where it finds the corresponding lines of the translatable source text.  I.e. your translation's line with the identifier XYZ: at the beginning renders a line in the source text which begins with the same identifier.
Zlz: line separation
HSh: hypertext syntax markers %1
jgt: File Coding System
doW: send to many lines
Sng: Use an editor that can wrap lines without inserting linebreaks.  Alternatively you can translate lines as text blocks which are separated by an empty line and may contain linebreaks.  But do it consistently and check even more carefully that your translation has the same number of blocks as the original has lines, and that they correspond to each other, and then convert them back to the needed form with regular expressions or ask the author to do that.
Ase: The source texts that translators work with are simple but not quite free of hypertext markers.  They are mainly the above-mentioned three markers that start with the %% sign.  The translator needn't know their exact meaning, he just must know that the MLHT variable %1 and the MLHT block marker %2 should remain untouched and while the enclosed %3 must be translated, and that all three kinds of placeholders should mark the same components of text meaning in the translation as in the original.  Of course they must be copied correctly.  Any misspelling or failure to close a bracket will force the MLHT author to debug the translated text before he can successfully incorporate it.
Wsb: When you want to know what effect the hypertext markers and variables have on the final appearance of the document, take a look at the source language's hypertext with your favorite browser.  Keep it ready for consultation whenever you are translating an MLHT text.
ecW: MLHT usually reads and writes texts in UTF-8 coding.  Many users prefer to use another coding system, such as latin-1 or euc-jp.  In such cases, you can use a converter such as, under GNU/Linux/Unix systems, %(c:recode):
WWs: The file should contain only those lines that were actually improved.  Others should be omitted or deleted.  There is always a certain risk that an already-improved text is overwritten by an older version, and this risk should be minimised.
Tan: FFII Translation Mailing List Information
bnW: Forum for discussion about and coordination of translation work to be done for the FFII pages.
Wps: AelWiki: Swpat Translation
Wao: This wiki page is used to allocate translation work to translators.
WoW: Wiki page is used for working out further hints for translators.

# Local Variables: ;
# coding: utf-8 ;
# srcfile: /usr/share/emacs/site-lisp/phm/mlht/langtxt.el ;
# mailto: mlhtimport@a2e.de ;
# passwd: XXXX ;
# feature: ffiidir ;
# dok: langtxt ;
# txtlang: en ;
# End: ;