Bug 94347 - characters "fh" merged into a ligature using font Calibri
Summary: characters "fh" merged into a ligature using font Calibri
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.2.6.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-18 20:36 UTC by James
Modified: 2015-09-19 21:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James 2015-09-18 20:36:12 UTC 
When I use the font Calibri the characters "fh" merged into a ligature. This causes numerous bugs:

1. I cannot use the cursor to select the "h" character without automatically selecting the "f" character and the character before the f if it is a non-space character.

2. Positioning the cursor after the h and hitting backspace deletes the f and positions the cursor before the h.

3. Positioning the cursor after the h and hitting left arrow moves the cursor to before the f.


Has this been fixed?  If not, cannot I suppress the use of ligatures?  If ligature use is implemented this badly, it should not be implemented at all.
Comment 1 tommy27 2015-09-19 05:51:55 UTC 
please retest with latest 5.0.1.2 release.
the 4.2.6.3 release you are using is obsolete and no longer supported.

I set status to NEEDINFO waiting for user feedback
Comment 2 tommy27 2015-09-19 05:52:13 UTC 
... and tell your O/S
Comment 3 Adolfo Jayme Barrientos 2015-09-19 21:05:03 UTC 
I can’t reproduce what you indicate. I’ve tested in both Windows 10 and Ubuntu 15.10, using Calibri Regular version 6.11 and LibreOffice 5.0.2.
Comment 4 James 2015-09-19 21:33:06 UTC 
I'm using Scientific Linux 7.1.  I actually just quickly downloaded the 5.0.1 release and both this bug and the other bug I just reported are still there.

Thanks for your help, but I'm afraid I'm not going to be able to provide you with the information that you need in order to debug and fix this bug.  So I'm just going to close this bug as resolved and move on. Regards.