OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xliff-comment] Grouping translations across <trans-unit>elements

On Wed, 2006-07-26 at 10:16 -0400, Corneliusson, Fredrik wrote:

> Hi,
> I have a question about best practice of the new XLIFF 1.2 grouping of
> translation units.
> In the XLIFF 1.2 draft it shows an example where the ending/beginning
> white space is not present in the source trans-unit but present in the
> translation of the merged trans-unit. How would the translator know
> that a whitespace should be added? Is there any best practice for
> this? If the whitespace between segments is in a skeleton file it will
> not end up at the correct place on back conversion and the merged
> source segments will be incorrect. 
> A possible solution for this would be to add all whitespaces between
> translatable trans-units as separate trans-units with translate
> attribute set to "no" (or set to already translated) so white space
> information can be included in a merged segment.
> What are your thoughts on this?
> Regards,
> Fredrik

Hi Frederick

I believe that you are referring to this example from section 2.9:

        <source>Richard stepped out of the kitchen hut. He noticed a movement from the corner of his 
        eye. A monkey had climbed on top of one of the workshop sh eds, trying to get in by the ventilation 
        <seg-source><mrk mtype="seg">Richard stepped out of the kitchen hut.</mrk>
         <mrk mtype="seg">He noticed a movement from the corner of his eye.</mrk>
         <mrk mtype="seg">A monkey had 
        climbed on top of one of the workshop sheds, trying to get in by the ventilation 

Spaces between segments are not included in <seg-source> element, but
they are present in <source> element. The tool processing the XLIFF file
should consider the content of the <source> element in first place. The
text to translate is the one in <source>, the <seg-source> element  is
optional and it may or may not include spaces in segmentation markup. 

The presence of spaces between sentences depends on the languages. If
the target language is Chinese, for example, there should not be any
space between sentences. In languages like Canadian french, there are
usually two regular spaces between sentences. When translating from
English to Chinese or Canadian French translators should treat spaces

Spaces that appear between sentences should not be stored in the
skeleton file. There is a risk of including a wrong number of spaces in
the translated document. Better let the translator add the correct
number of spaces (or remove them if necessary).

Best regards,
Rodolfo M. Raya
The information in this e-mail is intended strictly for the addressee,
without prejudices, as a confidential document. Should it reach you, not
being the addressee, it is not to be made accessible to any other
unauthorised person or copied, distributed or disclosed to any other
third party as this would constitute an unlawful act under certain
circumstances, unless prior approval is given for its transmission. The
content of this e-mail is solely that of the sender and not necessarily
that of Heartsome.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]