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


Andrea Pescetti píše v Po 28. 02. 2011 v 20:09 +0100:
Marc Paré wrote:
If this is an official part of the OpenSuse project and if it is not 
based on facts I would like to see a retraction on their part. I have no 
idea from where they got their information.

I have just got the information that it was based on
https://bugzilla.novell.com/show_bug.cgi?id=664816. It was another
duplicate of a bug that has been fixed a month ago.

So, the application is correct. We just need to better take care of
duplicates and improve communication inside the openSUSE project.

I must say I've seen, in non-publicly archived Italian mailing lists,
reliable reports about problems with LibreOffice Writer documents
containing tables. So the information is not totally made up. The
"tables" the post refers to should then be read as "Writer tables", I
suppose.

The aforementioned discussions spawned the following bug submissions:
- https://bugs.freedesktop.org/show_bug.cgi?id=33866
- https://bugzilla.novell.com/show_bug.cgi?id=664516

        + these are duplicates of the bug that started all the rumour

- https://bugs.freedesktop.org/show_bug.cgi?id=34565

        + it is NOT a data loss; it is quite annoying but a workaround
          exists; it is openSUSE-specific; Cedric is just working on it
          and the fix will be in 3.3.2 release


Best Regards,
Petr


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.