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


On 12/04/2010 09:49 PM, Caolán McNamara wrote:

I wouldn't like to see too much effort spent on binfilter though.
I understand the point. On the other side, leting it behind generate a
lot of - not very useful - job when wanting to do global changes, like
the RTL_CONST... macro, or getting ride of old type /  classes,... ?

at http://people.redhat.com/caolanm/callcatcher/DEV300_m86/ (I cleared
I will have a look at it.

"desktop" myself recently, I should generate up-to-date lists for
LibreOffice master)
would be great

Which make me think: as new feature, for the next LibO release after
3.3, could it be that StarOffice file format are not supported any more,
....
Or do you intend to drop this in a quicker way?

A lot of people are of the view to delete the whole thing. I'd prefer to
move it out of LibreOffice entirely into a standalone project that

As user, I would prefer to still be able to read the file "natively",
even if I can't write / save it anymore. Nothing more boring than having
to search for an add-on... First you have to know it exits, find it,
install it... Far above the average user expectation. I have see a lot
of people getting confused, not able to read a file anymore, simply
going back to the older version, or using afterward another product, not
always noticing they are reading in one format and saving in another one!
regards

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.