Bug 97860 - misplaced diacritics of Persian language
Summary: misplaced diacritics of Persian language
Status: RESOLVED DUPLICATE of bug 97171
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2016-02-14 18:57 UTC by Nima Az
Modified: 2016-02-22 16:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
bug screenshot 1 (107.03 KB, image/jpeg)
2016-02-19 07:41 UTC, Nima Az
Details
bug screenshot 2 (103.02 KB, image/jpeg)
2016-02-19 07:46 UTC, Nima Az
Details
bug screenshot 3 (105.98 KB, image/jpeg)
2016-02-19 07:47 UTC, Nima Az
Details
sample document (8.24 KB, application/vnd.oasis.opendocument.text)
2016-02-19 07:53 UTC, Nima Az
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nima Az 2016-02-14 18:57:35 UTC
Hi,

In this most recent version the diacritic characters of the Persian language appear misplaced.

The vowel diacritics that need to go above the character (like ُ and َ) are displayed below the character and that one that normally should go below the character (ِ) is displayed above the character.  Changing the font does solve this problem to some extent but I am required to used a specific font and by the way didn't have this problem in earlier versions.

Hope this gets fixed soon as I am doing my master's thesis and have a limited time, hence the critical severity.  I'm ready to provide further information if it may be needed.

Thanks.
Comment 1 raal 2016-02-15 21:29:23 UTC
Hello Nima,

Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Thank you
Comment 2 Nima Az 2016-02-19 07:41:27 UTC
Created attachment 122787 [details]
bug screenshot 1
Comment 3 Nima Az 2016-02-19 07:46:28 UTC
Created attachment 122788 [details]
bug screenshot 2
Comment 4 Nima Az 2016-02-19 07:47:14 UTC
Created attachment 122789 [details]
bug screenshot 3
Comment 5 Nima Az 2016-02-19 07:53:23 UTC
Created attachment 122790 [details]
sample document
Comment 6 Nima Az 2016-02-19 07:54:55 UTC
Hi again,

I have attached a sample document and three screenshots.  The "1.jpg" screenshot shows how the text must look like and that's how it's displayed in the previous release (a 5.0.x.x release).  "2.jpg" shows how it looks in 5.1.0.3.

As I said, this is somewhat dependent on the font.  When I use Tahoma, the text displays somewhat correctly.  "3.jpg" shows this case.

Hope it helps.

Best wishes,
Nima


(In reply to raal from comment #1)
> Hello Nima,
> 
> Thank you for filing the bug. Please send us a sample document, as this
> makes it easier for us to verify the bug. 
> I have set the bug's status to 'NEEDINFO', so please do change it back to
> 'UNCONFIRMED' once you have attached a document.
> (Please note that the attachment will be public, remove any sensitive
> information before attaching it.)
> How can I eliminate confidential data from a sample document?
> https://wiki.documentfoundation.org/QA/
> FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
> Thank you
Comment 7 Buovjaga 2016-02-21 15:43:09 UTC
Nima: does it help, if you disable Tools - Options - LibO - View - Use OpenGL for all rendering and restart LibO?
Comment 8 Nima Az 2016-02-22 15:59:49 UTC
Hi Beluga,

Yes, it works.

(In reply to Beluga from comment #7)
> Nima: does it help, if you disable Tools - Options - LibO - View - Use
> OpenGL for all rendering and restart LibO?
Comment 9 Buovjaga 2016-02-22 16:13:55 UTC
Ok, it seems to be the same as bug 97171, even though the original description was much more specific.

*** This bug has been marked as a duplicate of bug 97171 ***