A command-line tool to validate iOS, Android, and Mac localization files for format specifier errors and consistency.
Locheck is a command-line tool that validates iOS, Android, and Mac localization files to prevent runtime crashes caused by translation errors. It checks for consistency in format specifiers, plural forms, and missing arguments across `.strings`, `.stringsdict`, `.xcstrings`, and `strings.xml` files. By catching these issues early, it helps developers maintain reliable multilingual applications.
Mobile developers (iOS and Android) and localization teams who need to ensure translation files are error-free before shipping apps. It's particularly useful for projects with extensive localization across multiple languages.
Developers choose Locheck because it specifically targets format specifier mismatches that cause app crashes, supports both iOS and Android file formats, and integrates easily into Xcode workflows. Its focus on technical accuracy over convenience makes it a reliable safety net for localization quality.
Validate iOS, Android, and Mac localizations. Find errors in .strings, .stringsdict, and strings.xml files.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Validates consistency in format specifiers like %d and %@ across translations, preventing runtime crashes as demonstrated in the README examples where mismatches cause app failures.
Checks that all required plural forms are correctly defined in .stringsdict and .xcstrings files, ensuring proper localization for different quantities without manual oversight.
Uses the base language's string value, not the key, as the authoritative source for validation, accommodating custom string definitions as explained in the README for manually defined strings.
Supports both iOS (.strings, .stringsdict, .xcstrings) and Android (strings.xml) localization files, making it a versatile tool for mobile development teams.
Not available in standard package managers like homebrew/core and lacks a custom tap, requiring manual setup or reliance on Mint, which adds complexity compared to mainstream tools.
Purely command-line based with no graphical interface, making it less accessible for non-technical users or teams preferring visual feedback and ease of use.
Focuses solely on technical errors like format specifiers and plural forms, missing linguistic, stylistic, or context-based checks that comprehensive localization tools might offer.