Open MayuraVerma opened 6 years ago
The trick here is how we deploy localization. We are planning to deploy localizations with the app at this point, and not as separate packages. The biggest issue with separate packages it that they diverge from the app over time; keeping the strings together with the app reduces the management cost of this dramatically.
So I am going to postpone this for now. We may consider including a font for specific less-supported scripts that have an active localization as part of the app. But we don't want to do that generically right now.
Applicable to Windows now. But it should be considered for all platform.
We need to include a language font with the translation.
Most complex scripts primarily Indic scripts do not have any standard fonts, that is commonly available across all platform or even between two versions of the OS.
Eg.: Indic fonts available in Windows 7, is not available in Windows 10 by default.
So, if Keyman has to look identical, then there should be away to include language font with the translation.
As of now, only Windows version of Keyman can be localized. In future, when keyman on other platform is also localized. It should be kept in mind to allow a language font part of the language pack.