[Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out

Petr Mladek <pmladek -AT- suse.cz>
Mon, 28 Feb 2011 11:46:03 +0100

Hi Andreas,

Andreas Jaeger píše v Po 28. 02. 2011 v 09:49 +0100:

The transition from OpenOffice.org to LibreOffice still has a few minor 
documentation blips but more importantly, users should be cautious. The raft 
of new functionality has created a few specific issues, such as loss of data 
in tables. Though not quite ready for the production environment, user 
feedback is critical for smoothing performance and reliability.


I am not aware of any data loos in tables. Could you please be more
specific? Is there any bug number?


Best Regards,
Petr

Context

[Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Petr Mladek
- Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Andreas Jaeger
  - Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Marc Paré
  - Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Jos Poortvliet
    - Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Michael Meeks
      - Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Jos Poortvliet
        
        Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Helen South
- Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Andreas Jaeger
  - Re: [Libreoffice] [opensuse-announce] openSUSE 11.4 RC2 Steps Out · Petr Mladek

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.