Managing SIL and SIB Files in TsiLang Files Editor The TsiLang Files Editor is a powerful standalone utility designed to manage localization data for applications built with the TsiLang Components Suite. It allows developers and translators to edit translations without opening the IDE or modifying the application source code. When working with this editor, you will primarily interact with two file formats: SIL and SIB. Understanding how to manage these files effectively ensures a smooth, error-free localization workflow. SIL vs. SIB: Key Differences
Choosing the right format depends on your project structure and how you intend to distribute or translate your localization data. SIL Files (Text-Based) Format: Plain text files. Structure: Similar to standard INI files.
Merge-Friendly: Easy to track, diff, and merge using version control systems like Git.
Translators: Ideal for external translators who prefer lightweight text editors or automated translation tools. SIB Files (Binary-Based) Format: Binary storage.
Speed: Faster loading and saving times for exceptionally large projects.
Security: Keeps translation data hidden from casual viewing in text editors.
Packaging: Excellent for deployment when you want to bundle data into a single, compact file. Creating and Opening Files
The TsiLang Files Editor serves as a central hub for initializing and accessing your translation databases.
Creating New Files: Select File > New to generate an empty translation matrix. You can then manually define your target languages.
Importing Project Data: Use the TsiLang Expert inside your IDE to export string constants, form properties, and hardcoded text directly into a new SIL or SIB file.
Opening Existing Files: Select File > Open and use the file format dropdown to switch between .sil and .sib extensions. Managing Languages and Translations
The editor organizes localization data into a grid where rows represent source properties or IDs, and columns represent target languages. Adding and Removing Languages Use the Languages menu to add a new locale to your project.
Assign the correct locale ID (LCID) to ensure automatic language switching works correctly at runtime.
Delete obsolete languages to reduce the final file size of your deployment assets. Editing Content
In-Place Editing: Double-click any cell in the grid to input or modify text directly.
Multi-Line Text: Use the built-in multiline editor window for lengthy string resources or dialog messages.
Translation Memory: Leverage the editor’s dictionary support to automatically fill in recurring terms across different forms. Best Practices for File Management
Implementing a structured workflow prevents data corruption and streamlines collaboration with external translation teams.
Use SIL for Development: Keep your active localization files in SIL format during development. This allows your team to track translation changes alongside source code modifications in Git.
Compile to SIB for Release: Convert your final SIL files to SIB format before deployment if you want to optimize loading speeds and keep your localization files compact.
Automate Imports: Use command-line switches provided by the TsiLang Files Editor to automate the process of merging updated source strings into existing translation files during nightly builds.
Validate Regularly: Run the built-in validation checks to identify missing translations, mismatched format strings (like %s or %d), or corrupted character encodings before shipping an update.
If you want to tailor this article for your specific project, let me know:
Your primary development environment (C++Builder, Delphi, etc.)
The scale of your project (small app or enterprise multi-module suite)
Who manages your translations (in-house developers or external agencies)
I can add specific step-by-step tutorials or advanced configuration tips based on your setup.
Leave a Reply