OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  ITS in XLIFF 2.1 edits, feedback welcome

    Posted 04-26-2016 10:04
    Hi all, I did the following edits: - Added subsection for directionality to ITS non metadata - Added subsection for ID value to ITS non metadata - Added subsection for elements within text to ITS non metadata - Created elements within text subsection in the ITSM section, basically inserting Soroush’s input and slightly modifying it. David, can you regenerate the PDF and then all, can you have a look if this is the right think? I’d like to know whether - general: edits are in the right place - specific: markup is used properly, e.g. „code“ elements - cross-references are used properly - anything else Doing the edits I had a really hard time to digest the ITS related parts. Both from the point of view as a spec writer as well as an implementer this is hard to read. As suggested by Yves, having one ITS section would be much more easy to read than having three places to look at: element / attribute definitions, ITS data category sections in the module, and the ITS non-normative appendix. Thanks, Felix


  • 2.  Re: [xliff] ITS in XLIFF 2.1 edits, feedback welcome

    Posted 05-03-2016 15:35
    Felix, I did not manage to reprint due to travels. Should be able to reprint this week. Provided you did not break anything vital ;-) or hard to troubleshoot Cheers and thanks for moving things forward dF Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 On Tue, Apr 26, 2016 at 11:04 AM, Felix Sasaki < felix@sasakiatcf.com > wrote: Hi all, I did the following edits: - Added subsection for directionality to ITS non metadata - Added subsection for ID value to ITS non metadata - Added subsection for elements within text to ITS non metadata - Created elements within text subsection in the ITSM section, basically inserting Soroush’s input and slightly modifying it. David, can you regenerate the PDF and then all, can you have a look if this is the right think? I’d like to know whether - general: edits are in the right place - specific: markup is used properly, e.g. „code“ elements - cross-references are used properly - anything else Doing the edits I had a really hard time to digest the ITS related parts. Both from the point of view as a spec writer as well as an implementer this is hard to read. As suggested by Yves, having one ITS section would be much more easy to read than having three places to look at: element / attribute definitions, ITS data category sections in the module, and the ITS non-normative appendix. Thanks, Felix --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php