+++ This bug was initially created as a clone of Bug #659214 +++ Hi guys, bug #659214 adds support for some Cyrillic characters to the Liberations fonts family. M. Balabanov, a member of a localization mailing list reported a problem with the glyphs. The glyphs for CYRILLIC CAPITAL LETTER I WITH GRAVE (U+040D) is wrong (except for Mono Regular). Instead of Ѝ it is Ǹ (i.e it's swapped). The actual glyph is LATIN CAPITAL LETTER N WITH GRAVE (I just made that up, hopefully you get the point). This is with version: 1.07.1 of the fonts.
*** Bug 799473 has been marked as a duplicate of this bug. ***
I have fixed this issue in liberation-fonts-1.07.2, check for https://fedorahosted.org/liberation-fonts for latest release.
I have checked liberation-fonts-1.07.2. The glyphs for 'CYRILLIC SMALL LETTER I WITH GRAVE' (U+045D) are indeed improved, now with correct italic shapes in Serif, Sans, and Sans Narrow. The glyphs for 'CYRILLIC CAPITAL LETTER I WITH GRAVE' (U+040D) are still wrong though. Their current shapes in all fonts but Mono regular are still based on a capital Latin En (N) instead of on a capital Cyrillic I (И).
Does U+040D character has different shapes in normal and italic form?
U+040D should look exactly like 0+418 Cyrillic Capital Letter I (from the same font variant) + the grave accent This is the same in all forms - roman, itallic, oblique, tnin, bold, black, demibold, etc. The same rule is valid both in Bulgaria and Macedonia where the letter is used. If the italic/cursive variants have different shapes for 0+418 - use them. However for the styles of Liberation family this is not the case - Cyrillic itallic capital I is shaped the same way as the non itallic variant. Thus - just - copy and aggregate 0+418 and the glyph for grave you use. If you want to be extremely punctual - we can try to place the grave to optically balance in the middle (since it is optically blacker on one side), but to be honest - that will be pointless. Kind regards. al_shopov
Created attachment 568216 [details] Correct letter forms for U+040D and U+045D
Thanks for clarifications. I have done these changes and committed in upstream. This will be available with next release. Let me know, if required i can build this quickly in fedora with patch.
Hi, I have just verified that the glyphs look fine now. Thank you for the quick patches. I expect these will be included in next release of Fedora and perhaps with the next updates of Fedora 16.
liberation-fonts-1.07.2-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/liberation-fonts-1.07.2-4.fc17
liberation-fonts-1.07.2-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/liberation-fonts-1.07.2-4.fc16
Package liberation-fonts-1.07.2-4.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing liberation-fonts-1.07.2-4.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7730/liberation-fonts-1.07.2-4.fc17 then log in and leave karma (feedback).
liberation-fonts-1.07.2-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
liberation-fonts-1.07.2-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
liberation-fonts-1.07.2-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/liberation-fonts-1.07.2-6.fc17
liberation-fonts-1.07.2-6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/liberation-fonts-1.07.2-6.fc16
liberation-fonts-1.07.2-6.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
liberation-fonts-1.07.2-6.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.