[Neobrahmigp] [Ext] Re: Tamil LGR v2.12 - 06mar19

Tue Mar 5 15:03:20 UTC 2019

Thank you, Dr. Shanmugam. 

We will inform the NBGP once the updated files are posted at the proposals’ webpage [icann.org] .

Regards,

Pitinan

From: "Dr. Shanmugam Rajabadher" <shanfaace at gmail.com>
Date: Tuesday, March 5, 2019 at 21:21
To: Pitinan Kooarmornpatana <pitinan.koo at icann.org>
Cc: Sarmad Hussain <sarmad.hussain at icann.org>, "Neobrahmigp at icann.org" <Neobrahmigp at icann.org>
Subject: [Ext] Re: Tamil LGR v2.12 - 06mar19

Dear Pitinan, 

Thank you for sharing the files. I have made few corrections (Alignment) and sharing the files. I would also like to inform you that this could be treated as final. PFAs

Thanking all the panel members and for all the support

Thanks and regards,

Dr.Shanmugam R.

On Tue, Mar 5, 2019 at 3:03 PM Pitinan Kooarmornpatana <pitinan.koo at icann.org> wrote:

Dear Dr. Shanmugam, 

Please find attached the package of Tamil LGR version 2.12 dated 6 March 2019. (The date we are aiming to publish them)

Please note that. It seems like you were updating on the outdated version. E.g. the MSR version is still 3. 

Therefore, I moved the changes you have made from the latest file to update the version 20feb2019 in this package. 

Kindly review and finalize. Then kindly share on the NBGP mailing list, telling us to publish at the proposals’ webpage [icann.org] as the final version after public comment. 

Regards,

Pitinan

From: "Dr. Shanmugam Rajabadher" <shanfaace at gmail.com>
Date: Monday, March 4, 2019 at 21:10
To: Sarmad Hussain <sarmad.hussain at icann.org>
Cc: "Neobrahmigp at icann.org" <neobrahmiGP at icann.org>
Subject: [Ext] Re: Tamil LGR v2.10 - 20190220

Dear Dr.Sarmad, 

Sending the updated version of Tamil LGR doc and PDF. Also requesting Pitinan to update XML with IP suggestions  Please find the same. 

The following IP comments have been fixed.

(1) please remove commas between code points that are part of the same sequence (many places in the document)

(2) please use smaller point size for some cases so that sequences do not break into two lines (e.g. table 18)

(3) in table 24 change the header cell "Code points which cannot co-occur within a label" to "Sequences which cannot co-occur within a label" ; The same change is required in the table name.

(4) at the start of Section 7.1, there are some characters ("hri") that should be part of the link to section 6.1.3. Something went wrong.

(5) MUST FIX:  Section 6.2: 

In both the paragraph and Table 19, the code point value for TAMIL LETTER AI should be 0B90 and not 0B9C.

Thanks and Regards,

Dr.Shanmugam R

On Mon, Mar 4, 2019 at 8:58 AM Dr. Shanmugam Rajabadher <shanfaace at gmail.com> wrote:

Dear Dr.Sarmad, 

Thank you for sharing the comments. I will revert back with the updated version soon.

Thanks and regards,

Dr.Shanmugam R.

On Mon, Mar 4, 2019 at 8:54 AM Sarmad Hussain <sarmad.hussain at icann.org> wrote:

Dear Shanmugam and NBGP members,

IP has suggested some minor edits to consider before final submission of the proposal, listed in their message below.  

As next steps, once these edits are incorporated, the proposal will be published at the proposals’ webpage [icann.org] as the final version after public comment, and then IP will undertake its evaluation.

Regards,
Sarmad

TO: NeoBrahmi Generation Panel
From: Integration Panel

We reviewed the Tamil proposal dated 2019-02-20 and found a number of places where the text could be edited for further clarity and more consistency across the Root Zone LGR. Some of these suggestions have higher priority than others, but none are absolutely required. We leave that decision to the GP, but note that we plan to edit the version of the XML to be published with LGR-3 in line with the suggestions here.

There are two items that are MUST FIX.

- Integration Panel

DETAILED FEEDBACK

DOCX

In reviewing the new text it was noted that the LGR uses commas (,) to separate code points in sequences. This is unfortunate, because that use implies that the code points are a list of individual code points.

(1) please remove commas between code points that are part of the same sequence (many places in the document)

(2) please use smaller point size for some cases so that sequences do not break into two lines (e.g. table 18)

(3) in table 24 change the header cell "Code points which cannot co-occur within a label" to "Sequences which cannot co-occur within a label" ; The same change is required in the table name.

(4) at the start of Section 7.1, there are some characters ("hri") that should be part of the link to section 6.1.3. Something went wrong.

(5) MUST FIX:  Section 6.2: 

In both the paragraph and Table 19, the code point value for TAMIL LETTER AI should be 0B90 and not 0B9C.

XML

(1) The XML is missing some comments for the new rule and action.

A comment should be added to the <rule> element as follows:

     <rule name="no-mix-sri-shri" comment="Section 7: WLE 4: Two 
        representations of 'Shri' cannot be mixed in the same label" >

A comment should be added to the <action> element as follows:

    <action disp="invalid" match="no-mix-sri-shri" comment="do not 
        mix two representations of 'Shri' in the same label" />

(Note: the phrasing of the comment text is based on the model of the Arabic LGR, ensuring consistency)

 Done. See line 206 and 236.

(2) In reviewing the XML section on "Character Classes" we noted some additional small edits:

<p>Virama: All consonants contain an implicit vowel (a). A special
sign is needed to denote that this implicit vowel is stripped off. This is known
as the Pulli and encoded as U+0BCD ( ் ) TAMIL SIGN VIRAMA. The virama thus 
joins two adjacent consonants. In Tamil, thereare only two cases where this 
forms conjuncts. More details in Section 3.3.2, "Virama/Pulli" of the [Proposal].</p

and

<p>Visarga: The Visarga (or Aytham) is  used in Tamil to represent a sound very close to /ḵ/.
More details in Section 3.3.4, "Visarga/Aytham" of the [Proposal].</p>

This removes double names so the items in front of the ":" match the name of the character class as promised at the head of the section. It also fixes two typos (extraneous "2" and misspelled "adjacent")

  Done. See line 32-36 and 42-43.

Similar edits have been made in other LGRs in the list of character classes, so this would increase consistency.

(3) MUST FIX: 

The rule "preceded-by-X" uses look-ahead to match a Visarga, so it should be named "precedes-X" instead. 

The naming issue arises because the way the rule is defined in Section 7 does not translate directly to a context rule.

Section 7, WLE 3 , X cannot be preceded by X

the context should be "precedes-X" and the rule is applied to X as a not-when="precedes-X". The convention is that context rules are named for the context, so that a reader can correctly understand the following line in the XML:

<char cp="0B83" not-when="precedes-X" ...> 

as meaning X (08B3) cannot precede X.

------

Alternatively, it would be possible to change the rule to use  <look-behind>  and naming it "follows-X". This leads to the equivalent:

<char cp="0B83" not-when="follows-X" ...>

However, in that case, the rule also has to be changed to move the location of the <anchor/> element to after the <look-behind> element.

In the first alternative the name of the context is closer to the wording of the rule in Section 7, in the second alternative, all contexts in the LGR would consistently use <look-behind>. The choice between these alternatives is a matter of preference left to the GP.

 Selected first option. Updated the name of the rule "preceded-by-X" to "precedes-X". See 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/neobrahmigp/attachments/20190305/7720d518/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4610 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/neobrahmigp/attachments/20190305/7720d518/smime-0001.p7s>