Difference between revisions of "LingoBot Release Notes"
(→LRM 1.0 release - August 2017) |
|||
Line 1: | Line 1: | ||
+ | LingoBot is a new component of the Lingoport Suite. Development teams collaborate using products such as Slack and Flowdock. LingoBot facilitates Globalyzer, LRM, and Dashboard actions directly from within a collaboration environment. Furthermore, collaboration users receive notifications |
||
− | LingoBot is a new component of the Lingoport Suite. |
||
+ | |||
− | =LRM 1.0 release - September 2017= |
||
+ | =LingoBot 1.0 release - September 2017= |
||
− | *'''Integration with GlobalLink''': GlobalLink integration is now one of our supported packaged TMS connections. The configuration details are either at the project or group level. |
||
+ | *'''Branch by Branch''': LingoBot supports a branch level interaction. Once a parent project has been on-boarded, typically on a repository master branch, a child project can be created with the <code>duplicate project</code> command. |
||
− | *'''HTML/HTM''' extensions are supported: Well-formed HTML is required. Unlike other resource types, LRM only determines if the base resource file has changed. No comparison is made against the localized files. |
||
+ | *'''Branch i18n status''': The <code>i18n scan</code> command provides internationalization feedback on the files modified in that branch since it was created. |
||
− | *Ability to set '''SSL FTP connection implicit or explicit''': Flag is located in a project's <code>config_l10n_vendor.properties</code> file. |
||
− | *''' |
+ | *'''Branch translation status''': The <code>translation status</code> command provides feedback on the translation status of the resource files for that branch. |
+ | *'''Translate''': The <code>translate</code> command sends the files to the translation vendor. |
||
− | *'''No restriction on Android resource file names''': Pre LRM 3.2, Android file names were restricted to only strings.xml. To preserve this restriction, the project needs to be updated after adding '**/strings.xml' to the include portion of the project definition file. |
||
+ | *'''Notifications''': When files are sent for translation or received from translation, notifications are shown in the collaboration environment. |
||
− | *'''Pseudo-localization''' enhancements |
||
+ | *'''Pseudoloc''': The <code>pseudoloc</code> command creates pseudo-localized files for that branch. |
||
+ | *'''Direct Links''': With some commands, links are returned so the user can more easily go to the relevant Dashboard or repository for that project. |
Revision as of 19:19, 7 September 2017
LingoBot is a new component of the Lingoport Suite. Development teams collaborate using products such as Slack and Flowdock. LingoBot facilitates Globalyzer, LRM, and Dashboard actions directly from within a collaboration environment. Furthermore, collaboration users receive notifications
LingoBot 1.0 release - September 2017
- Branch by Branch: LingoBot supports a branch level interaction. Once a parent project has been on-boarded, typically on a repository master branch, a child project can be created with the
duplicate project
command. - Branch i18n status: The
i18n scan
command provides internationalization feedback on the files modified in that branch since it was created. - Branch translation status: The
translation status
command provides feedback on the translation status of the resource files for that branch. - Translate: The
translate
command sends the files to the translation vendor. - Notifications: When files are sent for translation or received from translation, notifications are shown in the collaboration environment.
- Pseudoloc: The
pseudoloc
command creates pseudo-localized files for that branch. - Direct Links: With some commands, links are returned so the user can more easily go to the relevant Dashboard or repository for that project.