Created attachment 123073 [details]
The same document (especially with many Japanese Furigana) is different between Windows and Linux if using japanese fonts.
It may depend on the spacing between kana and furigana (or between japanese and Occidental fonts) different in different OS.
It's version independent.
Pagination is compromised.
Please ask me for any info you may need.
See this discussion thread: https://lists.freedesktop.org/archives/libreoffice/2016-March/073509.html
It should get fixed with a unified font rendering backend.
Its a little too technical for my knowledge.
(In reply to Andrea from comment #2)
> That is?
> I apologize.
> Its a little too technical for my knowledge.
The dream is to get font rendering on Windows done with Freetype + Harfbuzz.
In my humble opinion on linux the mix kana-furigana-romaji is best handled by libreoffice on linux than on windows.
Make dreams come true.
W3C Working Group Note “Requirements for Japanese Text Layout” has an good example on this that you can catch up with.
The bug description is very general, can you be more specific about the differences you are seeing, an whether you have all the fonts used in the document on both systems or not.
I think the problem is related to spacing between furigana and kanji in ruby texts.
This spacing is different depending on operative systems, so the same document is formatted differently causing unconformity (paragraphs divided in 2 pages when opening on WindowsOS) if the document is open on windows or GNU/Linux.
I'm using the same fonts in both systems (HGSeikaishotaiPRO).
Don't know how to be more specific.
What I’m looking for is something like in the 1st pages, in like N foo and bar are spaced differently. For someone who does not know Japanese, I had absolutely no idea where to look for differences in the page.
Need to create a pdf.
Many many thanks
Created attachment 128545 [details]
kanji e Furigana spacing LINUX
File created on LINUX and opened on LINUX
Created attachment 128546 [details]
kanji e Furigana spacing WINDOWS
File created on LINUX and opened on WINDOWS
Thanks, so this looks like another instance of bug 55469.
*** Bug 55469 has been marked as a duplicate of this bug. ***
Andrea, it's later that should be marked as a duplicate.
Does it really matter! The other bug is older and have more information than this one.
*** This bug has been marked as a duplicate of bug 55469 ***