W3C home > Mailing lists > Public > public-iri@w3.org > May 2010

RE: [bidi] Re: Special ordering for BIDI URLs

From: Jonathan Rosenne <rosennej@qsm.co.il>
Date: Mon, 31 May 2010 18:32:29 +0300
To: "'Mohamed Mohie'" <MOHIEM@eg.ibm.com>, "'Adil Allawi'" <adil@diwan.com>
Cc: <aharon@google.com>, <bidi@unicode.org>, <bidi-bounce@unicode.org>, "'Mark Davis ?'" <mark@macchiato.com>, "'Matitiahu Allouche'" <matial@il.ibm.com>, "'Murray Sargent'" <murrays@exchange.microsoft.com>, "'Nasser Kettani'" <Nasser.Kettani@microsoft.com>, <public-iri@w3.org>, "'Shawn Steele'" <Shawn.Steele@microsoft.com>
Message-ID: <008d01cb00d6$7f7c1230$7e743690$@co.il>
> To clarify this situation , is there a near plan for have the full URL
> completely localized?

There isn't, there is a lot of opposition, there should be, eventually there will be and it will happen ...

Jony

> -----Original Message-----
> From: bidi-bounce@unicode.org [mailto:bidi-bounce@unicode.org] On
> Behalf Of Mohamed Mohie
> Sent: Monday, May 31, 2010 4:12 PM
> To: Adil Allawi
> Cc: aharon@google.com; bidi@unicode.org; bidi-bounce@unicode.org; Mark
> Davis ?; Matitiahu Allouche; Murray Sargent; Nasser Kettani; public-
> iri@w3.org; Shawn Steele
> Subject: [bidi] Re: Special ordering for BIDI URLs
> 
> It's stated below that "If everything is RTL then this problem is
> avoided."
> I assume that this include also localizing http, and the extension
> "html".
> A previous assumption was added as below:
> "
> a) Pure RTL URLs are not practical currently, because of the scheme
> (http
> etc...) and the extension (html, asp, php etc...). Localizing them on
> the
> client side would be a vast effort with hard issues of coordination,
> education and likely also politics.
> "
> 
> To clarify this situation , is there a near plan for have the full URL
> completely localized?
> 
> Thanks And Best regards,
> Mohamed Mohie , PMP
> ________________________________________________
> GCoC BIDI ,
> Advisory Software Engineer, Project Manager, M.Sc.
> IBM Egypt
> email : mohiem@eg.ibm.com
> 
> 
> 
> 
>   From:       Adil Allawi <adil@diwan.com>
> 
>   To:         Matitiahu Allouche <matial@il.ibm.com>
> 
>   Cc:         "aharon@google.com" <aharon@google.com>,
> "bidi@unicode.org" <bidi@unicode.org>,
>               bidi-bounce@unicode.org, Mark Davis ?
> <mark@macchiato.com>, Murray Sargent
>               <murrays@exchange.microsoft.com>, Nasser Kettani
>               <Nasser.Kettani@microsoft.com>, "public-iri@w3.org"
> <public-iri@w3.org>, Shawn
>               Steele <Shawn.Steele@microsoft.com>
> 
>   Date:       31/05/2010 03:53 ?
> 
>   Subject:    [bidi] Re: Special ordering for BIDI URLs
> 
>   Sent by:    bidi-bounce@unicode.org
> 
> 
> 
> 
> 
> 
> For the example I gave:
> 
> http://???.????????/ which tranaslated is http://register.saudi/ where
> "saudi" is the Arabic country name.
> 
> In LTR it is ordered:
> 
> http://IDUAS.RETSIGER/
> 
> In RTL it appears
> 
> /IDUAS.RETSIGER//:http
> 
> So in the LTR case the order of the entities are:
> 
> <text1><delimiters1><text3><text2><delimiters2>
> 
> Generally for an Arabic reader this will appear correct as the reader
> will
> jump to the rightmost Arabic word. But this is already a potentially a
> confusing situation. If the country code is put to the right of the
> domain
> name then it will be logically correct but will look wrong to the
> reader.
> 
> If everything is RTL then this problem is avoided.
> 
> Adil
> 
> On 31/05/2010 08:21, Matitiahu Allouche wrote:
>       For those on the list who do not read Arabic, could you show us
> in
>       pseudo-Bidi (upper case for Arabic letters) how the URL is
> displayed
>       in LTR direction and in RTL direction?
> 
> 
> 
Received on Monday, 31 May 2010 15:33:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 19:51:57 GMT