W27 Product Update: Async CLI file formats: TypeScript, YAML, PO, Flutter, Android, Xcode
by•
The async CLI now handles more file formats end to end: TypeScript locale modules, YAML, Gettext PO, Flutter ARB, Android strings, and Xcode .strings, String Catalogs (.xcstrings), and .stringsdict. Point a files[] entry at the source file and every lingo push runs each one through your engine's full pipeline. Translatable text is translated; everything structural is preserved – keys, IDs, metadata, placeholders, and code.
Full changelog: https://lingo.dev/en/changelog
9 views
Replies
The file-format part is more interesting than it looks at first glance.
Localization is not just moving strings between formats. A lot of meaning lives in the surrounding structure: placeholders, comments, key names, nesting, product-specific terms, and the conventions a team has built up over time.
The hard part is preserving that context while still letting the pipeline automate the repetitive parts.
Curious how you handle format-specific metadata during async jobs. Does the engine preserve enough surrounding context for reviewers to understand why a translation was made a certain way, or is the review mostly focused on the final string output?