[arabic-vip] URGENT: Response to public comments

[Abdulaziz Al-Zoman]

Dear all,

Nice to hear from you again. 

As I expected and discussed with you during the drafting of the report, the ZWNJ is a problematic to some Arabic Script communities (e.g., Arabic language speaking community). 

The comments might come from members of the Arabic language community, but they are related to Arabic script TLDs. As you know TLDs are not treated at the language level but rather script level. Therefore, their concerns are still valid since users see string of Arabic script characters and the ZWNJ (if it is part of the TLD) is invisible to them and most impotently they cannot understand its behavior and cannot coop with it. 

I would agree with you if TLD is associated with languages not the script.

-----------------------------
عبدالعزيز بن حمد الزومان
Abdulaziz H. Al-Zoman

> -----Original Message-----
> From: arabic-vip-bounces at icann.org [mailto:arabic-vip-bounces at icann.org]
> On Behalf Of Dr.Sarmad Hussain
> Sent: Saturday, November 26, 2011 5:26 PM
> To: Siavash Shahshahani
> Cc: arabic-vip at icann.org
> Subject: Re: [arabic-vip] URGENT: Response to public comments
> 
> Dear Siavash,
> 
> Thank you for your comments.  I understood the comment is referring to
> Arabic language as well.
> 
> regards,
> Sarmad
> 
> 
> On Sat, Nov 26, 2011 at 5:24 PM, Siavash Shahshahani <shahshah at irnic.ir>
> wrote:
> > Just a brief remark on the comments of T.B.Merghani of Sudan-ISOC and
> > Al Marzooqi of TRA-UAE on ZWNJ. In both cases the word 'Arabic' is
> > used to refer to Arabic language not Arabic script in general as used
> > by different languages. The comments made here were all discussed in
> > VIP Arabic Script group quite extensively and I don't see any new
> > issues raised. My apologies again as I won't be able to join the call
> at 8:00 UTC.
> > Regards,
> > Siavash
> >
> >
> > On 25.11.2011 08:46, Siavash Shahshahani wrote:
> >>
> >> Sorry, Baher, I'm teaching a class then and won't be able to join.
> >> I'll try to send written comments before the meeting.
> >> Siavash
> >>
> >>
> >> On 25.11.2011 01:06, Baher Esmat wrote:
> >>>
> >>> Re: [arabic-vip] URGENT: Response to public comments   Team:
> >>>
> >>>  I’m organizing the call to take place on Sunday at 8am UTC for 90
> >>> minutes.
> >>>
> >>>  Call details will be sent shortly.
> >>>
> >>>  If anyone needs a dial out please send me the number.
> >>>
> >>>  Best,
> >>>  Baher
> >>>
> >>>  On 11/24/11 11:55 AM, "Baher Esmat"  wrote:
> >>>
> >>>> Team:
> >>>>
> >>>> If you have not completed the Doodle poll please take a minute to
> >>>> do so: http://www.doodle.com/s3hw9kkpg2siw3kr [1].
> >>>>
> >>>> Here is a sample of the analysis document we need to submit by
> >>>> 28-Nov:
> >>>>
> >>>
> >>>
> >>> http://www.icann.org/en/public-comment/report-comments-idn-guideline
> >>> s-revision-02sep11-en.pdf
> >>>>
> >>>> [2]. Content of this sample document is NOT related to our project.
> >>>> The two sections team is expected to complete are section III
> >>>> (summary of comments) and section IV (analysis of comments). Don’t
> >>>> worry about the document format, I’ll take care of that.
> >>>>
> >>>> I’m also re-sending comments submitted (attached). Please try to
> >>>> read them before we get on the call.
> >>>>
> >>>> If any questions let me know.
> >>>>
> >>>> Best,
> >>>> Baher
> >>>
> >>>
> >>> Links:
> >>> ------
> >>> [1] http://www.doodle.com/s3hw9kkpg2siw3kr
> >>> [2]
> >>>
> >>>
> >>> http://www.icann.org/en/public-comment/report-comments-idn-guideline
> >>> s-revision-02sep11-en.pdf [3]
> >>> http://chapar1.nic.ir/baher.esmat@icann.org
> >
> >


-----------------------------------------------------------------------------------
Disclaimer:
This message and its attachment, if any, are confidential and may contain legally
privileged information. If you are not the intended recipient, please contact the
sender immediately and delete this message and its attachment, if any, from your
system. You should not copy this message or disclose its contents to any other
person or use it for any purpose. Statements and opinions expressed in this e-mail
are those of the sender, and do not necessarily reflect those of the Communications
and Information Technology Commission (CITC). CITC accepts no liability for damage
caused by this email.