Date:
prev next ·
Thread:
first prev next last
Hi Olivier,
On Tue, Dec 31, 2019 at 8:10 PM Olivier Hallot
<olivier.hallot@libreoffice.org> wrote:
Actually, I broke the rule of not splitting sentences into pieces, which
is a bad practice translation-wise. My bad.
%PRODUCTVERSION is a dynamic string that is updated each release, so it
doesn't serve to the purpose.
You could still have the strings translated with embedvar, couldn't you?
In worst case scenario you'll have as many strings as there are
versions (with only benefit that translators can not accidentally
change the version itself), but variable definitions can be nested, so
maybe it is possible to use variable id "productversion" in the
translatable string, and have something like <variable
id="productversion" localize="false"><variable
id="setmeaccordingtocontext" localize="false">actual
version</version></version>?
ciao
Chrisitan
--
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] Composite string in Help · Christian Lohmaier
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.