[arabic-vip] version 0.8 (wasRe: Arabic Script Issues Document Ver 0.7)

Tue Oct 4 04:55:35 UTC 2011

I'm in agreement with Andrew that this point should be raised.

Non-Space Mark should be discussed in the document in one place ... hence my earlier review (V.5) of the document suggested that ... and also my last review (V. 7).

I would recommend to move all the discussion about Non-Space Mark in one separate section and put all the issue there.

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

> -----Original Message-----
> From: arabic-vip-bounces at icann.org [mailto:arabic-vip-bounces at icann.org]
> On Behalf Of Andrew Sullivan
> Sent: Tuesday, October 04, 2011 1:00 AM
> To: arabic-vip at icann.org
> Subject: [arabic-vip] version 0.8 (wasRe: Arabic Script Issues Document
> Ver 0.7)
> 
> Dear colleagues,
> 
> I looked at version -08.  I've attached some comments.
> 
> The most serious are these:
> 
>     1.  I caught an issue near the end of section 6, number 1, where
>     it talks about the characters being "composed" under the Unicode
>     rules.  This isn't quite right.  I'm not exactly sure how to fix
>     this, so I couldn't suggest any text, but the issue is roughly as
>     follows.  The basic rule is that the candidate string to be a
>     U-label needs to be in NFC form.  NFC, which is a kind of
>     normalization, is often _not_ the composed form of the characters.
>     This is because early forms of Unicode might have encoded the
>     character by using multiple code points, because the precomposed
>     form of the character was not available.  The idea is that, if you
>     get a string from Unicode version 9000, you will still be able to
>     compare its NFC form with Unicode version 3, because the string
>     under Unicode version 9000 when run through NFC will produce
>     exactly what would have been typed under version 3 (modulo
>     characters that simply couldn't be written in version 3).
> 
>     So, there are two problems.  First, this text should not be
>     talking about "composed", but rather the "normalized" form.  This
>     is a detail.  The problem I see is that I still don't understand
>     well enough the use of the combining marks that are recommended
>     not to be allowed in this document.  If any of those combining
>     marks are part of the results of NFC processing, then when the
>     U-label is submitted to ICANN it is going to fail the test for
>     those combining marks, and the label will be rejected.
> 
>     Sorry for not realizing/explaining this earlier (I think it was
>     underlying what I was trying to get at in the discussion we had
>     very early on about normalization, but I didn't understand
>     properly how these things would fit together so I didn't make
>     myself clear enough).
> 
>     2.  I added a comment to the beginning of section 8 about
>     emphasising the ways that turning variants on or off in the root
>     will affect everyone further down the tree.  I don't feel super
>     strongly about this, but it would be nice to emphasize the
>     importance of this.
> 
>     3.  There remain some issues in the definitions that I find a
>     little troublesome.
> 
> As always, this is all just advice and the team should ultimately conclude
> what it wants to do about all these cases.  I'm just highlighting them in
> order to try to help the team polish an already very good report.
> 
> Best,
> 
> A
> 
> On Mon, Oct 03, 2011 at 11:31:31PM +0500, Sarmad Hussain wrote:
> > Dear Dr. Al-Zoman and All,
> >
> >
> >
> > Thank you for your timely review.  Please find attached some additional
> comments.
> >
> >
> >
> > Baher, there is a specific question for IDN VIP team regarding the
> dispute resolution section.
> >
> >
> >
> > Talk to most of you tomorrow.
> >
> >
> >
> > Regards,
> > Sarmad
> >
> >
> >
> >
> >
> >
> >
> > From: Abdulaziz Al-Zoman [mailto:azoman at citc.gov.sa]
> > Sent: Monday, October 03, 2011 5:08 PM
> > To: Sarmad Hussain; arabic-vip at icann.org;
> > siavash.shahshahani at gmail.com
> > Cc: Abdulaziz Al-Zoman
> > Subject: RE: [arabic-vip] Arabic Script Issues Document Ver 0.7
> >
> >
> >
> > Dear Dr. Sarmad,
> >
> >
> >
> > Thanks for your continuous effort to enhance the final report.   Please
> find enclosed my comments.
> >
> >
> >
> > -----------------------------
> >
> > عبدالعزيز بن حمد الزومان
> >
> > Abdulaziz H. Al-Zoman
> >
> >
> >
> > From: arabic-vip-bounces at icann.org
> > [mailto:arabic-vip-bounces at icann.org] On Behalf Of Sarmad Hussain
> > Sent: Monday, October 03, 2011 1:03 AM
> > To: arabic-vip at icann.org; siavash.shahshahani at gmail.com
> > Subject: [arabic-vip] Arabic Script Issues Document Ver 0.7
> >
> >
> >
> > Dear All,
> >
> >
> >
> > Here is another version, with additional comments incorporated in the
> document.  Kindly review this version for the conference call tomorrow.
> >
> >
> >
> > Again, have tried to address as many of the comments as suggested.
> However, there may be a few comments which may still remain unaddressed.
> I would suggest that we bring these up in the conference call with
> everybody to get the general consensus of the team.
> >
> >
> >
> > Apologies for having a short time to review a long document.  Again,
> both redline and cleaned versions are attached.  Please comment on the
> cleaned version.
> >
> >
> >
> > Regards,
> > Sarmad
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ----------------------------------------------------------------------
> > -------------
> > 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.
> >
> 
> 
> 
> 
> --
> Andrew Sullivan
> ajs at anvilwalrusden.com

-----------------------------------------------------------------------------------
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.