OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only

[Fwd: RE: XForms localization] Replies from W3C XForms List

  • 1.  [Fwd: RE: XForms localization] Replies from W3C XForms List

    Posted 02-06-2004 22:09
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    xliff message

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


    Subject: [Fwd: RE: XForms localization] Replies from W3C XForms List


    Hi,
    
    We have had two replies so far, one from T.V. Raman from IBM and one 
    from Leigh Klotz from Xerox. The general indication is that attributes 
    are not "normally" intended to contain translatable text. The response 
    from Leigh gives some more insight as to how the authors of the standard 
    foresaw how XForms localization would be handled.
    
    I have also trawled through the XForms schema and identified the 
    following attributes as having a content model of unrestricted xsd:string:
    
    <submission mediatype="">
    <bind p3ptype="">
    <input inputmode="">
    <textarea inputmode="">
    <secret inputmode="">
    <upload inputmode="">
    <range start="" end="" step="">
    <instance encoding="">
    
    None of these look likely to contain translatable text.
    
    If anybody finds any further attributes whose content is only xsd:string 
    I would be most grateful.
    
    Please find the responses from TV and Leigh below.
    
    Regards,
    
    AZ
    
    -------- Original Message --------
    From: - Fri Feb 06 20:29:25 2004
    X-UIDL: 4023f91100000001
    X-Mozilla-Status: 0013
    X-Mozilla-Status2: 00000000
    Return-Path: <Leigh.Klotz@pahv.xerox.com>
    Received: from p15143873.pureserver.info (root@localhost)	by 
    xml-intl.com (8.11.6/8.11.6) with ESMTP id i16KRiL03398	for 
    <azydron@xml-intl.com>; Fri, 6 Feb 2004 20:27:44 GMT
    X-ClientAddr: 13.13.138.18
    Received: from umbriel.useastgw.xerox.com (umbriel.xerox.com 
    [13.13.138.18])	by p15143873.pureserver.info (8.11.6/8.11.6) with 
    ESMTP id i16KRi203393	for <azydron@xml-intl.com>; Fri, 6 Feb 2004 
    20:27:44 GMT
    Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com 
    [13.242.128.10])	by umbriel.useastgw.xerox.com (8.12.9-20030917/8.12.9) 
    with ESMTP id i16KRapO003876;	Fri, 6 Feb 2004 15:27:36 -0500 (EST)
    Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])	by 
    godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id 
    MAA18199;	Fri, 6 Feb 2004 12:27:34 -0800 (PST)
    Received: by mercury.ADOC.xerox.com with Internet Mail Service 
    (5.5.2654.89)	id <DXMRMV84>; Fri, 6 Feb 2004 12:30:13 -0800
    Message-ID: 
    <51B8ABCE456FD111899900805F6FD6EE15EDF714@mercury.ADOC.xerox.com>
    From: Klotz, Leigh <Leigh.Klotz@pahv.xerox.com>
    To: 'azydron@xml-intl.com' <azydron@xml-intl.com>
    Cc: 'www-forms@w3c.org' <www-forms@w3c.org>
    Subject: RE: XForms localization
    Date: Fri, 6 Feb 2004 12:29:42 -0800
    MIME-Version: 1.0
    X-Mailer: Internet Mail Service (5.5.2654.89)
    Content-Type: text/plain;	charset="iso-8859-1"
    Content-Transfer-Encoding: 8bit
    X-MIME-Autoconverted: from quoted-printable to 8bit by xml-intl.com id 
    i16KRiL03398
    Status:
    
    The primary means for localization that we put into XForms is based on
    external instance data and the HTTP "Accept-Lang" header.
    
    For example (namespaces omitted)
    
    <head>
      <model>
       <instance src="my-data.xml" />
       <instance src="labels.xml" id="labels" />
       ...
      </model>
    </head>
    
      <body>
       <input ref="cc/expiry"><label ref="instance('labels')/expiry" /></input>
       ...
    </body>
    
    Assume that the my-data.xml XML tree looks like this:
       <order>
         <cc>
          <number/>
          <expiry/>
          <name/>
          <type/>
         </cc>
         ...
        </order>
    
    The labels.xml tree that comes back from the server will depend on what data
    the server chooses to provide.
    It can look at the "Accept-Lang" header in the HTTP request to determine
    what actual resource (file) on the server side to use.
    For example, for en-US it might look like this
       <labels>
         <expiry>Expiration Date</expiry>
         ...
       </labels>
    and for en-CA it might look like this
       <labels>
         <expiry>Expiry Date</expiry>
         ...
       </labels>
    and for fr it might look like this:
    <labels>
         <expiry>Date d'�ch�ance</expiry>
         ...
       </labels>
    
    A sprinkling of xml:lang attributes in the server files might help a server
    sort out exactly what XML to return in response to the labels.xml query, but
    in my experience translations are often produced by different individuals so
    combining the language strings into one file doesn't help matters.
    
    If you choose do to so however, you might combine the data together like
    this:
       <labels>
         <expiry xml:lang="en-US">Expiration Date</expiry>
         <expiry xml:lang="en-CA">Expiry Date</expiry>
         <expiry xml:lang="fr">Date d'�ch�ance</expiry>
         ...
       </labels>
    and then write a server-side expression that uses the following XPath
    expression in server-side XSLT to return only the labels matching the
    Accept-Lang header:
        /*[xml:lang=$acceptLang]
    
    A more complicated XPath and XSLT template could return all of the matching
    languages, in order of preference, and the XForms first-node rule would
    return the first matching value in the <label ref=...> expression in the
    form, and that would take care of the case where labels are not fully
    translated, so there would be a fallback.
    
    Leigh.
    
    -----Original Message-----
    From: T. V. Raman [mailto:tvraman@us.ibm.com]
    Sent: Friday, February 06, 2004 11:40 AM
    To: azydron@xml-intl.com
    Cc: www-forms@w3c.org
    Subject: XForms localization
    
    
    
    
    not that I am aware of --- I think we conciously (or perhaps
    unconciously) put anything that is likely to get rendered to the
    user as element content and used attributes exclusively
    for "qualifying" things e.g., appearance for controls, styling,
    binding etc etc
    
    
    
    >>>>> "Andrzej" == Andrzej Zydron <azydron@xml-intl.com> writes:
         Andrzej> Hi,
         Andrzej>
         Andrzej> I am a member of the OASIS XLIFF (XML Localization
         Andrzej> Interchange File Format) TC. I have been charged with
         Andrzej> investigating the localization issues regarding
         Andrzej> XForms. I have a fairly good grasp of the XForms
         Andrzej> elements that contain text data:
         Andrzej>
         Andrzej> <label> <hint> <help> <alert> <value> <message>
         Andrzej> <setvalue>
         Andrzej>
         Andrzej> Are there any XForm attributes that could contain
         Andrzej> translatable text?
         Andrzej>
         Andrzej> Thanks in advance,
         Andrzej>
         Andrzej> AZ
         Andrzej>
         Andrzej>
         Andrzej> --
         Andrzej>
         Andrzej>
         Andrzej> email - azydron@xml-intl.com smail - Mr. A.Zydron 24
         Andrzej> Maybrook Gardens, High Wycombe, Bucks HP13 6PJ
         Andrzej> Mobile +(44) 7966 477181 FAX +(44) 870 831 8868 www
         Andrzej> - http://www.xml-intl.com
         Andrzej>
         Andrzej> This message contains confidential information and
         Andrzej> is intended only for the individual named.  If you
         Andrzej> are not the named addressee you may not disseminate,
         Andrzej> distribute or copy this e-mail.  Please notify the
         Andrzej> sender immediately by e-mail if you have received
         Andrzej> this e-mail by mistake and delete this e-mail from
         Andrzej> your system.  E-mail transmission cannot be
         Andrzej> guaranteed to be secure or error-free as information
         Andrzej> could be intercepted, corrupted, lost, destroyed,
         Andrzej> arrive late or incomplete, or contain viruses.  The
         Andrzej> sender therefore does not accept liability for any
         Andrzej> errors or omissions in the contents of this message
         Andrzej> which arise as a result of e-mail transmission.  If
         Andrzej> verification is required please request a hard-copy
         Andrzej> version. Unless explicitly stated otherwise this
         Andrzej> message is provided for informational purposes only
         Andrzej> and should not be construed as a solicitation or
         Andrzej> offer.
         Andrzej>
         Andrzej>
    
    -- 
    Best Regards,
    --raman
    ------------------------------------------------------------
    T. V. Raman:  PhD (Cornell University)
    IBM Research: Human Language Technologies
    Architect:    Conversational And Multimodal WWW Standards
    Phone:        1 (408) 927 2608   T-Line 457-2608
    Fax:        1 (408) 927 3012     Cell: 1 650 799 5724
    Email:        tvraman@us.ibm.com
    WWW:      http://almaden.ibm.com/u/tvraman
    AIM:      TVRaman
    GPG:          http://www.almaden.ibm.com/cs/people/tvraman/raman-almaden.asc
    Snail:        IBM Almaden Research Center,
                   650 Harry Road
                   San Jose 95120
    
    
    
    -- 
    
    
    email - azydron@xml-intl.com
    smail - Mr. A.Zydron
             24 Maybrook Gardens,
             High Wycombe,
             Bucks HP13 6PJ
    Mobile +(44) 7966 477181
    FAX    +(44) 870 831 8868
    www - http://www.xml-intl.com
    
    This message contains confidential information and is intended only
    for the individual named.  If you are not the named addressee you
    may not disseminate, distribute or copy this e-mail.  Please
    notify the sender immediately by e-mail if you have received this
    e-mail by mistake and delete this e-mail from your system.
    E-mail transmission cannot be guaranteed to be secure or error-free
    as information could be intercepted, corrupted, lost, destroyed,
    arrive late or incomplete, or contain viruses.  The sender therefore
    does not accept liability for any errors or omissions in the contents
    of this message which arise as a result of e-mail transmission.  If
    verification is required please request a hard-copy version. Unless
    explicitly stated otherwise this message is provided for informational
    purposes only and should not be construed as a solicitation or offer.
    
    
    
    


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