Bug 143025

Summary: kanji not displayed in the right place of a cell in a table
Product: LibreOffice Reporter: jeandrof
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: trivial CC: jeandrof, l.lunak, marklh9, ming.v.hua
Priority: medium    
Version: 7.1.4.2 release   
Hardware: All   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 106045    
Attachments: document describing a japanese kanji

Description jeandrof 2021-06-23 18:10:20 UTC
Description:
When I create a table describing a kanji (kun and ON, examples of words), the kanji should be in the middle of its cell as requested, but is displayed above and a little further on the right hand side, making its upper side disappearing underneath the cell of the upper line of the table. Despite its appearance, when I try to select it, the selected zone is well located in the middle of the cell.

Steps to Reproduce:
1.create a table with 3 columns and at least 3 rows.
2.write headers in the cells of the first row.
3.select the vertical writing for asian police for the cells in the second row.
4.on the second row, in the central cell, write a kanji.
5.choose to display the kanji in the middle of its cell.

Actual Results:
the upper half of the kanji disappears under the upper cell.

Expected Results:
the kanji should appear in the middle of the cell.


Reproducible: Always


User Profile Reset: No



Additional Info:
in the other cells of the second row, when written vertically, it also happens to the hiragana and katakana.
Comment 1 jeandrof 2021-06-23 18:12:12 UTC
Created attachment 173116 [details]
document describing a japanese kanji
Comment 2 jeandrof 2021-06-23 19:06:51 UTC
Comment on attachment 173116 [details]
document describing a japanese kanji

I've noticed this bug since LibreOffice_7.1.2 version
Comment 3 Ming Hua 2021-06-23 21:59:11 UTC
Thanks for reporting this bug.  I can reproduce the vertical text displacement (by the way, they are technically not Kanjis -- which means Chinese/Han characters -- but Hiraganas and Katakanas) with the attached sample file and 7.1.4, but do not reproduce with 7.2.0 Beta1.

So this is likely already fixed by the efforts of improving vertical text display for Skia in the 7.2 development.  Reporter jeandrof, please test with either of the following two approaches to see if the problem is solved for you:

1. Disable Skia, by going to the View Options dialog (Tools > Options > LibreOffice > View), and uncheck the "Use Skia for all rendering" checkbox, then restart LibreOffice.

2. Download and install the 7.2.0 Beta1 version (it is a development build and will install in a different place than your regular LibreOffice, so they can co-exist and won't interfere with each other).

Either approach should solve your problem.
Comment 4 Ming Hua 2021-06-25 14:29:35 UTC
The reporter replied via private email, and said the problem disappears once he turned off Skia.

Luboš and Mark, I remember you discussing a similar issue on the mailing list, but I can't find a bug here to mark this as a DUPLICATE of.  There is bug 142174, but that one is still reproducible with 7.3/master, while this one is fixed in 7.2 Beta1 for me.

So can you point to the relevant bug for me?  And if there isn't one, how should we resolve this bug?  WORKSFORME?
Comment 5 Mark Hung 2021-06-26 09:07:32 UTC
(In reply to Ming Hua from comment #4)
> The reporter replied via private email, and said the problem disappears once
> he turned off Skia.
> 
> Luboš and Mark, I remember you discussing a similar issue on the mailing
> list, but I can't find a bug here to mark this as a DUPLICATE of.  There is
> bug 142174, but that one is still reproducible with 7.3/master, while this
> one is fixed in 7.2 Beta1 for me.
> 
> So can you point to the relevant bug for me?  And if there isn't one, how
> should we resolve this bug?  WORKSFORME?

Set this bug to be duplicate of bug 142174 ( it was set to resolved - fixed, check the comment there. )

*** This bug has been marked as a duplicate of bug 142174 ***