Difference between revisions of "L10n Vendors"
(→Supported L10n Vendors) |
(→Supported L10n Vendors) |
||
Line 8: | Line 8: | ||
The default location of the config_l10n_vendor.properties file is at the group level. |
The default location of the config_l10n_vendor.properties file is at the group level. |
||
− | The default settings |
+ | The default settings do not define a vendor so that an error will occur when prepping a kit, forcing the user to chose a vendor. The global L10n Vendor attributes are: |
*'''l10n.vendor=lingotek''' - uncomment if using Lingotek |
*'''l10n.vendor=lingotek''' - uncomment if using Lingotek |
||
*'''l10n.vendor=worldserver''' - uncomment if using Worldserver |
*'''l10n.vendor=worldserver''' - uncomment if using Worldserver |
||
*'''l10n.vendor=ftp''' - uncomment if using FTP |
*'''l10n.vendor=ftp''' - uncomment if using FTP |
||
− | *'''l10n.vendor.nonsupported.extensions''' - a vendor may not support a specific extension such as .json. Enter any extensions that are not supported by the vendor but are supported by LRM |
+ | *'''l10n.vendor.nonsupported.extensions''' - a vendor may not support a specific extension such as .json. Enter any extensions that are not supported by the vendor but are supported by LRM. See [[LRM Fixing Issues]] for LRM supported extensions. An error will occur if there is no conversion protocol for a non-supported extension. |
+ | Example file: |
||
<pre> |
<pre> |
||
#Default to 'no vendor defined' |
#Default to 'no vendor defined' |
||
Line 25: | Line 26: | ||
==FTP== |
==FTP== |
||
+ | To choose FTP as the vendor, uncomment the <code>l10n.vendor=ftp</code> in the config_l10n_vendor.properties file. |
||
− | The information that is needed to upload the files to |
+ | The information that is needed to upload the files to be translated as well as retrieve translated files is: |
+ | <pre> |
||
+ | #FTP Attributes |
||
+ | ## FTP inbound attributes for import kit files |
||
+ | ftp.in.host= |
||
+ | ftp.in.location.path= |
||
+ | ftp.in.password= |
||
+ | ftp.in.port= |
||
+ | #SSH, SSL or empty |
||
+ | ftp.in.protocol= |
||
+ | ftp.in.username= |
||
+ | # FTP outbound attributes for prep kit files |
||
+ | ftp.out.host= |
||
+ | ftp.out.location.path= |
||
+ | ftp.out.password= |
||
+ | ftp.out.port= |
||
+ | ftp.out.protocol= |
||
+ | ftp.out.username= |
||
+ | </pre> |
||
==Lingotek== |
==Lingotek== |
Revision as of 19:42, 28 April 2016
Supported L10n Vendors
Currently, LRM supports 3 paths for sending files to be translated. They are:
- FTP
- Lingotek
- Worldserver
The type of L10n Vendor is defined in the config_l10n_vendor.properties that can exist at either the group or project level. See Group Configuration Files
The default location of the config_l10n_vendor.properties file is at the group level. The default settings do not define a vendor so that an error will occur when prepping a kit, forcing the user to chose a vendor. The global L10n Vendor attributes are:
- l10n.vendor=lingotek - uncomment if using Lingotek
- l10n.vendor=worldserver - uncomment if using Worldserver
- l10n.vendor=ftp - uncomment if using FTP
- l10n.vendor.nonsupported.extensions - a vendor may not support a specific extension such as .json. Enter any extensions that are not supported by the vendor but are supported by LRM. See LRM Fixing Issues for LRM supported extensions. An error will occur if there is no conversion protocol for a non-supported extension.
Example file:
#Default to 'no vendor defined' #l10n.vendor=lingotek #l10n.vendor=worldserver #l10n.vendor=ftp l10n.vendor.nonsupported.extensions=
FTP
To choose FTP as the vendor, uncomment the l10n.vendor=ftp
in the config_l10n_vendor.properties file.
The information that is needed to upload the files to be translated as well as retrieve translated files is:
#FTP Attributes ## FTP inbound attributes for import kit files ftp.in.host= ftp.in.location.path= ftp.in.password= ftp.in.port= #SSH, SSL or empty ftp.in.protocol= ftp.in.username= # FTP outbound attributes for prep kit files ftp.out.host= ftp.out.location.path= ftp.out.password= ftp.out.port= ftp.out.protocol= ftp.out.username=