Hide Forgot
Description of problem: madan-fonts is supposed to work for Nepali font though, it doesn't have enough glyph coverage in fontconfig. Version-Release number of selected component (if applicable): madan-fonts-2.000-2.fc13.noarch How reproducible: always Steps to Reproduce: 1.fc-match -v "Madan"|grep -E " lang"|grep ne 2. 3. Actual results: No output Expected results: the lang spec should contains ne. Additional info:
This is raised during the testing of Bug#578041.
This is because of fontconfig ne.orth issue. This problem is already reported in upstream https://bugs.freedesktop.org/show_bug.cgi?id=24729 So we are waiting for long in upstream but no fixes yet.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
ping behdad moving this to F16
I'm not involved in Fedora anymore.
guess Parag was asking because you are still the owner of the fontconfig package in Fedora :)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
- This is resolved in upstream but nothing yet in Fedora. - This is part of Fedora 17 feature https://fedoraproject.org/wiki/Features/Additional_Indic_Langs
fontconfig-2.8.0-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fontconfig-2.8.0-6.fc17
still present.
(In reply to comment #11) > still present. Does that mean you can also still see this problem on even 2.9.0?
Yes, sorry i have not written much here. Have written more detail on upstream bug id http://bugs.freedesktop.org/show_bug.cgi?id=24729 submitted latest patch there as well. Actually parag's patch never got committed in uptream. This bug not affecting "Additional language" feature, so its fine if it takes more time.
fontconfig-2.8.0-6.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
should be fixed in fontconfig-2.9.91-1.fc18