[Neobrahmigp] Tamil - addendum about allocatable variants

[Sarmad Hussain]

Dear Shanmugam, NBGP members,

Please find some additional feedback from IP on Tamil LGR proposal for your consideration, below.

Regards,

Sarmad

  _____  

On review of the NeoB LGRs, the IP found that the only instance of allocatable variants is found in Tamil.


The Tamil GP justifies this choice by the fact that the adoption of  0BB6 0BCD 0BB0 0BC0 as the preferred method of encoding this sequences in Unicode 4.1 did not get fully adopted in practice, so the old legacy is still around and kicking. It would seem, users cannot tell the difference and won't know, possibly, which one they are using. Hence, using an allocatable variant appears to be a reasonable. 


Variant Set 5 — 2 Members


Source

Glyph

Target

Glyph

 

Type

Ref

Comment


 <file:///C:/Users/Michel.SUIGNARD/Dropbox/IP/LGR-3/LGR-3-staging4-NeoB/NeoBTestRelease-2018-06-25/lgr-3-tamil-script-2018-06-25-en.html#0BB6_0BCD_0BB0_0BC0> 0BB6 0BCD 0BB0 0BC0

ஶ்ரீ

 <file:///C:/Users/Michel.SUIGNARD/Dropbox/IP/LGR-3/LGR-3-staging4-NeoB/NeoBTestRelease-2018-06-25/lgr-3-tamil-script-2018-06-25-en.html#0BB8_0BCD_0BB0_0BC0> 0BB8 0BCD 0BB0 0BC0

ஸ்ரீ

↔

allocatable

 

 

 

However, That sequence repeated too many times in a label could create a large number of allocatable variants for a label. While, a four code-point sequence like ‘shrii/srii’ should typically only happen once in a label; there  really is no need to support the case of mixed SRII and SHRII in the same label.

The IP requests theTamil GP to create a WLE rule limiting the number of allocatable labels to no more than two (2) by adoptong a "no-mix" rule like those found in the Arabic LGR.  Adopting this rule would also require creating an <action> element to set the disposition of any label matching the rule to "invalid"

The following is an (unverified and untested) sample XML fragment that should indicate the general nature of such a rule. 

<rule name="Shrii">
   <char cp="0BB6 0BCD 0BB0 0BC0" />
</rule>
<rule name="Srii" />
   <char cp="0BB8 0BCD 0BB0 0BC0" />
</rule>
<rule name="no-mix-Shrii-and-Srii" />
    <choice>
        <rule>
           <rule by-ref="Shrii" />
           <any count="0+" />        
           <rule by-ref="Srii" />
        </rule>
        <rule>
           <rule by-ref="Srii" />
           <any count="0+" />        
           <rule by-ref="Shrii" />
        </rule>    
    <choice>
  </rule>
  
<action disp="invalid" not-match="no-mix-Shrii-and-Srii" />


The IP asks the GP to evaluate this and it the GP agrees, to add such a rule to the LGR after the necessary verification and testing.



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