Localization | : globe_with_meridians : Localization package | Internationalization library

I managed to do it by adding this to my index.html file:

I regard this as a major bug in String(localizable:). If we were using NSLocalizedString, we would have individual key: and value: parameters. String(localizable:) needs that.

I can think of two workarounds. One is: don't use String(localizable:). Just keep on using NSLocalizedString.

The other is to localize explicitly for English. Instead of entering the English user-facing text as the localized: parameter, enter a key string. Then, to prevent the keys from appearing in the user interface, export the English localization and "translate" the keys into the desired English user-facing text. Now import the localization to generate the correct English .strings files.

(If your development language isn't English, substitute the development language into those instructions.)

Now when you export a different localization, such as French, the element's id value is the key, to which the translator pays no attention, and the is the English, which the translator duly translates.

To change the English user-facing text later on, edit the English Localizable.strings file — not the code. Nothing will break because the key remains constant.

You need to install the date-fns package from NPM using npm install --save date-fns.

After your suggestion in the update, I got this workaround:

You only specified an English localization file: Shared.en.resx.

When you specify @loc["countries"] in the component, it attempts to use the browser locale to translate the text "countries".

The localizer looks for a resource file Shared.de.resx but that doesn't exist, so it defaults to the base translation, in this case English.

This is known bug of material library TextInputLayout already reported here.

Unfortunately there is no fix for it now.

PS: A possible workaround is to manually call textInputLayout.setHint(R.string.your_string) again on onRestoreInstanceState to update the text. (call it after super.onRestoreInstanceState(bundle)) or call it in onViewStateRestored

You are getting the undefined error because for few of the cases the post_categories array is empty and if u try accessing the 0th element it will throw an error. So add a null check for the array length and for id something like below

You have to change the placeholder of the textfield on renderInput without overwriting the data on params.inputsProps. This would be your new DesktopDatePicker.

You can try to add a delegate of GlobalCupertinoLocalizations instead of DefaultCupertinoLocalizations into your delegates: