Bug 47230 - "Fonts > Apply replacement table" does not adjust width of characters
Summary: "Fonts > Apply replacement table" does not adjust width of characters
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
(earliest affected)
3.5.0 release
Hardware: Other All
: low minor
Assignee: Not Assigned
Keywords: needsDevEval
Depends on:
Blocks: Font-Substitution
  Show dependency treegraph
Reported: 2012-03-12 04:40 UTC by Harald Koester
Modified: 2021-01-24 04:05 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Screen shot with bug. (52.20 KB, image/png)
2012-03-12 04:40 UTC, Harald Koester

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2012-03-12 04:40:05 UTC
Created attachment 58309 [details]
Screen shot with bug.

Problem description: 

If you use the Option "LibreOffice > Fonts > Apply replacement table" in order to replace fonts the character width is not adjusted to the replacement fonts. In order to reproduce the bug do:
[1] Start with no font replacements and open a new text document,
[2] Choose a font with a small character width (e.g. Linux Libertine G) and type in some text,
[3] Replace this font by a font with broad characters (e.G. Engravers MT): Tools > Options... > LibreOffice > Fonts > Apply replacement table. Result see Attachment.

Problem also exists if you print the document.

But with:
[1] Start with no font replacements and open a new text document,
[2] Replace a font with small characters (e.g. Linux Libertine G) by a font with broad characters (e.G. Engravers MT): Tools > Options... > LibreOffice > Fonts > Apply replacement table,
[3] Choose the font with small characters and type in some text,
the result is OK!

Problem also observed with Draw. (In my system there is a problem with Linux Libertine G in Draw. Perhaps it is better to use another font.)

Problem observed with Version 3.4.5 and 3.5.0.

See also bug 43185.
Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20120216 Firefox/3.6.27
Comment 1 bfoman (inactive) 2012-08-09 10:48:32 UTC
Confirmed with:
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit

Result as on screenshot - see attachment 58309 [details].
Comment 2 Joel Madero 2012-10-19 17:53:31 UTC
I can also confirm this:

Bodhi Linux

I believe that this is a duplicate -- I vaguely remember confirming something similar a few weeks back. I'm unable to find the other bug but if someone happens to stumble across the other one, please mark one of them as a duplicate of the other. 

Marking as NEW and prioritizing:

Minor: Makes creating high quality work harder under certain circumstances and/or forces users not to use certain features

Low: Not a very common feature at all, most users have no idea this feature even exists. Impact on users probably low because of this.

ProposedEasyHack added

Thanks for reporting.
Comment 3 Joel Madero 2014-02-27 23:03:31 UTC
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.

Thank you and apologies for the noise
Comment 4 Robinson Tryon (qubit) 2015-12-13 11:20:41 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2017-01-03 19:48:48 UTC Comment hidden (obsolete)
Comment 6 Harald Koester 2017-12-19 22:37:45 UTC
Checked with version 5.4.3 (64 bit, Win 10).

With the procedure of the original description it works for me now, but if you go on with:

[4] Remove the font replacement: ... Options > Fonts > uncheck "Apply replacement table", then OK. Nothing changed. The replacement is not removed. Expected: Removal of replacement.

[5] Insert one character into the text. Now the replacement is removed, but the distance between the characters is not adapted to the changed font. Expected: Correct distance between characters.
Comment 7 Harald Koester 2019-01-24 09:36:22 UTC
Bug according comment 6 still exists with version 6.1.4. (64 bit, Win 10)
Comment 8 QA Administrators 2021-01-24 04:05:48 UTC
Dear Harald Koester,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team