OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only

  • 1.  RE: [xliff] SubFlows and inline codes

    Posted 01-27-2015 18:01
    Hi, Yves, I'm curious about something. Our OM has a method that will take some text and if it finds an original code, it automatically encodes it for you using the appropriate inline tag and <originalData>. We also can decode the string so that it can be stored in our TM without XLIFF native tags. However, this round-tripping causes us to lose any attributes on the inline tags, such as canCopy or canRemove for example. The only solution to roundtrip the data seems to be to store this data as part of the TM or treat the XLIFF as a sort-of skeleton for the TM data. I'm wondering if you have this problem and if you have any solutions for it. Thanks, Ryan


  • 2.  Re: [xliff] SubFlows and inline codes

    Posted 01-27-2015 19:04
    Ryan, seeing your interesting questions on the mailing list. I must ask Are you planning to submit a talk for 6th Symposium in Berlin on your Object model? http://locworld.com/call-papers-feisgiltt-2015/ https://www.easychair.org/conferences/?conf=feisgiltt2015 That would be a great contribution! 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, Jan 27, 2015 at 6:00 PM, Ryan King < ryanki@microsoft.com > wrote: Hi, Yves, I'm curious about something. Our OM has a method that will take some text and if it finds an original code, it automatically encodes it for you using the appropriate inline tag and <originalData>. We also can decode the string so that it can be stored in our TM without XLIFF native tags. However, this round-tripping causes us to lose any attributes on the inline tags, such as canCopy or canRemove for example. The only solution to roundtrip the data seems to be to store this data as part of the TM or treat the XLIFF as a sort-of skeleton for the TM data. I'm wondering if you have this problem and if you have any solutions for it. Thanks, Ryan
    Original Message


  • 3.  RE: [xliff] SubFlows and inline codes

    Posted 01-27-2015 21:35




    Hi David, yes, I will be submitting something either about our OM, or about the consumption of it to support XLIFF 2.0 in our localization tools and processes.
     
    From: Dr. David Filip [mailto:David.Filip@ul.ie]

    Sent: Tuesday, January 27, 2015 11:03 AM
    To: Ryan King
    Cc: Yves Savourel; xliff@lists.oasis-open.org
    Subject: Re: [xliff] SubFlows and inline codes
     

    Ryan, seeing your interesting questions on the mailing list.

    I must ask Are you planning to submit a talk for 6th Symposium in Berlin on your Object model?


    http://locworld.com/call-papers-feisgiltt-2015/


    https://www.easychair.org/conferences/?conf=feisgiltt2015


    That would be a great contribution!


    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, Jan 27, 2015 at 6:00 PM, Ryan King < ryanki@microsoft.com > wrote:

    Hi, Yves, I'm curious about something. Our OM has a method that will take some text and if it finds an original code, it automatically encodes it for you using the appropriate inline tag and <originalData>. We also can decode the string
    so that it can be stored in our TM without XLIFF native tags. However, this round-tripping causes us to lose any attributes on the inline tags, such as canCopy or canRemove for example. The only solution to roundtrip the data seems to be to store this data
    as part of the TM or treat the XLIFF as a sort-of skeleton for the TM data. I'm wondering if you have this problem and if you have any solutions for it.

    Thanks,
    Ryan


    Original Message


  • 4.  RE: [xliff] SubFlows and inline codes

    Posted 01-27-2015 19:48
    Hi Ryan, I'm not sure if what we do can help much, but here it goes: Basically our OM maps all attributes in the inline codes, so it has access to everything. Round trips to JSON, etc. retain all that. As for other types of roundtrips--for example we have components that reads XLIFF2 and produce various translation package from that, including XLIFF1.2--we do it like you described: Store the original inline code and, if needed, spit it back. But this is obviously not ideal. On a side note: Nowadays many TM tools don't even bother to store the original codes, they just store the ids+types and use that to map the leveraged codes into the document. The only time you would/could need the original codes in the TM is for translations that have extra codes compared to the source. Not sure that helped... Cheers, -yves
    Original Message


  • 5.  RE: [xliff] SubFlows and inline codes

    Posted 01-27-2015 20:00
    Thanks Yves for the reply. Our OM also maps all attributes in the inline codes, so we could serialize to JSON and preserve everything as well. The problem comes when we encounter what you described in your second paragraph: having to convert XLIFF to a translation package. In our case, our "package" is a cloud-based storage with a web editor. In any case, that seems to be a common challenge. Thanks for the TM detail as well. Ryan
    Original Message


  • 6.  RE: [xliff] SubFlows and inline codes

    Posted 03-03-2015 16:23
    As per the TC call this morning, I am verifying that this thread resolved my question. Thanks, Ryan
    Original Message


Related Content