Bug 90788

Summary: An irritating bug with a font
Product: LibreOffice Reporter: jlbraga
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: minor CC: aron.budea, fitojb, ilmari.lauhakangas
Priority: medium    
Version: 4.4.1.2 release   
Hardware: Other   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: there — it happened again

Description jlbraga 2015-04-22 19:31:58 UTC
Hi.

When using a free font named Racing Sans, sometimes I want to write the word "Velocity" in a title, and when I press the "c" key, it makes a paragraph without showing the "c". However, it considers the "c" to be there. Sometimes it only happens when I set its size to 45,5 so the title I want to write fits the whole size of the screen, sometimes I can enter the words the right way and when I enter the file, the text is with a paragraph instead of a "c", but when I donwzize it, the "c" appears...and there was a time when I enter the file and the letters were all out of place, and ones behind others...

Is the problem from the font or from Write? I don't know if in any of the other programs the same thing happens...
Comment 1 Adolfo Jayme Barrientos 2015-04-22 21:26:52 UTC
Can you attach a screenshot?
Comment 2 jlbraga 2015-04-23 17:58:42 UTC
Created attachment 115040 [details]
there — it happened again

It was properly written, thenb I opened the file and it had the bug again.
Comment 3 Buovjaga 2015-04-27 18:52:59 UTC
Downloaded font from here: http://www.impallari.com/projects/update/53

There *is* something fishy with that c going on.

This happened only with 4.4, not with 5.0:

Was at zoom level 120%.
Started writing Velocity with font size 45,5.
After I hit i, the whole word turned invisible.
Any other zoom level brought it back.
It didn't break the word like in attachment 115040 [details]
It didn't matter, if paragraph was centered or not.
After save & reload, the word was visible even at 120% zoom.

Tried in GIMP, Inkscape - no such effect.

To the original reporter: can you try with 5.0 alpha? It installs separately and will not mess with your user profile: http://dev-builds.libreoffice.org/daily/master/Win-x86@39/

I'll set to NEEDINFO, while we wait for more info & experiences.

Tested on:
Win 7 Pro 64-bit, Version: 4.4.3.1
Build ID: b2f347f2ac68821efc00b6f1793cda90af748118
Locale: fi_FI

Version: 5.0.0.0.alpha1+ (x64)
Build ID: f0edb677f09ad338e22ac3b5d91497b4479e0b3c
TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-27_01:54:20
Locale: fi_FI
Comment 4 Aron Budea 2015-04-30 04:49:10 UTC
I also tried this, and here's my experience. At first it was basically the same as Beluga's.

After further tries:

-"c" followed by "i" is essentially what brings forth the weird behavior,

-in the simplest form, changing font in an empty document to Racing Sans One, and writing "ci" makes the text disappear,

-this produces a result very similar to what is described in the bug report: if a single "a" is written with the starting font in an empty document, and followed by "ci" in Racing Sans One, then it breaks into three lines with one character each ("c" becomes invisible, but it's there),

-there is some kind of variance and "memory" involved, because sometimes after trying different things, the bug could not be reproduced for a while even after restarting Writer, but then later appeared again,
(some of those tries involved: selecting font via dropdown, typing in font name with input help, changing font size, switching spellcheck language, all with frequent restarts of Writer application).


This was done with 4.4.2.2 release version on Windows 7.
I also could _not_ reproduce it with a recent 5.0 debug build.
Comment 5 Buovjaga 2015-04-30 08:03:44 UTC
Thanks for testing, Aron.

Well, even though this works in 5.0, let's set to NEW anyways, so that this doesn't rot in NEEDINFO forever.

Severity is not major, though: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
Comment 6 Aron Budea 2016-08-11 23:11:10 UTC
This seems to have been fixed since then. Please test with current LibreOffice versions (5.1.5 or 5.2.0).