One of the most powerful capabilities of the TsiLang Components Suite is its flexibility in how you store and manage translation data. For developers building multilingual applications with Delphi or C++Builder, understanding when and how to use external translation files – specifically .SIL and .SIB – can significantly streamline your localization process and enhance team collaboration.
In this post, we’ll explore how to take full advantage of TsiLang’s external file workflow, comparing the two file types, detailing runtime loading techniques, and sharing best practices for real-world projects.
By default, TsiLang allows you to store translations internally within your application’s .DFM files. This is convenient for simple or lightweight apps. However, for production-grade or frequently updated applications, externalizing your translations into separate files offers key advantages:
TsiLang supports two external file formats:
| Feature | .SIL (Text-based) | .SIB (Binary) |
|---|---|---|
| Format | Human-readable INI format | Compiled binary format |
| Editable by | Any text editor, SIL Editor | SIL Editor only |
| Ideal for | Version control, translators | Runtime performance, integrity |
| Loading Speed | Slower | Very fast |
| Data Integrity Checks | Basic | Strong |

.SIL files during development to ease collaboration and versioning. Before release, convert them to .SIB for better performance and stability.To begin using external files, use TsiLang Expert within your RAD Studio, Delphi or C++Builder IDE:
You can also merge files to preserve existing translations while incorporating updates.
We recommend the following way to load translations from the external files at runtime:
// be sure to adjust file path to the actual file!
siLangDispatcher1.FileName := 'MyAppTranslations.sil';
// or for binary files
// siLangDispatcher1.FileName := 'MyAppTranslations.sib';
siLangDispatcher1.LoadAllFromFile(siLangDispatcher1.FileName);
At the very first line we set-up the FileName property of the TsiLangDispatcher component. This will ensure that all forms created later at run-time will load translations from this file.
The second line loads translations to all currently created application forms.
This approach works seamlessly with TsiLangDispatcher, which handles synchronized language switching across all forms.
Our software products – Resource Builder, HelloApp Studio, SIL Editor, and Dictionary Manager – are examples of applications that follow the described workflow.
If you’re serious about delivering high-quality multilingual software, learning how to use external translation files in TsiLang Components Suite is essential. It empowers your team with agility, control, and performance – whether you’re localizing internal tools or shipping global apps.
Share this article
Your app’s next language starts here
Try every feature with your own project.
Fully functional trial. Keep your IDE running while your localized application runs.
Learn & connect
© 1998–2026 Igor Siticov, SiComponents. TsiLang®, Resource Builder® and SiComponents® are registered trademarks of Igor Siticov.
RAD Studio, Delphi and C++Builder are trademarks and/or registered trademarks of Embarcadero Technologies, Inc.