firetongue
A framework-agnostic translation and localization library for Haxe, supporting TSV/CSV files, variable replacement, and font rules.
What is firetongue?
FireTongue is a translation and localization framework for Haxe that manages multilingual content through external TSV/CSV files. It solves the problem of hardcoding text in applications by providing a system to load locale-specific strings, handle variable insertion, and support complex grammar rules across different languages.
Haxe developers building games or applications that require support for multiple languages, especially those using frameworks like OpenFL or Flixel-UI.
Developers choose FireTongue for its framework-agnostic design, robust file parsing, and advanced features like redirect tokens and font replacement, which streamline localization workflows without locking them into a specific GUI library.
Overview
A translation/localization framework written in Haxe
Use Cases
Best For
- Localizing Haxe games for international markets
- Managing translation files in TSV or CSV format
- Handling dynamic text with variable placeholders
- Reducing duplication in translation entries with redirects
- Swapping fonts automatically based on locale
- Integrating localization with Flixel-UI for HaxeFlixel projects
Not Ideal For
- Projects requiring real-time translation updates without file reloads
- Teams that prefer YAML or JSON over TSV/CSV for translation data
- Applications needing out-of-the-box pluralization and gender support without custom flag design
- Non-Haxe developers seeking a cross-platform localization library
Pros & Cons
Pros
Works with any Haxe framework or standalone, using customizable file loading to avoid vendor lock-in, as shown in the README's initialization examples.
Supports variable replacement with <X> placeholders and redirect tokens <RE> to manage complex grammar and reduce duplication, enabling flexible sentence structures across languages.
Provides native language names and custom notes via index.xml, facilitating user-friendly locale selection interfaces without requiring GUI library dependencies.
Enables automatic font and size swapping per locale through fonts.xml configuration, crucial for handling international typography differences.
Cons
Requires strict UTF-8 encoding and precise TSV/CSV formatting with specific rules, which can lead to parsing errors if not followed exactly, as emphasized in the README's warnings.
Involves multiple configuration files (index.xml, fonts.xml) and a specific folder structure, increasing the learning curve and setup time for new users.
Lacks built-in support for pluralization or gender; developers must design flag systems manually for such complexities, adding overhead compared to more automated solutions.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.