Bug ID: 1078661
Summary: Deprecate the usage of U+0BB8 U+0BCD U+0BB0 U+0BC0
for SRII per latest unicode standard
QA Contact: extras-qa(a)fedoraproject.org
Description of problem:
Complex glyph SRI was changed from U+0BB8 U+0BCD U+0BB0 U+0BC0 to U+0BB6
U+0BCD U+0BB0 U+0BC0 in Unicode 4.1. Lohit-Tamil displays the complex glyph for
both forms for backward compatibility. However this also prevents migration to
latest standard as some input tools too offer same functionality leading to
more content created with U+0BB8 U+0BCD U+0BB0 U+0BC0 as SRI which increases
the need for backward compatibility. To break this vicious cycle, I propose
U+0BB8 U+0BCD U+0BB0 U+0BC0 should not be substituted with complex glyph SRI
and should be displayed normally. Apple / iOS fonts already do this complying
with latest unicode standard. Failing to move to single consistent
representation in line with latest unicode leads to fragmentation within
unicode text, a greater cause for worry than backward compatibility.
I understand the larger problem of standardization cannot happen only by
changing this font, but its a start and Lohit being the only maintained free
Tamil font, can help in the process.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ஸ்ரீ (U+0BB8 U+0BCD U+0BB0 U+0BC0) should be displayed as ஸ்(U+0BB8 U+0BCD)
ரீ(U+0BB0 U+0BC0) without a space in middle and not compounded form.
U+0BB8 U+0BCD U+0BB0 U+0BC0 giving complex glyph SRI
U+0BB8 U+0BCD U+0BB0 U+0BC0 should not give complex glyph SRI, should give
U+0BB8 U+0BCD and U+0BB0 U+0BC0 seperately.
Ligature2: "'abvs' Above Base Substitutions in Tamil lookup 0 subtable"
u0BB8_u0BCD.half u0BB0 u0BC0
in Lohit-Tamil.sfd should be removed.
See also bug 450699
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug