Hello Creating a title page / text page file with two formats ("magazine" texte presentation) 1) the external border color changes to grey when selected to blue 8 2) The background image settings does not stay the one selected (juxtapose becomes fulfill) 3) Some margin values are changed on reopening. 4) on image deletion or moving undo does not work properly Regards JL
Could you attach any example documents to allow others to check on different system/build?
Created attachment 63275 [details] .doc file with the bug and .pdf file to show the right formatting Hello Here is the text presentation (in .doc) that does not keep the page formatting Two different page format. Saved with the format shown in the pdf and reopened the border color goes from blue 8 to grey and the text looses completely the image background. The bug occurs in the first page format And in the second page format . The pdf file shows the text in the right presentation. Regards JL
Agreed the size of the font is different (header)
I reduce this one to 1 problem. [Reproducible] with parallel installation of Master "LOdev 3.7.0.0.alpha0+ - ENGLISH UI / German Locale [Build ID: c7e559]" {tinderbox: @16, pull time 2012-10-03 05:46:26} on German WIN7 Home Premium (64bit). Steps how to reproduce: Open "formatbugword.doc" with LibO and a Copy of the document with MS WORD VIEWER Expected: look equal Actual: Font size for Link text in page heading - is smaller than for page body text in MS WV, - but much bigger in LibO. Already a prolbem sith LibO 3.3.3 and also with AOOo 3.4.1 (and OOo 1.1.5), so this one seems inherited from OOo. I can't reproduce the problem with a simple self created .doc from LibO 3.7.0 @flyingvjlh@gmail: Can you contribute some information how you created the .doc and may be attach a more simple document only for this page header font size bug? Please see <http://wiki.documentfoundation.org/BugReport#General_information> item 4! Can you please submit different reports for all problems you see referring to your test kit here due to <https://wiki.documentfoundation.org/QA-FAQ#How_to_use_attached_sample_documents_for_multiple_Bug_Reports>? Thank you! @Florian: <https://wiki.documentfoundation.org/BugTriage#Process> item 5 @Cédric: 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.
Restricted my LibreOffice hacking area
** 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.2 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-05-02
Confirmed. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58 Locale: fi-FI (fi_FI)
** 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
Worth noting is that the header starts with a 20pt carriage return, then two 20pt spaces followed by the 10pt link (www.lesoreilles.com) followed by another 20pt space. So, it isn't too surprising that LO displays everything in size 20.
** 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
Created attachment 163090 [details] formatbugword.docx: round-tripped by MS Word 2003 repro 7.1+ Worth noting that this docx version opens fine. This is what the page2 header looks like: <w:hdr> <w:p w:rsidR="006B0539" w:rsidRDefault="006B0539"> <w:pPr> #pararaph #1 <w:rPr> <w:rFonts w:ascii="Arial" w:hAnsi="Arial" w:cs="Arial"/> <w:sz w:val="28"/> <w:szCs w:val="28"/> <w:lang w:val="fr-FR"/> </w:rPr> </w:pPr> </w:p> <w:p w:rsidR="006B0539" w:rsidRDefault="006B0539"/> #paragraph #2 </w:hdr> So the first paragraph (in the header on page 2) has direct paragraph formatting applied, setting the size to 14 and font to arial. The second paragraph is just defaults, so it should be size 10 Times New Roman. VERY STRANGE that such a basic thing is not being done here...
Created attachment 163093 [details] charFormatOnParagraphMarker.doc: MSWord2003 created minimal example of what is causing problems with page2 header. This should be a one-page document with two empty paragraphs - one huge and one tiny. (In reply to Justin L from comment #9) > So, it isn't too surprising that LO displays everything in size 20. Actually, this part looks JUST FINE after it has been round-tripped first by Word 2003. So perhaps there is some flaw in the .doc format of this particular file. Unfortunately, the round-trip did not fix the header on page2.
OK - Lets focus this bug report on the problem discussed in comment 9, which comment 12 notes is "fixed" when first round-trippedy by MS Word 2003 (and thus reduced to trivial importance). Just ignore the hugely problematic page2 header bug, which is covered by meta bug 125905.
header3.xml contains (simplified - and *split hyperlink combined*...): <w:p w:rsidR="006B0539" w:rsidRDefault="006B0539"> <w:pPr> <w:jc w:val="center"/> </w:pPr> <w:r> <w:rPr> <w:rFonts w:eastAsia="Times New Roman"/> <w:sz w:val="40"/> </w:rPr> <w:t xml:space="preserve"> </w:t> </w:r> <w:hyperlink r:id="rId1" w:history="1"> <w:r> <w:rPr> <w:rStyle w:val="Hyperlink"/> </w:rPr> <w:t>www.lesoreilles.com</w:t> </w:r> </w:hyperlink> <w:r> <w:rPr> <w:sz w:val="40"/> </w:rPr> <w:t xml:space="preserve"> </w:t> </w:r> </w:p> Nothing about charstyle Hyperlink or DefaultParagraphFont which it is based on reset the character size. So only the normal paragraph style specifies the size the link should take. Walking away - way too complex and dangerous territory to risk for a trivial problem.
Created attachment 171013 [details] formatbugword_word2003.pdf: how it looks in MS Word 2003 The PDF from the zip confused me, because it looks just like LO 7.2+ shows it. But according to Word, the link SHOULD be a tiny size 10.
Dear flyingvjlh, 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