| Summary: | Image position changed when anchored as character, with ODT document | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Maxime THEPAULT <maxime> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 4.0.2.2 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: |
Screenshot of text aligned
Screenshot of text and images that have moved a doc without suprise ODT document with the bug |
||
|
Description
Maxime THEPAULT
2013-04-01 07:49:21 UTC
Hello Maxime, I think if you have those issues with anchorage as character and position images change? it's time to think anchorage to paragraph, which is more flexible. But provide a little sample will be better in order to be more explicit. Thank you, Jacques Guilleron Created attachment 77299 [details]
Screenshot of text aligned
I done that screenshot, I continue to write my text and add images at the end of the file, and I save and close ODT file.
Created attachment 77300 [details]
Screenshot of text and images that have moved
I open again the ODT file, and sometimes, the text and / or images have moved.
Hi Maxime, Did you try to insert before the last sentence a manual break by Insert > Manual break > Page break ? Also because you are at the end of page, see in your paragraph settings, particularly Format > Paragraph > Text Flow > Options > Orphan control or Widow control. It's hard to tell you without the document itself what is convenient for. Have a nice day, Jacques µGuilleron All my settings are default, and before or after a PNG image, I just use "Enter" key of my keyboard, nothing else. If you try to create an ODT file with some text, images, save and close it ; after you open that file again, and I hope you will find same surprises that me... Created attachment 77393 [details]
a doc without suprise
Hi Maxime, So do I. You have some text and images and I have no issue when I reopen it. Have a nice day, Jacques Guilleron In you ODT file, image is anchored "at character" not "as character". In french : j'utilise l'option "comme caractère". Also, my ODT docs are long, for example 20, 30 or 40 pages, and I see often that bug. Thank you ;) Created attachment 77399 [details]
ODT document with the bug
Hi Maxime, Thank you to provide this sample. I don't reproduce but I understand this can happen. LO use templates to provide documentation. Can you see here: https://wiki.documentfoundation.org/Documentation/Development#Contributors.27_Guide especialy Producing-LO-userguides.odt how this is done. You can also use http://fr.libreoffice.org/forums/ in order to get a better answer. Those lists are made for you. Have a nice day, Jacques Guilleron I understand... but it don't solve the bug. Do you think LibreOffice coders will try to find and fix it ? If not, I will try with anchorage as paragraph ;) reproducible with LO 4.0.2.2 (Win7 Home, 64bit) Steps done: Step 1: Open the attached document with the bug Step 2: Go to page 26 and check the alignment to assure that it is like the attached "before" screenshot Step 3: Save under a new name and close LO Step 4: Open the saved file and go to page 26 to check the alignment Result: No changes. Everything is fine as before. The difficulty is that it's not systematic... For example : I work few minutes or few hours, all is aligned, but the next day I check and it's not aligned. It's not only with one operation, often it's ok, but with many operations, at the end the alignment changed. Thank you for your help ;) Hi Maxime, A possible cause for your trouble could be, in your page Format, Use dynamic spacing, which allow LO to use spacing between header or/and footer. Can you try, when this happens, to uncheck this feature and see if this fix your issue? Thank you, Jacques Guilleron Hi, I tried that with few documents, for now it's ok. But, I didn't changed a lot of documents, I will give new lessons in the end of 2013. So, I think the bug is "solved" at this time, and I will try more documents later. Thank you ;) Please avoid to place bug on fixed if one only have workaround. Reopening it as bug 80287 ... |