Fight Goblins, not Servers™

Thank you for contributing to The Forge's translation effort!

The Forge uses a combination of keys and gettext-like strings as translation keys.
Because we use different frameworks from Foundry VTT, the strings in this project may appear unusual. Please read through the instructions and examples given here below before starting your translations.
You can also contact us on our Discord or via [email protected] if you have any questions.

Available Languages

Because of the number of strings involved, we will only be translating into specific languages at this time.
Currently, these are English, French, Japanese, Spanish, and German. If you'd like your language to be supported, please give us a shout in the #feature-suggestions channel on our Discord.

Language Switching

It is possible to view The Forge's site in your own language, to see what a string looks like in its natural habitat.
To do so, follow these steps:
- Navigate to https://forge-vtt.com
- Open the browser's dev tools console with F12
- Type await Utils.api("profile", {"lang": "fr"});
- Finally, reload the page
You can replace fr with any of the other supported language codes: en, fr, de, es, and ja.

Interpolation

{{ and {{- are interpolation prefixes, and }} is an interpolation suffix.
Where you encounter these interpolation markers, treat the prefix and the suffix, and everything between them, as a word that should not be translated.
Make sure to keep the same prefix as the source string.
For example:
"The goblin ate my {{homework}}." -> "Le gobelin a mangé mon {{homework}}."
"The goblin ate my {{- homework}}." -> "Le gobelin a mangé mon {{- homework}}."

Component Interpolation

{ and } are component interpolation markers. They have the same rules as regular interpolation markers and can be a word or a number:{book}, {package}, or {0}, {1}, {2}, etc.
Numbers indicate that a numbered component will be inserted there. Treat them the same way you would treat regular interpolation markers.
For example:
"The {0} ate my {1}." -> "Le {0} a mangé mon {1}."
"The {creature} ate my {item}." -> "Le {creature} a mangé mon {item}."

Context

Sometimes it is useful to have different forms of the same string. In such cases, a specific _context will be added after an underscore at the end of a key. When you see this, use the context to inform your translation.

Plurals

Plurals are like a special context, where the context specifies an amount. For some languages, simply having a singular_one and plural _othertranslation is sufficient, but other options like _many, _few, _zero and more are possible.
Some languages may have more complicated plural forms than English. If a string doesn't translate well into one of the keys available, please let us know by commenting on that string.
For example:
"GOBLIN_one": "{{count}} goblin" -> "GOBLIN_one": "{{count}} gobelin"
"GOBLIN_other": "{{count}} goblins" -> "GOBLIN_other": "{{count}} gobelins"
"GOBLIN_many": "a lot of goblins" -> "GOBLIN_many": "beaucoup de gobelins"

Nesting

This is rare, but sometimes we reference one string from inside of a different one. This can be particularly helpful when combined with plurals.
$t( and )are the nesting prefix and suffix. If you encounter them, treat the prefix and the suffix, and everything between them (including other markers), as a word that should not be translated.
For example:
"There, in the distance! I see $t(GOBLIN, {\"count\": {{hordeSize}} })!" -> Là, au loin ! Je vois $t(GOBLIN, {\"count\": {{hordeSize}} }) !

Consistency

Please maintain consistency with the source language, English, as much as possible, and reference the accompanying glossary information to ensure consistency between components.