Difference between revisions of "Machine Translation"
(→How the process works) |
|||
| (4 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
== How the process works == |
== How the process works == |
||
| − | Once you've setup your LRM project to use a |
+ | Once you've setup your LRM project to use a Machine Translator vendor for translation then the following occurs when there is a change in a base resource file: |
* The changed text is machine translated to each target locale language |
* The changed text is machine translated to each target locale language |
||
* In each of the corresponding target resource files the corresponding machine translated text will replace the current text. If the change to the base resource file was a new key/value then this new key/value will be added to the target resource file |
* In each of the corresponding target resource files the corresponding machine translated text will replace the current text. If the change to the base resource file was a new key/value then this new key/value will be added to the target resource file |
||
| Line 15: | Line 15: | ||
*** To prevent a ''parameter mismatch'' error, LRM will add the missing parameter to the end of the text (''{0} personnes ont été invitées à soirée'' '''''{1}'''''. Since this may not be syntactically correct, the email contains the information about the modification. |
*** To prevent a ''parameter mismatch'' error, LRM will add the missing parameter to the end of the text (''{0} personnes ont été invitées à soirée'' '''''{1}'''''. Since this may not be syntactically correct, the email contains the information about the modification. |
||
| − | == Supported |
+ | == Supported File Types == |
| − | Machine translation supports the following |
+ | Machine translation supports the following files types |
| + | * [[LRM_JSON_Support#json_parser_type | ''json'']] |
||
| − | * |
||
| + | * [[LRM_msg_Support#msg_parser_type|''msg'']] |
||
| + | * [[LRM_Properties_Support#properties_parser_type|''properties'']] |
||
| + | * [[LRM_rjs_Support#js_parser_type|''js'']] |
||
| + | * [[LRM_strings_Support#strings_parser_type|''strings'']] |
||
| + | * [[LRM_XML_Support|''xml'']] including .resx, .rxml and Android files. |
||
Latest revision as of 20:43, 10 July 2020
LRM and Machine Translation
How the process works
Once you've setup your LRM project to use a Machine Translator vendor for translation then the following occurs when there is a change in a base resource file:
- The changed text is machine translated to each target locale language
- In each of the corresponding target resource files the corresponding machine translated text will replace the current text. If the change to the base resource file was a new key/value then this new key/value will be added to the target resource file
- The changed target resource files will be pushed to the repository.
- An email will be sent out only if some type of error or modification occurred during the machine translation process. These include:
- An email is sent if the connection information is incorrect or some other unexpected connection issue occurs.
- An email is sent if one of the target locales is not supported (see below for information on setting up the locale mapping file)
- An email is sent if, for some unknown reason, the text could not be machine translated. In this case, LRM will pseudo-localize the text and the email will list those files and keys where the values were pseudo-localized.
- An email is sent if, for some unknown reason, the machine translation added or deleted some of the parameters in the text. In this case, LRM fixes the text by either adding missing parameters to the end of the line or deleting extra parameters. The email will list those files and keys where parameter manipulation occurred. Example:
- Text sent for machine translation is {0} people have been invited to {1} party
- Text returned from machine translation for French is {0} personnes ont été invitées à soirée
- To prevent a parameter mismatch error, LRM will add the missing parameter to the end of the text ({0} personnes ont été invitées à soirée {1}. Since this may not be syntactically correct, the email contains the information about the modification.
Supported File Types
Machine translation supports the following files types
