Created attachment 599423 [details] Glyphs for Telugu nakaarapollu and repha Telugu script has special form of vowelless NA called four-pronged nakaarapollu. Strictly speaking nakaarapollu means nakaara + pollu=virama so regular form of vowelless-NA న్ is also nakaarapollu but Telugu old grammarian Brown has specifically called a distinct form as nakaarapollu. The recommended model for getting Telugu nakaarapollu is NA + ZWJ + VIRAMA. Please find more details in the document: https://sites.google.com/site/jamadagni/files/utcsubmissions/11409-telugu-nakaara-pollu.pdf Likewise Telugu script has old repha form which is not found in common usage in current Telugu script. A modern-style Telugu font can allow user to select old-style reph by using the sequence RA + VIRAMA + ZWJ + CONSONANT because the plain RA + VIRAMA + CONSONANT would be presented as RA with sub-base form of CONSONANT. Please find more details in the document: https://sites.google.com/site/jamadagni/files/utcsubmissions/12017-telugu-reph-model-finalize.pdf These two documents have been approved by the UTC in the Feb 2012 meeting: http://www.unicode.org/L2/L2012/12007.htm <quote> [130-A15] Action Item for Deborah Anderson, Editorial Committee: Update the core specification text on Telugu nakaara-pollu based on input in document L2/11-409. [130-A16] Action Item for Deborah Anderson: Incorporate text on Telugu Reph from L2/12-017 into the Telugu block description. </quote> It is requested to: 1) add the glyphs for nakaarapollu and repha to the Lohit Telugu font: 2) add substitution mapping of NA + ZWJ + VIRAMA to the nakaarapollu glyph 3) add requisite OT markups for repha glyph so that a compliant OT system can recognize the repha glyph and render sequence of RA + VIRAMA + ZWJ + CONS using that glyph.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
we will do this in Lohit2. Moving to
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Hello. I note that I had provided the glyphs for the nakaarapollu and reph. I'm not sure why action is not taken on this bug. Anyhow, I am sorry to say that the sequence mentioned by me in the bug summary for nakaarapollu i.e. NA + ZWJ + VIRAMA is not correct and not approved by UTC -- I apologise for this serious gaffe. As per the very Unicode reference doc L2/11-409 I had provided (my own) the NA + ZWJ + VIRAMA is theoretically applicable for the isolate glyph but is not appropriate in running text because ZWJ + VIRAMA requests C2-conjoining forms. The UTC only approved documenting this written form as an alternate presentation of vowelless NA when isolate. So the request about nakaarapollu may be ignored. However the part about the reph is entirely appropriate and approved by the UTC. As such, it should be possible to add the requisite OT tags so that shaping engines can display it when requested by RA + VIRAMA + ZWJ + C.
I am still not clear on implementation of Reph. Need to do some experimentation. From experience as soon as we use feature Reph, its started get ordering at the end of syllable. Will try this soon.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.