<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: 13px">
<div>My main point is that I think consistency is important. Perhaps rendering labels in LTR order always would work, perhaps rendering in RTL order if there's any RTL characters would work. The problem is that when some parts are rendered in one direction
and others in another direction, then it becomes terribly unclear what the URL is doing.</div>
<div> </div>
<div>Martin mentioned that users had to learn what <a href="http://microsoft.com">
http://microsoft.com</a> meant, and I think they can adapt to whatever ordering happens, so long as it is reasonable.</div>
<div> </div>
<div>I also think this needs a lot of thought, because I'm not sure at all that this is very clear in terms of a full IRI. I certainly haven't thought about it enough. In a full URL I think it's less clear because we don't necessarily know what the server's
using for delimiters. What happens with "http://mydomain.com/mypage.html?user=shawn&flags=fun" ? If the whole thing's RTL, do you render as fun=flags&shawn=user?html.mypage/com.mydomain//:http ? What if the "flags=" and "user=" stay LTR? And then there're
all the systems that use completely different syntax to do that type of thing. Even saying IRIs have to be LTR is hard because individual words obviously can't be LTR if they're RTL words, so in that case, what's being a delimiter and what's part of a word?
Is _ a delimiter or word part?</div>
<div> </div>
<div>-Shawn</div>
<div> </div>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<hr tabindex="-1">
<div style="DIRECTION: ltr" id="divRpF257534"><font color="#000000" size="2" face="Tahoma"><b>From:</b> idna-update-bounces@alvestrand.no [idna-update-bounces@alvestrand.no] on behalf of Slim Amamou [slim@alixsys.com]<br>
<b>Sent:</b> Thursday, November 05, 2009 9:06 AM<br>
<b>To:</b> Martin J. Dürst<br>
<b>Cc:</b> Alireza Saleh; muhtaseb@kfupm.edu.sa; public-iri@w3.org; idna-update@alvestrand.no; Lisa Dusseault; Shawn Steele; Abdulrahman I. ALGhadir<br>
<b>Subject:</b> Re: IDNAbis spec<br>
</font><br>
</div>
<div></div>
<div>hi everybody,<br>
<br>
On Wed, Nov 4, 2009 at 6:57 PM, Shawn Steele <span dir="ltr"><br>
</span>
<blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<span dir="ltr">(...)</span><br>
<br>
I think that labels are like a list. If I have a list (a, b, c, d), then I expect the list to be in order a, b, c, d. In an RTL context I would reasonably expect the list to be rendered (d, c, b, a). If the individual values happen to be in different scripts,
that's not going to change the fact that I expect the list to have each element progress in an orderly fashion from least significant to most significant.<br>
</blockquote>
<br>
This is actually not obvious, for example for numbers, the order is left to right and arabic readers don't have any problem with that.
<br>
<br>
In my opinion, enforcing LTR on IRIs is a better solution than //:http. An it seems that relevant specs (RFC3987 and w3c IRI bidi examples) are on my side.<br>
<br>
I raised that issue a while back on IDN wiki. You can see the discussion and the relevant specs here :
<a href="http://sn.im/t2ojj" target="_blank">http://sn.im/t2ojj</a><br>
<br clear="all">
<br>
-- <br>
Slim Amamou | Óáíã ÚãÇãæ<br>
<a href="http://alixsys.com" target="_blank">http://alixsys.com</a><br>
</div>
</div>
</div>
</body>
</html>