Bug 84518 - Unable to select by character in formula bar due to possible ligature substitution
Summary: Unable to select by character in formula bar due to possible ligature substit...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-30 16:24 UTC by js54434
Modified: 2014-10-14 22:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description js54434 2014-09-30 16:24:17 UTC
When I type in something with "fi" in the formula bar, the cursor can't go between the "f" and the "i". When moving the cursor with arrow keys, the cursor remains on one side or the other of the "fi" when it should be in the middle. Sometimes this means you select more letters than it appears if you click and drag then copy and paste text from the formula bar.
Comment 1 Owen Genat (retired) 2014-10-05 06:46:42 UTC
This is presumably a Calc problem (formula bar?), thus component set to Spreadsheet. It sounds like a ligature substitution issue (f+i->fi), but I am unable to reproduce the problem under GNU/Linux using v4.3.2.2. Possibly a MacOS build or MacOS font issue. Summary edited for clarity.

Please confirm that my adjustment of the component and summary are accurate. What font are the problem entries set in? Status set to NEEDINFO. Please set back to UNCONFIRMED once the requested information is provided. Thanks.
Comment 2 js54434 2014-10-06 23:04:26 UTC
The font used was the default font, Liberation Sans. This was in Calc.
Comment 3 Alex Thurgood 2014-10-14 15:16:58 UTC
Confirming, pretty annoying that, seems like an automatic ligature is created

LO 4322 OSX 10.9.5
Comment 4 Alex Thurgood 2014-10-14 15:18:02 UTC
reproduced in 4142
Comment 5 Alex Thurgood 2014-10-14 15:22:06 UTC
Worksforme in 

Version: 4.4.0.0.alpha0+
Build ID: 7dc6c9af4ba313f054331f5130470d83d875bc16

master daily build

As I don't know which piece of code changed, or whether it will be backported,
setting as resolved worksforme
Comment 6 Alex Thurgood 2014-10-14 15:24:14 UTC
@js54434 : please try a latest daily dev build. If it still doesn't work for you with a fresh user profile, re-open.
Comment 7 js54434 2014-10-14 15:38:21 UTC
I just tried the last development build I could find for OS X 10.7, 

Version: 4.3.3.0.0+
Build ID: 50eac342603ca08d808f53dc9a32bb9d1dfba372

and the problem still exists.
Comment 8 Alex Thurgood 2014-10-14 15:41:03 UTC
4333 is not a dev build, but the future 433 release.
Comment 9 Alex Thurgood 2014-10-14 15:42:15 UTC
(In reply to js54434 from comment #7)
> I just tried the last development build I could find for OS X 10.7, 
> 
> Version: 4.3.3.0.0+
> Build ID: 50eac342603ca08d808f53dc9a32bb9d1dfba372
> 
> and the problem still exists.

http://dev-builds.libreoffice.org/daily/master/
Comment 10 Alex Thurgood 2014-10-14 15:46:05 UTC
If those master builds don't work with 10.7, then I'm afraid you are stuck with your problem and it will never be resolved, unless by chance someone finds the code code and agrees to backport it to a stable version that runs on 10.7
Comment 11 Alex Thurgood 2014-10-14 15:48:50 UTC
(In reply to js54434 from comment #7)
> I just tried the last development build I could find for OS X 10.7, 
> 
> Version: 4.3.3.0.0+
> Build ID: 50eac342603ca08d808f53dc9a32bb9d1dfba372
> 
> and the problem still exists.

In fact, latest nightly dev build is here
http://dev-builds.libreoffice.org/daily/master/MacOSX-10.9-x86_64@53/2014-10-14_02.40.20/master_nightlies~2014-10-14_02.40.20_LibreOfficeDev_4.4.0.0.alpha0_MacOS_x86-64.dmg
Comment 12 js54434 2014-10-14 22:53:56 UTC
(In reply to Alex Thurgood from comment #10)
> If those master builds don't work with 10.7, then I'm afraid you are stuck
> with your problem and it will never be resolved, unless by chance someone
> finds the code code and agrees to backport it to a stable version that runs
> on 10.7

This appears to be the case. In any event, I'm glad the problem seems to be fixed in future versions.