Bug 107185 - Furigana (ruby) text appears too far from base text, often closer to preceding/following line
Summary: Furigana (ruby) text appears too far from base text, often closer to precedin...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Ruby CJK-Japanese
  Show dependency treegraph
Reported: 2017-04-15 16:01 UTC by y3kcjd5
Modified: 2022-07-08 03:20 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:

Document demonstrating furigana and stress mark position (11.05 KB, application/vnd.oasis.opendocument.text)
2017-04-19 21:52 UTC, y3kcjd5
PDF of demonstration document (15.39 KB, application/pdf)
2017-04-19 21:57 UTC, y3kcjd5
Guessed examples (249.69 KB, application/x-zip-compressed)
2017-05-05 13:53 UTC, JO3EMC

Note You need to log in before you can comment on or make changes to this bug.
Description y3kcjd5 2017-04-15 16:01:26 UTC
For whatever reason, furigana text always has way too much whitespace between it and the base characters it's supposed to be attached to. This is especially bad if they're set to appear above (or to the right of in vertical text) the base characters, because somehow they end up closer to the preceding line of text than the one they're on. 

Steps to Reproduce:
1. Produce some text with furigana on top (Alt,O,I,Enter for furigana menu)
2. Put another line of text above it
3. Remove all extra whitespace between lines (line spacing 1 etc.)

Actual Results:  
Furigana appear closer to the wrong line of text

Expected Results:
Furigana should hug the text it's modifying, much like font effects in the character properties menu (over/underlines, stress dots, etc.). At the very least there should be an option (in the furigana menu?) to manually adjust furigana elevation.

Reproducible: Always

User Profile Reset: No

Additional Info:

User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
Comment 1 madmalkav 2017-04-19 21:28:01 UTC
Can you confirm which version of LO are you using, OS, etcetera? Similar issues have been solved recently in some other bugs ( #55469 , #103730)
Comment 2 y3kcjd5 2017-04-19 21:52:54 UTC
Created attachment 132700 [details]
Document demonstrating furigana and stress mark position

I'm using version, Windows 7 64 bit. I recently upgraded from 5.1.2 in an attempt to solve this and it DID get better, but it's still an issue. I'm aware that some fonts include inordinate amounts of whitespace in their specifications, but I know that this is not the issue because stress marks can be rendered correctly where I'd expect the furigana to go. I've generated a document demonstrating this, though the font (KaiTi) was too large to embed. I'll see if I can attach it separately.
Comment 3 y3kcjd5 2017-04-19 21:57:11 UTC
Created attachment 132701 [details]
PDF of demonstration document

Unfortunately the font file alone seems too big to upload as well. Windows 7 users Should get the FangSong and KaiTi fonts with the OS, so hopefully someone can reproduce this. I'm attaching a PDF showing what I see as well. Note the position of the stress marks (suspended to the right of "ミろる") as compared to the furigana (suspended to the right of "こば")
Comment 4 madmalkav 2017-04-26 13:05:39 UTC
This exceeds my knowledge, I don't know if it is an issue with the font or the rendering. It would be great if Khaled Hosny could take a look at it. Not adding him to the bug CC as I don't know the "netiquette" involved in that.
Comment 5 JO3EMC 2017-05-05 13:53:19 UTC
Created attachment 133092 [details]
Guessed examples

I suppose this issue is talking about adjustment of the distance between "Ruby text" and "Base text".

Attached some example files.

See "Bug 107185 JO3EMC 1H".(either PNG or ODT)
Ruby text "いろは" binded to Base text "まみむめも".
But on the display, "いろは" positioned to almost same distance between "まみむめも" and "かきくけこ" in the above line.
It is difficult to recognize which is the Base text of "いろは", from appearance.
So, we want to position "いろは" more closer to "まみむめも".
It is so desirable that the distance between "Ruby text" and "Base text" is manually user adjustable.

Enhancement request, I think.
But I'd like to set the status to "New", cause reproduced.

Of course, not only horizontal text direction, but also vertical.
See "Bug 107185 JO3EMC 1V".
We get the same resul.....
whoops...base line of the "Base text" was disturbed...
This issue shold be another report. ;-)

Build ID: 2514e38f8ebb95f51783ce321a84d6c55bba1de4
CPU threads: 4; OS: Windows 6.2; UI render: default; 
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-04_00:30:46
Locale: en-US (ja_JP); Calc: group

Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1
CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; 
Locale: en-US (ja_JP); Calc: group
Comment 6 QA Administrators 2019-11-16 03:41:37 UTC Comment hidden (obsolete)
Comment 7 y3kcjd5 2020-03-10 02:58:35 UTC
Confirmed relevant in version (x64), Build ID 4d224e95b98b138af42a64d84056446d09082932.
Upon trying to generate another PDF from the demo document for side-by-side comparison, I discovered that the stress dots are no longer being rendered at all.
Comment 8 QA Administrators 2022-03-11 03:51:48 UTC
Dear y3kcjd5,

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