Hi, I attach file original.doc with table - if opened, the left cell in the last but one line (cell AA) is empty, but should not be. It is perhaps problem with versioning - see the following text. This was observed in LO 4.2.1.1, but also in LO41, LO40 and even Apache OO40. The text, which should be displayed there is "Počet realizovaných patentov, nových technológií, predaných licencií a pod." (see the attached PDF) I can, however, display some text in the cell by the following procedure: 1. click in the table and hit CTRL-A twice to highlight the table 2. Using the Drop down menu set the style to "WW-Základný text 21" - some text appears in the AA cell 3. Hit CTRL-M - even more text appears in the AA cell, but it is not the same text as in the PDF file. The text which appears is: "Počet realizovaných patentov, nových technológií, predaných licencií a pod.patentov, nových technológií, predaných licencií ap.patentov, nových technológií, predaných licencií ap." Not only that - The text in the last line is different now: Instead of "Školiteľ skončených ašpirantov/doktorandov (počet)" I can see there "Školiteľ skončených ašpirantov/doktorandov (počet) Počet realizovaných patentov, nových technológií, predaných licencií ap. Pedagogická činnosť (počet hodín ročne):" See the attached screenshot LOTableBug.png I've tried to investigate the problem deeper. I've converted the doc file in Microsoft Office 2013 to docx, rtf and odt (attached). Then I viewed the source - inside in all of them I was able to find both the correct and incorrect string. Thus, I assume, that this is a problem with versioning (or something similar) in the document (neither MS Office nor Libreoffice shows any versions or revisions) - LO displays the incorrect version. The table behaves strange in general - if different paragraph styles are applied, text in different cells vanishes - this is perhaps another problem -- Milos
Created attachment 94457 [details] files demonstrating the problem
Thank you for your bug report, I can reproduce this bug running Version: 4.2.3.1 Build ID: 3d4fc3d9dbf8f4c0aeb61498a81f91c5b7922f13 OS: Mac osx 10.9.2 I have compared it with Microsoft word 2007 on Windows 7 and there the text is shown.
tested under Win7x64 issue confirmed in OOo 3.3.0, LibO 4.2.5.2 and yesterday 4.4 daily master build bug is inherited from OOo
** 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.1 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-07-18
Created attachment 117322 [details] screenshot I confirm issue under Win8.1 x64 using LibO 4.4.5.1 the issue persists with the .DOC and .RTF files from attachment 94457 [details] if I use LibO 5.1.0.0 alpha the .DOC rendering is even worse (see screenshot) while the .RTF bug remains the same. interestingly the .DOCX version is correctly rendered in both versions
** 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
I can confirm same behavior still in Version: 5.3.0.0.alpha0+ m
Still repro with: Version: 5.4.0.0.alpha0+ Build ID: 33f5bc54aaa7fe7aa9335726e30f9c349155e04d CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-12-01_23:21:05 Locale: nl-NL (nl_NL); Calc: CL
Created attachment 136950 [details] tdf75281_minimal.doc: reduced test created by MSO2003 I wonder if this document is somehow corrupt. In this minimal test, if the first cell is selected and any change is made to the character font properties, then the document works fine. For example, if in MSO you make A1's contents bold, then A2's contents become visible in LO. I don't think that it is worth investigating this particular bug.
** 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 Milos Sramek, 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://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
Created attachment 177852 [details] The original DOCX file in Word 2013 and current Writer It seems to work in DOCX and DOC formats, but not in RTF. Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: eb69767d7c1bb8e6e780fd9503f08c9d7f5ecb45 CPU threads: 13; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded What we see is style inheritance: Normal paragraph style has some font effects enabled: Strikethrough, Shadow, Small caps and Hidden. Most of the document got rid of these by direct formatting. Some parts are using the Body Text 2 style which overrides and disables these. In DOC and DOCX this works fine (at least nowadays).
Created attachment 177853 [details] The original DOC file in Word 2013 and current Writer Looks pretty much the same.
Created attachment 177854 [details] The original RTF file in Word 2013 and current Writer RTF does not import the override of disabling the previously enabled font attributes in the paragraph style inheriting from Normal. Similar happens with the Heading 1 and Heading 3 style paragraphs which are the first three title lines of the page.