Until version 18.104.22.168, the OpenType ligatures and context alternatives worked quite fine. However, in 22.214.171.124, OpenType ligatures and context alternatives do not work at all anymore.
For me, this is a major problem since I am working a lot with old German fonts that heavily rely on theses features.
Correction: Ir stopped working in 5.1.x, it worked in 5.0.x.
What is the state of OpenGL rendering on your Please copy and paste details from the Help -> About LibreOffice dialog
If enabled, any improvement if you disable from Tools -> Options -> View "Use OpenGL for all rendering (on restart)"?
Please copy and paste details from the Help -> About LibreOffice dialog and let us know which build of Windows you are working on.
Windows 7 SP1 x64
Version: 126.96.36.199 (x64)
CPU-Threads: 16; BS-Version: Windows 6.1; UI-Render: GL;
Gebietsschema: de-DE (de_DE)
Turning on an off OpenGL and restarting does not change anything.
OK, thanks, one more question. Which fonts are you using that contain the ligatures?
I am mainly using proprietary fonts emulating old-style German lettering and handwriting created by http://www.fraktur.biz/. But I guess, also other OpenType smart fonts will cause issues.
duplicate of bug 66916?
(In reply to raal from comment #6)
> duplicate of bug 66916?
Not sure, as it used to work in 5.0.x, apart from a strange detail problem. But basically, it worked.
Cn you attach test case? If it worked in 5.0, we can bibisect it.
The problem ia that the font I am using is proprietary, so I cannot attach it. However, maybe you can verify first, if OpenType ligatures and context alternatives work at all in 5.1.x. Somehow, ir does not look like it.
(In reply to Patrick Schönbach from comment #9)
> The problem ia that the font I am using is proprietary, so I cannot attach
> it. However, maybe you can verify first, if OpenType ligatures and context
> alternatives work at all in 5.1.x. Somehow, ir does not look like it.
We are very busy with testing, so would appreciate, if you checked it and created a test case with non-proprietary fonts :)
(In reply to Buovjaga from comment #10)
> (In reply to Patrick Schönbach from comment #9)
> > The problem ia that the font I am using is proprietary, so I cannot attach
> > it. However, maybe you can verify first, if OpenType ligatures and context
> > alternatives work at all in 5.1.x. Somehow, ir does not look like it.
> We are very busy with testing, so would appreciate, if you checked it and
> created a test case with non-proprietary fonts :)
Ok. Could you maybe name a suitable OpenType font I could use?
(In reply to Patrick Schönbach from comment #11)
> Ok. Could you maybe name a suitable OpenType font I could use?
Not off the top of my head. Needs searching.
Created attachment 124958 [details]
Font for test case
Created attachment 124959 [details]
(In reply to Patrick Schönbach from comment #14)
> Created attachment 124959 [details]
> Test case
For me, the "eer" is joined. I have to test on Windows later.
64-bit, KDE Plasma 5
Build ID: 188.8.131.52 Arch Linux build-1
CPU Threads: 8; OS Version: Linux 4.5; UI Render: default;
Locale: fi-FI (fi_FI.UTF-8)
For me, on Windows, nothing is joined on the latest 5.1.x version on Windows.
Created attachment 124983 [details]
printscreen from 5.2
I can confirm with Version: 184.108.40.206.alpha1+
Build ID: e76d458422b0f0f713cc17bf47ca94c33ac570a7
CPU Threads: 1; OS Version: Windows 6.1; UI Render: default;
TinderBox: Win-x86@39, Branch:master, Time: 2016-05-03_06:32:27
This seems to have begun at the below commit.
Adding Cc: to Tor Lillqvist ; Could you possibly take a look at this one?
bf46c56d1ea254c094510b7dd92d8d3d14b7a475 is the first bad commit
Author: Norbert Thiebaud <firstname.lastname@example.org>
Date: Fri Jan 22 03:32:58 2016 -0800
author Tor Lillqvist <email@example.com> 2016-01-07 13:05:58 (GMT)
committer Tor Lillqvist <firstname.lastname@example.org> 2016-01-21 10:04:04 (GMT)
commit 4622689fad7ddff72cd08da9611ccfacdb0aa7bd (patch)
parent 88b458d55dc1f56e13bbf34aa7c6758e13707fa1 (diff)
tdf#96420: Re-introduce SimpleWinLayout
I can also reproduce this bug on Windows 10
Version: 220.127.116.11 (x64)
Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default;
Locale: zh-CN (zh_CN)
After I installed FreeSerif font, input many “f”, no ligature appeared.
*** Bug 99812 has been marked as a duplicate of this bug. ***
*** Bug 102191 has been marked as a duplicate of this bug. ***
I think this should fixed in Version: 18.104.22.168.alpha1+
did you effectively test this in 5.3.x?
thanks for confirming this has been FIXED