OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only

Groups - XLIFF 1.1 PO/ POT Representation Guide (xliff-profile-po-1.1-draft-1.zip) uploaded

  • 1.  Groups - XLIFF 1.1 PO/ POT Representation Guide (xliff-profile-po-1.1-draft-1.zip) uploaded

    Posted 09-20-2005 13:46
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    xliff message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: Groups - XLIFF 1.1 PO/ POT Representation Guide (xliff-profile-po-1.1-draft-1.zip) uploaded


    Updated XLIFF 1.1 PO / POT Representation Guide - responding to issues
    reported by XLIFF TC
    
    (Issues addressed below by Asgeir Frimannsson)
    1) Examples of converted PO files.
    I have provided two sample PO/XLIFF files, displaying the most common use
    of PO. I have not provided examples of e.g. multiple PO domains, as I've
    never seen any practical use of these in the community anyway.
    
    2) Comment from Doug Domeny about use of <ph> elements:
    http://lists.oasis-open.org/archives/xliff/200507/msg00008.html
    I agree with Doug here that in many cases <x/> elements might be a better
    option than <ph>. I have changed the guide (Section 3.4 and 5.6.3), leaving
    the option open to use either <ph> or </x>. This is similar to how it's
    done in the HTML repr. guide in many cases.
    
    3) Typy
    Fixed the typo found at the end of section 3.3
    
    4) Use of context-groups in Section 5.5. (PO References) Haven't changed
    anything here, but I'll mention the issue again. Here, multiple
    context-group exists within the same hierarchical level in the document.
    The XLIFF spec is a bit unclear if this is legal or not. For
    example:
    <trans-unit id="1">
      <source>hello world</source>
      <context-group name="po-reference" purpose="location">
        <context type="sourcefile">example.c</context>
        <context type="linenumber">34</context>
      </context-group>
      <context-group name="po-reference" purpose="location">
        <context type="sourcefile">otherfile.c</context>
        <context type="linenumber">233</context>
      </context-group>
    </trans-unit>
    
    Another way of doing it would be e.g.:
    <trans-unit id="1">
      <source>hello world</source>
      <context-group name="po-reference" purpose="location">
        <context type="x-po-reference">example.c:34</context>
        <context type="x-po-reference">otherfile.c:233</context>
      </context-group>
    </trans-unit>
    
    
     -- Mr. Tony Jewtushenko*
    
    The document named XLIFF 1.1 PO/ POT Representation Guide
    (xliff-profile-po-1.1-draft-1.zip) has been submitted by Mr. Tony
    Jewtushenko* to the OASIS XML Localisation Interchange File Format (XLIFF)
    TC document repository.
    
    Document Description:
    Updated XLIFF 1.1 PO/POT representation Guide - responding to issues raised
    by XLIFF TC.
    
    View Document Details:
    http://www.oasis-open.org/apps/org/workgroup/xliff/document.php?document_id=14587
    
    Download Document:  
    http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/14587/xliff-profile-po-1.1-draft-1.zip
    
    
    PLEASE NOTE:  If the above links do not work for you, your email application
    may be breaking the link into two pieces.  You may be able to copy and paste
    the entire link address into the address field of your web browser.
    
    -OASIS Open Administration
    


    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]