Is it safe to use .islu translation files in Inno Setup for all languages?

Question

I\'m using Inno Setup for my open source project WinSCP.
So far I\'m generating Inno Setup .isl translation files from our project-specific translation file

Answer 1

After few months of using this, I can confirm that adding the UTF-8 BOM and using the .islu extension for all Inno Setup translations seems to work well.

---

The .islu files are documented since Inno Setup 5.5.9:

If no code page currently exists for the language, set LanguageCodePage to 0, use a special .islu extension for the language's file, and encode this file as Unicode. Note: this makes your language file unusable by Non Unicode Inno Setup so only do this if really needed. Also note: a LanguageName setting in a .islu file does not need to use the special "<nnnn>" encoding mentioned above.