Apache OpenOffice (AOO) Bugzilla – Issue 15643
automatically set the compatibility mode for documents written in OOo 1.0.1
Last modified: 2013-08-07 15:20:27 UTC
A slide created with Impress 1.0.1 does not look right in 1.1b2: Step to reproduce (see attachments) - open sxi attachment in 1.1b2 Expected result: slide should look identical in 1.1b2 and 1.0.1 Current result: see the screenshot for the many differences. (note: I filed bug 15642 for the greek/roman issue)
Created attachment 6902 [details] guilty sxi file
Created attachment 6903 [details] 1.0.1 screenshot (correct one)
Created attachment 6904 [details] 1.1b2 screenshot (incorrect one)
Reassigned to Christian.
set to new
In OOo1.0.1 we use the printer metric for the document (font) formating. This behaviour has been changed and now the documents are printer metric independent. To change back the default you must select 'Use printer metrics for document formating' in 'Tools/Options/Presentation/General/Compatibility'.
I close the issue.
I'll reopen this bug with a new summary. I am grateful to give me a way to set the compatibility mode, but I am just a user amongst tens/hundreds/etc. of thousands others. I reported the problem but imo, the majority of the other users will say: bah let's drop OOo, their format is not stable, one can not read document that have been written in 1.0. I think that when a document has been written with 1.0.1, the compatibility mode should be triggered, or the document should be converted. Word/PowerPoint is quite good to open old files. I know reopening bug is a bit like spam, but imho, it's a serious flaw . Of course, (I won't reopen it if you won'tfix it again)
I think Pierre is right. Please have a look.
I will have a look at whether the "use printer metrics"-flag is initialized with the wrong value for (slightly) older OpenOffice Draw and Impress documents.
I can not reproduce the bad layout of the second attached bitmap. This is due to our increasing the resolution of the printer independent rendering to 600 DPI or above (the exact id of that fix I can not remember.)
Do you have the id of the bug fix at hand that I mentioned above?
This issue is duplicate to issue 15437 Issue 15437 is fixed and integrated in OOo 1.1.1 I close this issue. Please reopen it if the bug still occures in OOo1.1.1. *** This issue has been marked as a duplicate of 15437 ***
I close this issue as duplicate to issue 15437