docx document opened incorrectly. Attached the docx document and the correct document in pdf as opened by Microsoft Word.
Created attachment 74943 [details] PDF file as opened by Word.
Created attachment 74944 [details] docx file that cannot be opend correctly by LO.
Not a Valid Bug report. Of course, I see lots of problems in the sample document when I open it, bot lots of them already might have been reported ... So I hijack this report for 1 obvious problem: Steps how to reproduce [Reproducible] with parallel Dev-installation of "Version 4.1.0.0.alpha0+ (Build ID: 2b9394f0c009b385756a0c5d75e3c1cd412f723) TinderBox: Win-x86@6, Branch:master, Pull Time: 2013-02-14_00:13:52" ENGLISH UI / German Locale on German WIN7 Home Premium (64bit) with LODev/4 Masters User Profile: 1. Open sample document 2013-02-16 16:09 UTC Expected: Under some kind of sub heading a text field should show text "Maskine efterset og fejlsøgt,fodspark knækket ..." Actual: That text field is repeated lots of ties in the table The problem might have deeper roots, I wonder whyI don't see any info in Field dialog in column "Selction" Same problem in AOOo 3.4.1, so I think problem is inherited from OOo @Erik P. Olsen: Thank you for your report – unfortunately important information is missing. Please do not misunderstand this message. We are interested in your report, but some technicalities have to be respected so that we can start to fix a problem. May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? It would be great if you could extract additional problems and submit separate bugs citing this sample here <https://wiki.documentfoundation.org/QA-FAQ#How_to_use_attached_sample_documents_for_multiple_Bug_Reports> and adding me to CC Please add all information requested in following: - Write a meaningful Summary describing EXACTLY what the problem is - Attach screenshots with comments if you believe that that might explain the problem better than a text comment. Best way is to insert your screenshots into a DRAW document and to add comments that explain what you want to show (attachment 68877 [details], attachment 68490 [details]) - Contribute a document related step by step instruction containing every key press and every mouse click how to reproduce your problem (similar to example in Bug 43431) – if possible contribute an instruction how to create a sample document from the scratch - add information -- what EXACTLY is unexpected -- concerning your Operating System (Version, Distribution, Language) -- concerning your LibO localization (UI language, Locale setting) May be you want to test <https://www.libreoffice.org/get-help/bug/> for submitting bug reports (Available since LibO 3.5)? You reach that Bug Submission Assistant via LibO menu 'Help -> Feedback / Bug Report'. The assistant will collect and insert such information automatically. @Michael: Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug or forward the Bug if it's not your turf
(In reply to comment #3) > Not a Valid Bug report. Of course, I see lots of problems in the sample > document when I open it, bot lots of them already might have been reported > ... > > So I hijack this report for 1 obvious problem: > > Steps how to reproduce [Reproducible] with parallel Dev-installation of > "Version 4.1.0.0.alpha0+ (Build ID: 2b9394f0c009b385756a0c5d75e3c1cd412f723) > TinderBox: Win-x86@6, Branch:master, Pull Time: 2013-02-14_00:13:52" ENGLISH > UI / German Locale on German WIN7 Home Premium (64bit) with LODev/4 Masters > User Profile: > > 1. Open sample document 2013-02-16 16:09 UTC > Expected: Under some kind of sub heading a text field should show text > "Maskine efterset og fejlsøgt,fodspark knækket ..." > Actual: That text field is repeated lots of ties in the table > > The problem might have deeper roots, I wonder whyI don't see any info in > Field dialog in column "Selction" > > Same problem in AOOo 3.4.1, so I think problem is inherited from OOo > > @Erik P. Olsen: > Thank you for your report – unfortunately important information is missing. > Please do not misunderstand this message. We are interested in your report, > but some technicalities have to be respected so that we can start to fix a > problem. > May be hints on <http://wiki.documentfoundation.org/BugReport> will help you > to find out what information will be useful to reproduce your problem? > > It would be great if you could extract additional problems and submit > separate bugs citing this sample here > <https://wiki.documentfoundation.org/QA- > FAQ#How_to_use_attached_sample_documents_for_multiple_Bug_Reports> and > adding me to CC > > Please add all information requested in following: > - Write a meaningful Summary describing EXACTLY what the problem is > - Attach screenshots with comments if you believe that that might explain > the > problem better than a text comment. Best way is to insert your screenshots > into a DRAW document and to add comments that explain what you want to show > (attachment 68877 [details], attachment 68490 [details]) > - Contribute a document related step by step instruction containing every > key press and every mouse click how to reproduce your problem > (similar to example in Bug 43431) > – if possible contribute an instruction how to create a sample document > from the scratch > - add information > -- what EXACTLY is unexpected > -- concerning your Operating System (Version, Distribution, Language) > -- concerning your LibO localization (UI language, Locale setting) > > May be you want to test <https://www.libreoffice.org/get-help/bug/> for > submitting bug reports (Available since LibO 3.5)? You reach that Bug > Submission Assistant via LibO menu 'Help -> Feedback / Bug Report'. The > assistant will collect and insert such information automatically. > > @Michael: > Please set Status to ASSIGNED and add yourself to "Assigned To" if you > accept this Bug or forward the Bug if it's not your turf I take it that you are in possession of the docx document in question and that the way LO should display it after open is sufficiently documented in the attached pdf-file. I can add that my platform is linux amd64, fedora 16 flavour, LO version 3.4.6 release. I can't see that you need more info in order to deal with the bug. But if you need me to run any diagnostics on the document in my environment, please let me know.
several issues with this file on OSX as well. So platform > All.
** 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.0.0.5 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-09-03
Still doesn't match the PDF. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: b216cc1b8096eb60c27f67e8c27b7cd756c75e38 TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-11-12_00:06:20 Locale: fi-FI (fi_FI)
When this bug was created, it looked awful. From 4.2.3 it looks differently. Although this is still not correct, I'll close this one as WFM referring to the original issue and open a new bug, mostly because of lengthy comments and repeating.