Difference between revisions of "Localyzer Express"

From Lingoport Wiki
Jump to: navigation, search
(→‎Supported Resource Files)
(→‎Introduction)
 
(49 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Introduction =
  
= Introduction =
  +
== Localyzer Express Video ==
−
'''Resource files''' are used by internationalized applications to display user facing strings, such as user interface labels, in different locales (languages, country, variant). As an example, ''messages.properties'', an English resource file, can be translated in French and Japanese, resp. ''messages_fr.properties'' and ''messages_ja.properties''.
 
  +
This 6'30" video introduces Localyzer Express:
  +
* https://vimeo.com/502774520
   
  +
== Getting Started ==
−
'''Localyzer Express''' is a GitHub application which allows for an '''near immediate translation of standard application resource files'''. Example of application resource filsThe GitHub application installation takes a couple of minutes. Configure the repositories based on the expected locales and format for the source and target file naming convention, which branches and directories to include or exclude, and the system will then automatically '''machine translate''' those files.
 
  +
'''[https://github.com/marketplace/localyzer-express Localyzer Express]''' is a '''GitHub application''' which allows for a '''near immediate translation of standard application resource files'''.
   
  +
'''Resource files''' are used by internationalized applications to display user facing strings (such as user interface labels) in different locales (languages, country, variant).
−
'''Localyzer Express''' is a GitHub specific and simplified version of the more fully fledged '''Localyzer'''.
  
  +
As an example, ''messages.properties'', an English resource file, can be translated in French and Japanese, respectively ''messages_fr.properties'' and ''messages_ja.properties''.
  +
  +
To use Localyzer Express:
  +
* Install the [https://github.com/marketplace/localyzer-express Localyzer Express] GitHub application for an organization and choose the respositories (or all) that you would like translated
  +
* Configure each repository, choosing source and target locales, resource type, file naming conventions, repository branches to include and/or exclude, and resource directories to include and/or exclude.
  +
  +
Localyzer Express will then automatically '''machine translate''' target resource files as modifications to source resource files are committed to the repository.
  +
  +
'''Localyzer Express''' is a GitHub specific and streamlined version of the more fully fledged '''Localyzer'''.
   
 
Note: '''LocalyzerQA''' allows for post editing in a QA fashion translation from Localyzer Express
  
Note: '''LocalyzerQA''' allows for post editing in a QA fashion translation from Localyzer Express
Line 16: Line 28:
 
* iOS .strings files
  
* iOS .strings files
   
−
Contact ''info at lingoport (.) com'' as '''Localyzer''' for support of non standard and other file types, and other translation processes.
 +
Contact ''info@lingoport.com'' for support of non standard and other file types, and other translation processes.
   
−
= Adding the GitHub Localyzer Express Application =
 +
= Adding the GitHub Localyzer Express GitHub App =
 
This should take a few minutes at most.
 
This should take a few minutes at most.
   
  +
* Go to https://github.com/marketplace/localyzer-express
−
== Search for Localyzer Express in GitHub Marketplace ==
  
−  
−
* Go to https://github.com/marketplace
  
−
* In the search box, type "Localyzer Express"
  
 
* Install the application
  
* Install the application
−
* Select which repositories to include or select all repositories
 +
* Select which repositories to include (or select all repositories)
   
 
The next section details how to use the Localyzer Express configuration application.
  
The next section details how to use the Localyzer Express configuration application.
Line 34: Line 43:
 
*[[Localyzer Express Repository Validation]]
  
*[[Localyzer Express Repository Validation]]
 
*[[Localyzer Express Repository Translation]]
  
*[[Localyzer Express Repository Translation]]
  +
*[[Localyzer Express Application for LocalyzerQA ]]
   
 
= Translation Configuration Templates =
  
= Translation Configuration Templates =
  +
Templates are saved configurations that can be reused when configuring repositories.
  +
*[[Localyzer Express Templates]]
  +
  +
= License =
  +
[[LocalyzerExpress License]]
  +
  +
= Localyzer Express Release Notes =
  +
  +
==Localyzer Express 1.3.0 - June 2022==
  +
* <b>Introduced Applications</b>: An application is a set of repository/branches and is used by <code>LocalyzerQA</code> when performing corrections. See [[ LocalyzerQA_Release_Notes#LocalyzerQA_1.3.0_-_May_2022 | LocalyzerQA Release Notes]].
  +
  +
==Localyzer Express 1.2.0 - December 2021==
  +
* When configuring your custom Machine Translation Engine, you can now choose to '''update terminologies/glossaries/dictionaries when LocalyzerQA post edits are processed.'''
  +
* Allows an email recipient to be configured to receive notification of machine translation issues.
  +
  +
==Localyzer Express 1.1.0 - July 2021==
  +
*'''Multiple Machine Translation Engines''': Localyzer Express now supports four Machine Translation Engines:
  +
** AWS Translate
  +
** Google Translate
  +
** Microsoft Translator
  +
** Systran
  +
  +
When configuring your Localyzer Express plan, you may choose the type of machine translation engine. Use either Lingoport credentials or your custom credentials.
  +
  +
The default is to use AWS with Lingoport credentials.
  +
  +
==Localyzer Express 1.0.0 - March 2021==
  +
*'''Initial Release'''

Latest revision as of 18:50, 22 August 2022

Introduction

Localyzer Express Video

This 6'30" video introduces Localyzer Express:

Getting Started

Localyzer Express is a GitHub application which allows for a near immediate translation of standard application resource files.

Resource files are used by internationalized applications to display user facing strings (such as user interface labels) in different locales (languages, country, variant). As an example, messages.properties, an English resource file, can be translated in French and Japanese, respectively messages_fr.properties and messages_ja.properties.

To use Localyzer Express:

  • Install the Localyzer Express GitHub application for an organization and choose the respositories (or all) that you would like translated
  • Configure each repository, choosing source and target locales, resource type, file naming conventions, repository branches to include and/or exclude, and resource directories to include and/or exclude.

Localyzer Express will then automatically machine translate target resource files as modifications to source resource files are committed to the repository.

Localyzer Express is a GitHub specific and streamlined version of the more fully fledged Localyzer.

Note: LocalyzerQA allows for post editing in a QA fashion translation from Localyzer Express

Supported Resource Files

The following resource file types are supported by Localyzer Express, provided they follow the standards:

  • properties files
  • resx files
  • json files (no arrays allowed)
  • Android strings.xml files
  • iOS .strings files

Contact info@lingoport.com for support of non standard and other file types, and other translation processes.

Adding the GitHub Localyzer Express GitHub App

This should take a few minutes at most.

The next section details how to use the Localyzer Express configuration application.

Configuring the Automated Translation for one Repository

Translation Configuration Templates

Templates are saved configurations that can be reused when configuring repositories.

License

LocalyzerExpress License

Localyzer Express Release Notes

Localyzer Express 1.3.0 - June 2022

  • Introduced Applications: An application is a set of repository/branches and is used by LocalyzerQA when performing corrections. See LocalyzerQA Release Notes.

Localyzer Express 1.2.0 - December 2021

  • When configuring your custom Machine Translation Engine, you can now choose to update terminologies/glossaries/dictionaries when LocalyzerQA post edits are processed.
  • Allows an email recipient to be configured to receive notification of machine translation issues.

Localyzer Express 1.1.0 - July 2021

  • Multiple Machine Translation Engines: Localyzer Express now supports four Machine Translation Engines:
    • AWS Translate
    • Google Translate
    • Microsoft Translator
    • Systran

When configuring your Localyzer Express plan, you may choose the type of machine translation engine. Use either Lingoport credentials or your custom credentials.

The default is to use AWS with Lingoport credentials.

Localyzer Express 1.0.0 - March 2021

  • Initial Release
Retrieved from "http://wiki.lingoport.com/index.php?title=Localyzer_Express&oldid=96534"