Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | embedded pictures loses their top spacing | ||
---|---|---|---|
Product: | Writer | Reporter: | balazsa <attila.balazs> |
Component: | ui | Assignee: | michael.ruess |
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | OOo 1.1 RC5 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | 17567, 18732 | ||
Issue Blocks: | |||
Attachments: |
Description
balazsa
2003-09-26 08:53:26 UTC
please attach a document that shows this error reassigend to jw Created attachment 9828 [details]
when you open the file you will see the image in line with the paragraph above however its top spacing property set to 3mm when you change the value (even with 0.1mm) the picture will jump into its proper place
A good example of this is when you embed a picture in the header and SAVE the file as a WORD document. Close the document and then open it back up. The header area losses it's spacing and scrunches the image. In addition the image seems all messed up afterwards. I would say this is priority 5 not 3 After tweeking this a little more I found that if I use a jpeg file instead of a gif file then the image will show true after saving, closing and reopening in Word format. To stop the header from reducing down, in Page Style I had to uncheck Auto Fit Height and Use Dynamic Spacing and Adjust to the right size -- a very tedius exercise. BUT I was able to get the results I needed. confirmed on OOo1.1 reassigned to od set status to new set os to all set target to OOo2.0 accepted. Defect will be fixed by the internal re-work and improvement of the Writer fly frame object positioning algorithm in internal cws swobjpos02. fixed in internal cws swobjpos02 OD->MRU: Checked in internal installation set of swobjpos02 - please verify. Checked fix with internal CWS swobjpos2. Verified. Fix will be part of OO 2.0. Checked with OO 2.0 snapshot build 680m35. Closed. |