Difference between revisions of "Terms and Definitions"

From Lingoport Wiki
Jump to: navigation, search
(Definitions)
 
(47 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  +
See a definition of this term on the Terms and Definition page by clicking this link.
  +
  +
= Definitions =
  +
  +
;Agent Node <span id="AgentNode"></span>: When using Distributed Pull Requests, the Agent Node is the system is the system that performs the work before returning to the Master node. There can be one or more Agent Nodes.
  +
  +
;Automation Job <span id="AutomationJob"></span>: The Jenkins job created to check code out of the repository. The code is scanned by Globalyzer or it the resource files are monitored and sent for translation.
  +
  +
; Baseline <span id="Baseline"></span>: A snapshot of the state of the resource files at a particular point in time. Used by LRM in order to detect changes to existing keys. Also helps detect modifications to translation resource files that were not made by LRM.
  +
  +
; Branch <span id="Branch"></span>: When a developer works on a new change, they should create a branch. This allows them to work on the fix without changing the master code. When development is complete, the branch is merged back into the master code.
  +
  +
; Computer Assisted Translation <span id="CAT"></span>: Translation system utilizing automated tranlation.
  +
 
; Continuous Globalization <span id="ContinuousGlobalization"></span>: The process of integrating <b>internationalization (i18n)</b> and <b>localization (L10n)</b> continuously into software development.
 
; Continuous Globalization <span id="ContinuousGlobalization"></span>: The process of integrating <b>internationalization (i18n)</b> and <b>localization (L10n)</b> continuously into software development.
  +
  +
; Continuous Globalization System <span id="continuousglobalizationsystem"></span> : A system with LRM, Globalyzer Client, Jenkins, and Dashboard which can communicate with the code <b>repository</b> to get updated code as well as send and receive <b>resource files</b> from translation management systems.
   
 
;Continuous Integration <span id="ContinuousIntegration"></span> : (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.
 
;Continuous Integration <span id="ContinuousIntegration"></span> : (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.
   
  +
;Continuous Integration Continuous Delivery (or Deployment) <span id="CICD"></span>: (CICD or CI/CD) A variation of Continuous Integration
; Dashboard <span id="Dashboard"></span> :
 
  +
See <b>Lingoport Dashboard</b>
 
  +
; Dashboard <span id="Dashboard"></span> : See <b>Lingoport Dashboard</b>
  +
  +
; Dashboard Client <span id="DashboardClient"></span>: See <b>Lingoport Dashboard Client</b>
  +
  +
; Dashboard System <span id="DashboardSystem"></span> : The physical machine where the <b>Dashboard Server</b> and <b>Dashboard Client</b> reside.
  +
  +
; Decorated <span id="Decorated"></span> : A decorated string in a resource file contains a URL so that translators can see the context of the resource.
  +
  +
; Developer Machine <span id="DeveloperMachine"></span> : is where you install the Globalyzer clients so that internationalization and localization issues can be addressed.
  +
  +
; Embedded String <span id="embeddedString"></span> : A hard-coded string in source code. For internationalization, this must be externalized to a resource file for translation.
  +
  +
; False Positive <span id="falsepositive"></span> : an issue that has been detected by a rule in a ruleset as a candidate for internationalization that does not need to be translated for a variety of reasons.
   
 
; globalization <span id="globalization"></span>: (G11n) Refers to a broad range of engineering and business development processes necessary to prepare and launch products and company activities globally.
 
; globalization <span id="globalization"></span>: (G11n) Refers to a broad range of engineering and business development processes necessary to prepare and launch products and company activities globally.
Line 13: Line 42:
   
 
; Globalyzer API <span id="GlobalyzerAPI"></span>: Allows you to create Globalyzer projects and scans, execute scans, and generate reports from a java program.
 
; Globalyzer API <span id="GlobalyzerAPI"></span>: Allows you to create Globalyzer projects and scans, execute scans, and generate reports from a java program.
  +
 
; Globalyzer Client <span id="GlobalyzerClient"></span>: The Globalyzer API, Globalyzer CLI and Globalyzer Workbench and their supporting code files.
 
; Globalyzer Client <span id="GlobalyzerClient"></span>: 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 Command Line <span id="GlobalyzerCommandLine"></span>: 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 <b>Globalyzer Lite Project Definition XML files</b>.
 
  +
;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 in IDE <span id="GlobalyzerIDE"></span>: Globalyzer Lite incorporated into common IDEs (Integrated Development Environment) such as Eclipse, IntelliJ, and Visual Studio.
;Globalyzer project: Source code must be defined in a project before it can be <b>scan</b>ed
 
  +
;Globalyzer Server : Location of user administration and Globalyzer customization. Each account and user can create and share among team members, centralized <b>rule set</b> controls, which make Globlayzer highly customizable.
 
  +
;Globalyzer Lite <span id="GlobalyzerLite"></span>: 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 <b>Globalyzer Lite Project Definition XML files</b>.
;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.
 
  +
;Globalyzer Lite Project Definition XML files <span id="LiteProjectDefn"></span> : XML file with details on what projects to scan, what rule sets to use and reports to generate.
  +
  +
;Globalyzer project <span id="Globalyzerproject"></span>: Source code must be defined in a project before it can be <b>scan</b>ed
  +
  +
;Globalyzer Server <span id="GlobalyzerServer"></span> : Location of user administration and Globalyzer customization. Each account and user can create and share among team members, centralized <b>rule set</b> controls, which make Globlayzer highly customizable.
  +
  +
;Globalyzer Workbench <span id="GlobalyzerWorkbench"></span>: 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 <span id="groupname"></span> : In LRM, all projects are part of a group. This group is defined in the project definition file when the project is created.
  +
  +
; headless installation <span id="headless"></span> : Installing LRM or Globalyzer using an XML file with settings instead of using the installation GUI or answering prompts from the command line. It is also a way to automate installation.
  +
  +
; InContext Translation <span id="ICT"></span> : Allows the translator to see the context of strings in the translation management system (TMS) or computer assisted translation (CAT) system.
  +
  +
; InContext QA <span id="IQA"></span> : Enables users to review translations in their context and make improvement suggestions.
  +
  +
; instrumented resource files <span id="instrument"></span> : Internal Lingoport process to enable InContext features on resource files.
  +
  +
; Integrated Developement Environment (IDE)<span id="IDE"></span> :software application that provides comprehensive facilities to computer programmers for software development. An IDE normally consists of a source code editor, build automation tools and a debugger.
  +
 
; internationalization <span id="internationalization"></span>: (I18n) The process of designing a software application so that it can potentially be adapted to various languages and regions without engineering changes.
 
; internationalization <span id="internationalization"></span>: (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
 
  +
; i18n <span id="i18n"></span>: Internationalization
;Jenkins: An open source automation server written in Java. [https://jenkins.io Jenkins] helps to automate the non-human part of the whole software development process.
 
  +
; kit version: When a <b>prep kit</b> is created for translation it is given a version number that LRM uses to coordinate sending and receiving translations and email notifications.
 
  +
;Jenkins <span id="Jenkins"></span>: An open source automation server written in Java. [https://jenkins.io Jenkins] helps to automate the non-human part of the whole software development process. The End User License Agreement for the Jenkins Plugin is located at [[JenkinsPluginEULA|JenkinsPluginEULA]]
; 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.
 
  +
;Jenkins job <span id="Jenkinsjob"></span>:An automation script that runs under Jenkins.
; Lingoport Suite <span id="LingoportSuite"></span>: 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 <b>Lingoport Suite</b>.
 
  +
; kit version <span id="kitversion"></span>: When a <b>prep kit</b> is created for translation it is given a version number that LRM uses to coordinate sending and receiving translations and email notifications.
; localization : (L10n) The process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text.
 
  +
; LRM : See <b>Lingoport Resource Manager</b>
 
  +
; LingoBot <span id="lingobot"></span>: A customized bot for Lingoport Slack and MS Team integration
; LRM Server: This term is used interchangeably with <b>LRM</b>.
 
  +
; LRM Database: The MySQL database used by <b>LRM</b> to manage resource files and translation status. The database is created when <b>LRM Server</b> is installed.
 
  +
; Lingoport Resource Manager <span id="LingoportResourceManager"></span>: (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.
;LRM Project: The encapsulation of the location of the resource files, locales for translation and processing information for <b>LRM</b>.
 
  +
;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.
 
  +
; Lingoport Dashboard <span id="LingoportDashboard"></span>: 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.
;project name: In LRM, to work with <b>resource files</b>, 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 <b>group</b>, but the same project name can exist in different groups.
 
  +
;project definition file: Or <b>project definition xml</b>. A file used to create a project. Both <b>LRM</b> and <b>Globalyzer Lite</b> use project definition files to create projects. The xml files used are very different.
 
  +
; Lingoport Dashboard Client <span id="LingoportDashboardClient"></span>: Uses the Globalyzer scans and LRM analysis data and uploads the information to the dashboard browser for a visual representation of issues and resources.
;repository : The location of the source code for the <b>Globalyzer project</b> and/or the location of the resource files for <b>LRM</b>.
 
  +
;resource bundle: A file that contains locale-specific data. It is a way of internationalizing an application by making the code locale-independent.
 
  +
; Lingoport Dashboard Server <span id="LingoportDashboardServer"></span>: The <b>SonarQube</b> dashboard that has been modified with Lingoport widgets to display Globalyzer issues and LRM resource status.
;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 <b>Globalyzer Server</b>
 
  +
; Lingoport Project <span id="LingoportProject"></span>: A Globalyzer project and an LRM project that is displayed in the Lingoport Dashboard.
; scan : Analyze source code to detect globalyzer issues using <b>rule sets</b> from the <b>Globalyzer server</b>.
 
  +
; 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. [https://www.sonarqube.org/ SonarQube]
 
  +
; Lingoport Products <span id="LingoportProducts"></span>: Tntegrated Lingoport components: Globalyzer, Lingoport Resource Manager (LRM), InContext Translation and InContext QA which create & maintain software for any language or cultural format in every release increment.
; stack installer : See <b>Lingoport Suite Installer</b>
 
  +
; test : A test definition used to trying bookmarks. <span id="test"></span>
 
  +
; Lingoport Suite Installer <span id="LingoportSuiteInstaller"></span> : The automated install application to install the <b>Lingoport Suite</b>.
; 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.
 
  +
; localization <span id="localization"></span>: (L10n) The process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text.
; Workbench : See <b>Globalyzer Workbench</b>
 
  +
  +
; localization vendor <span id="localizationVendor"></span> : also, localization service provider, a translation vendor responsible for translating resource files.
  +
  +
; LRM <span id="LRM"></span>: See <b>Lingoport Resource Manager</b>
  +
  +
; LRM Server <span id="LRMServer"></span>: This term is used interchangeably with <b>LRM</b>.
  +
  +
; LRM Database <span id="LRMDatabase"></span>: The MySQL database used by <b>LRM</b> to manage resource files and translation status. The database is created when <b>LRM Server</b> is installed.
  +
  +
;LRM Project <span id="LRMProject"></span>: The encapsulation of the location of the resource files, locales for translation and processing information for <b>LRM</b>.
  +
  +
;Master Node <span id="MasterNode"></span>: When using Distributed Pull Requests, the Master Node is the system with Jenkins, Dashboard and the Node configurations defined.
  +
  +
;On-boarding <span id="onboarding"></span>: The process of creating the LRM projects and the corresponding jobs in Jenkins for automation.
  +
  +
;prep kit <span id="prepkit"></span>: 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 <span id="projectname"></span>: In LRM, to work with <b>resource files</b>, 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 <b>group</b>, but the same project name can exist in different groups.
  +
  +
;project definition file <span id="projectdefn"></span>: Or <b>project definition xml</b>. A file used to create a project. Both <b>LRM</b> and <b>Globalyzer Lite</b> use project definition files to create projects. The xml files used are very different.
  +
  +
;repository <span id="repository"></span> : The location of the source code for the <b>Globalyzer project</b> and/or the location of the resource files for <b>LRM</b>.
  +
  +
;resource bundle <span id="resourcebundle"></span>: A file that contains locale-specific data. It is a way of internationalizing an application by making the code locale-independent.
  +
  +
;resource files <span id="resourcefiles"></span>: A set of files, one file for each spoken language which stores localized text.
  +
  +
; rule set <span id="ruleset"></span> : 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 <b>Globalyzer Server</b>
  +
  +
; scan <span id="scan"></span>: Analyze source code to detect globalyzer issues using <b>rule sets</b> from the <b>Globalyzer server</b>.
  +
  +
; SonarQube <span id="SonarQube"></span>: 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. [https://www.sonarqube.org/ SonarQube]
  +
  +
; Stack Installer <span id="stackinstaller"></span> : The automated install application to install the Lingoport products and supporting software on the server.
  +
  +
; Stack Updater <span id="stackupdater"></span> : The automated application to update the Lingoport products and supporting software on the server.
  +
  +
; translation management systems <span id="TMS"></span>: (TMS) Programs and vendors that support complex translation tasks.
  +
  +
; translation vendor <span id="translationvendor"></span>: Company or group that does the actual translation from one language to another.
  +
  +
;version control system <span id="vcs"></span>: The versioning system used for code repositories. These can be Git, Subversion, TFS (Team Foundation Server).
  +
  +
; VCS <span id="vcs"></span>: See '''Version control system'''
  +
  +
; Workbench <span id="Workbench"></span>: See <b>Globalyzer Workbench</b>

Latest revision as of 21:23, 10 December 2019

See a definition of this term on the Terms and Definition page by clicking this link.

Definitions

Agent Node
When using Distributed Pull Requests, the Agent Node is the system is the system that performs the work before returning to the Master node. There can be one or more Agent Nodes.
Automation Job
The Jenkins job created to check code out of the repository. The code is scanned by Globalyzer or it the resource files are monitored and sent for translation.
Baseline
A snapshot of the state of the resource files at a particular point in time. Used by LRM in order to detect changes to existing keys. Also helps detect modifications to translation resource files that were not made by LRM.
Branch
When a developer works on a new change, they should create a branch. This allows them to work on the fix without changing the master code. When development is complete, the branch is merged back into the master code.
Computer Assisted Translation
Translation system utilizing automated tranlation.
Continuous Globalization
The process of integrating internationalization (i18n) and localization (L10n) continuously into software development.
Continuous Globalization System  
A system with LRM, Globalyzer Client, Jenkins, and Dashboard which can communicate with the code repository to get updated code as well as send and receive resource files from translation management systems.
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.
Continuous Integration Continuous Delivery (or Deployment)
(CICD or CI/CD) A variation of Continuous Integration
Dashboard  
See Lingoport Dashboard
Dashboard Client
See Lingoport Dashboard Client
Dashboard System  
The physical machine where the Dashboard Server and Dashboard Client reside.
Decorated  
A decorated string in a resource file contains a URL so that translators can see the context of the resource.
Developer Machine  
is where you install the Globalyzer clients so that internationalization and localization issues can be addressed.
Embedded String  
A hard-coded string in source code. For internationalization, this must be externalized to a resource file for translation.
False Positive  
an issue that has been detected by a rule in a ruleset as a candidate for internationalization that does not need to be translated for a variety of reasons.
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 in IDE
Globalyzer Lite incorporated into common IDEs (Integrated Development Environment) such as Eclipse, IntelliJ, and Visual Studio.
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.
headless installation  
Installing LRM or Globalyzer using an XML file with settings instead of using the installation GUI or answering prompts from the command line. It is also a way to automate installation.
InContext Translation  
Allows the translator to see the context of strings in the translation management system (TMS) or computer assisted translation (CAT) system.
InContext QA  
Enables users to review translations in their context and make improvement suggestions.
instrumented resource files  
Internal Lingoport process to enable InContext features on resource files.
Integrated Developement Environment (IDE) 
software application that provides comprehensive facilities to computer programmers for software development. An IDE normally consists of a source code editor, build automation tools and a debugger.
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. The End User License Agreement for the Jenkins Plugin is located at JenkinsPluginEULA
Jenkins job
An automation script that runs under Jenkins.
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.
LingoBot
A customized bot for Lingoport Slack and MS Team integration
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 Dashboard Client
Uses the Globalyzer scans and LRM analysis data and uploads the information to the dashboard browser for a visual representation of issues and resources.
Lingoport Dashboard Server
The SonarQube dashboard that has been modified with Lingoport widgets to display Globalyzer issues and LRM resource status.
Lingoport Project
A Globalyzer project and an LRM project that is displayed in the Lingoport Dashboard.
Lingoport Products
Tntegrated Lingoport components: Globalyzer, Lingoport Resource Manager (LRM), InContext Translation and InContext QA 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.
localization vendor  
also, localization service provider, a translation vendor responsible for translating resource files.
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.
Master Node
When using Distributed Pull Requests, the Master Node is the system with Jenkins, Dashboard and the Node configurations defined.
On-boarding
The process of creating the LRM projects and the corresponding jobs in Jenkins for automation.
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  
The automated install application to install the Lingoport products and supporting software on the server.
Stack Updater  
The automated application to update the Lingoport products and supporting software on the server.
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.
version control system
The versioning system used for code repositories. These can be Git, Subversion, TFS (Team Foundation Server).
VCS
See Version control system
Workbench
See Globalyzer Workbench