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


Let me start off by saying, I don't know how many times I coded something to fix one thing, worked on it for hours, that despite not seeing other errors, I fixed the thing I started out on.

That said. An amazingly simple test is to print the document with the old version and the new version, overlap them, hold it up to a window or put it on a light table. Objects not matching are much easier to see and, after 12 hours, I just might be mentally capable of actually seeing them.

I am very grateful and respect all working with LIbreOffice and this is not a slight. Do not misunderstand me.
Just what works for me.

If the same thing could be done on screen, it would be wonderful.
New version: Top layer 50%, Old version: bottom layer 75% transmissive.

This assumes locked-down test files. The other error I've tended to make is thinking I put a test file back the way it was instead of opening a fresh copy of the test file to check how I did.

It's not being lazy, just human and tired.

On 2/25/2013 2:46 PM, Joel Madero wrote:
On Mon, Feb 25, 2013 at 11:38 AM, Tanstaafl <tanstaafl@libertytrek.org>wrote:

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?


I didn't read the whole thread as I just have a lot on my plate but being
involved with QA I have a few points;

1) are these reported as bug reports?

2) is it one document or all documents?

then please note:

3) Writer and Spreadsheet account for about 75% of our use base (if you
look at number of bugs reported against writer and spreadsheet you'll get
an idea of how popular they are). Because the vast number of our developers
work for FREE we have to prioritize and get to bugs that impact the largest
number of users. We have very few developers who know the presentation
code, those ones do a tremendous amount of work and should be thanked by
everyone for the service they provide.

4) If you want to contribute (either by developing, helping QA or giving
money) it may help get bugs squashed faster - there are plenty to go around
;)

Best,
Joel




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