In 4.0.2 everything worked fine. In 4.0.3.3 suddenly a newline is added after each picture. Resulting in a separation of the picture and caption after every save and reopen.
Running Lubuntu 12.04 64Bit
Sorry again: Running Lubuntu 12.10 64Bit
Hi Etienne, thanks for the report. Can you pls attach a test document? regards, Cor
Created attachment 79798 [details] odt file that remains stable
Created attachment 79799 [details] doc file that has a newline after picture It seems that this bug might only be triggered if the picture was set to "in line with text" at the wrapping setting of MS Word. This is the LO setting "as character" for the anchor
thanks Etienne. I can partly confirm: - open .odt in 4.0.3 - save as .doc - open .doc again: extra line is added - open .odt in 4.0.2 - save as .doc - open .doc again: extra line is nót added however... when I open the .doc that you attached in 4.0.2, I see the extra line too...
Dear Cor, thanks for checking. I understood that the newline is added when saving in 4.0.3. The attached doc was already saved in 4.0.3, thus has this newline already in the file.
thanks again! set some values for the bug
Created attachment 79867 [details] odt file that ads newlines in footer after total_pages, after filnename and again after the graphics The newline not only is added after a graphics, but also after some fields such as: * total pages? * filename This can be reproduced when saving the Newline_in_Footer as .doc
Miklos - IIRC you and/or Cedric were looking at something like this ? :-)
*** Bug 65080 has been marked as a duplicate of this bug. ***
*** Bug 65104 has been marked as a duplicate of this bug. ***
I also confirm. LO 4.0.3 on Windows. It is very annoying when each time I open the document I must delete extra new lines multiplying all the time after filesave! I encountered problems with pictures and footers. When You close/open the document several times the footer becomes half a page size.... I set high priority because it always destroys the document.
This isn't just when saving as a .doc file; it applies to .odt as well.
(In reply to comment #13) > I also confirm. LO 4.0.3 on Windows. It is very annoying when each time I > open the document I must delete extra new lines multiplying all the time > after filesave! I encountered problems with pictures and footers. When You > close/open the document several times the footer becomes half a page > size.... I set high priority because it always destroys the document. I have same problem as Piotr with footers, at least when saving in .doc format.
David - It's not about the footer but new line is created after fields. Since You probably have <page number> field in your footer it is so. I also noticed that some work around is possible because it happens mostly when field is the last character. So try to enter some character after page number for example "- page number -" and maybe it will help.
*** Bug 65538 has been marked as a duplicate of this bug. ***
*** Bug 65540 has been marked as a duplicate of this bug. ***
Created attachment 80583 [details] Three Screenshots
If a footnote is placed at the end of a paragraph and the document is saved as a Microsoft Word 97/2000/XP/2003 document, and the document is then opened, a new empty paragraph has been inserted after the footnote. If this document is saved as a .doc again, then another empty paragraph is inserted. See previously attached jpg "Three Screenshots." This does not happen when the document is saved as an ODF Text Document (.odt). My only work-around is to insert some spaces after the footnote number in the body of the text, and then select those spaces and do: Format: Character: Position: Normal.
(In reply to comment #16) > David - It's not about the footer but new line is created after fields. > Since You probably have <page number> field in your footer it is so. > > I also noticed that some work around is possible because it happens mostly > when field is the last character. So try to enter some character after page > number for example "- page number -" and maybe it will help. Thank you Piotr. I tried your workaround and it works perfectly. Obviously not ideal, but it will help alot until this bug is fixed.
*** Bug 65950 has been marked as a duplicate of this bug. ***
*** Bug 66375 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 66165 ***
*** Bug 67761 has been marked as a duplicate of this bug. ***