For that, import generated app_localizations.dart file and pass needed values. Next, update the MaterialApp widget with the localizationsDelegates and supportedLocales props. It will let you correct typos, optimize text, and update translations on the fly. In case you are interested in instant updates of translations without the need for new releases, check out the Flutter Over-the-Air translation updates feature. You are ready to do QA check and publish the app! Your Flutter app now has ready translations for the next release. ARB files will be downloaded from Localizely platform and put in the proper place in your Flutter project. In your IDE go to Tools | Flutter Intl | Integrate with Localizely and run Download ARB files command. If you have previously invited your teammates to the Localizely project, you can assign them a task to translate newly added string keys. Feel free to explore the Sample project or just take a look at Getting started guide to grasp the basic concept and options.
Localizely has an editor on Translations page that reminds of Excel tables commonly used for translations management. It depends on what fits into your workflow better. Note: Alternatively you can always add new string keys in Localizely platform first, and then download them for development. You will be asked for your personal API token which you can get from My Profile page, and project ID we mentioned in the previous step. In your IDE go to Tools | Flutter Intl | Integrate with Localizely and run Connect command. You can change the main language later if needed.Įach project gets a unique ID (you can find it in My projects page), that is needed for the next step. Give your project a name and set your main and other languages. Once you sign up to Localizely, just go to My projects page and tap “ +” button (or explore the Sample Project if you wish to get more familiar with Localizely features first). Here is how to streamline the localization workflow: Step 1: Create a project in Localizely Part 2: Managing your translationsĪs your app grows with the number of string keys and the number of different languages for end-users, it gets more complicated to maintain translations. That way you can add the same key to all ARB files. As an alternative way, you can just add a translation string in Dart code, and extract it to ARB files via intention action in Android Studio or via code actions in VS Code.
0 kommentar(er)
