https://bugs.documentfoundation.org/show_bug.cgi?id=162173
Bug ID: 162173
Summary: Writer incorrectly displays justified text in docx
(2010-365) files with non-breakable spaces
Product: LibreOffice
Version: 24.2.5.2 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Description:
When using docx files (Word 2010-365 version) created in LO (due to journal
policy accepting only docx files) containing paragraphs with justified
alignment and non-breakable spaces, some (apparently random) characters are
displayed outside the paragraph margin or words are split incorrectly (without
hyphen while word splitting is disabled). The wrong appearance is preserved
when saving as odt, but is fixed when saving as docx (Word 2007) and then
re-opened, as suggested here
https://www.reddit.com/r/libreoffice/comments/1crpj9a/writer_242_new_issues_with_justified_text/?rdt=51105
Steps to Reproduce:
1. Open the attached file Bug_report.docx.
2. Optionally - delete the non-breakable space on the first line of the
paragraph and re-insert it to reproduce the bug.
3. Optionally replace spaces with non-breakable spaces before and after
"analysis" on the second line to reproduce the same behaviour.
Actual Results:
The first line of the paragraph ends with "a p". The space is a non-breakable
space, the "p" is part of a word that has been incorrectly split.
Expected Results:
The two words "a published" should be moved to a next line after replacing the
Reproducible: Sometimes
User Profile Reset: No
Additional Info:
The behaviour seems somewhat random, inserting non-breakable space at different
places not always reproduces the bug. However, once problem appears, it can be
consistently reproduced by deleting and re-inserting the non-breakable space.
Sometimes, words are not split but some characters appear outside the paragraph
margin. Exporting to PDF or saving as ODT does not change appearance. Saving as
DOCX with Word 2007 compatibility solves the issue. Saving the same (corrected)
document as 2010-365 docx does not reproduce the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
