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

Mhh, I did not see your note as anything new. But Maybe I should have 
mailed that ;-) 
But ignored? Far from that. 

Cor, thank you for the reply.

In my mind it doesn't make any sense that the mailing lists are so self
contained that I have to guess in which one I have to post. 
And if I fail to post on the right list it will be either ignored or not
answered (which from the poster's point of view is the same...)
It doesn't also make sense that I have to subscribe to several mailing lists
when ONE forum would be enough. 

See the OOo wiki for analyses/ideas/tasks on Calc and performance. 
And also the LibreOffice dev list shows abundant signs of awareness that 
improvements on performance are very important.

It wouldn't cross my mind searching the OOo wiki, when I'm asking to the LO
community. I'm finished with the OOo community for a long time. They
had/have a serious attitude/communication problem which I hope doesn't
propagate to LO (and your answer shows that it's not ;) )

What puzzles me is that I can't find any logic that LO/OOo which is the
Office suite behind the ODF standard is in fact LESS efficient handling that
format than another FLOSS program...

View this message in context:
Sent from the Discuss mailing list archive at

Unsubscribe instructions: E-mail to
*** All posts to this list are publicly archived for eternity ***


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.