Bug 129092 - The font Times New Roman:dlig does not create ligatures
Summary: The font Times New Roman:dlig does not create ligatures
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.4.0.0.alpha0+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Font-Rendering
  Show dependency treegraph
 
Reported: 2019-11-29 02:34 UTC by mkassler
Modified: 2021-08-01 02:11 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Evidence of ligature problem (20.85 KB, application/vnd.oasis.opendocument.text)
2019-12-28 22:50 UTC, mkassler
Details
Screenshot with ligatures (138.57 KB, image/jpeg)
2019-12-29 09:58 UTC, Dieter
Details
Page showing Writer's failure to create ligatures (21.96 KB, application/vnd.oasis.opendocument.text)
2019-12-29 21:42 UTC, mkassler
Details
.pdf showing TimesNewRoman:dlig does not work (97.48 KB, application/pdf)
2019-12-31 00:24 UTC, mkassler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mkassler 2019-11-29 02:34:23 UTC
I am not sure whether this feature is currently supported; if not, I'd like it to be. Although I have changed my default font to Times New Roman:dlig when I type 'fi', 'fl', etc. no ligatures are automatically created. An AskLibreOffice comment suggests it should work, but I can't get it to work.
Comment 1 Dieter 2019-12-28 18:17:50 UTC
(In reply to mkassler from comment #0)
> An AskLibreOffice comment suggests it should work, but I can't get it to work.

Works for me in

Version: 6.5.0.0.alpha0+ (x64)
Build ID: e26d89371f0e4f41476c9a99be01d98dedb76776
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-GB
Calc: threaded

and also in

Version: 6.3.4.2 (x64)
Build-ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded


Please add screenshot or PDF-Print of your result
Comment 2 mkassler 2019-12-28 22:50:48 UTC
Created attachment 156823 [details]
Evidence of ligature problem
Comment 3 Dieter 2019-12-29 09:58:04 UTC
Created attachment 156831 [details]
Screenshot with ligatures

When I open your document, everythings looks right to me.
Comment 4 mkassler 2019-12-29 21:42:21 UTC
Created attachment 156839 [details]
Page showing Writer's failure to create ligatures
Comment 5 Dieter 2019-12-30 10:14:45 UTC
Again, I can't see a problem in your document. Please add a PDF-Print or a screenshot, so I can see the difference with screenshot in comment 3

=> NEEDINFO
Comment 6 mkassler 2019-12-31 00:24:06 UTC
Created attachment 156859 [details]
.pdf showing TimesNewRoman:dlig does not work
Comment 7 QA Administrators 2019-12-31 03:28:13 UTC Comment hidden (obsolete)
Comment 8 Dieter 2019-12-31 07:46:58 UTC
In the PDF I can see the difference in your document, but I can't reproduce it. Perhaps somebody else can help.

Additional information: When I open your document, I always get the following warning: "This document contains macros.Macros may contain viruses. Execution of macros is disabled due to the current macro security setting in Tools - Options - LibreOfficeDev - Security. Therefore, some functionality may not be available."

I don't know, if you get a better result in a document without a macro.

Are you still using LO 6.4.0.0? Please paste inormations from Help => About LibreOffice
Comment 9 mkassler 2019-12-31 08:22:41 UTC
I am using:

Version: 6.4.0.1 (x64)
Build ID: 1b6477b31f0334bd8620a96f0aeeb449b587be9f
CPU threads: 8; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; 
Locale: en-AU (en_AU); UI-Language: en-GB
Calc: CL
Comment 10 Buovjaga 2020-04-29 18:18:25 UTC
(In reply to mkassler from comment #9)
> I am using:
> 
> Version: 6.4.0.1 (x64)
> Build ID: 1b6477b31f0334bd8620a96f0aeeb449b587be9f
> CPU threads: 8; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; 
> Locale: en-AU (en_AU); UI-Language: en-GB
> Calc: CL

Try turning this off: Tools - Options - LibreOffice - View - Use OpenGL for all rendering
Comment 11 mkassler 2020-04-29 22:52:34 UTC
Use OpenGL is off.
Comment 12 QA Administrators 2020-04-30 03:57:57 UTC Comment hidden (obsolete)
Comment 13 Buovjaga 2020-04-30 16:54:07 UTC
(In reply to mkassler from comment #4)
> Created attachment 156839 [details]
> Page showing Writer's failure to create ligatures

No problem here

Version: 7.0.0.0.alpha0+ (x64)Build ID: 5063669a17538ea353e34ab0990363399d34f4f4CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: fi-FI (fi_FI); UI-Language: en-USCalc: threaded
Comment 14 Xisco Faulí 2020-06-17 15:54:28 UTC
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 15 mkassler 2020-06-18 05:39:52 UTC
This still does not work. However, the desired behaviour can be obtained by using Autocorrect to replace .*.fi.* with the 'fi' ligature, and similarly for 'fl'.
Comment 16 Dieter 2020-06-18 05:59:54 UTC
(In reply to mkassler from comment #15)
> This still does not work.

Please add informations from Help => About LibreOffice
Comment 18 QA Administrators 2020-06-19 03:51:50 UTC Comment hidden (obsolete)
Comment 19 Stéphane Guillou (stragu) 2021-07-31 11:28:28 UTC
I can't reproduce either on:

Version: 7.0.6.2 (x64)
Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: en-AU (en_AU); UI: en-US
Calc: threaded

or:

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 67f2a99229101757af4f40118f4d3c83ba38648b
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: en-AU (en_AU); UI: en-US
Calc: threaded

mkassler, if you still see the issue in a recent version of LibreOffice, could you please share the whole of the version information that is in Help - About? There should be a button to copy all the information, so you can paste it here and we can learn more about what operating system version and system settings you use. It might give us more hints.
Comment 20 mkassler 2021-07-31 23:32:18 UTC
I have got around this problem by using AutoCorrect to replace 'fi' with a single-character ligature, etc.