Languages

Want to help the FileFlows community and translate the application into additional languages? This guide will help you get started!

Translation Structure

Translations are split between the main application and individual plugins.

• Main application translations: Located in the en.json file within the Client/wwwroot/i18n folder on the FileFlows GitHub repository: [invalid URL removed].

• Plugin translations: Each plugin has an i18n folder within its repository containing translation files. For example, the translations for the Basic plugin are located here: https://github.com/revenz/FileFlowsPlugins/tree/develop/BasicNodes/i18n.

---

Translation Format

Translations are stored in JSON format, using the ICU Message Format for flexible formatting and localization.

For more information on the format, refer to:

• ICU Message Format: https://unicode-org.github.io/icu/userguide/
• https://github.com/jeffijoe/messageformat.net?tab=readme-ov-file

---

Adding a New Language

To add a new language:

1. Create a copy of the en.json file and save it with the appropriate two-letter ISO-639-1 language code.
2. Translate each string in the new language.
3. Delete any strings you don't want to translate to use the English defaults.

Tip

Missing translations will automatically fall back to English.

---

Submitting Your Translations

Once you've created your translation file:

• Create a pull request on the appropriate GitHub repository.

Or

• Post your changes in the FileFlows Discord support channel.

---

Contributing Tips

• Cultural awareness: Use culturally appropriate language and avoid offensive terms.

By contributing your translations, you're helping make FileFlows accessible to a wider audience!