Extends Angular CLI to improve i18n extraction and merge workflow with normalized translation files.
ng-extract-i18n-merge is an Angular CLI extension that improves the extraction and merging of i18n translation files (XLIFF format) for Angular projects. It automates the process of updating target translation files when source strings change, manages translation states, and normalizes file output to ensure clean diffs. It solves the problem of manual and error-prone translation file management in Angular applications.
Angular developers and teams building multilingual applications who need a streamlined workflow for managing i18n translation files, particularly those using Angular's built-in i18n extraction tools.
Developers choose this tool because it seamlessly integrates with Angular CLI, replacing the default extraction builder with enhanced automation for merging and normalization. Its unique selling point is the ability to keep translation files consistently formatted and easy to review, reducing manual overhead and potential errors in the i18n process.
Extract and merge i18n xliff translation files for angular projects.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Intelligently adds new translations and removes deleted ones from target locale files while preserving translation states, reducing manual errors and effort as highlighted in the key features.
Normalizes translation files with whitespace collapsing and stable sorting, making diffs easy to read and review, which is core to the project's philosophy for better collaboration.
Offers extensive options like fuzzy matching, prefix-based ID filtering, and multiple sorting strategies, allowing fine-tuned control over i18n workflows as detailed in the configuration table.
Replaces Angular's default extract-i18n builder with minimal setup, enabling use of standard ng extract-i18n commands without disrupting existing workflows.
Upgrading between major versions (e.g., v1 to v2 or v3) requires specific migration steps and changes defaults, which can break existing configurations and necessitate manual adjustments.
With numerous options like prettyNestedTags, sort strategies, and context inclusion, setup can be overwhelming for teams seeking a simple, out-of-the-box solution.
Only supports Angular's XLIFF-based i18n extraction (e.g., xlf, xliff2), not alternative formats like JSON, which may be preferred in modern or cross-framework projects.