Bug 100566 - DOCX: multiline bookmarks rendered wrong
Summary: DOCX: multiline bookmarks rendered wrong
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) rc
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:docx
Depends on:
Blocks: DOCX
  Show dependency treegraph
Reported: 2016-06-23 14:54 UTC by Andrey Skvortsov
Modified: 2019-12-11 11:20 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

test document (13.88 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2016-06-23 14:54 UTC, Andrey Skvortsov

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Skvortsov 2016-06-23 14:54:10 UTC
Created attachment 125862 [details]
test document

If bookmark text contains several line, then if inserted reference text, it's shown as one line.

To reproduce the issue:

1. Open attached docx document
2. See original text of bookmark and reference text as it was created by MS Word 2010 (two lines)
3. Insert another reference text (Insert->Cross-reference) for the bookmark 'm'
4. Old reference text is now on one line, but it has two lines.
5. New reference text is also on one line.

If you save and open document in MS Word and update fields values (press F9), then both bookmark references will be converted back to two lines.

Or alternatively:
1. Create empty document in Writer
2. Write "First line", press <Shift Enter> (new line without new paragraph), write "Second line"
3. Select both lines
4. Insert->Bookmark with name 'm'
5. Insert->Cross-reference bookmark reference for 'm'
6. Bookmark is inserted as one line, but it should be pasted as two lines.
Comment 1 Buovjaga 2016-06-26 12:23:23 UTC
I inserted to the end of the text and I could reproduce.

Arch Linux 64-bit, KDE Plasma 5
Build ID: ff25ea3d5ccf3a990767cbb1ef99037d3f84b072
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on June 26th 2016
Comment 2 QA Administrators 2017-12-10 16:43:23 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-12-11 03:37:53 UTC
Dear Andrey Skvortsov,

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