[xliff-tools] Another question on PO and XLIFF
Asgeir Frimannsson
asgeirf at redhat.com
Mon May 2 18:33:34 PDT 2005
Hi,
On Tue, 3 May 2005 02:00, Rodolfo M. Raya wrote:
> On Mon, 2005-05-02 at 17:26 +0200, Fredrik Corneliusson wrote:
>
> Hi,
>
> > However I saw that the translate project's po2xliff filter uses the
> > last version described, and the xliff2po takes care of recreating the
> > \n.
>
> What does that filter do when the translator adds an extra line feed in
> the translated version because the text is too long?
>
> For example:
>
>
> msgid ""
> "Line 1\n line 2\n"
> "Line 3.\n"
>
>
> converted as
>
>
> <trans-unit xml:space="preserve">
> <source>
> Line 1
> line 2
> Line 3.
> </source>
> </trans-unit>
>
>
>
> could be translated as:
>
>
> <trans-unit xml:space="preserve">
>
> <source>
> Line 1
> line 2
> Line 3.
> </source>
>
> <target>
> Línea 1
> línea 2
> Long line here
> 3.
> </target>
> </trans-unit>
>
>
> is this converted to
>
>
> msgid ""
> "Line 1\n line 2\n"
> "Line 3.\n"
> msgstr ""
> "Línea 1\n línea 2\n Long line here\n 3\n."
>
>
> ?
>
> How does that filter know when to break a long line? For example, from
>
>
> msgstr ""
> "Línea 1\n línea 2\n Long line here\n 3\n."
>
>
> to
>
>
> msgstr ""
> "Línea 1\n línea 2\n "
> "Long line here\n 3\n."
>
>
> or to
>
>
> msgstr ""
> "Línea 1\n "
> "línea 2\n "
> "Long line "
> "here\n 3\n."
>
>
> ?
I guess the point here is that this is a XLIFF editor problem, not a
conversion problem. Translators should not insert extra newline characters,
but turn on dynamic word-wrapping or similar in the editor. Formatting
characters belong to the source format, not to to the visual format of the
source format in the editor.
cheers,
asgeir
More information about the xliff-tools
mailing list