Bug 87805 - Wrong formatting of DOCX file: too much breaks no underlining
Summary: Wrong formatting of DOCX file: too much breaks no underlining
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX
  Show dependency treegraph
 
Reported: 2014-12-28 19:31 UTC by Yan Pas
Modified: 2018-12-21 03:51 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
buggy file (34.62 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-12-28 19:31 UTC, Yan Pas
Details
screenshot (113.97 KB, image/png)
2014-12-28 19:32 UTC, Yan Pas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yan Pas 2014-12-28 19:31:40 UTC
Created attachment 111436 [details]
buggy file

MS Word and even Google Docs open it correctly, but LO inserts too much breaks and doesn't underline strings
Comment 1 Yan Pas 2014-12-28 19:32:34 UTC
Created attachment 111437 [details]
screenshot

Added screenshot
Comment 2 Urmas 2014-12-28 21:12:11 UTC
Confirming.
Comment 3 Robinson Tryon (qubit) 2015-12-09 18:45:00 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2017-12-10 16:39:48 UTC Comment hidden (obsolete)
Comment 5 Yan Pas 2017-12-20 08:47:38 UTC
Still exists 5.4.3.2
Comment 6 QA Administrators 2018-12-21 03:51:25 UTC
** Please read this message in its entirety before responding **

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug