excel_localization 包使开发者能够通过从 Excel 文件生成变量值来管理应用本地化,无需在翻译过程中使用上下文。它通过允许团队在熟悉的电子表格格式中编辑翻译,然后自动生成代码资源,从而简化国际化流程。这种方法简化了开发人员与翻译人员之间的协作,确保在 Android、iOS、Web 和 Windows 平台上实现一致且可扩展的本地化。
适合场景
管理多语言应用内容
从电子表格生成本地化文件
与非技术翻译人员合作
自动化翻译资产生成
支持跨平台本地化
主要特点
基于Excel的翻译管理
上下文无关的本地化
自动代码生成
跨平台支持
与 Flutter 项目的轻松集成
适合对象
使用外部翻译人员的Flutter团队
需要频繁本地化更新的项目
寻求简化国际化工作流程的开发者
使用结构化翻译数据的团队
针对多种语言的应用
使用建议
需要正确的Excel文件格式
手动设置初始配置
与 Excel 的有限实时同步
最适合批量处理
依赖于源数据的准确性
原始 README
以下为关联源码仓库的 README 原文快照,最新内容请访问源码仓库。
Excel Localization
A tool which automatically generates Flutter localization resources from CSV and Excel files.
This is especially useful as any team member can edit the CSV/Excel file, with the subsequent translations imported into the project via a terminal command. Basic variables (strings and integers) are supported, however neither genders nor plurals are planned to be supported. If you require such functionality, consider using arb_generator.
In order to use the excel_localization package, please provide your translations in a CSV or Excel file. For CSV files, delimiters , and ; have been tested to work.
Here you can see samle of csv how user need to arrange data
keys
fr
en
en_GB
hi
plainText
Bonjour le monde!
Hello world!
Hello world!
हैलो वर्ल्ड!
welcome
Bienvenu %name$s!
Welcome %name$s!
Welcome %name$s!
स्वागत%name$s!
favoriteColor
Quelle est votre couleur préférée?
What is your favorite color?
What is your favourite colour?
आपका पसंदीदा रंग कौनसा है?
Localizations can be specified for a region by appending the country code.
The package used your input file in order to generate a file named file_name in output_dir you provided. The following example uses the default class_name I18n with a dependency on BuildContext.
Firstly, add the I18nDelegate to your delegates:
classMyAppextendsStatelessWidget{
@overrideWidgetbuild(BuildContext context) {
returnMaterialApp(
navigatorKey: I18n.languageKey, //<== This is require if you like to call words without context
localizationsDelegates: [
constI18nDelegate(),
GlobalMaterialLocalizations.delegate,
GlobalWidgetsLocalizations.delegate,
GlobalCupertinoLocalizations.delegate,
],
supportedLocales: I18nDelegate.supportedLocals,
home: Home(),
);
}
}
Then use the generated I18n class!
classHomeextendsStatelessWidget{
@overrideWidgetbuild(BuildContext context) {
returnScaffold(
appBar: AppBar(
title: Text('excel localization sample"'),
),
body: Center(
child: Column(
children: <Widget>[
Text(I18n.of(context).plainText),
Text(I18n.of(context).welcome(name: 'Simran')),
Text(I18n.of(context).favoriteColor),
// To access variable without con the way is given below just replace of(context) to translate keyword// Make sure you add navigatorkey parameter in MaterialApp or GetMaterialAppText(I18n.translate.plainText),
Text(I18n.translate.welcome(name: 'Simran')),
Text(I18n.translate.favoriteColor),
],
),
),
);
}
Supporting a language (i.e. ga or cy) not included in GlobalMaterialLocalizations requires adding a material localization class and delegate. Although this is out of the scope of this package, a warning is logged to the console during code generation. More info.
Rules and functionalities
Locale
Locales are specified in the top row and are expected to be given in the form en or en_US.
Default language
The column at start_index is considered the default language. This means that:
If this column does not have a value, the loca key instead will be used.
If another language does not have translations for a given key, the value of the default language will be used.
Keys
Each loca key must begin with a lowercase letter, after which any combinations of lowercase, uppercase, digits or underscores are valid.
Variables
In order to include variables in loca strings, they need to be written in the format %<VAR NAME>$<VAR TYPE>. Presently only integers and strings are supported as variable types.
%myVariable$d (d stands for an int)
%myVariable$s (s stands for a String)
All variables are required. Consider the key welcome from example. The generated function signature is
Stringwelcome({
requiredString name,
})
Note that if the variable's name starts with a number, the generated variable name will be var<VAR NAME>. So, for instance, %1$d would become var1.
You can also watch youtube Video to understand this plugin