3GPP documentation is a good example of Word documents, which are not at all comfortable to read with LibreOffice (or OpenOffice - this error has been there "always"). Attached is 3GPP specification 25.133 v11.2.0 as both original Word document and as PDF, which is exported from MS Word 2010. The original Word document can also be fetched from here: http://www.3gpp.org/ftp/Specs/2012-09/Rel-11/25_series/25133-b20.zip If the Word document is opened in any MS Word installation (in almost any computer, with almost any Word version), the document looks the same. Cover page looks good, page numbers stay the same. The attached PDF represents how the document should look like. But when the same document is opened in LibreOffice (for example 3.6.1.2, Build ID e29a214), the cover page formatting is messed up, and also other pages are formatted slightly differently. This causes e.g. page numbers to run slightly differently than in Word. I remember that these formatting problems have appeared always in all OpenOffice versions, with all 3GPP documents. Thus it is not comfortable to read 3GPP documents with LibreOffice and companies working with 3GPP related development have to stick with MS Word. The attached ZIP file (25133-b20.zip) contains following: - 3GPP specification document in both original Word format - PDF document created with MS Word showing how the document should look like
The attachment file was too large, so I had to take out the original Word document from the attachment and store only the PDF file. The original Word document is stored in 3GPP website, here: http://www.3gpp.org/ftp/Specs/2012-09/Rel-11/25_series/25133-b20.zip
Created attachment 68513 [details] Zip containing PDF presenting how the Word document should look like
Created attachment 69332 [details] Side-by-side screenshots of how a cover page looks in Word and LibreOffice. Reproduced with Windows 7 and version 3.6.2.2, see attachment. I was actually thinking about submitting this bug a while ago.
Changing status to new.
I think I'll go increase this in severity. A good portion of the Word documents out there use cover pages, and it's a serious bug that LibreOffice can't use them.
This lack of cover page support has prevented me from making a complete switch to LO.
It is rather a feature request.
Alright; I've changed its severity.
Restricted my LibreOffice hacking area
The problem with 3GPP files still exist in current version, another example is http://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-b00.zip
*** Bug 85309 has been marked as a duplicate of this bug. ***
tested under Win7x64. bug not present in LibO 3.3.4 bug present in LibO 3.4.3 and following releases including 4.3.2 and recent 4.4.x master. compare screenshots in attachment 108217 [details] edited version field
Migrating Whiteboard tags to Keywords: (notBibisectable)
According to comment #12, this is not an enhancement request. In LO 5.1.3.0.0+, I see 279 pages instead of 277 in the pdf. Nothing that prevent to work with this document. The only real problem is the cover page which is messed up. Same problem in current master. Tested under Ubuntu 15.10 x86-64. Best regards. JBF
This regression was introduced before branch 4.4, thus it can't be bibisected with the current bibisect repositories. Changing keyword 'notBibisectable' to 'preBibisect'
Created attachment 127298 [details] image showing how the page looks (~fine) in LO 3304
Created attachment 127326 [details] LO 5.1.5.2 screendump Created a new attachment showing the document cover page on Libre Office writer, version 5.1.5.2. The problem still exists, sorry.
Created attachment 134726 [details] Screen capture from Libre Office 5.3.4.2 Just bumping this up with a new screen capture from LibreOffice 5.3.4.2. The error exists still.
** 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 129336 has been marked as a duplicate of this bug. ***
(In reply to QA Administrators from comment #19) > ** 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 I tested with Libreoffice Writer , and find the bug is still exist: DISTRIB_ID=ManjaroLinux DISTRIB_RELEASE=18.1.4 and my OS is: Libreoffice Writer Version: 6.3.3.2.0+ Build ID: 6.3.3-1
Created attachment 158544 [details] Original DOC of 277 pages Since original DOC is no longer available through link, I add it here. Various LO versions open different number of pages. It's 274 in 7.0+ and it opens rather slow.
Created attachment 158545 [details] Original DOC with just pages 1-2 from MSO Makes no sense to open 277 pages just to show cover. Here is DOC with just pages 1-2 saved in MSO.
Created attachment 158546 [details] Original DOC pages 1-2 saved as DOCX in MSO Let's also keep and DOCX, although bug is about DOC.
Created attachment 158547 [details] Original DOC pages 1-2 as PDF from MSO
Created attachment 158548 [details] DOC page 1 compared MSO LO As can be seen, OO and LO 3.4.0 were not perfect, but were spoiled in 3.4.x and never fixed up to 7.0+.
Created attachment 158549 [details] DOCX pages 1-2 compared MSO LO DOCX is worse, LO opens 3 pages of 2 pages sample all the way from LO 3.3.
These shortened page 1/2 documents consist almost entirely of frames. So this will be frame anchoring problems, perhaps related to overlap. There is also a page break here, to really mess you up if you substitute a relative-to-page anchor to something else.
*** Bug 142475 has been marked as a duplicate of this bug. ***
(In reply to Timur from comment #29) > *** Bug 142475 has been marked as a duplicate of this bug. *** So it is such a long running issue and not a recent regression ?
(In reply to Banibrata Dutta from comment #30) > (In reply to Timur from comment #29) > > *** Bug 142475 has been marked as a duplicate of this bug. *** > > So it is such a long running issue and not a recent regression ? You reported DOC with screenshot attachment 172314 [details]. And previous situation is in screenshot attachment 158548 [details]. It looks worse but I don't see it was even OK and it's from Linux (I see it in 5.2).
Dear Kalle Tuulos, 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
Focusing on the main issue, where the top frame drops down over other text, that actually looked good in 3.4.1, but not in 3.4.2. All duplicates really are 3GPP documents. The 3GPP picture placement on this one is interesting. in MS Word 2010 I see it on the right side, but the "box" is huge - extending from the left edge of the page. Looking at the image properties doesn't show anything unusual, but pressing OK makes the image jump to the left side of the page (where LO used to show it before LO 7.4). It changed in LO 7.4 with commit 1539a0fcd31f4ba7ef71adf4ae7761dc445199f5 Author: Justin Luth on Sat Aug 13 12:29:12 2022 -0400 tdf#77964 doc import: 0x1 placeholder is for AS_CHAR
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d42f519be7bcc8e194899a6b3225bcee7e54bc16 tdf#60683 tdf#55946 doc import: use style's anchor info It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Justin L from comment #33) > The 3GPP picture placement on this one is interesting. in MS Word 2010 I see > it on the right side, but the "box" is huge - extending from the left edge > of the page. Looking at the image properties doesn't show anything unusual, > but pressing OK makes the image jump to the left side of the page (where LO > used to show it before LO 7.4). A simple round-trip doesn't fix it, but if I add one character into the frame and resave, then it looks OK in LO. (Oh, but if I remove that character, then it looks bad again...) The cursor in the frame that I assume belongs to the image has a huge cursor in it. Likely typing a character in her properly sizes the paragraph. I have to assume I just exposed a layout bug here. It has all the markings of layout issues anyway.