Terms and Definitions

Continuous Globalization

The process of integrating internationalization (i18n) and localization (L10n) continuously into software development.

Continuous Integration  

(CI) A development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.

Dashboard  

See Lingoport Dashboard

globalization

(G11n) Refers to a broad range of engineering and business development processes necessary to prepare and launch products and company activities globally.

g11n

Globalization

Globalyzer

Lingoport's product to find and fix internationalization (i18n) issues that inhibit localization and global user experience during development.

Globalyzer API

Allows you to create Globalyzer projects and scans, execute scans, and generate reports from a java program.

Globalyzer Client

The Globalyzer API, Globalyzer CLI and Globalyzer Workbench and their supporting code files.

Globalyzer Command Line

Globalyzer commands can be executed from the Linux command line. There is also a Globalyzer Ant Client, Maven Client and XSL Client.

Globalyzer Lite

Application for scanning code for internationalization issues on the fly and generating corresponding reports. It does not require an external database. Globalyzer Lite parses and executes Globalyzer Lite Project Definition XML files.

Globalyzer Lite Project Definition XML files  

XML file with details on what projects to scan, what rule sets to use and reports to generate.

Globalyzer project

Source code must be defined in a project before it can be scaned

Globalyzer Server  

Location of user administration and Globalyzer customization. Each account and user can create and share among team members, centralized rule set controls, which make Globlayzer highly customizable.

Globalyzer Workbench

A fully functional code analysis and editing Eclipse environment for finding, fixing, testing and reporting on internationalization issues in a wide variety of programming languages.

group name  

In LRM, all projects are part of a group. This group is defined in the project definition file when the project is created.

internationalization

(I18n) The process of designing a software application so that it can potentially be adapted to various languages and regions without engineering changes.

i18n

Internationalization

Jenkins

An open source automation server written in Java. Jenkins helps to automate the non-human part of the whole software development process.

kit version

When a prep kit is created for translation it is given a version number that LRM uses to coordinate sending and receiving translations and email notifications.

Lingoport Resource Manager

(LRM) Lingoport's product to detect & manage changes to resource files in your source code. It also streamlines translation jobs and can automate localization updates between development and translation.

Lingoport Dashboard

The hub of the Lingoport Suite. See it all, drill down, create notifications and manage the process. Bridge gaps between localization & development. Increase visibility and track globalization metrics.

Lingoport Suite

Three integrated Lingoport components: Globalyzer, Lingoport Resource Manager (LRM) and Lingoport Dashboard which create & maintain software for any language or cultural format in every release increment.

Lingoport Suite Installer  

The automated install application to install the Lingoport Suite.

localization

(L10n) The process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text.

LRM

See Lingoport Resource Manager

LRM Server

This term is used interchangeably with LRM.

LRM Database

The MySQL database used by LRM to manage resource files and translation status. The database is created when LRM Server is installed.

LRM Project

The encapsulation of the location of the resource files, locales for translation and processing information for LRM.

prep kit

When translations are required for a project, an LRM prep kit is created to send to the localization vendor with the appropriate files and changes needed.

project name

In LRM, to work with resource files, a project must be created first. All LRM action is done upon that project. Status is based on the project. The project name must be unique within its group, but the same project name can exist in different groups.

project definition file

Or project definition xml. A file used to create a project. Both LRM and Globalyzer Lite use project definition files to create projects. The xml files used are very different.

repository  

The location of the source code for the Globalyzer project and/or the location of the resource files for LRM.

resource bundle

A file that contains locale-specific data. It is a way of internationalizing an application by making the code locale-independent.

resource files

A set of files, one file for each spoken language which stores localized text.

rule set  

Based on programming languages and specific application demands, rule sets let you precisely hone internationalization detection and issue filtering, so that you get reliable results across your company or department. Rule sets reside on the Globalyzer Server

scan

Analyze source code to detect globalyzer issues using rule sets from the Globalyzer server.

SonarQube

The central place to manage code quality, offering visual reporting on and across projects and enabling the ability to replay the past to follow metrics evolution. SonarQube

stack installer  

See Lingoport Suite Installer

translation management systems

(TMS) Programs and vendors that support complex translation tasks.

translation vendor

Company or group that does the actual translation from one language to another.

Workbench

See Globalyzer Workbench