mixing different direction labels within same domain

[JFC Morfin]

At 10:44 10/08/2011, Abdulrahman I. ALGhadir wrote:
>Content-Language: en-US
>Content-Type: multipart/alternative;
> 
>boundary="_000_E393942FC3AB7F4C9C50F559E9E4E45F13AE6518ry2mail2citcgov_"
>
>Dear JFC,
>Thank you for letting me in this I'll try to gather most of pointed 
>issues in IDNA and I'll try to send to you later hopefully!
>
>But have ever seen this proposed solution on improving the display of URI?
><http://www.unicode.org/review/pri185/>http://www.unicode.org/review/pri185/
>This solution has been pended waiting for any feeds on it so that 
>they can publish it, and I think this solution will solve most of 
>confusing problems in the display, yet it'll give us defending 
>points on removing some limitations  in the IDNA (hopefully!).
>
>Abdulrahman,

Dear Abdulrahman,

Thank you for your annouced help. I am looking for your contribution 
to add to our wiki consolidation.

At this stage I am just trying to compile the post IDNA2008 problems 
people raise in various areas. And possibly the terminology which can 
be adequate to describe/address them among network operations and use 
oriented WGs and NGOs (ICANN, IETF, ITU, IUTF). This is for all these 
people to come with a simple, consistent, stable way to address them 
at protocol level and then be able to discuss with Unicode what they 
may need from them. In focusing first on the roots of the problems in 
his are, one may help others to identify a similar problem they were 
not aware until now.

Thank you for quoting pri185: from it I am going to try to extract 
the problems they raise; in the way it impacts us. However, I am not 
familiar with Bidi. So I would prefer specialists to summarize the 
difficulties they meet and Unicode discusses. So, ICANN and other 
people might understand better, decide if they also are impacted and 
how to handle a possible difficulty they would have identified this 
way in their own bailiwick.

Best!
jfc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.alvestrand.no/pipermail/idna-update/attachments/20110811/0b3434d1/attachment.html>