Bug 138869 - Writer kerning not applied across edits within the same word
Summary: Writer kerning not applied across edits within the same word
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.0.beta1+
Hardware: All Windows (All)
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-12 20:22 UTC by dev
Modified: 2022-12-11 03:21 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Kerning - single typed block (9.33 KB, image/png)
2020-12-12 20:23 UTC, dev
Details
Kerning - across edits (9.51 KB, image/png)
2020-12-12 20:24 UTC, dev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dev 2020-12-12 20:22:46 UTC
Description:
If a word comprises letters that were typed at different times, the segments appear to be kerned separately and then composed for rendering, resulting in kerning NOT being applied between segments (of the same word). Screenshots attached.

Steps to Reproduce:
1. For an existing letter pair that is usually adjusted by kerning, overtype the second letter with the same letter.

Actual Results:
Unadjusted (large) inter-letter spacing is used between the letters. This can also be seen in a generated PDF.

Expected Results:
Letter spacing should be kerned as usual.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Attachments: small screenshots show the inconsistency of the word "We".

As a workaround, I can type the whole word again, in place of the misaligned word.

This bug might be due to the display being composed from pre-kerned strings of text, whereas kerning should be applied after composing the text.
Comment 1 dev 2020-12-12 20:23:54 UTC
Created attachment 168115 [details]
Kerning - single typed block
Comment 2 dev 2020-12-12 20:24:47 UTC
Created attachment 168116 [details]
Kerning - across edits
Comment 3 dev 2020-12-20 01:53:41 UTC
Same occurs for ligatures, as occurs for kerning.
Comment 4 pavlog 2020-12-28 19:41:58 UTC
Can't reproduce it in 

Version: 7.2.0.0.alpha0+ (x64)
Build ID: ecb916667b633f8647790e040226b093760e6cfe
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 5 Natali Eroshenko 2021-08-12 13:47:26 UTC
don`t repro in Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: en-US (ru_RU); UI: en-US
Calc: threaded
Comment 6 Buovjaga 2022-05-13 11:06:45 UTC
There were changes made to kerning a while ago. Could you test with a daily build Win-x86_64@tb77-TDF from https://dev-builds.libreoffice.org/daily/master/current.html ? It installs separately.

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 7 QA Administrators 2022-11-10 04:03:25 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2022-12-11 03:21:04 UTC
Dear dev,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp