Hi all,
To be honest, I think we don't have the (wo)man power to maintain
translations for two branches.
It would be better to concentrate on AOO42X and to export translations
to the source on a regular base.
E.g. we now have a complete Ukrainian UI on Pootle, but I cannot build a
test version, because the translation is not in our code.
Regards,
Matthias
Am 13.06.22 um 06:40 schrieb Peter Kovacs:
>
> Am 11.06.22 um 14:54 schrieb Arrigo Marchiori:
>
>>> We could then think of a Version Mapping and a back push translation
>>> system.
>>> This is just a crazy Idea at this moment, to manage the string changes
>>> between Versions.
>> What do you mean exactly?
>>
>> I would expect l10n-savy developers to push changes from the Pootle
>> development repository into AOO41X or other branches, at appropriate
>> times (for example, before a beta release).
>
> I use 41x and 42x as an example. The amount of Strings used in 41x and
> 42x are different. The PO files do not match.
>
> And we will have that also in future. The way we are developing
> currently that we have one productive release and we build one
> development release, leads to the point that we might have 2 releases.
>
> I would like to try to have an auto backport script the creates from
> the development branch PO files PO files of the older version.
>
> That is is the Idea at least
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
smime.p7s
Description: S/MIME Cryptographic Signature
