Date: prev next · Thread: first prev next last
2022 Archives by date, by thread · List index


it is great that there is now a solution to invoke Calc-Function names
at Wikipages. I have written after I asked in August about the place
where I can find the files where the calc functions are translated a
program that extracts out of the files the strings. It creates one
CSV-File per language where a file with strings for Calc-Functions
exists. You can find the CSV-Files and the program at this page.

From my point of view it is great if it is possible to copy a function
example from a Wikipage or a documentation page into calc. In Germany
usually the semicolon is the separator and in other countries it is the
comma in functions. For strings there are also different characters
used. It is the " and the '. Does the separator depend on the language
version or on the settings of a user. Im working since more than two
years at program that converts Spreadsheetfunctions into source code.
With this program if only parts of it are used it is also possible to
transfer a function from one language into another one and changing
through that the separator of function arguments and for strings and
also the notation for a cell from the A1-Format where a cell address
consists out of letters and number into a R1C1-Format where the column
and the row are numbers. Replacing is propably for the examples accurate
enough but it is theoretically possible that a string contains a name
that is also a function name. What will you do with the mentioned cases
where separators are different depending on a criteria I dont know yet.
Will this be a local translation work or is there a possibility to find
it out depending on the language and create a automatically solution to
use the most common one.



Am 21.10.2022 um 18:35 schrieb sophi:
Le 21/10/2022 à 16:37, Ilmari Lauhakangas a écrit :

during LibreOffice conference 2022 I had a conversation with an
Italian translator. He said it would be nice to import Calc function
name translations into the translation memory of the wiki to speed
things up. I started thinking that it would be even better to
automatically get the correct translated name using a template or a
widget. I quickly understood a template would not be practical. A
widget would require modifying the page content with Javascript,
which is always a bit awkward and also slows down the page load.

While researching the topic, I ran into an extension that enables the
use of Lua programming language to have essentially a much nicer
template syntax:

I set up a local MediaWiki instance to develop the Calc function name
module and now Guilhem kindly enabled the extension in TDF wiki.

The module is called in wiki content like so:


It calls the module, a function inside it and passes arguments for
the Calc function name and the language code. Conveniently the
{{#translation:}} magic word allows us to automatically pass the
correct language code.

The module code can be examined here:

I will gradually put the module to use in the coming weeks. I have a
Firefox Greasemonkey script to automate replacing the names in
content when editing an article.

Using the module will allow removing many repeating strings from
translation. These function strings which occur on their own are
usually in the beginning and end of the Calc function articles as
well as within tables showing examples.

When a function name occurs inside a paragraph, any existing
translations will be marked as outdated. It is not necessary to copy
& paste the module invocation syntax to the existing translations in
this case. It is enough to just confirm the already translated

Steve is working on updating articles, but he does not need to worry
about the module syntax. I will take care of everything when I
eventually mark the new articles for translation.

As the first tries, I changed these pages:

As mentioned, when you see outdated translations in your language for
the ABS article, just confirm them, no need to copy the module syntax.

I will wait for a bit before continuing, so let me know if there are
any issues. I will also reach out to individual translators, who
already worked on the articles.

That is really great, thanks a lot Ilmari for your work on it and
implementing it so quickly :)

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


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.