MHonArc v2.5.0b2 -->

















xliff message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: RE: [xliff] Revised Committee Draft XLIFF 1.2 Spec




From: "Lieske, Christian" <christian.lieske@sap.com>
To: "XLIFF TC" <xliff@lists.oasis-open.org>
Date: Thu, 11 May 2006 08:29:05 +0200









Dear all,
 
I wonder about the repurcussions of phrases like "tool makers can include the spaces 
in the markup". How will tool users be 
able to know what a specific tool maker really supports in his XLIFF 
implementation?
 
Best regards,
Christian



  

  

  From: Rodolfo M. Raya 
  [mailto:rmraya@heartsome.net]
Sent: Mittwoch, 10. Mai 2006 
  19:20
To: Magnus Martikainen
Cc: XLIFF 
  TC
Subject: RE: [xliff] Revised Committee Draft XLIFF 1.2 
  Spec


  
On Wed, 2006-05-10 at 02:17 -0700, Magnus Martikainen wrote: 
  
Hi all, 
    

Regarding point 5) 
    below I would like to clarify that the segmentation markup is entirely 
    optional and does not affect the functionality of the files as XLIFF files. 
    The filter will ignore the segment boundaries when back-converting to the 
    native format, and thus the entire content of the <target> element 
    will be used, including content appearing outside of segments. 
    

The segmentation 
    markup is intended for tools such as translation memories to optimize 
    recycling of previously translated content, and as such it often makes more 
    sense to not include spaces between sentences in the segments (though that 
    is entirely up to the tools). This does not in any way prevent users from 
    editing the content between the segments, removing spaces or adding 
    additional ones as needed. In fact it is fully allowed (and may frequently 
    happen) that only part of the translated content in the <target> 
    element is part of segments.  

The example in point 5) attempts to explicitly show this by 
    not including the space characters in the segments (which normally gives 
    better re-use when applying a TM). Perhaps we need to clarify the text in 
    the specification to make that more 
  explicit?

Hi Magnus,

Thanks for the 
  explanation.

I would be happy if the text below the example is 
  enhanced with a sentences stating that tool makers can include the spaces in 
  the markup if desired.
Best regards,
Rodolfo

  

    

    

      

        

          

          

            
--
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. 
          







References:

RE: [xliff] Revised Committee Draft XLIFF 1.2 Spec
From: "Rodolfo M. Raya" <rmraya@heartsome.net>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]