[Neobrahmigp] FW: Defect in the Root Zone LGR for Malayalam?

Pitinan Kooarmornpatana pitinan.koo at icann.org
Tue Aug 6 10:24:24 UTC 2019


Dear Veena, 

 

Please find below a message from the IP to NBGP regarding an issue in the integrated Malayalam LGR. 

The IP found the discrepancy of rule #1 in three places : XML , proposal, and the response to public comment. 

 

Kindly review and let us know your feedback. 

 

Regards,

Pitinan

From: Integration Panel
To: NeoBrahmi Generation Panel
Re: Issue in Root Zone LGR for Malayalam

The IP has become aware of an issue in the published version of the RZ-LGR for Malayalam.

 

The RZ-LGR-3 version of the Malayalam LGR uses formulation of WLE Rule 1 that (while matching the XML file in the Malayalam LGR proposal) is more permissive than what the proposal document calls for in Section 7. 

 

The XML files allow 0D7B to precede Halant, while the text of the proposal document does not, and furthermore, the text gives one example of a sequence that should not be allowed by WLE Rule 1. 

At issue is sequence 1b from section 6.1, which the proposal text says should be disallowed because it doesn't render consistently. WLE Rule 1 for H (until the April version of the proposal) did allow the sequence, because VIRAMA was allowed to follow 0D7B.

This provision was removed in the April version for the DOCx but not in the XML version of the proposal, and the RZ-LGR-3 version of the XML has been published with the more permissive rule.

One effect is that sequence 1b, which, if permitted, should have been a variant, is now permitted without being a variant, a situation that constitutes a "loophole" that would allow variant labels to be allocated as if unrelated.

The WLE rule in question was first changed in response to public comment (it did not allow 0D7B in the 2018-09-25 version).  Here's a comment on sequence 1b:

 

Normally, with the proposal clearly worded one way and the XML different, this could have been a "clerical error" and handled accordingly. However, given that the public comment response and the final proposal are different, it is not possible to unambiguously determine the underlying intent.

 

As it stands, if we leave the Root-Zone's XML version of the rule as is, that XML would be missing a variant definition; Section 6.1 makes it  clear that a variant would have been required for sequence 1b if not disallowed. If we change the rule to match the proposal document, then the proposal XML file and response to public comment would need to be revised. 

 

We have further received reports that question the analysis of the three sequences in Section 6.1 and  that come to different conclusions on  which ones are unambiguously supported (and which ones should be supported). In particular it is claimed that sequence 1b is not supported by Windows' shaping engine (and neither is 1a).

 

We therefore request the GP to revisit this issue and to resolve how to address this going forward. 

 

In particular, we would also like the GP to confirm which software platforms support which sequences.


--IP

 

PS: we are aware that some parties are planning to approach Unicode to request a change to table 12-38. While no such proposal has been received by Unicode today, there is the possibility, but not a certainty, that Unicode's position on the status of that sequence could change in the future.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/neobrahmigp/attachments/20190806/98b920bc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 43846 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/neobrahmigp/attachments/20190806/98b920bc/image001-0001.png>
-------------- 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/20190806/98b920bc/smime-0001.p7s>


More information about the Neobrahmigp mailing list