Question on correctly implemention localization

[iyanushow]

Hi @descorp, I'm having some trouble correctly implementing localization for drop in components. Currently, i have it working for payment method names using a locale arg e.g de. However, drop in component stays in english. We're using session payment and the BE shopperLocale matches the app locale sent

• Does the shopperLocale have to be in the format de_DE to work? or is there support for just locale e.g de

• to support custom combinations of some supported languages e.g de_FR or de_PL Do I need to add all these locale combinations as described in localization.md and add translations for them though they're just using de translations, or is there a way to enforce them to use the translations for de_DE.

[descorp]

Hey @iyanushow

However, drop in component stays in english.

On iOS, Android or both?

This behaviour is a bit different for iOS and Android.
On iOS one must use exact value from the table since SDK is picking exact match (this is known limitation).

On Android it is "out-of-the-box" localisation, so it is possible to use de or de-FR instead of de-DE

[iyanushow]

Hi @descorp , thanks for the response.
We're building for both iOS and android.

[descorp]

In this case, the easiest way is to use only the locales from the table - this will work on both platforms.

[iyanushow]

Thank you.
I tried adding overrides for ios, created the localizable strings file and created the individual translation files (through file inspector), added the overrides, but they were not applied. Any idea what I might be missing here?

[descorp]

This is another known limitation, sorry.
On iOS SDK overrides only work in "natural" mode (when locale is selected by OS based on shopper's phone preferences); when one "enforce" locale by setting locale parameter to <AdyenCheckout> it only search for right string on SDK internal files.

[iyanushow]

Ooh okayy. Thank you for clarifying.