Bug 52248 - Graphite font: some punctuations between two non-breakable spaces disappear
Summary: Graphite font: some punctuations between two non-breakable spaces disappear
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
3.5.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 21:52 UTC by Olivier R.
Modified: 2016-01-20 05:01 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Test file (10.40 KB, application/vnd.oasis.opendocument.text)
2012-07-18 21:52 UTC, Olivier R.
Details
Description (18.28 KB, image/png)
2012-07-18 22:06 UTC, Olivier R.
Details
example of differences between Graphite font and non-Graphite fonts (13.22 KB, image/png)
2012-10-07 09:26 UTC, Olivier R.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier R. 2012-07-18 21:52:22 UTC
Created attachment 64366 [details]
Test file

This bug can be easily reproduced:

Type:
«[nbsp]Salut[nbsp]![nbsp]»

[nbsp] = non-breakable space

Set the font to "Linux Libertine G" or "Linux Biolinum G".
The punctuation between the two non-breakable spaces will disappear.

It works properly with the font "Linux Libertine" and "Linux Biolinum". I assume this is a bug with the Graphite renderer.

This concerns only 4 characters: ":" ";" "!" and "?"

Unfortunately, we often have to write some of these punctuations between two non-breakable spaces.

Reproduced with LO 3.5.5 and 3.6.
Confirmed on the French mailing-list.
Comment 1 Olivier R. 2012-07-18 22:06:37 UTC
Created attachment 64367 [details]
Description
Comment 2 Jean-Baptiste Faure 2012-10-06 16:29:35 UTC
As shown in the second attachment (https://bugs.freedesktop.org/attachment.cgi?id=64367) using the option frsp=0 solves the problem. 
I do not know if it is only a workaround or if the incompatibility between non-breakable space character and the automatic management of the non-breakable spaces by the graphite font is normal.

Best regards. JBF
Comment 3 Olivier R. 2012-10-07 09:21:17 UTC
OK, let’s try to be clear. This is a usability issue.

Jean-Baptiste, does it sound logical to you that in order to write in French, you have to disable the option specifically dedicated to the French language?

Actually, it’s not necessary, as with the Graphite font you can write in French without having to add yourself these non-breaking spaces. The Graphite font will do that for you within the punctuation characters.

So what the issue really is:

1. People don’t know it.
2. When we set this font to a text, this issue makes think that this is a bug from LibreOffice or the font itself.
3. By default, LibreOffice adds theses non-breaking spaces for the texts set to the French language.

So, by default, at least, the text should look correct whatever we want to do with the Graphite font.

And disable the French spaces option is *not* the solution because this kind of font is specifically made, among other things, to handle the way we use spaces in our texts.

By the way, I think the non-Graphite versions of these fonts should be included by default in LO, as people might not want to bother with these very specific typographical issues.
Comment 4 Olivier R. 2012-10-07 09:26:39 UTC
Created attachment 68197 [details]
example of differences between Graphite font and non-Graphite fonts

Jean-Baptiste, look how the Graphite font is intended to be used. You don’t have to use manual non-breaking spaces. The font handles that for you.
Comment 5 QA Administrators 2015-01-05 17:52:08 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

Thank you for your help!

-- The LibreOffice QA Team
Comment 6 Olivier R. 2015-01-05 18:24:48 UTC
Problem still here in LO 4.3.5
Comment 7 QA Administrators 2016-01-17 20:04:19 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (5.0.4 or later)  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Comment 8 Jean-Baptiste Faure 2016-01-19 06:05:21 UTC
Still reproducible with LibreOffice 5.0.5.0.0+ but not with LibreOffice 5.1.1.0.0+.
Will test with the master if I can build it next night.

Best regards. JBF
Comment 9 Jean-Baptiste Faure 2016-01-20 05:01:18 UTC
Works in master too. Closing as WorksForMe. Feel free to reopen if you disagree.

Best regards. JBF