Additional Deployments: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
* [[Globalyzer Lite for Developers]] | * [[Globalyzer Lite for Developers]] | ||
''' | '''Code Verification''' | ||
* [[Globalyzer and Check in Verification]] | * [[Globalyzer and Check in Verification]] | ||
Revision as of 22:07, 21 September 2017
Recommended
Globalyzer Suite Linux System
Team Members
Code Verification
Team Members
- Globalyzer Workbench for i18n Specialists
- i18n Specialists use the powerful Globalyzer Workbench to refine rule sets and interactively internationalize applications.
- Globalyzer Lite for Developers
- Developers run Globalyzer Lite from within their Integrated Development Environments (IDEs), getting quick feedback on potential i18n issues within their code.
Continuous Globalization
- Globalyzer Lite for Continuous Globalization
- Simple to set up.
- Lighter interface for Continuous Globalization.
- Projects can be analyzed concurrently.
- Globalyzer CLI for Continuous Globalization
- Legacy standard for Continuous Globalization.
- Projects must be analyzed one at a time.
- Globalyzer API for Continuous Globalization
- Most powerful and most flexible option.
- Requires writing your own Java program(s).
- LRM for Continuous Globalization
- Keeps tabs on the status of translations and resource files.
- Automates much of the translation process.
- Continuous Globalization
- Combination of the above sections.
Code Verification
- Globalyzer and Check in Verification
- Analyze source code during commit check in.
- Reject commits that fail i18n requirements.