support multiple localizations at the same time

[Claudishe]

Hello,
Thank you for this nice plugin.

Our app uses multiple locale at the same time : a generic user locale (which work fine with this plugin), but also a specific locale in some context (ex : viewing a document in french while the rest of the interface is in english).

Migrating from i18n, I cannot access a specific locale key (eg : $en().hello, $fr().hello).
I have tried with S.load(Locale('fr'), and with Localizations.override(Locale('fr')) with a specific localization context, but it seems the messagelookup always uses the Intl.defaultLocale to do the message lookup.

It would be nice to be able to have a typed access to a locale specific translations (without having to do the untype lookup.

Thank you !

[aleksakrstic]

Hi @Claudishe
Thats true, it always uses Intl.defaulLocale.
Are both locales set dynamically in your case, or one is hardcoded?

[Claudishe]

Hi @aleksakrstic .
In my case, both are dynamic. The app is a cash register/point of sale app, so one is the language of the cashier/user, and the other is the language of the customer/client.
So both languages are used at the same time.

What I ended up was copying the generated files and adding a 'Locale' parameter to my inherited S file. Works, but I have to redo the same operation everytime a new translation key is added. Since INTL plugin is not open-source, I cannot modify the generation code.

Here's an edited bit of my code :

class StaticS extends S {
  String locale;

  StaticS(this.locale);

@override
  String discountOn(Object description) {
    return Intl.message(
      'discount on $description',
      name: 'discountOn',
      desc: '',
      locale: locale,
      args: [description],
    );
  }

Usage

class TranslationHelper extends S {
  static StaticS fr = StaticS('fr');
  static StaticS en = StaticS('en');
  static StaticS nl = StaticS('nl');
  static S currentS;
}

switch (customer.language.toLowerCase()) {
      case 'fr':
        return TranslationHelper.fr;
      case 'nl':
        return TranslationHelper.nl;
      default:
        return TranslationHelper.en;
    }

[aleksakrstic]

Hi @Claudishe
That is a temporary solution I wanted to propose you.
Since this is requested few more times, I think we will plan multi-locale support for one of upcoming releases.

[Claudishe]

Thanks, looking forward to that release !

[guominfang]

I have the same problem

[aleksakrstic]

Seems support for this would make breaking changes for current usages.
We will need to postpone this for one of the future major versions.
Not expected soon, no known date yet.

[nielsenko]

I have a PR localizely/intl_utils#18 that allows multiple instances of the generated localization class to co-exist for different locales. It is fairly easy to use something like provider, riverpod or plain old InheritedWidget to have different parts of the widget-tree translated to different locales at the same time.

[jack24254029]

Hi @Claudishe Thats true, it always uses Intl.defaulLocale. Are both locales set dynamically in your case, or one is hardcoded?

Hi @aleksakrstic
When I use Intl.defaultLocale on the _firebasemessagingBackground of FCM, it will get en_US on first time.
It will be return correct locale after first time.

Do you know why?

Thank you very much.

[lzoran]

The release of the new major version of the intl_utils package will most likely not be soon (PR#18 indeed solves the issue but introduces the breaking change for existing users).

Alternatively, maybe usage of the Intl.withLocale can help.

Example:

...
import 'package:intl/intl.dart';
import 'generated/intl/messages_all.dart';

...

      // Somewhere in the widget
      FutureBuilder<bool>(
          future: initializeMessages('de'), // make sure you have loaded messages for the locale before usage
          builder: (BuildContext context, AsyncSnapshot<bool> snapshot) {
            if (snapshot.hasData) { // use messages once they are loaded
              return Text(
                Intl.withLocale('de', () => S.of(context).yourStringKey),
              );
            }

            return const Text('');
          }),
...