Hi Michael, *,
On Wed, Jun 10, 2026 at 2:07 PM Michael Wolf <milupo@sorbzilla.de> wrote:
So, the 2,609 strings are correct?
Correct as that indeed was a change that cause the strings to be
treated as new strings. (not the one linked initially, but
https://gerrit.libreoffice.org/c/core/+/206192 )
Seemed me too many, especially
because I am translator for two languages, I have to translate 5,218
strings then.
With changes like that where the same string should be reused/it isn't
the actual string that changed but surrounding information, you should
never assume to have to do it manually (when using weblate, if you're
not using LO's translation process but do it on your own you'll have
to deal with it yourself).
It was my bad for not realizing when I updated the templates last
time, but I honestly just didn't expect such a change to happen.
Anyhow, sorry for those who started reapplying the translations for
the affected strings manually, you should have had more
trust/confidence ;) Nobody wants to waste translators' time with busy
work like that.
ciao
Christian
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Re: [libreoffice-l10n] Really 2,609 new strings? · Heiko Tietze
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.