On 04/05/11 12:51, Dotan Cohen wrote:
On Mon, May 2, 2011 at 15:24, Joep L. Blom<jlblom@neuroweave.nl>  wrote:
Tom,
Thanks for your quick reply.
Sorry, that I didn't mention my soft- and hardware.
AMD Phenom II Ubuntu Lucif (10.4) LO  libreoffice-3.3.2.2.
The file is not very confidential: an invitation for a party.
I will mail it to your personal E-mail address with the attachment in a
moment.
Joep
Please send te document to me as well. I will file bugs on the
applicable portions of the document.
I would also appreciate if you comment on this very relevant Ubuntu
bug regarding LO/MSO compatibility:
https://bugs.launchpad.net/ubuntu-website/+bug/773243
Thanks.
Dotan,
Thanks. I don't think it helps to add a "me too" to the claim of ubuntu 
which is not correct. I don't think it is a fault of ubuntu but of MS$ 
who tries to monopolize the office field.
I can send you the file to your private mail-address but see the mail of 
Tom Davies who suspect -as I do also - it is a MS$ trick which of course 
is extremely stupid as older MSO versions cannot read the file as well.
Joep
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-users] .docx can't be read (continued)
 
  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.