i18n-translate

To translate Camunda Modeler plugin i18n strings, provide a target language code to generate locale files. The workflow reads German base files and writes translated JSON values to the target locale directory while maintaining exact keys, placeholders, and BPMN domain terms.

Filling missing i18n translations involves diffing existing locale JSON files against the authoritative German base. This process identifies missing keys and regenerates complete language packs by translating German values while preserving technical placeholders and structural formatting.

I18n JSON diffing compares your target locale file with the German base file to detect new or modified translation keys. It isolates untranslated strings and updates the language pack by translating only the missing values without overwriting existing valid translations.

Yes, you can preserve BPMN and DMN domain terms during Camunda Modeler UI translation. The translation process explicitly focuses on maintaining technical vocabulary and domain-specific terminology alongside exact JSON keys and placeholders to ensure consistency across all locales.

Yes, the Camunda Modeler translation workflow supports regenerating complete language packs. By using the provided translation process, you can fully regenerate locale files from the German base, ensuring all missing keys are filled and existing translations are synchronized.

I18n JSON placeholders break during Camunda Modeler plugin translation if target language values alter original placeholder syntax. The translation workflow specifically maintains exact placeholders and structural keys from German base files to prevent broken variable interpolation in the plugin.