Localization
Supported Languages
Document Reader SDK supports the following languages:
- Arabic (ar)
- Bangla (bn)
- Czech (cs)
- Danish (da)
- German (de)
- Greek (el)
- English (en)
- Spanish (es)
- Finnish (fi)
- French (fr)
- Hebrew (he)
- Hindi (hi)
- Croatian (hr)
- Hungarian (hu)
- Indonesian (id)
- Italian (it)
- Japanese (ja)
- Korean (ko)
- Malay (ms)
- Norwegian (nb)
- Dutch (nl)
- Polish (pl)
- Portuguese (pt)
- Romanian (ro)
- Russian (ru)
- Slovak (sk)
- Swedish (sv)
- Thai (th)
- Turkish (tr)
- Ukrainian (uk)
- Vietnamese (vi)
- Chinese Simplified (zh-Hans)
- Chinese Traditional (zh-Hant)
Customizing Localization
Regula SDK supports localization. If any language is required by your application but is not supported by Regula SDK, or you want to change our localized strings, you can add localized strings to resource files and allow the Regula SDK to be presented to the users in their desired system locale.
The list of available strings can be found here.
Xamarin.Android
To do this, simply add the needed strings to Strings.xml
file.
Info
For more information on localizing your application and best practices, please see the official Microsoft documentation.
Xamarin.iOS
To get started, include the string resource file named RegulaSDK.strings
to your project's Resources folder. This filename is required and customization will only work if it is set as specified. Also, notice that this file has to be located in the corresponding .lproj
folder, e.g. es.lproj
.
Don't forget to add the
CFBundleLocalizations
property to the Info.plist
file and specify the languages.
Info
For more information on localizing your application and best practices, please see the official Microsoft documentation.
Now you can redefine every string in Regula SDK with the appropriate translated values. This way, when the user has their device's System Language set to a language supported by your application, Regula SDK will utilize the appropriate string resources.
Warning
Avoid changing the iOS system language (by using the AppleLanguages pref key) from within your application. This goes against the basic iOS user model for switching languages in the Settings app and uses a preference key that is not documented. At some point in the future, the key name may change and that would break your application.