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


Hi Valter, *,

On Sat, Nov 23, 2013 at 1:21 PM, Valter Mura <valtermura@libreoffice.org> wrote:
In data giovedì 21 novembre 2013 21:49:57, Andras Timar ha scritto:

could you confirm me the package migration is from 4.1 to 4.2 ?

If the announce didn't make it through, then let me know - as gmail
user I don't notice when mails don't make it to the list..

Migration copied libo_help/ui to libo41_help/ui - and 4.2 took the
libo_help/ui ones as well, but did update it against the templates
that were updated for 4.2

I'm currently working on an important revision of the help, indipendent from
the translation, and I need to know if I can safely continue this revision in
4.2, leaving 4.1 in its present state.

4.2 can be used, however for 4.1 I did run it against the updates that
occured during break of string freeze on 4-1 branch not long ago.

If you did trigger the manual update and fixed the strings (mostly
changes to the xml-attributes, but also new documentation for
date/time related functions in base.

ciao
Christian

-- 
To unsubscribe e-mail to: l10n+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/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.