Special cases translators ought to know?

Hello all,

JO3EMC made an interesting observation a few days ago in Weblate: "It appears that the translated word for each of STRPOOLCOLLBLAHBLAHBLAH must be unique." [1]

At least I was unaware of this requirement and it isn't mentioned anywhere in the wiki as far as I can tell. Now the question arises: are there other special cases like this that translators ought to be aware of? There's a little bit of information on the wiki [2], but I don't know how up to date or complete that is.

BR,
Tuomas

[1] https://translations.documentfoundation.org/translate/libo_ui-master/swmessages/en/?checksum=567eac4187d03720#comments
[2] https://wiki.documentfoundation.org/UI_and_Help_files_Content_Guide#Unique_terms

Hi *,

Now the question arises: are
there other special cases like this that translators ought to be aware
of? There's a little bit of information on the wiki [2], but I don't
know how up to date or complete that is.

Well, I wouldn't call them special cases, rather it is just hard to
not make a mistake due to the size of the project/amount of strings
there are.

Following restrictions apply/cause runtime issues if not met:
* Calc function names must be unique (e.g. *STRLIST_FUNCITON_NAME*)
* math symbol names must not contain whitespace
* Style names must be unique (e.g. STR_POOLCOLL*, STR_POOLNUMRULE*)
* the | symbol in windows installer strings - that is the one I count
as non-intuitive

ciao
Christian

Hi all,

Hi *,

Now the question arises: are
there other special cases like this that translators ought to be aware
of? There's a little bit of information on the wiki [2], but I don't
know how up to date or complete that is.

Well, I wouldn't call them special cases, rather it is just hard to
not make a mistake due to the size of the project/amount of strings
there are.

Following restrictions apply/cause runtime issues if not met:
* Calc function names must be unique (e.g. *STRLIST_FUNCITON_NAME*)
* math symbol names must not contain whitespace
* Style names must be unique (e.g. STR_POOLCOLL*, STR_POOLNUMRULE*)
* the | symbol in windows installer strings - that is the one I count
as non-intuitive

In addition to what Christian said (and is noted in the wiki), you
sometimes have interesting comments in the code, like there:
https://git.libreoffice.org/core/+/master/sw/inc/strings.hrc#302

To access those comments, click the link to Source string location in
the String information area of the Weblate editor. It's not for all type
of strings, but that can be of great help.

Cheers
Sophie