Am 07.03.2026 um 21:43 schrieb Matthias Seidel:
Hi Pedro,
I think we plan to release 4.2.0 at some time, so cherry-picking
something that isn't ready would not be a good idea.
However, we could call the icon set "experimental". But this would
need discussion.
Regarding translation: The process is broken for years. At the moment
we are not able to update the translation.
Of course we could wait until it is working again...
you need to do various manual steps to integrate the translation into
trunk. And to update the translation from the trunk are other steps
needed to do.
The broken part is you can easy do something wrong resulting in more
work to fix the damage. Which describes a bit the situation.
My idea is to automate it, but i did not came around to do it and i
tried to win a friend for the task, but this did not result in any
progress. (yet)
I could do the following.
- get the latest translation into our repository.
- publish mechtildes guide and scipts.
- and someone tries to improve the guide locally.
the guide is written for the server. so some scripts may fail locally if
you do not install pootle too. (which is not covered in the guide.)
so currently you need some tech skills to get it to work.
Regards,
Matthias
Am 07.03.26 um 21:06 schrieb Pedro Lino via dev:
Can we merge the Pilot-Pirx-iconset branch into Trunk and cherry pick
to 4.2.0 to be included in Dev6?
Is it technically possible to update the translations for Dev6?
Best,
Pedro
On 03/07/2026 2:38 PM WET Matthias Seidel
<[email protected]> wrote:
Hi All,
Our last 4.2.0 Developer Builds is more than 2 years old...
https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev5/
Time for Dev6?
Although I still think that we should integrate updated translations.
Regards,
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
