Bug 130217 - FILEOPEN DOCX Hanging indent in table is not ignored if it would hide the paragraph
Summary: FILEOPEN DOCX Hanging indent in table is not ignored if it would hide the par...
Status: RESOLVED DUPLICATE of bug 130218
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-27 12:33 UTC by NISZ LibreOffice Team
Modified: 2020-01-27 12:40 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2020-01-27 12:33:16 UTC
Description:
ttached table is reduced (and extended) from attachment #130321 [details] of bug #105261.

Originally it contained a table with some centered paragraphs (“TIPOLOGIA CONTRATTO”) that had 3.75 cm hanging indent set. This is sort of ignored by Word, but Writer tries to display the paragraphs with this applied, causing only the ends of the words being visible.
Extending the test file with copies of the same paragraph, but changing the alignment to left, right and justified shows similar results with the left and justified aligned text being unreadable.
Copying the extended table and disabling the hanging indent gets the same appearance in Word as with the large hanging indent (so it has no visual effect).
This also appears correctly in Writer too.

Steps to Reproduce:
Open attached document in Word and Writer

Actual Results:
The text in the first table is not entirely visible in case of left, centered and justified alignments. In case of right alignment its only visible by chance: switching to RTL direction in Writer hides that too.

Expected Results:
Extraneous hanging indent should be ignored in tables, so that text is visible like in Word.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Timur 2020-01-27 12:40:01 UTC

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