RE: [xliff] Presentation

[Yves Savourel <ysavourel@translate.com>]

In slide 14,  I suggest that it be made very clear that a Skeleton file is entirely optional.   For example in Oracle we're extracting our seeddata files in their entirety to XLIFF files,  and we can build our native translated files directly from XLIFF files without any other information.
[YS] Good point. Will make adjustements.

•  
• In slide 41,  I'm not really understanding what is meant by this statement:  "Any XML-enabled translation tool can work with an XLIFF document, as long as the text to translate is initially copied in the <target> elements. However, this does not mean it support all XLIFF features, but just allow to translate <target> content."   I think but am now sure that you're trying to make the point that any XML enabled tool can edit XLIFF,  as long as it results in the translation representing  <source> be written to the <target> element.  Or am I missing the intent?  Also,  the wording in the red text is a little awkward - maybe change "support" to "supports".
  [YS] You got the meaning. The idea is to make sure people understand the difference between a tool that "support" XLIFF because it support XML, and one that "understand XLIFF" including <alt-trans> etc. I'll try to reword that better.
•  
• All the XLIFF files representing the demo are in "XML" extension - I suggest that we use "XLF",  which is,  per our 1.0 spec,  the recommended XLIFF file extension.
  [YS] I did that originaly, but when to .xml because of problem when double-clicking on the links from PowePoint

 

I'll post a final-final version with all changes from today's feedback at the end of the day. If other changes need to be made after 4pm Colorado Time today they won't be in the printed slides LISA will have but we can still make adjustements for the slides used in the presentation and posted for download.

 

Cheers,

-yves