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


On 2013-02-25 8:35 AM, Thorsten Behrens <thb@documentfoundation.org> wrote:
Stephan P. wrote:
Honestly, how does this happen? If nobody is working on Impress to even
check these absolutely basic things, be honest enough about it and drop it
from LO. But constantly, with every release, breaking things that worked
fine is plain ridiculous.

There is a quite a range of possibilities here - QA volunteers
focusing more on other applications, platform specific problems,
document-specific bugs etc etc. The best advice to give at this point
probably is: get involved with our QA team! E.g. it could be you
running a handful of regression tests, on your platform, with your
files, prior to releases.

One other thing...

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

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

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

--
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.