fvtt-localization

Foundry VTT localization is implemented by creating language files like lang/en.json with namespace keys and calling game.i18n.localize or game.i18n.format in your module code. You integrate these string keys into Handlebars templates and the module manifest to render multilingual UIs.

The best way to structure Foundry VTT i18n language files is using JSON files with hierarchical namespace conventions. You define keys like MODULE.Title and MODULE.Label in lang/en.json, ensuring consistent string key naming and integration with the module manifest for seamless translation loading.

Yes, Foundry VTT supports pluralization through the game.i18n API. You use game.i18n.format with specific localization patterns in your language files to handle plural forms, ensuring your module or system UI correctly displays singular and plural strings across different languages.

To apply i18n to Handlebars templates in Foundry VTT, you use template localization patterns to bind language file string keys directly within the template HTML. This approach ensures that common UI elements and dialogs automatically render translations without requiring manual string replacement in the JavaScript logic.

You use game.i18n.localize when you need to fetch a simple translated string by its key, and game.i18n.format when you need to inject dynamic variables or handle pluralization within the translated string. Both methods pull from your defined language files to populate UI text.