[Mailman-i18n] One tip

James Henstridge james@daa.com.au
Mon, 13 Nov 2000 22:31:51 +0800 (WST)

On Mon, 13 Nov 2000, Juan Carlos Rey Anaya wrote:

> James Henstridge wrote:
> > 
> > This limits the positioning of the bold text for translations (ie. it
> > must always go before).  I don't know if that is a problem in this
> > case.
> At first sight I see one inconvenient:
> If we let all to be in one string to translate, we also give a chance
> translators to mispell at translation time.
> example)
> msgid "<strong>Hello Word</strong>"
> msgstr "<strong>Hola Mundo>/strong>"

This is not the only occasion when the translated string has some
requirements on it.  The most obvious is format strings (I suppose with
named substitutions like %(name)s, mistyping may be more common).

Also, the translator should probably be escaping entities in these
strings (unless mailman does that), so pretending the string is not an
HTML fragment may not be the best idea.

> When we later look for this message in catalog, this error can make the
> browser not to display the proper page.

invalid translations can cause all sorts of problems.  This is not the
only case.