Bug 141005

Summary:	Bottom and descent values ignored for vertical writing
Product:	LibreOffice	Reporter:	Y. Kawara <sutetecoaca>
Component:	LibreOffice	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nagharshita16, serval2412
Priority:	medium
Version:	7.0.4.2 release
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:
Attachments:	Example of misaligned text GIMP vs Inkscape vs LibreOffice - my font My font in FontForge GIMP vs Inkscape vs LibreOffice - commercial font Commercial font in FontForge

Description Y. Kawara 2021-03-13 20:17:49 UTC

Description:
I am developping Japanese fonts, and I have noticed that LibreOffice should not be used as a reference to check vertical writing.

The problem is that LibreOffice ignores the fonts' baseline/descent values and uses the lowest point of the path to place the characters vertically. This breaks the text alltogether, and is specially noticeable with characters having a proportional height, but it does happen with fixed height as well, as the path never exactly fills the height.

GIMP uses the baseline to align the characters. That does not misaligns the text, but I believe that once it'll allow to change fonts within the same text element, you will see it because they have different bottom/baseline ratios.

So far in Linux only Inkscape does it right and is consistent with how Japanese word processors like Word (and possibly Adobe software) display vertical characters. Inkscape seems to use either the descent or bottom value.

I believe this kind of issue is what is preventing LibreOffice from being massively used in Japan.

Steps to Reproduce:
1. Type in some vertical text

Actual Results:
Notice the inconsistent vertical spacing.

Expected Results:
Spacing should be consistent.


Reproducible: Always


User Profile Reset: No



Additional Info:
Use bottom or descent value to align characters vertically, not the lowest point of the path.

Comment 1 Y. Kawara 2021-03-13 20:18:50 UTC

Created attachment 170459 [details]
Example of misaligned text

Comment 2 Y. Kawara 2021-03-13 20:19:54 UTC

Created attachment 170460 [details]
GIMP vs Inkscape vs LibreOffice - my font

Comment 3 Y. Kawara 2021-03-13 20:20:36 UTC

Created attachment 170461 [details]
My font in FontForge

Comment 4 Y. Kawara 2021-03-13 20:21:12 UTC

Created attachment 170462 [details]
GIMP vs Inkscape vs LibreOffice - commercial font

Comment 5 Y. Kawara 2021-03-13 20:21:52 UTC

Created attachment 170463 [details]
Commercial font in FontForge

Comment 6 Harshita Nag 2021-04-09 16:52:05 UTC Comment hidden (obsolete)

Hello sutetecoaca@mutsuba.info,

Thank you for reporting the bug. I can confirm that the bug is present in the master.

I am setting the status of this bug to NEW.

Version: 7.0.5.2
LibreOffice-7.0.5-x86_64.AppImage, Branch:master, Time: 2021-04-9_22:05:41

Comment 7 Harshita Nag 2021-04-25 05:56:28 UTC

Hello Y. Kawara,

    Thank you for reporting the bug. I can confirm that the bug is present in the 
    master.

    I am setting the status of this bug to NEW.

    Version: 7.0.5.2
    LibreOffice-7.0.5-x86_64.AppImage, Branch:master, Time: 2021-04-9_22:05:41

Comment 8 QA Administrators 2023-04-26 03:23:34 UTC Comment hidden (obsolete)

Dear Y. Kawara,

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://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

Comment 9 Julien Nabet 2023-12-16 22:11:55 UTC

There have been some improvements in fonts management these last years, would it be possible you give a try to last LO version (7.6.4)?

If you still reproduce this, would it be possible to have a sample document (just one page) with a font which can be downloaded freely?
I mean, it would help devs to reproduce this quickly.

Comment 10 Y. Kawara 2024-02-10 07:42:37 UTC

Fixed in last public release. Thanks!

Comment 11 Julien Nabet 2024-02-10 09:10:53 UTC

Thank you for the feedback Y. Kawara!

Let's put this one to WFM then.