Created attachment 125724 [details]
original docx with problems
Tried in the following releases:
Build ID: 1:5.1.3-0ubuntu1
And there are several pieces of text that is missing from the document. I've attached original docx and two pdf files one generated from libreoffice and one from MS word viewer that will "show" the correct content.
Created attachment 125725 [details]
MS word viewer PDF
Created attachment 125726 [details]
LO generated PDF
It's really important when reporting to be more specific than you have been. You've provided a multi-page document and just kind of said "stuff is missing" and left it to the triager to do the work.
Marking as NEEDINFO as we don't have the time to dig into a multi-page document without more guidance.
Please do the following:
1) Provide a detailed list of what is missing (page, the words missing)
We may close this as INVALID if it seems like it's multiple bugs reported in a single report and ask that you separate the bug into individual issues with much simpler documents.
Mark as UNCONFIRMED once you've provided better guidance. Thank you
Created attachment 125729 [details]
missing text marked
It starts just after the text: "Er referens:"
The following words / numbers are missing on page1:
Also the second sales email is shifted to the right side.
Also interesting, where the first text starts missing the "pagebreak" appears.
I've attached a PDF with markup as well.
The extra page issue is a duplicate of bug 64372.
This bug report should focus on the missing text which I'm guessing all came from a mail-merge. For example, Luna 1 is [ FILLIN Projektnamn \* MERGEFORMAT ]
bisected: The text is missing from the earliest version of bibisect43all. Inherited from OOo.
Assuming bisected to imply bibisected, thus adding the latter. This is to make queries for "bibisected" not miss out bisected bugs.
Deleting 'bisected' and 'bibisected' from keywords as the problematic commits
hasn't been identified.
Setting Assignee back to default. Please assign it back to yourself if you're
still working on this issue
** 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!
This was fixed in 6.4 since:
Jan-Marek Glogowski <firstname.lastname@example.org> Tue Oct 29 14:39:05 2019 +0100
Jan-Marek Glogowski <email@example.com> Mon Nov 11 11:38:30 2019 +0100
tdf#128460 import SwInputField from DOCX FILLIN
@Jan-Marek thanks for fixing this one :)
*** This bug has been marked as a duplicate of bug 128460 ***