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


Hi :)
I think the 3.3.2 should be fine.  Have you had any troubles so far?  
Regards from
Tom :)




________________________________
From: James Wilde <james.wilde@sunde-wilde.com>
To: users@global.libreoffice.org
Sent: Fri, 26 August, 2011 10:58:45
Subject: [libreoffice-users] Problems with Lion?

Running v3.3.2 on Mac OSX recently upgraded to Lion (10.7.1)

Lion has had its teething troubles, and I seem to remember seeing a comment in 
here about a problem with running LibO on Lion.  So far I've not had any 
troubles, but I was wondering.

Does it make any difference which version one is running?

TIA

//James
-- 
For unsubscribe instructions e-mail to: users+help@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
-- 
For unsubscribe instructions e-mail to: users+help@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.