When working with multiple languages in Xcode’s String Catalog, good organization and consistency are key. Here are some best practices to follow:
Always start with a complete and well-structured source language. This makes it easier to track missing translations and maintain consistency.
Instead of generic names like label1, use meaningful keys such as LoginButtonTitle. This helps translators and developers understand the context.
Define plural forms and variations (e.g., gender, device type) directly in the catalog to avoid hardcoding conditions in your app logic. For example:
"%d comment", other = "%d comments""%d komentář", few = "%d komentáře", other = "%d komentářů"Use the catalog’s description fields or developer comments to provide translators with context. This reduces ambiguity and improves translation quality.
Keep all language versions up to date and validate them during development. Missing or outdated translations can break the user experience.
Localazy makes handling multiple languages smoother and error-free:
With these practices and Localazy’s automation, your String Catalogs stay consistent, well-structured, and ready for global audiences.
Please help us with improving our documentation.
We appreciate all your feedback.