That's great, people which use master for translation will be our canary
birds!
If devs start changing caps, ', ... etc, please warn us so we can spam
them. :)
12.12.2014 u 11:54, Olivier Hallot je napisao/la:
On 12/12/2014 08:18, Sérgio Marques wrote:
Sorry, I don't get it. Now: 4.4 was created and translations from 4.3
appeared there.
Future: Which translations will appear in 4.5 when it is created - from
4.4 or from master? Translations of the same strings can differ between
them.
Yes me too. Shopie´s explanation make it even more difficult to understand
the procedure.
Since I do my own compilation, for me it will mean that all strings will
be updated periodically in pootle under the "master" branch. So I will
get the updates once in a day/week/month, for example.
The number of strings on a monthly basis are expected to be lower than
on updated once in a half-year for a major release.
Those who will translate the master branch can check the results with
the nighly builds.
when it comes to branch for a new release, a snapshot of the master
translation will be taken and named release X.Y. Then all translation of
the release follows. Like with developers, a fix in a translation on a
branch shall be fixed also in master branch.
This scheme does not means we will get less work, it means we will get
more time to translate a big, hopefully incremental, chuck of new strings.
--
To unsubscribe e-mail to: l10n+unsubscr...@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
