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


Gordon,

Ignoring. But you might like to bookmark this handy link:

http://downloadarchive.documentfoundation.org/libreoffice/old/

When the development RC2 version is processed, it becomes to "release" notation.  

So folks using 4.0.5 release are using the same code base as 4.0.5.2, or 4.1.0 is using the code 
base of 4.1.0.4--the extra RC builds were needed at 4.1.0

Stuart

 

-----Original Message-----
From: Gordon Burgess-Parker [mailto:gbplinux@gmail.com]
Sent: Monday, August 26, 2013 3:18 PM
To: users@global.libreoffice.org
Subject: Re: [libreoffice-users] .docx file format disturb in libreoffice 4.0
Writer

On 26/08/13 21:15, Gordon Burgess-Parker wrote:
On 26/08/13 19:12, Tom Davies wrote:


i would still tend to go with the 4.0.5 because that 3rd digit, the .5, is
roughly the equivalent of "Service Pack 5".  The 4.1.0 has no service packs.
The 4.1.1 has 1.  So the 4.0.5 is more stable and less likely to have unpleasant
unexpected surprises.


So what is 4.1.05 - which is what I have...



Sorry, ignore!

--



-- 
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.