[Bug 1016989] New: [ml_IN] non-standard sequence sequence for stacked chillu-N and RRA in Lohit Malayalam font should be removed

bugzilla at redhat.com bugzilla at redhat.com
Wed Oct 9 06:10:50 UTC 2013


https://bugzilla.redhat.com/show_bug.cgi?id=1016989

            Bug ID: 1016989
           Summary: [ml_IN] non-standard sequence sequence for stacked
                    chillu-N and RRA in Lohit Malayalam font should be
                    removed
           Product: Fedora
           Version: rawhide
         Component: lohit-malayalam-fonts
          Assignee: psatpute at redhat.com
          Reporter: samjnaa at gmail.com
        QA Contact: extras-qa at fedoraproject.org
                CC: fonts-bugs at lists.fedoraproject.org,
                    i18n-bugs at lists.fedoraproject.org, psatpute at redhat.com



This is related to bug #1016984 which I reported just now.

As per TUS 6.2 chapter 9.9 p 321 (p 351 of PDF) the correct sequence to get the
display of stacked chillu-N on top of RRA in Malayalam is: CHILLU N + VIRAMA +
RRA. That is: ൻ്റ  = 0d7b 0d4d 0d31. However, currently Lohit Malayalam font
does not support this sequence. In bug #1016984 I have requested to add it.

Apart from that, note that currently the sequence being used to display stacked
chillu-N on top of RRA in Lohit font is ന്റ = 0d28 0d4d 0d31. This is
non-standard. It is inadvisable to retain this sequence as having two
canonically non-equivalent sequences display the same is a security issue of
confusability.

My request from the POV of being standard-compliant would be to remove this
sequence.

However I am sure (based on personal email communication) there will be
objection from people such as Santosh Thottingal since they do not agree with
the standard on this matter. They maintain that NA + VIRAMA + RRA is the
correct sequence to get this display.

I have told them that if they disagree with the standard then they should
discuss the matter on the Unicode and try to make the Unicode Technical
Committee accept their view. Otherwise such sequences will just be
standards-non-compliant and the existing diversified situation will only be
aggravated.

Certainly the current standard-prescribed sequence should be included to be
standards compliant. For that I have already filed the separate bug. For 100%
compliance the old non-standard should be removed. To track that I am filing
this bug now.

In the face of community objection, it is up to the project maintainer to
decide about this.

Version-Release number of selected component (if applicable):
2.5.4

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ALH5tjahY0&a=cc_unsubscribe


More information about the fonts-bugs mailing list