Re: Marking lists for translation the right way

[Andika Triwidada <andika gmail com>]

On Tue, Sep 17, 2013 at 12:54 AM, Alexandre Franke
<alexandre franke gmail com> wrote:
> Hi,
>
> https://bugzilla.gnome.org/show_bug.cgi?id=708039
>
> This happens for instance in the new appdata which can have lists of features.
> Should we have the whole list as a single string, making it mandatory
> to check that every <li> tag has a matching </li> but allowing for
> more freedom to translate the whole block and make it more fluid in a
> given language, or should we mark each list item as translateable thus
> having one less error source, but reducing flexibility for
> translators?

You can add some notes for translator, explaining relations between those
items. Translation tools I use don't have built-in check for tag completeness,
so personally I prefer not to have those tags visible in translation
to lessen errors.

> --
> Alexandre Franke


Regards!
Andika