Coding in translations

[Gwork]

Hi,

Sometimes strings in the source-text should not be translated because they're used to replace with other stuff when displayed on screen.
The obvious one is $ followed with a string between curvy brackets {xx}.
But I wonder how this is for other markings I find: e.g. between square brackets [xx], between double underscores __xx__ and in html-like constructions: what should I keep as the original and what should I translate?

Regards,
Hans

[Gwork]

My findings on this subject:
<string> you should keep the string. it will be replaced with a picture
__string__ you should translate, it will become an italic string

But of course - sometimes strings refer to untranslated text in images - so it remains depending on the game situation.

[Tisaac]

Hi,

Sometimes strings in the source-text should not be translated because they're used to replace with other stuff when displayed on screen.
The obvious one is $ followed with a string between curvy brackets {xx}.
But I wonder how this is for other markings I find: e.g. between square brackets [xx], between double underscores __xx__ and in html-like constructions: what should I keep as the original and what should I translate?

Regards,
Hans

That's quite game dependant. In this case (Agricola), the only thing you should not translate are stuff inside <>, which the translation system should prevent you to do in theory.
The square bracket just means "use dominican font for this part of text"

[ufm]

Hi,

Sometimes strings in the source-text should not be translated because they're used to replace with other stuff when displayed on screen.
The obvious one is $ followed with a string between curvy brackets {xx}.
But I wonder how this is for other markings I find: e.g. between square brackets [xx], between double underscores __xx__ and in html-like constructions: what should I keep as the original and what should I translate?

Regards,
Hans

That's quite game dependant. In this case (Agricola), the only thing you should not translate are stuff inside <>, which the translation system should prevent you to do in theory.
The square bracket just means "use dominican font for this part of text"

Honestly, Keyflower translation was a mess.