Bug 124834 - On Windows Writer types backwards with IFAOGrec-Unicode font
Summary: On Windows Writer types backwards with IFAOGrec-Unicode font
Status: RESOLVED DUPLICATE of bug 121486
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3 all versions
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-19 02:49 UTC by Jeremy
Modified: 2019-09-02 09:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Brief video of the problem (308.99 KB, video/quicktime)
2019-04-19 02:51 UTC, Jeremy
Details
The font in question (IFAOGrec-Unicode) (521.89 KB, application/x-font-ttf)
2019-04-19 02:52 UTC, Jeremy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy 2019-04-19 02:49:37 UTC
Description:
When using the IFAOGrec-Unicode font in Writer and Calc on Windows, typing goes backwards from the cursor.  This font works as expected in all other programs I have tried and it works fine in Writer and Calc on Linux and Mac.  

Steps to Reproduce:
1.Install IFAOGrec-Unicode font on Windows.
2.Open Writer and change to IFAOGrec-Unicode font.
3.Begin typing.  It will appear backwards from the cursor

Actual Results:
The text being typed will appear backwards from the cursor going to the left off the screen.

Expected Results:
The typing appears normally advancing toward the right as it is typed.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Comment 1 Jeremy 2019-04-19 02:51:08 UTC
Created attachment 150868 [details]
Brief video of the problem
Comment 2 Jeremy 2019-04-19 02:52:16 UTC
Created attachment 150869 [details]
The font in question (IFAOGrec-Unicode)
Comment 3 Jeremy 2019-04-19 05:13:48 UTC
This problem first shows up in 5.3.0.1.  It works fine in 5.2.7.2.  I believe harfbuzz was first used in version 5.3.
Comment 4 ⁨خالد حسني⁩ 2019-08-21 21:25:32 UTC

*** This bug has been marked as a duplicate of bug 121486 ***
Comment 5 Jeremy 2019-08-22 00:24:54 UTC
Thank you so much! I can confirm the fix to the other bug solves this issue.  Do you happen to know what the problem in the font is?  If so, I'd be glad to pass that on to the font maker.  In any case, thanks!
Comment 6 ⁨خالد حسني⁩ 2019-08-22 07:59:33 UTC
(In reply to Jeremy from comment #5)
> Thank you so much! I can confirm the fix to the other bug solves this issue.
> Do you happen to know what the problem in the font is?  If so, I'd be glad
> to pass that on to the font maker.  In any case, thanks!

The xAvgCharWidth in the OS/2 table (https://docs.microsoft.com/en-us/typography/opentype/spec/os2#xavgcharwidth) is negative, which makes no much sense as individual glyph widths can’t be negative. Looks like a faulty font generation tool.