Other strange translation strings

[Tout]

There is strings I believe to be related with naming location but I do not clearly understand how manage them. I try to read english.cfg and even mapgen.cpp. I imagine the correct translation for

#: data/translations/english.cfg:174
msgid "$name|ham,$name|ton,$name|field"

is simply

msgstr "$name,$name,$name"

But I need more information.

[yeti]

I imagine the correct translation for

#: data/translations/english.cfg:174
msgid "$name|ham,$name|ton,$name|field"

is simply

msgstr "$name,$name,$name"

It may be quite the contrary.

Normally, what's before `|' is a prefix making the msgid unique, and what's after `|' is the actual message to translate -- when sgettext() is used (see gettext manual). However, BfW uses `^' for this purpose (`TitleScreen button^Tutorial') so who knows. There's no way to make an appropriation from a name algorithmically in my language anyway... <sigh>

[sanna]

I believe that this is a formula for creating place names, using a name from names.cfg i combination with the strings after |. These strings predate gettext, but I'm not sure if they in fact are used.

[cedric]

There is strings I believe to be related with naming location

Right. So far we've not found an easy way to turn them into french-sounding location names. We might just let them untranslated.

One of the problems being that the base names are too much biased towards english. Not sure it is worth feeding locale-based names to the generator, though.

--
Cedric