RE: [PLS1.0] i18n comment: Sub-elements for example

> > R103-30:
> > Resolution: Rejected
> > 
> > - You asked to add markup in the example element.
> > - We rejected it with motivations.
> > - No answer
> > 
> > + E-mail Trail
> > - Original Comment Richard Ishida (2006-03-21)
> >   http://lists.w3.org/Archives/Public/www-voice/2006JanMar/0089.html
> > - VBWG official response to last call issue VBWG (2006-05-26)
> >   http://lists.w3.org/Archives/Public/www-voice/2006AprJun/0075.html



The i18n WG still feels that markup would be better for bidi text than
Unicode control codes, but we will not insist on this if it will force you
back to WD.

Reasons we prefer markup include:

1. start and end markers are visible, which decreases the likelihood of
errors

2. correct application of bidi information can be checked as part of the
well-formedness and validation checks on the document

3. the scope of the embeddings is easier to manage (eg. if a PDF control is
omitted after an RLE, it is not clear in marked up content where the
embedded directionality should terminate - markup makes that clear).


RI
 


============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)

http://www.w3.org/People/Ishida/
http://www.w3.org/International/
http://people.w3.org/rishida/blog/
http://www.flickr.com/photos/ishida/


 


________________________________

        From: Baggia Paolo [mailto:paolo.baggia@xxxxxxxxxxxx] 
        Sent: 26 May 2006 15:23
        To: www-voice@xxxxxx
        Cc: Baggia Paolo; Richard Ishida
        Subject: Re: [PLS1.0] i18n comment: Sub-elements for example
        
        
         
        Issue R103-30
        
        Proposed Classification: Feature Request 
        
        Resolution: Reject 
        
        The element has XML Schema type 'string' [1] which allows
        embedding of directionality marks and overrides (e.g. 0x200E,
0x200F,
        0x202D, 0x202E, 0x202C). We've reviewed the I18N FAQ [2] and Unicode
        Technical Report #20 [3] and believe that embedded character codes
are
        appropriate for the element.
        
        PLS documents cover a single language. We've assumed that the
examples
        would be in the same language as the lexicon and that adding
xml:lang to
        was therefore unnecessary. In the case of 'borrowed' words
        such as 'hors d'oeuvres', the example would be written in the
borrowing
        language as in "As an appetizer, he prepared a wide selection
        of hors d'oeuvres such as cucumber sandwiches and garlic hummus with
        baked pita.".
        
        [1] http://www.w3.org/TR/xmlschema-2/#string 
        [2] http://www.w3.org/International/questions/qa-bidi-controls 
        [3] http://www.w3.org/TR/unicode-xml/#Charlist
        
        Paolo Baggia, editor PLS spec.
        
        
------------------------------------------------------------------------
        ---
        From: 
        Date: Tue, 21 Mar 2006 17:51:43 +0000
        To: www-voice@xxxxxx, public-i18n-core@xxxxxx 
        Message-Id: <20060321175142.BB70C4EFDE@xxxxxxxxxxxx> 
        
        
        Comment from the i18n review of:
        http://www.w3.org/TR/2006/WD-pronunciation-lexicon-20060131/
        
        Comment 30
        At http://www.w3.org/International/reviews/0603-pls10/
        Editorial/substantive: S
        Owner: RI
        
        Location in reviewed document:
        4.8
        
        Comment: 
        If the example element can contain only text, it will not be
possible to
        apply directional markup to bidirectional text. Since this text can
be
        harvested for reading elsewhere, we propose that you allow, as a
minimum
        a span-like element within the example element that can support a
        dir=ltr|rtl|lro|rlo attribute to handle bidirectional text.
        
        
        You could also allow xml:lang on the span-like element for language
        markup.
        
        
        Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia
S.p.A.
        
        ================================================
        CONFIDENTIALITY NOTICE
        This message and its attachments are addressed solely to the persons
        above and may contain confidential information. If you have received
        the message in error, be informed that any use of the content hereof
        is prohibited. Please return it immediately to the sender and delete
        the message. Should you have any questions, please send an e_mail to
        <mailto:webmaster@xxxxxxxxxxxxxxxx>webmaster@xxxxxxxxxxxxxxxxx Thank
you
        <http://www.loquendo.com>www.loquendo.com
        ================================================