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

Hi :)
I am not sure if people are aware but under Sun a lot of bugs just got ignored or left to rot 
because the aim at that time was stability.  If a bug is known about and still exists in a new 
version then that qualifies as being "stable".  Unstable is where you can't rely on long running 
bugs still being around.  If you are not sure whether something has been fixed or not then it 
really means the thing is unstable.  Companies using the program may have written work-around or 
patches that they applied each time to each new release but if a particular problem had been sorted 
out in a newer version then should such a company apply their patch or not!  So, Sun wanted 
"stability" so that companies could rely on all the problems being well known.

Hmm, does that sound a tad bitter?  I wasn't even around for that.  I used Go-oo without even 
knowing that it wasn't pure OOo for the last couple of years that OOo was under Sun.  Before that i 
was an MS fanboy.  

Under TDF the main aim has been to declutter all the code, streamline it, remove old outdate 
comments and translate the remaining ones into English.  Also re-writting chunks done in weird 
languages, such as Java, in order to consolidate it  into just 1 language throughout and generally 
de-spaghettfy it.  At the same time they have also managed to add in 'new' functionality to help 
bring the program out of the late 90's and well into this century.  They've also fixed quite a lot 
of bugs although mostly that has been to try to make it compatible with the latest changes in the 
MS formats.  I think they have done a remarkable job.  

Now it should be easier to address individuals bugs.  Many of which have probably just dropped out 
due to the de-spaghettifying.  

You could help by test-driving the latest beta-release each time and adding a comment to your 
bug-report to let people know that it still exists.  if you leave bug-reports  until after release 
then less people will be looking into it.  Pre-release catches the attention of the most devs.  

I don't think it's fair to blame TDF for the failures of Oracle or Sun and it's not fair to assume 
that just because your pet peeves haven't been sorted by Sun that they are not going to be sorted 
under TDF.  
Regards from 
Tom :)  

From: Ken Springer <>
Sent: Sunday, 5 May 2013, 13:49
Subject: [libreoffice-users] Re: Paragraph styles

On 5/5/13 2:35 AM, Milos Sramek wrote:
Dear Ken,

could you please post numbers of these bugs here? The topic sounds to be

Dňa 05.05.2013 00:32, Ken Springer wrote / napísal(a):
As I noted in private email, LO still has not assigned two bugs I
filed to anyone yet.  They are classified a low priority.  As I
mentioned, the issues are *not* low priority to me, so if they don't
want to fix them, I'll pay for a program where the developers do care
to fix the low priority issues.

Will wonders never cease... The first one has been assigned to someone. 

Maybe there's hope after all, as I've got a list from long ago that I 
never bothered to file as these were never addressed and assigned, so I 
never bothered.


Mac OS X 10.8.3
Firefox 20.0
Thunderbird 17.0.5

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.