OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  Mistakes in the spec

    Posted 02-03-2015 14:24
    I have found the following errors in the spec so far: 1-  http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#canoverlap In the example, the first <pc> element has an extra forward slash ;            <source><pc id="1" dataRefStart="3" dataRefEnd="4" canOverlap="no"/> Should be:              <source><pc id="1" dataRefStart="3" dataRefEnd="4" canOverlap="no">   2- http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#spanningcodeusage The <sc> element contains text, but it should be empty;         Text in <sc id="1"> </sc>bold        <sc id="2">i </sc>and<ec startRef="1">0 </ec> italics        <ec startRef="2">i0</ec> Should be:         <unit id="1">         <originalData>           <data id="d1"> </data>           <data id="d2">i </data>          <data id="d3">0 </data>          <data id="d4">i0 </data>         </originalData>         <segment>           <source>Text in <sc id="1" dataRef="d1"/>bold <sc id="2" dataRef="d2"/>                   and<ec startRef="1" dataRef="d3"/> italics<ec startRef="2" dataRef="d4"/>.           </source>         </segment>         </unit>     3- http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#duplicatingexistingcode Third line, a typo with “use”;                 If the base code is associated with some original data: the new code simply use these data. Should be:             If the base code is associated with some original data: the new code simply uses these data.   Soroush.


  • 2.  RE: [xliff] Mistakes in the spec

    Posted 02-03-2015 15:06
    Good 3 catches Soroush. -ys   From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Soroush.Saadatfar Sent: Tuesday, February 3, 2015 7:24 AM To: xliff@lists.oasis-open.org Subject: [xliff] Mistakes in the spec   I have found the following errors in the spec so far: 1-  http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#canoverlap In the example, the first <pc> element has an extra forward slash ;            <source><pc id="1" dataRefStart="3" dataRefEnd="4" canOverlap="no"/> Should be:              <source><pc id="1" dataRefStart="3" dataRefEnd="4" canOverlap="no">   2- http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#spanningcodeusage The <sc> element contains text, but it should be empty;         Text in <sc id="1"> </sc>bold        <sc id="2">i </sc>and<ec startRef="1">0 </ec> italics        <ec startRef="2">i0</ec> Should be:         <unit id="1">         <originalData>           <data id="d1"> </data>           <data id="d2">i </data>          <data id="d3">0 </data>          <data id="d4">i0 </data>          </originalData>          <segment>           <source>Text in <sc id="1" dataRef="d1"/>bold <sc id="2" dataRef="d2"/>                   and<ec startRef="1" dataRef="d3"/> italics<ec startRef="2" dataRef="d4"/>.           </source>          </segment>         </unit>     3- http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#duplicatingexistingcode Third line, a typo with “use”;                 If the base code is associated with some original data: the new code simply use these data. Should be:             If the base code is associated with some original data: the new code simply uses these data.   Soroush.


  • 3.  Re: [xliff] Mistakes in the spec

    Posted 07-07-2015 14:52
    Soroush, Yves, DavidW, all the three errors reported by Soroush are now fixed in the Docbook source of the 2.1 wd and will appear fixed in next printout. Cheers dF Dr. David Filip ======================= OASIS XLIFF TC Secretary, Editor, and Liaison Officer  LRC CNGL CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto:  david.filip@ul.ie On Tue, Feb 3, 2015 at 3:05 PM, Yves Savourel < ysavourel@enlaso.com > wrote: Good 3 catches Soroush. -ys   From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Soroush.Saadatfar Sent: Tuesday, February 3, 2015 7:24 AM To: xliff@lists.oasis-open.org Subject: [xliff] Mistakes in the spec   I have found the following errors in the spec so far: 1-  http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#canoverlap In the example, the first <pc> element has an extra forward slash ;            <source><pc id="1" dataRefStart="3" dataRefEnd="4" canOverlap="no"/> Should be:              <source><pc id="1" dataRefStart="3" dataRefEnd="4" canOverlap="no">   2- http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#spanningcodeusage The <sc> element contains text, but it should be empty;         Text in <sc id="1"> </sc>bold        <sc id="2">i </sc>and<ec startRef="1">0 </ec> italics        <ec startRef="2">i0</ec> Should be:         <unit id="1">         <originalData>           <data id="d1"> </data>           <data id="d2">i </data>          <data id="d3">0 </data>          <data id="d4">i0 </data>          </originalData>          <segment>           <source>Text in <sc id="1" dataRef="d1"/>bold <sc id="2" dataRef="d2"/>                   and<ec startRef="1" dataRef="d3"/> italics<ec startRef="2" dataRef="d4"/>.           </source>          </segment>         </unit>     3- http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#duplicatingexistingcode Third line, a typo with “use”;                 If the base code is associated with some original data: the new code simply use these data. Should be:             If the base code is associated with some original data: the new code simply uses these data.   Soroush.