Strange `translatable' strings

[yeti]

I suppose these messages are not translatable(?)

Code: Select all

#: data/scenarios/tutorial/utils.cfg:13
msgid "{END_MESSAGE}"
msgstr ""

#: data/scenarios/tutorial/utils.cfg:21
msgid "{QUESTION}"
msgstr ""

#: data/scenarios/tutorial/utils.cfg:25
msgid "{ANSWER}"
msgstr ""

#: data/scenarios/Eastern_Invasion/Northern_Outpost.cfg:337
msgid "{M}"
msgstr ""

Beside that, Elivsh Archer, Aveneger, Marksman, Ranger and Sharpshooter descriptions are not translatable now, which is a shame as I've already translated them ;-)

[sanna]

I suppose these messages are not translatable(?)

Code: Select all

#: data/scenarios/tutorial/utils.cfg:13
msgid "{END_MESSAGE}"
msgstr ""

#: data/scenarios/tutorial/utils.cfg:21
msgid "{QUESTION}"
msgstr ""

#: data/scenarios/tutorial/utils.cfg:25
msgid "{ANSWER}"
msgstr ""

#: data/scenarios/Eastern_Invasion/Northern_Outpost.cfg:337
msgid "{M}"
msgstr ""

They shouldn't be translated! They are parameters to a macro. I guess that the translation would have to be handled from where the macro is called, not in the macro-definition, so the underlines should be removed at these places.

Beside that, Elivsh Archer, Aveneger, Marksman, Ranger and Sharpshooter descriptions are not translatable now, which is a shame as I've already translated them

Yes, underlines needed in these unit-files.

[Dacyn]

They shouldn't be translated! They are parameters to a macro. I guess that the translation would have to be handled from where the macro is called, not in the macro-definition, so the underlines should be removed at these places.

like this:

Code: Select all

#define MESSAGE MESSAGE
[message]
message={MESSAGE}
[/message]
#enddef
{MESSAGE ( _ "Translatable string")}

?
what should I do with the 'SET_OBJECTIVES' macro?

[yeti]

what should I do with the 'SET_OBJECTIVES' macro?

I must confess I don't understand WML much, maybe an equivalent of N_() is needed?

[isaac]

Yann, our Gettext lord, is already working in that, so don't worry, it will be fixed soon