RE: [xliff-comment] using xliff to translate html

["Yves Savourel" <ysavourel@translate.com>]

Hi everyone,

Just to add more on the discussion, I've attached is an example of HTML
extracted to XLIFF:

- TestPage.htm is the original file.
- TestPage.xlf is the XLIFF extraction.
- TestPageOutput.htm is the original file with the extracted parts marked up
between braces ('{...}').

This illustrates a few things:

- Only translatable text and codes within translatable text are extracted.

- Using inline codes in <source> (and <target>) allows XLIFF to present a
common representation of the codes to all tools, regardless of the original
format of the codes. But at the same time, the original code is available if
need to be.

- It is possible to have some context information by using the existing
values for restype. However, it is arguable that a better context
information would be the actual name of the tag (or the sequence of tags)
from where the text was extracted. For example, here there is no distinction
between the text extracted from a title attribute and the content of a
<caption> element, they are both annotated with restype='caption' (there is
no 'title' value in the current list of restype values). It's likely that we
will need to add new values to the restype list or find a better mechanism
(using <context> for example).

- Sub-flow text (e.g. the text of the alt attribute in a <img> element) can
be extracted as a separate entry. Another way to do this would be to use the
<sub> element inside the <bpt> element containing the image.


Note this is just one way of mapping HTML to XLIFF, but as it was already
mentioned the TC needs to develop a set of guidelines for this, so everyone
could do the same mapping.

I hope this help
-yves

TestPage.zip