Repository navigation
Replies: 1 comment
|
It would also be wonderful to see support for additional languages in the future, including Russian, German, French, and Spanish. FluidVoice keeps becoming more feature-rich, and navigating all its settings and features can be challenging for users who don't speak English. Localization would make the app much more accessible and convenient for people around the world. I'd be happy to help with the Russian translation if there's an opportunity to contribute. I think allowing the community to contribute translations would be a great idea. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Proposal
Make FluidVoice's UI localizable, then add Traditional Chinese (
zh-Hant) and Simplified Chinese (zh-Hans) as the first translations.Why
FluidVoice dictates in many languages, but the app itself is English-only:
knownRegionsisen, Base, there is no String Catalog, and none of the roughly 1,300 SwiftUI string literals inSources/go through localization. People who dictate in Chinese, Japanese, Korean and other languages still have to set up and troubleshoot the app in English.Scope I'd suggest (one PR per step, each with screenshots)
Localizable.xcstrings(and anInfoPlist.xcstringsfor the permission prompts), and add the locales toknownRegions. SwiftUIText("…"),Button("…"),Toggle("…")and similar already takeLocalizedStringKey, so most call sites need no code change. OnlyStringvalues built in view models move toString(localized:). English output stays byte-for-byte the same.docs/localization.mdso other contributors can add languages without touching code.I'd keep each PR focused and separate from feature work.
Questions for maintainers
Once you approve, I'll open a tracking issue and link it here as CONTRIBUTING asks.
All reactions