Bug 366411

Summary: Font Viewer reverses and disconnects Arabic letters
Product: [Applications] kfontview Reporter: Samir Nassar <samir>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: REPORTED ---    
Severity: normal CC: amgadelsaiegh, mikewortin, samir
Priority: NOR    
Version: 5.18.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=343289
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Image of Font Viewer showing the problem compared to proper display.
Hebrew screenshot

Description Samir Nassar 2016-08-04 15:35:00 UTC
When viewing an Arabic fonts Font Viewer doesn't properly handle the display of Arabic fonts. The writing is displayed left-to-right instead of right-to-left and the letters are not properly connected.

This happens even when the preview text is changed to an Arabic sentence.

Reproducible: Always

Steps to Reproduce:
1. View an Arabic font.
2. Change the preview text to Arabic

Actual Results:  
It displayes the preview text left-to-right and disconnected.

Expected Results:  
It should display the preview text right-to-left and properly connected.
Comment 1 Samir Nassar 2016-08-04 15:37:21 UTC
Created attachment 100453 [details]
Image of Font Viewer showing the problem compared to proper display.
Comment 2 Mike Wortin 2020-03-11 17:18:23 UTC
Also valid for Hebrew on latest stable KDE release (Arch). The order of the Hebrew sentence should be reversed and ideally it has to be aligned to the left.
Comment 3 Mike Wortin 2020-03-11 17:18:58 UTC
Created attachment 126729 [details]
Hebrew screenshot
Comment 4 Christoph Feck 2020-04-09 21:29:54 UTC
I cannot read the screenshots, but do they show actual text, or just a list of glyphs as in the Latin section above? As far as I know, the shaping depends on context, and ideally the font display should show all possible shapes, not just a sample text. Does selecting a different Unicode block help, e.g. Arabic Presentation Forms-A or -B?
Comment 5 amgad elsaiegh 2022-08-21 19:51:13 UTC
2 years passed and issue is not solved!