Created attachment 119275 [details] image showning overlapping alphabets in LibreOffice LibreOffice does not render Nafees Nastaleeq Urdu fonts properly. Attached image contains the Urdu language alphabets in Nafees Nastaleeq font. These alphabets are overlapping each other. Honestly, I am not sure if this is the problem with the font or the LibreOffice rendering. If I am mistaken, please let me know and I will contact the font developers. Thanks, Ahsan
If you upgrade to LibreOffice 5.0.2, are you still able to reproduce the problem?
I am using Fedora 22 and LibreOffice (LO) 5 has not been pushed to updates repositories yet. In Fedora, I will check it with 5 as soon as 5 lands in repos. I briefly tried checking it with LO 5 in a Debian 8.2 Virtual Machine. As compared to Fedora which has the following collection of Nafees Urdu fonts nafees-pakistani-web-naskh-fonts nafees-riqa-fonts nafees-web-naskh-fonts nafees-nastaleeq-fonts nafees-tehreer-naskh-fonts nafees-pakistani-naskh-fonts nafees-naskh-fonts, the Urdu font choice in Debian is limited to Nafees Web Naskh only and apparently the problem does not occur. However, I think, it needs a bit more testing with other Nafees font variants. I will try manually installing fonts in Debian at the weekend and let you know the results. In the meanwhile, if LO lands to Fedora updates repository, I will recheck and share the results. A screenshot of Nafees Web Naskh in Debian 8.2 is available below. http://postimg.org/image/3ndjanzxr/full/ Please let me know if you need more information.
You can also use this method to test right away: https://wiki.documentfoundation.org/Installing_in_parallel/Linux
I checked with LibreOffice 5 in Fedora 23 Beta Virtual machine and here are the results. http://postimg.org/image/5g86a3z1r/full/ It appears that the problem is with one font (Nafees Nastaleeq). I am not sure if the problematic font is bitmap or scalable. I have contacted the author of the font and waiting for his response.
(In reply to MalangBadshah from comment #4) > I checked with LibreOffice 5 in Fedora 23 Beta Virtual machine and here are > the results. Thanks for the follow-up! > It appears that the problem is with one font (Nafees Nastaleeq). I am not > sure if the problematic font is bitmap or scalable. I have contacted the > author of the font and waiting for his response. Sounds good. Status -> NEEDINFO Please change the status back to UNCONFIRMED once you have info from the font author. Thanks!
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Sun, 11 Sep 2016 21:43:24 +0200
Created attachment 127265 [details] font_name_size_garbled_image
I contacted the author but unfortunately didn't receive any feedback. I am inclined to the opinion that 'nafees-nastaleeq' is a bitmap font while 'jameel-noori-nastaleeq' seems to be an svg based font. Another related issue is the garbled font name and size as shown in the attached image.
I could swear there was a similar issue 2-3 months ago about font names overwriting previous entries in font selection combo box, but can't find it. Likely it was also UNCONFIRMED, too, so no big deal.
(In reply to Aron Budea from comment #9) > I could swear there was a similar issue 2-3 months ago about font names > overwriting previous entries in font selection combo box, but can't find it. > Likely it was also UNCONFIRMED, too, so no big deal. Maybe bug 100398?
(In reply to Buovjaga from comment #10) > Maybe bug 100398? I'm thinking of a different one (I can recall seeing a screenshot), but this looks like the same issue, too.
Found the garbled font name issues I was thinking of: bug 99134 and bug 99736. That bug should be fixed in recent releases (5.2).
Malang: can you test with LibreOffice 5.2.1? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED DUPLICATE of 99134, if the problem went away.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170328
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170502