OASIS XML Localisation Interchange File Format (XLIFF) TC

Re: AW: [xliff] Revised XLIFF Profile for Java Resource Bundles

  • 1.  Re: AW: [xliff] Revised XLIFF Profile for Java Resource Bundles

    Posted 05-03-2006 12:21
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    xliff message

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


    Subject: Re: AW: [xliff] Revised XLIFF Profile for Java Resource Bundles


    On Wed, 2006-05-03 at 13:48 +0200, Florian Sachse wrote:
    Dear Christian, dear Rodolfo,
     
    I think we can drop my message msg00013.html, because we do not know if the .NET profile or Winres profile will be part of the initial deliverables for XLIFF 1.2
     
    Instead I would like to raise the quation how you feel about undecorating escaped control characters after tagging the placables.
     
     " Florian''s example: '{'The disk \"{1}\" contains {0,choice,0#no files|1#one file|1<{0,number,integer} files}.}"
     
    Instead of
     
    Florian''s example: '{'The disk \"<ph ...>{1}</ph>\" contains <ph...>{0,choice,0#no files|^#one file|1<{0,number,integer} files}</ph>.}
     
    it would be nicer to have:
     
    Florian's example: {The disk \"<ph ...>{1}</ph>\" contains <ph...>{0,choice,0#no files|^#one file|1<{0,number,integer} files}</ph>.}
     
    Mapping of ' -> ' ' and { to '{' is needed to keep { as a control character. after tagging the control sequences are either stored in the sceleton file or within the ph tags. The mapping is not needed and for a translator it would be much easier to edit the unmapped text.
     
    Just an idea.
     
    Best regards from Bonn,
    Florian


    Hi Florian,

    A section explaining how to deal with single quotes and escaped braces is needed. Filters should do the necessary cleanup and let translators only see relevant text.

    I also noticed that in case of choice-type replaceables, each option should be parsed and translatable text enclosed in <sub> elements. By doing this, the sample would become:

    {The disk \"<ph ...>{1}</ph>\" contains <ph...>{0,choice,0#<sub>no files</sub>|^#<sub>one file</sub>|1<{0,number,integer} <sub>files</sub>}</ph>.}

    Thanks for the feedback.

    Best regards,
    Rodolfo
    --
    The information in this e-mail is intended strictly for the addressee, without prejudices, as a confidential document. Should it reach you, not being the addressee, it is not to be made accessible to any other unauthorised person or copied, distributed or disclosed to any other third party as this would constitute an unlawful act under certain circumstances, unless prior approval is given for its transmission. The content of this e-mail is solely that of the sender and not necessarily that of Heartsome.


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