OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only
Expand all | Collapse all

Re: [xliff] Simplified XLIFF element tree

Asgeir Frimannsson

Asgeir Frimannsson08-25-2010 21:44

  • 1.  Re: [xliff] Simplified XLIFF element tree

    Posted 08-25-2010 21:44
    ----- "Andrzej Zydron" 


  • 2.  Re: [xliff] Simplified XLIFF element tree

    Posted 08-26-2010 21:08
      |   view attached

    Attachment(s)

    vcf
    azydron.vcf   251 B 1 version


  • 3.  RE: [xliff] Simplified XLIFF element tree

    Posted 09-02-2010 04:52
    Hi everyone,
    
    >> 1) Having to duplicate source text
    >> ( -> same approach as


  • 4.  Re: [xliff] Simplified XLIFF element tree

    Posted 09-21-2010 17:16
      |   view attached

    Attachment(s)

    vcf
    azydron.vcf   251 B 1 version


  • 5.  RE: [xliff] Simplified XLIFF element tree

    Posted 09-02-2010 04:52
    I've tried to take a step back and look at this from a more general view.
    Here are a my two cents:
    
    
    === First, the issue of storing the un-segmented content:
    
    There seem to be two models:
    
    A) storing the segmented content as a copy of the original source.
    
    B) marking up the source with specific elements for segmentation.
    
    The solution A requires to duplicate the source, which means a danger of having possible discrepancies between the original and the segmented source (what do we do in those cases?). It seems also a waste of space: no matter what the tool used large files always end up being a problem at some point. We should try to avoid making it worst.
    
    Note that having a separate original-source would be basically the reverse of