Hi Tuomas,
On Wednesday, 2022-09-28 16:01:16 +0300, Tuomas Hietala wrote:
There's an error I'd like to fix in Finnish translation of one of the
strings in librelogo/source/pythonpath. It seems to be one of the LibreLogo
keywords.
However, I wonder if changing the translation will break any existing
documents that use that keyword.
I don't know details, but I think it would break. It just looks like the
script text is processed.
Is there a locale-independent
representation in the file format that is decoupled from the UI
translations?
Doesn't look like.
I'm also interested in hearing what's the situation with regard to other
kinds of keywords, such as function names in Calc.
Completely different. Calc function names are stored using fixed English
or programmatical names in both ODF OpenFormula (ODFF) and OOXML. UI
translations of function names are only view and input related.
Make sure you don't translate to duplicated function names and use only
allowed characters. See also
https://bugs.documentfoundation.org/show_bug.cgi?id=128200
Eike
--
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
--
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
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.