Localisation

Platform	Status	Where
iOS	done	`vulture-ios/Packages/DesignSystemvulture-ios/Modules/App/Resources/Localizable.xcstringsvulture-ios/LOCALIZATION_STYLE.md`
Android	done	`vulture-android/core/designsystem/src/main/resvulture-android/scripts/convert_strings.py` strings_ios.xml generated from the iOS catalogs.
Web	done	`vulture-web/locales`

Behaviour

Eight languages, all complete: en (source), nl, de, fr, es, cs, it, pl. The website and the browser extensions use the same eight.
US English, sentence case, an informal “you” in every language; aviation terms and unit abbreviations stay untranslated.

iOS String Catalogs are the source. Android generates strings_ios.xml from them (scripts/convert_strings.py, checked in CI with --verify) and never edits them by hand.
Android overrides some English text for sentence case and no ellipsis (ANDROID_WORDING, decisions §17); Android-only strings live in each module in all 8 locales.
Known gaps in the conversion: substitutions, the zero plural form and colliding keys.