| Summary: | [FILEOPEN] New lines missing in field (from custom docprop) in specific DOCX | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Cor Nouws <cno> |
| Component: | filters and storage | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | aron.budea, cno, ilmari.lauhakangas, jluth, libreoffice |
| Priority: | medium | Keywords: | filter:docx |
| Version: | 4.3.0.4 release | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=100526 https://bugs.documentfoundation.org/show_bug.cgi?id=47811 https://bugs.documentfoundation.org/show_bug.cgi?id=147861 |
||
| Whiteboard: | interoperability | ||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 112969 | ||
| Attachments: |
Screen shot showing correct field display on page 1 in Word
Image showing current situation of fields without space in LibreOffice Minimized document from Word Screenshot of the minimized document in Writer and Word |
||
|
Description
Cor Nouws
2016-06-21 16:57:43 UTC
Created attachment 125812 [details]
Image showing current situation of fields without space in LibreOffice
Confirmed. Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ 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 ** 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 bug still present in Version: 6.2.0.0.alpha0+ Build ID: e46f8a9a4e3c5b0542c0813b476b449f3af8d607 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-10-07_21:58:32 Locale: nl-NL (nl_NL.UTF-8); Calc: threaded Created attachment 154897 [details]
Minimized document from Word
Created attachment 154898 [details] Screenshot of the minimized document in Writer and Word Bibisected using bibisect-win32-4.3 to: author Michael Stahl <mstahl@redhat.com> 2014-03-02 00:32:17 +0100 committer Michael Stahl <mstahl@redhat.com> 2014-03-03 13:53:23 +0100 fdo#47811: RTF import: fix Database field content Before that only one field was imported, since this all the field names are merged into that one. Probably we can't say it worked fine before, so not setting regression tag. The idea is that the information comes from a variable - which excludes any kind of formatting etc. (In fact, I have no idea how MS Word allowed this "adres" variable to contain a carriage return because the UI doesn't seem to allow it.)
However, in this case the data doesn't even exactly match the variable's content, as can be seen (in MS Word) when pressing F9 with the field selected. In this case, it becomes three lines long instead of four.
But yes, when pressing F9 on the field, MS Word still maintains several paragraphs of content. So somehow the variable accepts carriage returns. In LO those are stripped out and all the text becomes one long variable string. So the first question is - can we import a \n into a variable string?
<property fmtid="{D5CDD505-2E9C-101B-9397-08002B2CF9AE}" pid="3" name="adres">
<vt:lpwstr>
Aan de Voorzitter van de Tweede Kamer der Staten-Generaal_x000d_Postbus 20018_x000d_2500 EA DEN HAAG_x000d_ _x000d_
</vt:lpwstr>
</property>
And then secondly (and much less important), since the content doesn't match the variable, how do we keep the displayed value and still maintain some kind of connection to the variable behind it? (This happens in DOC's read-only-field, but DOCX emulates as editable content field.)
Dear Cor Nouws, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug still present in current versions (checked in Version: 7.6.3.2 (X86_64) / LibreOffice Community Build ID: 29d686fea9f6705b262d369fede658f824154cc0 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: nl-NL (en_US.UTF-8); UI: en-US Calc: threaded) |