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


We would like to get some idea of how much time would be reasonable for the language teams to get notice of the completion of the global "3.7 Features and Fixes" page to allow you for translation?

If, for example, the "3.7 Features and Fixes" page was ready for translation 7 days before the official release of LibreOffice 3.7, would this leave you enough time to translate? Would you need more time than this?

We are just trying to see if we could coordinate more language communities to complete these pages and ready by the official release dates.

FYI, I am involved in completing the features pages on the global site and usually get an OK from the devs to start on working on the new release page when the version is in final RC version.

Any feedback on this would be appreciated.

Cheers,

Marc

--
Marc Paré
Marc@MarcPare.com
http://www.parEntreprise.com
parEntreprise.com Supports OpenDocument Formats (ODF)
parEntreprise.com Supports http://www.LibreOffice.org


--
Unsubscribe instructions: E-mail to l10n+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/l10n/
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.