Created attachment 74107 [details] Multi-column 1-page .doc file which doesn't display correctly in LibreOffice LibreOffice 3.6.5.2 generally works quite well for me. However, it doesn't correctly display a certain .doc file (BWDoc1.doc) I have created. This specific .doc file was created using Foxit PhantomPDF's OCR on 1 page I scanned from an old (1905, so in the public domain) reference/study Bible we have. The top of the page has 4 columns -- with the 2 outermost columns of the same size and the 2 innermost columns of the same size, but the outermost/innermost columns of differing sizes. (Column1Width = Column4Width and Column2Width = Column3Width, but Column1Width != Column2Width). and the bottom of the page has 3 equal-width columns. I realize that this is quite a complex document, but MS Office Word Viewer 11.8169.8172 SP3 opens and displays this file correctly. and Lotus Symphony 3.01 opens it and displays it fairly well, but not perfectly. I am running 64-bit Microsoft Windows 7 Home Premium (SP1). Thank you. RJ USA
I can confirm this 'behavior'/rendering issues. I also see that this .doc is 'rtf-based' (I don't know what the exact words are, but I see rtf code in it). So I'm not sure this is just a renamed extension (from .rtf to .doc) or it's just saved that way. @Miklos: do you mind have a look at this rtf(/doc)? Thanks in advance, Joren
Thank you for confirming that you, too, see the problem. It looks like you are certainly right that "this .doc is 'rtf-based'". I had used FoxIt Phantom PDF's OCR capability to create both a .doc file and a .rtf file, and just noticed that they were BOTH 71 KB in size. So, I tried using WinMerge to compare the 2 files - and they are identical. I just tried opening both (.doc and .rtf) files using LibreOfficePortable's (from PortableApps) Writer 4.0.0.3, and see that the problem still exists there, so I don't know whether you might want to update the version # in the bug list. Thank you. - RJ On 2/3/2013 5:30 PM, bugzilla-daemon@freedesktop.org wrote: > Jorendc <mailto:joren.libreoffice@telenet.be> changed bug 60205 > <https://bugs.freedesktop.org/show_bug.cgi?id=60205> > What Removed Added > Status UNCONFIRMED NEW > QA Contact joren.libreoffice@telenet.be > CC vmiklos@suse.cz > Ever confirmed 1 > > *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=60205#c1> > on bug 60205 <https://bugs.freedesktop.org/show_bug.cgi?id=60205> from > Jorendc <mailto:joren.libreoffice@telenet.be> * > I can confirm this 'behavior'/rendering issues. > > I also see that this .doc is 'rtf-based' (I don't know what the exact words are, but I see rtf code in it). > So I'm not sure this is just a renamed extension (from .rtf to .doc) or it's just saved that way. > > @Miklos: do you mind have a look at this rtf(/doc)? > > Thanks in advance, > Joren > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. >
Thanks for your reply. (In reply to comment #2) > so I don't know whether you might want to update the version # in the > bug list. The version in this bug report is the oldest version of LibreOffice we can confirm this behavior. So now is the oldest version 3.6.5.2. Nothing to change there right now :-). PS: please use the Bugzilla interface (https://bugs.freedesktop.org/show_bug.cgi?id=60205) instead of replying the email you receive OR delete all previous text when you reply. It isn't that organized when you just reply the email (see your comment in this bug report). No worry, no man killed, just a tip :-).
Problem still exists in LibreOffice 4.2.3.3.
** 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 on a currently supported version of LibreOffice (4.4.3 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-06-08
Created attachment 116378 [details] Multi-column doc viewed with MS Word Viewer
Created attachment 116379 [details] Multi-column doc viewed with LibreOffice
Created attachment 116380 [details] Multi-column doc viewed with OpenOffice
At your request, I checked and the bug is still present in LibreOffice 4.4.3.2 (using 64-bit MS Windows 7 Home Premium [SP1]). I have attached 3 screenshots: 1. How the document looks (essentially correctly [very similar to my original -- unscanned, unOCR'd] document]) in MS Word Viewer 11.8416.8405. [It looks essentially the same in MS Word Starter 2010.] 2. How the document looks (incorrectly) in LibreOffice 4.4.3.2 3. How the document looks (more incorrectly) in OpenOffice 4.1.1 P.S. - I hope it was OK for me to attach a screenshot of MS Word Viewer (a copyrighted program).
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
The bug is still present in LibreOffice 5.1.5.2, using Windows 7 Home Premium, 64-bit (SP3). Looking at this document looks essentially, though not exactly, the same as in the earlier LO version which I reported this for.
** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
Looks the same issue like in Bug 105971: absolute position to margin with "Layout in table cell" from DOC is not read well in LO.
** 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
Dear rj_libreoffice, 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
Repro 7.4+.
I see essentially the same problem with the current LibreOffice Fresh, v7.3.2.2. (x64), using Windows 10 Home. See new screenshot.
Created attachment 179768 [details] Essentially the same problem seen with LO v7.3.2.2 (x64), Win 10 Home
Although I think it does look somewhat better than in LibreOffice 3.6.5.2, the problem's still there in LibreOffice: Version: 7.6.5.2 (X86_64) / LibreOffice Community Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Focusing on the "Romans 1" textbox, we get {\sp{\sn fBehindDocument}{\sv 1}} \shpz1 {\sp{\sn shapeType}{\sv 202}} {\sp{\sn dxTextLeft}{\sv 0}} {\sp{\sn dyTextTop}{\sv 0}} {\sp{\sn dxTextRight}{\sv 0}} {\sp{\sn dyTextBottom}{\sv 0}} {\sp{\sn fFitShapeToText}{\sv 1}} {\sp{\sn fFilled}{\sv 0}} {\sp{\sn fLine}{\sv 0}} {\sp{\sn dxWrapDistLeft}{\sv 63500}} {\sp{\sn dyWrapDistTop}{\sv 63500}} {\sp{\sn dxWrapDistRight}{\sv 63500}} {\sp{\sn dyWrapDistBottom}{\sv 63500}} {\sp{\sn fLayoutInCell}{\sv 1}} Note that these name/value pairs are not part of the RTF specification, so it is an application-specific extensions to the standard where fLayoutInCell is defined. layoutInCell is a key factor in proper placement of in-table shapes. The vertical anchor is not specified, so it should be treated as the page margin \pvmrg (or in this case cell margin since it is fLayoutInCell) (but LO is using its default of paragraph - see bug 48442 where this was deal with for frames).