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


Hi :)
Nice to see these got fixed before almost anyone knew there was even a problem and waaaay before 
AOO dealt with the issues! :))
Good work and congrats to the devs, yet again :)
Regards from 
Tom :)  





________________________________
From: Cor Nouws <oolst@nouenoff.nl>
To: Girvin R. Herr <girvin.herr@sbcglobal.net> 
Cc: Tom Davies <tomdavies04@yahoo.co.uk>; Tanstaafl <tanstaafl@libertytrek.org>; 
"users@global.libreoffice.org" <users@global.libreoffice.org> 
Sent: Friday, 26 July 2013, 22:54
Subject: Re: [libreoffice-users] Attempting to open any Microsoft XML document causes General I/O 
error after upgrade to 4.1


Hi,

Girvin R. Herr wrote (26-07-13 22:57)
FWIW:
I do not know the correlation of versions between LO and AOO, but today
I got the following two security reports from the AOO users forum:

FYI:
http://listarchives.documentfoundation.org/www/discuss/msg09642.html

Cheers,
Cor

-- 
  - Cor Nouws
  - http://nl.libreoffice.org
  - The Document Foundation Membership Committee Member



-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

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.