@@ -489,16 +489,16 @@ Plugin API is new SeleniumLibrary 4.0
489
489
490
490
= Language =
491
491
492
- SeleniumLibrary offers possibility to translte keyword names and documentation to new language. If language
492
+ SeleniumLibrary offers the possibility to translate keyword names and documentation to new language. If language
493
493
is defined, SeleniumLibrary will search from
494
494
[https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#module-search-path | module search path]
495
- Python packages starting with `robotframework_seleniumlibrary_translation ` by using
496
- [https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/ | Python pluging API]. Library
495
+ for Python packages starting with `robotframework-seleniumlibrary-translation ` by using the
496
+ [https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/ | Python pluging API]. The Library
497
497
is using naming convention to find Python plugins.
498
498
499
- The package must implement single API call, ``get_language`` without any arguments. Method must return a
499
+ The package must implement a single API call, ``get_language`` without any arguments. The method must return a
500
500
dictionary containing two keys: ``language`` and ``path``. The language key value defines which language
501
- the package contains. Also value should match (case insentive ) the library ``language`` import parameter.
501
+ the package contains. Also the value should match (case insensitive ) the library ``language`` import parameter.
502
502
The path parameter value should be full path to the translation file.
503
503
504
504
== Translation file ==
@@ -507,8 +507,8 @@ The file name or extension is not important, but data must be in [https://www.js
507
507
format. The keys of json are the methods names, not the keyword names, which implements keywords. Value of
508
508
key is json object which contains two keys: ``name`` and ``doc``. The ``name`` key contains the keyword
509
509
translated name and `doc` contains translated documentation. Providing doc and name are optional, example
510
- translation json file can only provide translations to keyword names or only to documentatin . But it is
511
- always recomended to provide translation to both name and doc. Special key ``__intro__`` is for class level
510
+ translation json file can only provide translations to keyword names or only to documentation . But it is
511
+ always recommended to provide translation to both name and doc. Special key ``__intro__`` is for class level
512
512
documentation and ``__init__`` is for init level documentation. These special values ``name`` can not be
513
513
translated, instead ``name`` should be kept the same.
514
514
@@ -519,9 +519,10 @@ Template translation file, with English language can be created by running:
519
519
languages, it only provides easy way to create full list keywords and their documentation in correct
520
520
format. It is also possible to add keywords from library plugins by providing `--plugings` arguments
521
521
to command. Example: `rfselib translation --plugings myplugin.SomePlugin /path/to/translation.json` The
522
- genered json file contains `sha256` key, which constains the sha256 sum of the library documentation,
523
- the sha256 sum is used by `rfselib translation --compare /path/to/translation.json` command, which compares
524
- transation to to library and prints outs a table which tell if there are changes needed for translation file.
522
+ generated json file contains `sha256` key, which contains the sha256 sum of the library documentation.
523
+ The sha256 sum is used by `rfselib translation --compare /path/to/translation.json` command, which compares
524
+ the translation to the library and prints outs a table which tells if there are changes needed for
525
+ translation file.
525
526
526
527
Example project for translation can be found from
527
528
[https://github.com/MarketSquare/robotframework-seleniumlibrary-translation-fi | robotframework-seleniumlibrary-translation-fi]
0 commit comments