I have updated the "Variables and symbols in the UI files" part of the "UI and Help files Content Guide"

Hi Jesper, *,

Is <FILENAME> really a variable that will be replaced with something?
IIRC it's shown to user literally, and thus should be translated...

Best regards,
Mihkel
Estonian team

Hi Mihkel and everybody else,

I have not changed anything in that sentence, and I actually wondered
something similar when I saw it.

It is only mentioned once in the entire UI for 4.4, in this complete string:

<FILENAME>

Here is the search:
https://translations.documentfoundation.org/da/libo_ui/translate/#search=<FILE&sfields=source&soptions=exact

In Norwegian Bokmål and German it has been translated. In Swedish, French
and Danish it has not been translated.

It does not make much sense to put the string <FILENAME> up on Pootle for
translation, if it should not be translated, so that speaks for that it
should actually be translated – contrary to the instructions on
https://wiki.documentfoundation.org/UI_and_Help_files_Content_Guide#Variables_and_symbols_in_the_UI_files
.

Could someone knowledgeable on the subject tell us whether it should be
translated or not?

Jesper

On the other hand, there are variables like

<FIELDNAME>
<FIELDNAME1>
<FIELDNAME2>
<FIELD>
<LOGICOPERATOR>
<VALUE>
etc.

that really should not be translated.

This search reveals a few of them:
https://translations.documentfoundation.org/da/libo_ui/translate/#search=<F&sfields=source&soptions=exact&unit=28753831

So maybe the wiki should have said:

• *<X>*, where X is a word in uppercase letters, is *normally* a variable
which should not be translated. Some examples are <FIELDNAME>, <FIELD>,
<LOGICOPERATOR> and <VALUE>.
• *<FILENAME>* is NOT a variable, though, and you should translate it!

But let us get some input from people with knowledge on the subject. :slight_smile:

Jesper

Hi,

On the other hand, there are variables like

<FIELDNAME>
<FIELDNAME1>
<FIELDNAME2>
<FIELD>
<LOGICOPERATOR>
<VALUE>
etc.

that really should not be translated.

This search reveals a few of them:
https://translations.documentfoundation.org/da/libo_ui/translate/#search=<F&sfields=source&soptions=exact&unit=28753831

So maybe the wiki should have said:

• *<X>*, where X is a word in uppercase letters, is *normally* a variable
which should not be translated. Some examples are <FIELDNAME>, <FIELD>,
<LOGICOPERATOR> and <VALUE>.
• *<FILENAME>* is NOT a variable, though, and you should translate it!

But let us get some input from people with knowledge on the subject. :slight_smile:

It is hard to give rules when it comes to LibreOffice, which uses a
mix of technologies. <FILENAME> in backgroundpage.ui is a placeholder,
it will be replaced by the actual filename. It does not matter what
you write there (translated or not), it will be replaced. So it would
be better to make <FILENAME> non-translatable in the source (I've just
done it), and do not confuse translators with exceptions.

Regards,
Andras

Thank you for the clarification, Andras!

While it may be hard to make rules for these things in LibreOffice, I
believe we as translators do need some rules (I know that I do). So that is
why I am trying to improve the existing rules, even though it may be a hard
task. Also, being a new translator, I probably have a fresh look at things,
which I would like to use to improve the existing internal documentation if
possible.

Jesper

Hi Jesper,

Thank you for the clarification, Andras!

While it may be hard to make rules for these things in LibreOffice, I
believe we as translators do need some rules (I know that I do). So that is
why I am trying to improve the existing rules, even though it may be a hard
task. Also, being a new translator, I probably have a fresh look at things,
which I would like to use to improve the existing internal documentation if
possible.

Thanks for improving the guide. I wrote it for new comers and it's great
that you correct it where it was not precise enough.

Kind regards
Sophie

Thanks, Sophie!

Kind regards,
Jesper