Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index



One other thing...

Are the problems you are experiencing happening with just this one
document? Or does it happen with multiple other documents?

I haven't had time to test any other, but I suspect this is not the only 
one.

Were the problem documents created originally in LibO (or OOo)?

To the best of my knowledge with an early version of OOo.

I've been using LO, OOo, SO, etc. since it was called StarOffice 5.0, 
btw.. Impress (or what it was called back then) in StarOffice 5.2 was 
very stable and did everything I needed it to do in terms of 
presentations... Good old times :-) Since then every major release had 
new bugs that made Impress unusable and I had to wait or the .1 or .2.

What format are the documents? Ie, are they .odp? .ppt? .pptx?

ODP.

All the best,

Stephan





--
View this message in context: 
http://nabble.documentfoundation.org/Why-is-Impress-screwed-up-with-EVERY-release-tp4039942p4040207.html
Sent from the Users mailing list archive at Nabble.com.
-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.