Created attachment 65286 [details]
Test file (its text displayed as "Thhittt" in LibO 3.6, and "Thitt" in LibO 3.4.2
The attached file contains the text "Thitt" formatted by the Graphite font Linux Libertine G, but displayed as "Thhittt" in Writer 3.6. It seems, it is a regression in the Graphite ligature handling, because "Thitt" has been displayed by LibO 3.4.2 correctly.
Examining the content.xml, there are some character formatting boundaries here, with explicit style definitions:
<text:p text:style-name="P1"><text:span text:style-name="T1">T</text:span>hit<text:span text:style-name="T1">t</text:span></text:p></text:p>
Testing (part of the original bug report from Kim Bastin:
"Running LibreOffice 3.6.0 rc4 under WinXP SP3, with fonts Linux Libertine G and Linux Biolinum G, I see the following problem affecting ligatures:
In Writer, type
Save the file (this is essential)! Place cursor before h and type T. I get
(Note Th is a ligature.)
Type hat again, save file, place cursor before t and type f. I get
(Note ft is a ligature.)
Save, then place cursor before f and type f.
(!!). (ffi and fi are ligatures.)
The bug only occurs with characters that were typed before the file was last saved.
The extra characters are not ‘real’: if you delete one h in Thhat, both h’s disappear. So it’s a display bug, but a persistent one: if you close the file, close Writer, relaunch Writer and open the file again, the ‘ghost’ letters still appear."
Confirmed by me on Linux/LibreOffice 126.96.36.199 (original bug reporter: Kim Bastin).
There is no problem with LibO 188.8.131.52, yet.
Still in LibO 184.108.40.206
Still in LibO 3.6.2 rc1
And in LO 220.127.116.11.
Still broken in LO 3.6.3.
You are welcome to keep the tap dripping, but the plumber is not going to magically turn up and fix this for a while. I would suggest you try the tap again for Libo 3.8, but even then I make no guarantees.
Please be aware that you do have a simple workaround. Also the whole problem is the character formatting boundaries. This is a relatively rare problem with a simple workaround. If you have a real use case issue rather than 'hey I found something funky', then please add it to this bug.
Especially the likely not independent bug 52540 is a serious regression in Graphite support, but this is also an annoying problem, also in simple text editing (without document saving). Thanks for your feedbacks.
It is not a 'rare' problem. Do you know how much efforts it take to clean out all these dummy styles?
*** This bug has been marked as a duplicate of bug 52028 ***
Nothing in the description of bug 52028 matches the behaviour of the present bug.
The most common source of ligatures in modern texts are combining diacritic in "good" fonts. So it would be nice to have someone actually investigate this trivial bug.
I just downloaded this test file with libo 18.104.22.168 as distributed with Ubuntu Precise, opened it. It rendered as Thitt, complete with a ligature. I saved as .fodt and the double span had gone away. So is there still a bug? I concur that this is a side effect of bug 52028. All the other tests in the bug description also worked just fine.
I can’t comment on LO 22.214.171.124 in Ubuntu. The bug is still there in LO 126.96.36.199 under Windows XP. Saving as .fodt is not an option in this version, so I can’t comment on that either.
Checked in 4.0.2: this regression results bad character or ligature duplication (both in ODF, and PDF export). In my test, not only the previously saved, but all text could have problem with a simple text modification.
Workaround: delete and rewrite the text with the problem, or select it, and clear direct formatting by Ctrl-M.
The workaround doesn't work for the similar problem at automatic hyphenation (Bug 52540)
The serious text modification has been fixed, see Bug 52540, but for the missing ligatures need a new issue.