Lingoport Wiki - User contributions [en]

Command Center Release Notes

2026-04-14T19:50:19Z

Olibouban:

= Upcoming =
== Version 4.2.z (''Expected'' May 2026) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples| ChatGPT]]

=== Localyzer ===

==== XTM Context ====
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

==== String Prompting ====
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

==== Min/Max String Length ====
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

==== Do Not Translate (DNT) ====
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

==== ChatGPT ====
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

==== Signed Commits ====
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

==== ICU Message Format - CLRD Updates ====
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Overall===

==== API ====
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

==== UI Improvements====
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

==== Fixes ====
* 9264 - WorldServer Project ID is editable again.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-14T19:48:50Z

Olibouban: /* Version 4.2.z (Expected May 2026) */

= Upcoming =
== Version 4.2.z (''Expected'' May 2026) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples| ChatGPT]]

=== Localyzer ===

==== XTM Context ====
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

==== String Prompting ====
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

==== Min/Max String Length ====
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

==== Do Not Translate (DNT) ====
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

==== ChatGPT ====
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

==== Signed Commits ====
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

==== ICU Message Format - CLRD Updates ====
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Command Center ===

==== API ====
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

==== UI Improvements====
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

==== Fixes ====
* 9264 - WorldServer Project ID is editable again.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-14T19:48:35Z

Olibouban:

= Upcoming =
== Version 4.2.z (Expected May 2026) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples| ChatGPT]]

=== Localyzer ===

==== XTM Context ====
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

==== String Prompting ====
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

==== Min/Max String Length ====
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

==== Do Not Translate (DNT) ====
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

==== ChatGPT ====
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

==== Signed Commits ====
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

==== ICU Message Format - CLRD Updates ====
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Command Center ===

==== API ====
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

==== UI Improvements====
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

==== Fixes ====
* 9264 - WorldServer Project ID is editable again.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-14T19:47:59Z

Olibouban:

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples| ChatGPT]]

=== Localyzer ===

==== XTM Context ====
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

==== String Prompting ====
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

==== Min/Max String Length ====
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

==== Do Not Translate (DNT) ====
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

==== ChatGPT ====
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

==== Signed Commits ====
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

==== ICU Message Format - CLRD Updates ====
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Command Center ===

==== API ====
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

==== UI Improvements====
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

==== Fixes ====
* 9264 - WorldServer Project ID is editable again.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Figma API Project

2026-04-14T14:19:00Z

Olibouban: Olibouban moved page Figma API Project to Figma Plugin and Localyzer Project

#REDIRECT [[Figma Plugin and Localyzer Project]]

Figma Plugin and Localyzer Project

2026-04-14T14:19:00Z

Olibouban: Olibouban moved page Figma API Project to Figma Plugin and Localyzer Project

= Introduction =
'''Show translations within Figma with the Lingoport Localyzer Figma plugin.'''

To get the Figma plugin, log on to your Figma account and follow this link:
* https://www.figma.com/community/plugin/1202323341358312750/Lingoport-Localyzer

The video below explains how to configure and use the Figma plugin:
* https://vimeo.com/817611549

The image will be used below to show the Figma side of the configuration:

[[File:Figma Intro.png|600px]]
''Lingoport Localyzer Figma plugin: the page was translated into French.''

== Set up overview ==

To set up the Figma Plugin with Command Center, the following elements need to be configured:
* '''An API User''': the link between the Figma plugin and the Command Center Localyzer project
* '''A repository / branch''' with <code>figma/locales/en/translation.json</code>
* A '''Command Center Figma project''' configured on the repository
* Provide access to the Command Center Localyzer project to the '''API User'''
* The '''Figma plugin''' in Figma

== Overall interaction ==

=== From Figma to Command Center Localyzer===
From the Figma plugin, strings are sent to an existing Command Center Localyzer project's repository. Those strings are stashes in a repository under a top level directory called <code>locales</code>, a sub-directory called <code>en</code> (if English is the source locale), and in a file called <code>translation.json</code>: so
* <code>figma/locales/en/translation.json</code>

The Command Center Localyzer project leverages the overall functionality for any other Command Center Localyzer projects, such as access, email notification, TMS, analysis, translation, etc.

=== From Command Center Localyzer to Translation ===
As a Localyzer project, the <code>translation.json</code> file can be sent for translation, like any other projects. Best is to keep two letters locales, such as <code>ja</code> for Japanese/Japan or <code>fr</code> for French/France.
The translated files will be stashed in the repository under their respective locale directory, for example
* <code>figma/locales/fr/translation.json</code>
* <code>figma/locales/ja/translation.json</code>

=== From Command Center back to Figma ===
For those strings which were passed from Figma to Localyzer and were translated, the Figma plugin will retrieve those translations and display the page in that locale. Those strings which were not translated will show in the source locale.

= Create API user =
API Users are used to authenticate and authorize API actions on Command Center. The Figma plugin needs an API user and token in order to communicate with a Command Center Localyzer project with that API User configured.

To set up an API user, please see:
* [[Users %26 Teams#Create and Configure Users]]

And choose the role API user. The API user name and token will be used to configure the Figma plugin.

= Create a Command Center Figma Project =
[[Create_a_Figma_project]]

= Set up the Lingoport Localyzer Figma plugin=
To get the Figma plugin, log on to your Figma account and follow this link:

* https://www.figma.com/community/plugin/1202323341358312750/Lingoport-Localyzer

or navigate to the plugin search box and type <code>Lingoport</code> as shown in the introduction image above

Enter the following configuration elements for the Lingoport Localyzer Figma plugin:
* The URL to your Command Center
* The API user name configured above
* The API token

[[File:Figma Plugin.png|center|200px]]

At that point, the drop down below will show those projects accessible to the API User. Select he project configured above.

== Context ==
Optionally, click the '''Enable Context Screenshots''' checkbox: This option associates the design element as the context for the strings sent to Command Center for translation. This works with projects whose TMS or LLM has an InContext server.

== Modes and Variable Tables ==
Optionally, click the '''Enable Variable Table Translation'''. This option leverages the Figma Modes Variable Tables. See:
* https://help.figma.com/hc/en-us/articles/15343816063383-Modes-for-variables

'''If your organization does not use Modes, do not click this option'''.

If it does, this option allows for a faster and more elegant solution. It also allows to see the variable tables with each column showing one of the 'modes', here one of the locales. Switch locales on the <page>[var tables] to see the design in a different locale, including the keys used later on by developers with 'Figma 2 Dev'.

[[File:FigmaVariableTable.png|center|700px]]

* '1': Once translation is returned, if the Variable Table option is enabled, a new page with 'Var Table' shows.
* '2': Select the locale, or 'mode' in this Figma framework, in which to view the application
* '3': To open the table with the variables, click on 'Variable Table'
* '4': Each column is a 'mode', here a locale. This table provides one view with the source strings, the keys, the translated strings.

= Verification of the setup, actions =
* With the plugin active, in the source English page, select a few items to be sent to Command Center Localyzer using the selection cursor.
* The selected strings will appear in the plugin.
* Click on the x to eliminate those strings which do not need to be sent to Localyzer.
* Click Review export.
* Click Export to Command Center.

* In Command Center Localyzer, analyze the project: The number of source words should now have increased.

* Send the file to translation.

* Upon translation, go back to Figma.

In Figma, select one of the locale that was translated: A new page appears, as shown in the introduction above for French, with the locale in square brackets, as with <code>[fr]</code> above.

To verify the context was associated correctly, browse to the associated Localyzer project, navigate to the String Manager and click on the context indicator.

Globalyzer and ChatGPT

2026-04-09T14:17:08Z

Olibouban: /* ChatGPT only Scanning */

== ChatGPT Use in Globalyzer ==

Use ChatGPT either:
* As a second pass once Globalyzer Scanning using Rules has identified candidate issues
* Directly to scan for i18n issues

== Globalyzer Rules Based Scanning + ChatGPT ==

In the Globalyzer Settings of each project locate "Apply ChatGPT prediction to Globalyzer reports" select "Yes". This will bring up a ChatGPT token form entry.
* Copy your ChatGPT Token in this field.
* The ChatGPT token will start with "sk-" and is generally around 50 characters in length.
 

[[File:Chatgpt-GZ-Enable.png|1024px|center]]

=== ChatGPT Functionality ===

Once the Token has been added to the configuration, the next time a project analysis is performed there will be an automatic query to ChatGPT for every item identified as an issue by Globalyzer. This occurs post Globalyzer Scan and the run details are logged in the same way as a project run. It is important to note that the scan will only occur if a particular issue has not been previously scanned. This means that if an analysis is performed again immediately after an analysis run, only issues which are new or changed since the previous analysis will be sent to ChatGPT. This reduces the overall cost of incorporating ChatGPT into a Globalyzer environment.

=== Issues Page ChatGPT Indicators ===
Once an analysis has completed, opening up the Issues page will show there is a new icon being provided for each issue detected as highlighted below. This icon indicates the ChatGPT determined result for each issue as to whether ChatGPT identifies the issue as either:
* True positive "Orange"
* False positive "Green".

[[File:IssuesChatgptIcons.png|1024px|center]]

=== Issues Page Individual Issue ChatGPT Indicators ===

When expanding a single issue as shown below, in addition to the normally found items, there is an indicator for AI Prediction similar to what was shown prior to expanding the issue. Also, below the code snippet there is a new button "AI prediction reason". Selecting this button will send another request to ChatGPT asking for a more detailed explanation of why the line item was determined to be a true or false positive. Using this functionality will provide more information on what the determining factor was as additional time is taken by ChatGPT to analyze the reasoning. This can sometimes result in a change from true positive to false positive or the reverse.

[[File:IssuesAiPredictive.png|1024px|center]]

=== AI Prediction Reason ===

*Currently In Progress

=== Cost of Incorporation ===

Although it is impossible to be completely accurate regarding the costs of leveraging ChatGPT in Globalyzer, below are some real use data collecting that should prove useful. The Prediction Type of "AI Prediction" is the automated prediction that is obtained after each project analysis is performed. The AI Prediction Reason is the more in-depth query to determine the reasoning that a true positive or false positive was arrived at in the AI Prediction Scan.

*The below data was captured in October of 2025 for reference.

{| border="1" class="wikitable" style="text-align:left; width=50%;"
! Prediction Type !! Issues Checked !! Tokens Used !! Tokens/Issue !! Positive Issues !! Negative Issues !! Input Cost !! Output Cost !! Total Cost !! Cost/Issue
|-
| AI Prediction || 96 || 5417 || 56.43 || 48 || 48 || $0.014 || $0.015 || $0.03 || $0.003125
|-
| AI Prediction Reason|| TBD || TBD || TBD || TBD || TBD || TBD || TBD || TBD || TBD
|}

== ChatGPT only Scanning ==
Globalyzer can also use ChatGPT directly without using the Globalyzer Scanning rules. The result will be reported in the same way as with Globalyzer Rules. However, the fine control that Globalyzer rules permits is not available with a direct ChatGPT scanning.

The cost of scanning is directly dependent on the size of the source code.

Globalyzer and ChatGPT

2026-04-09T14:15:49Z

Olibouban:

Globalyzer and ChatGPT

2026-04-09T14:14:28Z

Olibouban: /* ChatGPT Use in Globalyzer */

== ChatGPT Use in Globalyzer ==

Use ChatGPT either:
* As a second pass once Globalyzer Scanning using Rules has identified candidate issues
* Directly to scan for i18n issues

=== Globalyzer Rules Based Scanning + ChatGPT ===

In the Globalyzer Settings of each project locate "Apply ChatGPT prediction to Globalyzer reports" select "Yes". This will bring up a ChatGPT token form entry.
* Copy your ChatGPT Token in this field.
* The ChatGPT token will start with "sk-" and is generally around 50 characters in length.
 

[[File:Chatgpt-GZ-Enable.png|1024px|center]]

==== ChatGPT Functionality ====

Once the Token has been added to the configuration, the next time a project analysis is performed there will be an automatic query to ChatGPT for every item identified as an issue by Globalyzer. This occurs post Globalyzer Scan and the run details are logged in the same way as a project run. It is important to note that the scan will only occur if a particular issue has not been previously scanned. This means that if an analysis is performed again immediately after an analysis run, only issues which are new or changed since the previous analysis will be sent to ChatGPT. This reduces the overall cost of incorporating ChatGPT into a Globalyzer environment.

==== Issues Page ChatGPT Indicators ====
Once an analysis has completed, opening up the Issues page will show there is a new icon being provided for each issue detected as highlighted below. This icon indicates the ChatGPT determined result for each issue as to whether ChatGPT identifies the issue as either:
* True positive "Orange"
* False positive "Green".

[[File:IssuesChatgptIcons.png|1024px|center]]

==== Issues Page Individual Issue ChatGPT Indicators ====

When expanding a single issue as shown below, in addition to the normally found items, there is an indicator for AI Prediction similar to what was shown prior to expanding the issue. Also, below the code snippet there is a new button "AI prediction reason". Selecting this button will send another request to ChatGPT asking for a more detailed explanation of why the line item was determined to be a true or false positive. Using this functionality will provide more information on what the determining factor was as additional time is taken by ChatGPT to analyze the reasoning. This can sometimes result in a change from true positive to false positive or the reverse.

[[File:IssuesAiPredictive.png|1024px|center]]

==== AI Prediction Reason ====

*Currently In Progress

=== ChatGPT only Scanning ===
Globalyzer can also use ChatGPT directly without using the Globalyzer Scanning rules. The result will be reported in the same way as with Globalyzer Rules. However, the fine control that Globalyzer rules permits is not available with a direct ChatGPT scanning.

=== Cost of Incorporation ===

Although it is impossible to be completely accurate regarding the costs of leveraging ChatGPT in Globalyzer, below are some real use data collecting that should prove useful. The Prediction Type of "AI Prediction" is the automated prediction that is obtained after each project analysis is performed. The AI Prediction Reason is the more in-depth query to determine the reasoning that a true positive or false positive was arrived at in the AI Prediction Scan.

*The below data was captured in October of 2025 for reference.

{| border="1" class="wikitable" style="text-align:left; width=50%;"
! Prediction Type !! Issues Checked !! Tokens Used !! Tokens/Issue !! Positive Issues !! Negative Issues !! Input Cost !! Output Cost !! Total Cost !! Cost/Issue
|-
| AI Prediction || 96 || 5417 || 56.43 || 48 || 48 || $0.014 || $0.015 || $0.03 || $0.003125
|-
| AI Prediction Reason|| TBD || TBD || TBD || TBD || TBD || TBD || TBD || TBD || TBD
|}

Globalyzer and ChatGPT

2026-04-09T14:13:13Z

Olibouban:

== ChatGPT Use in Globalyzer ==

Use ChatGPT either:
* As a second pass once Globalyzer Scanning using Rules has identified candidate issues
* Directly to scan for i18n issues

=== Enabling ChatGPT as a Second Pass on candidate issues ===

In the Globalyzer Settings of each project locate "Apply ChatGPT prediction to Globalyzer reports" select "Yes". This will bring up a ChatGPT token form entry.
* Copy your ChatGPT Token in this field.
* The ChatGPT token will start with "sk-" and is generally around 50 characters in length.
 

[[File:Chatgpt-GZ-Enable.png|1024px|center]]

==== ChatGPT Functionality ====

Once the Token has been added to the configuration, the next time a project analysis is performed there will be an automatic query to ChatGPT for every item identified as an issue by Globalyzer. This occurs post Globalyzer Scan and the run details are logged in the same way as a project run. It is important to note that the scan will only occur if a particular issue has not been previously scanned. This means that if an analysis is performed again immediately after an analysis run, only issues which are new or changed since the previous analysis will be sent to ChatGPT. This reduces the overall cost of incorporating ChatGPT into a Globalyzer environment.

==== Issues Page ChatGPT Indicators ====
Once an analysis has completed, opening up the Issues page will show there is a new icon being provided for each issue detected as highlighted below. This icon indicates the ChatGPT determined result for each issue as to whether ChatGPT identifies the issue as either:
* True positive "Orange"
* False positive "Green".

[[File:IssuesChatgptIcons.png|1024px|center]]

==== Issues Page Individual Issue ChatGPT Indicators ====

When expanding a single issue as shown below, in addition to the normally found items, there is an indicator for AI Prediction similar to what was shown prior to expanding the issue. Also, below the code snippet there is a new button "AI prediction reason". Selecting this button will send another request to ChatGPT asking for a more detailed explanation of why the line item was determined to be a true or false positive. Using this functionality will provide more information on what the determining factor was as additional time is taken by ChatGPT to analyze the reasoning. This can sometimes result in a change from true positive to false positive or the reverse.

[[File:IssuesAiPredictive.png|1024px|center]]

==== AI Prediction Reason ====

*Currently In Progress

=== ChatGPT as the Scanning Mechanism ===
Globalyzer can also use ChatGPT directly without using the Globalyzer Scanning rules. The result will be reported in the same way as with Globalyzer Rules. However, the fine control that Globalyzer rules permits is not available with a direct ChatGPT scanning.

=== Cost of Incorporation ===

Although it is impossible to be completely accurate regarding the costs of leveraging ChatGPT in Globalyzer, below are some real use data collecting that should prove useful. The Prediction Type of "AI Prediction" is the automated prediction that is obtained after each project analysis is performed. The AI Prediction Reason is the more in-depth query to determine the reasoning that a true positive or false positive was arrived at in the AI Prediction Scan.

*The below data was captured in October of 2025 for reference.

{| border="1" class="wikitable" style="text-align:left; width=50%;"
! Prediction Type !! Issues Checked !! Tokens Used !! Tokens/Issue !! Positive Issues !! Negative Issues !! Input Cost !! Output Cost !! Total Cost !! Cost/Issue
|-
| AI Prediction || 96 || 5417 || 56.43 || 48 || 48 || $0.014 || $0.015 || $0.03 || $0.003125
|-
| AI Prediction Reason|| TBD || TBD || TBD || TBD || TBD || TBD || TBD || TBD || TBD
|}

Create a Globalyzer only project

2026-04-09T14:07:38Z

Olibouban: /* Setting */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =
Globalyzer scans code for i18n issues based on two different methods:
* using [https://www.globalyzer.com/gzserver/help/usersguide/ruleSets.html rules] configured in [https://www.globalyzer.com/gzserver/help/usersguide/toc.html Globalyzer Server] with an optional LLM (ChatGPT) second pass on those issues
* using an LLM (ChatGPT) directly

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a [[System_Files | System file]].

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''LiteProjectDefinition.xml'''

then the entry for Project Definition File would be:

/lingoport/LiteProjectDefinition.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-09T14:05:42Z

Olibouban: /* Project Definition File */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =
Globalyzer scans code for i18n issues based on two different methods:
* using [https://www.globalyzer.com/gzserver/help/usersguide/ruleSets.html rules] configured in [https://www.globalyzer.com/gzserver/help/usersguide/toc.html Globalyzer Server] with an optional LLM (ChatGPT) second pass on those issues
* using an LLM (ChatGPT) directly

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a [[System_Files | System file]].

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-09T14:04:28Z

Olibouban: /* Globalyzer Settings */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =
Globalyzer scans code for i18n issues based on two different methods:
* using [https://www.globalyzer.com/gzserver/help/usersguide/ruleSets.html rules] configured in [https://www.globalyzer.com/gzserver/help/usersguide/toc.html Globalyzer Server] with an optional LLM (ChatGPT) second pass on those issues
* using an LLM (ChatGPT) directly

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-09T14:03:50Z

Olibouban: /* Globalyzer Settings */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =
Globalyzer scans code for i18n issues based on two different methods:
* using [[https://www.globalyzer.com/gzserver/help/usersguide/ruleSets.html|rules]] configured in [[https://www.globalyzer.com/gzserver/help/usersguide/toc.html|Globalyzer Server]] with an optional LLM (ChatGPT) second pass on those issues
* using an LLM (ChatGPT) directly

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-09T14:00:49Z

Olibouban: /* Globalyzer Settings */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =
Globalyzer scans code for i18n issues based on two different methods:
* using rules configured in Globalyzer Server with an optional LLM (ChatGPT) second pass on those issues
* using an LLM (ChatGPT) directly

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-09T14:00:30Z

Olibouban: /* Globalyzer Settings */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =
Globalyzer scans code for i18n issues based on two different methods:
* using rules configured in Globalyzer Server with an optional LLM (ChatGPT) second pass on those issues
* using an LLM (ChatGPT) directly

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-06T21:51:59Z

Olibouban: /* Samples */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Command Center Release Notes

2026-04-06T21:51:20Z

Olibouban: /* Globalyzer */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples| ChatGPT]]

=== XTM Context ===
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is editable again.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-06T21:51:08Z

Olibouban: /* Globalyzer */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples| ChatGPT}}

=== XTM Context ===
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is editable again.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Create a Globalyzer only project

2026-04-06T21:49:31Z

Olibouban: /* Globalyzer Settings */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using an LLM ]

== Setting ==

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-06T21:48:57Z

Olibouban: /* Data Source Settings */

= Data Source Settings=

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Create a Globalyzer only project

2026-04-06T21:48:11Z

Olibouban: /* Data Source Settings */

= Data Source Settings=

== Project Definition File ==
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

==== Samples====
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using an LLM ]

== Create ==

For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.

[[File:GzDSSelection.png|center|600px]]

If the repository has branches that merge into the project branch, this can be specified.

Click ''Next''

=Project Name =

The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.

[[File:GzName.png|center|600px]]

# Set the '''Group Name'''. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
# Set the '''Project Name'''. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
# Select the '''Project Run Type'''. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.

Select ''Next''

=Accessors =

[[File:GzAccessors.png|center|600px]]

Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.

Select ''Next''

= Globalyzer Settings =

[[File:GzLitePDF.png|center|600px]]

Both of the prompts on this page depend on files in the '''Settings -> System Files -> Globalyzer Lite Files''' and '''Custom Scripts'''. If these are not set up then use the default settings.

'''Script to Generate Globalyzer reports'''.

'''Apply ChatGPT Prediction to Globalyzer Reports'''. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.

'''ChatGPT Token'''. Token used by ChatGPT when leveraging ChatGPT predictions.

For details on using ChatGPT with Globalyzer see [[Globalyzer and ChatGPT]]

'''Project Definition File''' Where in the repository is the Globalyzer Lite Project Definition file?

For example, if your repository is
<nowiki>https://github.com/Acme/MyProject</nowiki>

and the Lite Project Definition File is in the '''lingoport''' folder and called '''PDF.xml'''

then the entry for Project Definition File would be:

/lingoport/PDF.xml

If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: '''Invalid lite file'''. The file needs to be correct before moving forward.

Select '''Next'' to validate the Globalyzer configuration:

=Validate Globalyzer Configuration=

[[File:GzValidate.png|center|600px]]

Click ''Create'' to finalize the project creation. This will display the new project. Click Analyze for the first results.

Individual Project Tasks

2026-04-06T21:46:38Z

Olibouban: /* Project Definition File */

= Introduction =
[[File:ProjectOverview2.jpg|500px|center]]
When a user selects a project name from the Projects page, the Project Overview page comes up with a summary of the project. There are a number of tabs on the top of the page. The tab that is selected is highlighted. For this example the Overview button [[File:OverviewIconSelected.jpg|60px]] is highlighted for the Project Overview page.

* '''Overview''' - a summary of the project, showing the data source, history, and a summary of Globalyzer and Localyzer configuration
* '''Globalyzer''' - a detail of the Globalyzer information including the number of issues found
* '''Localyzer''' - a detail of the Localyzer information including the locales and translation status
* '''Issues''' - detailed information about the Globalyzer and Localyzer issues
* '''Logs''' - report of the various actions performed on the project.
* '''Configure''' - allows the user to modify the project.

= Analyze Project =
[Admin, Manager]

[[File:InProcessAnalyzeProject.jpg|500px|center]]

The Analyze Project icon [[File:AnalyzeProjectIcon.jpg|30px]] will run the project. When the button is selected, the icon will be shown twirling and a message will come up in the upper left about the job processing.

= Overview =
[Admin, Manager, Developer, Translator]

[[File:ProjectOverview2.jpg|500px|center]]

Once a project is created, selecting its name will open the Project Overview. Note that the Overview tab [[File:OverviewIconSelected.jpg|60px]] on the top is highlighted. The Overview page is a project summary page, showing the Globalyzer and Localyzer summaries and the Project History. Any of the analysis lines are selectable and will open the corresponding logs.

The Analyze project button [[File:AnalyzeProjectIcon.jpg|30px]] will run the project.

= Globalyzer =
[Admin, Manager, Developer, Translator]

[[File: GlobalyzerReport.jpg|500px|center]]

The Globalyzer Icon [[File:GlobalyzerIcon2.jpg|60px]] opens the Globalyzer Report page with the details of the Globalyzer analysis.

* '''Total Remaining Issues''' - all the issues that Globayzer has identified. This card is selectable and will take you to the Issues page.
* '''Total Issues Fixed''' - how many issues have been fixed since the project was created.
* '''Total Issues Density''' - number of issues divided by the number of lines of code that were scanned.
* '''Issues Types Breakdown''' - What types of issues were found.
* '''Issues Priorities Breakdown''' or '''Issues Severities Breakdown'''- A list of the severity of the issues. This can be toggled in the Advanced Settings.
* '''Issue Scans Breakdown''' - The rulesets used and the items scanned for.

= Localyzer =

[Admin, Manager, Developer, Translator]

[[File:LocalyzerReport.jpg|500px|center]]

The Localyzer Icon [[File:LocalyzerIcon2.jpg|60px]] opens up the Localyzer Report page. The Localyzer page has a number of icons on the left side for actions that can be done.

[[File:SendKitToTranslation.jpg|30px]] '''Send kit to translation''' - send the latest prep kit to be translated at the specified Translation Management System or Machine Translation engine.

[[File:CheckImportIcon.jpg|30px]] '''Check Import''' - Check the translation management system to see if translations are available to import. If previous translations passed the incoming checks but failed on pushing to the repository, Check Import will try again pushing to the repository those checked files.

[[File:LocalyzerDownloadFilesToTranslate.jpg|30px]] '''[[Download files to translate]]''' - Download the files for a translation kit. Those files may have been sent to a TMS or an MT. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:LocalyzerUploadTranslatedFiles.jpg|30px]] '''[[Upload translated files]]''' - Upload files which were translated for a prep kit sent to translation for one locale. The files may have been sent to a TMS. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:DeactivateLastTranslationKitIcon.jpg|30px]] '''Deactivate last translation kit''' - deactivate the last translation kit that was sent. A translation kit cannot be deactivated if any part of it has been imported.

[[File:ResetAllTranslationKitsIcon.jpg|30px]] '''Reset all translation kits''' - this is used as a reset for the project.

[[File:CreateProjectBaselineIcon.jpg|30px]] '''Create project baseline''' - Set the baseline so that the database can keep track of translation changes and imports. While creating and configuring the project, it does not have a baseline.

= String Manager =

== Introduction video ==
Click on the image below to watch a String Manager introductory video:
[[File:String Manager Video.jpg|200px|center|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]

== Overview ==
[Admin, Manager, Developer, Translator]

[[File:String Manager.jpg|500px|center]]

String manager provides visibility into each key/value pair managed by Localyzer. A link for a specific resource points the browser to GitHub, GitLab or Bitbucket repository/project/branch/key-value pair. Typically, only developers will have access to their repositories and modify source strings.

'''Developers''' create and maintain the '''source''' strings, and if some strings need to be changed, only developers can change them. Users without access to the repository can copy the link and send it to the development team with some explanation, via Slack, Teams, Email, etc.

'''Localyzer''' makes changes to the '''target files''' with translations, pseudo-translation, context files, or LocalyzerQA type files. Developers should not modify those, especially outside of the branch where Localyzer pushed them, for fear of merge conflicts.

== Search ==

From the search box input text, find strings that match by
* their values
* their keys
* their filename
* their description

== Filter ==
Filtering is based on attributes of the key value pairs:
* to be sent
* sent and are not yet translated
* translated
* to be reviewed (or not)
* reviewed (or not)
* have context (or not)

== Sort ==

Sort strings based on
* the text itself
* the key
* the filename
* the time it was found.

* In the screen shot above, strings that match 'model' and are 'to be sent' are displayed.

Strings can be set 'to be reviewed', or 'reviewed', or neither. Certain strings will be marked 'to be reviewed' by the system. Filtering allows to select strings based on the status of the string.

== Expanded view ==

To see the expanded view of a key/value pair, click on the right down arrow.

[[File:StringManagerExpandedView.png|center|500px]]

* The top label shows the string value
* File and line number: The location of the string
* String key: the key for that string
* Source reviewed: a yes/no flag to indicate if the string was reviewed
* Source review recommended: a yes/no flag to indicate that string may be rewritten
* Do not translate: if set, the translation must match the source string
* String length min/max: If set, the source and translated strings number of characters must be within the boundaries. Click the arrow to set the boundaries
* Prompt: The specific string prompt, passed to the translation connection. See [[Prompting]].
* Translation status: The string was translated, is being translated, has not been translated in how many locales
** Note: To see which are those locales, hover over the numbers

== Multi String Selection ==

To select specific strings, click on the multistring selector, then click each string:

[[File:Multiselection.png|center|500px]]

To help with the selection, use filter and search.

=== Send selected string to translation ===

Once strings are selected, click '''Send to translation''', pick the locales (all, some), and click '''Send selected strings'''.

[[File:MultiselectionTranslation.png|center|500px]]

=== Context Capture (See below) ===

== Context Capture ==

For project whose [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS has an InContext server]], context can be acquired in 3 different ways and shown in the String Manager.

=== Webapp Context Capture ===
Project must be configured with a context locale, say 'la' for Latin. This will create a set of resource files in the context locale, - like 'la' (Latin). To capture the context, run the application in the Context Locale (la) and use the [[InContext_Installation#Chrome_Extension_Installation|Lingoport Google Chrome extension]] to capture the context. The context will be pushed to the InContext Server associated with the TMS.

=== Figma ===
Use the Figma extension with the [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin|Enable Context Screenshots]] option set, on a project whose TMS as an InContext Server.

Each string will then be sent to Command Center with the design element as the context. The context PNG will be stored in the InContext Server.

=== Add Screenshots ===
Another option is to use the multi string selector '''or''' the context indicator to add a screen shot as a context for those selected strings.

'''Multi selector and Context'''
* Click on the multi selector (the list list icon)
* Select the strings
* Click on 'Assign Context Image'
* Add an image
* Click 'Upload'

[[File:Multi Select Screenshot.png|500px|center]]

'''Context Indicator''' for an individual string association:
* Click on the context selector
* Add an image
* Click 'Upload'

== Context Viewing ==
When context has been associated with a string, the context indicator will show up as 'blue'. Otherwise, it will stay 'grey'. To view a context, click on the indicator. The context will pop up.

[[File:Show Context.png| 500px|center]]

Filter those strings which do or don't have context, as above.

== Sending Context to Translation ==
Context works for projects whose TMS has been configured with an InContext Server and PXML (see below). When sending files to translation, the PXML file will have an lrm_incontext element with the URL to the context for that string, held in the InContext Server.

Here is an example of Trados Enterprise showing the context:
[[File:Context All results - dogs.jpg|center |500px]]

=== PXML ===
When sending translation with context, best is to send them as PXML files.

* [[PXML | PXML]]

=== Prompting ===
Prompting is passing textual data for the project files to be translated. Prompting can be at the System level, the Project level, and the String level:

See: [[Prompting]]

Prompting can then be used by an LLM, optionally with Context, so that the translation is of better quality.

=== ChatGPT / LLM ===
When sending to an LLM configured with InContext Server, the context will be passed as an automatic prompt for better quality translation, as showing a string on an application screenshot helps an LLM disambiguate the meaning and potential translation for a UI string.

= Issues =
[Admin, Manager, Developer, Translator]

[[File:Issues.jpg|500px|center]]

The Issues icon [[File:IssuesIcon.jpg|60px]] opens the Issues page and will show all the Globalyzer and Localyzer issues. Once the issues page is open, the issues can be searched, filtered and sorted.

[[File:IssuesDetail.jpg|500px|center]]
Selecting an issue in the list will show more detail about the issue, including its status, type and priority.
*'''Go to line in source code''' - will take the user to the line of code in the repository, for users with repository access.
*'''Learn more about this issue''' - will open up documentation about the issue.
*'''Comments''' - any comments can be added about Globalyzer issues. They will remain after further analyses.

= Project logs =
[Admin, Manager, Developer, Translator]

[[File:ProjectLogs.jpg|500px|center]]

The Console Logs icon [[File:LogsIcon.jpg|60px]] opens up the logs to show when the project has been analyzed. Selecting any of the lines will open the log and show more detail.

[[File:ProjectLogDetail.jpg|500px|center]]

In this example:
* The user making the change is '''testAdmin'''
* The version of Command Center is given
* One setting in the '''General Settings''' was changed
** Tags were modified on the project: '''FTP''' to '''FTP''' and '''Build 5'''

= Edit Project configuration =
[Admin, Manager]

[[File:EditProjectConfiguration.jpg|500px|center]]

The Edit icon [[File:ConfigureIcon.jpg|60px]] will open the Edit Project Configuration page. There are several icons on the left side of the page.

[[File:ValidateProjectIcon.jpg|30px]] - validate the Localyzer configuration finds the resource files.

[[File:DuplicateProjectIcon.jpg|30px]] - make a copy of this project

[[File:CleanProjectWorkspaceIcon.jpg|30px]] - refresh the project

[[File:DeleteProjectIcon.jpg|30px]] - remove the project from Command Center

[[General Settings]]

[[Data Source Settings]]

[[Access Settings]]

[[Globalyzer Settings]]

[[Localyzer Settings]]

== Edit a project ==

There are multiple ways to get to edit a project.

[[File:EditProject1.jpg|500px|center]]

First, from the Projects page, hover over the project and the Edit button will appear.

[[File:EditProject2.jpg|500px|center]]

Second, select the project name (or the Globalyzer or Localyzer icon) to go to the Overview, Globalyzer or Localyzer page. Select the Configure button on the top to get to the Edit Project Configuration page.

[[File:EditProjectConfiguration.jpg|500px|center]]

From this page, any of the settings can be changed.

When changes are made and saved, a notice appears at the top of the screen about the project being updated. The project does not run until it is manually run or by an automated task.

Individual Project Tasks

2026-04-06T21:40:47Z

Olibouban: /* Project Definition File */

= Introduction =
[[File:ProjectOverview2.jpg|500px|center]]
When a user selects a project name from the Projects page, the Project Overview page comes up with a summary of the project. There are a number of tabs on the top of the page. The tab that is selected is highlighted. For this example the Overview button [[File:OverviewIconSelected.jpg|60px]] is highlighted for the Project Overview page.

* '''Overview''' - a summary of the project, showing the data source, history, and a summary of Globalyzer and Localyzer configuration
* '''Globalyzer''' - a detail of the Globalyzer information including the number of issues found
* '''Localyzer''' - a detail of the Localyzer information including the locales and translation status
* '''Issues''' - detailed information about the Globalyzer and Localyzer issues
* '''Logs''' - report of the various actions performed on the project.
* '''Configure''' - allows the user to modify the project.

= Analyze Project =
[Admin, Manager]

[[File:InProcessAnalyzeProject.jpg|500px|center]]

The Analyze Project icon [[File:AnalyzeProjectIcon.jpg|30px]] will run the project. When the button is selected, the icon will be shown twirling and a message will come up in the upper left about the job processing.

= Overview =
[Admin, Manager, Developer, Translator]

[[File:ProjectOverview2.jpg|500px|center]]

Once a project is created, selecting its name will open the Project Overview. Note that the Overview tab [[File:OverviewIconSelected.jpg|60px]] on the top is highlighted. The Overview page is a project summary page, showing the Globalyzer and Localyzer summaries and the Project History. Any of the analysis lines are selectable and will open the corresponding logs.

The Analyze project button [[File:AnalyzeProjectIcon.jpg|30px]] will run the project.

= Globalyzer =
[Admin, Manager, Developer, Translator]

[[File: GlobalyzerReport.jpg|500px|center]]

The Globalyzer Icon [[File:GlobalyzerIcon2.jpg|60px]] opens the Globalyzer Report page with the details of the Globalyzer analysis.

* '''Total Remaining Issues''' - all the issues that Globayzer has identified. This card is selectable and will take you to the Issues page.
* '''Total Issues Fixed''' - how many issues have been fixed since the project was created.
* '''Total Issues Density''' - number of issues divided by the number of lines of code that were scanned.
* '''Issues Types Breakdown''' - What types of issues were found.
* '''Issues Priorities Breakdown''' or '''Issues Severities Breakdown'''- A list of the severity of the issues. This can be toggled in the Advanced Settings.
* '''Issue Scans Breakdown''' - The rulesets used and the items scanned for.

=== Project Definition File ===
To create a Globalyzer project, a Project Definition File must exist in a repository, either
* in the project repository, typically under <code>lingoport/LiteProjectDefinition.xml</code> or
* as a System file.

Samples:
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using an LLM ]

= Localyzer =

[Admin, Manager, Developer, Translator]

[[File:LocalyzerReport.jpg|500px|center]]

The Localyzer Icon [[File:LocalyzerIcon2.jpg|60px]] opens up the Localyzer Report page. The Localyzer page has a number of icons on the left side for actions that can be done.

[[File:SendKitToTranslation.jpg|30px]] '''Send kit to translation''' - send the latest prep kit to be translated at the specified Translation Management System or Machine Translation engine.

[[File:CheckImportIcon.jpg|30px]] '''Check Import''' - Check the translation management system to see if translations are available to import. If previous translations passed the incoming checks but failed on pushing to the repository, Check Import will try again pushing to the repository those checked files.

[[File:LocalyzerDownloadFilesToTranslate.jpg|30px]] '''[[Download files to translate]]''' - Download the files for a translation kit. Those files may have been sent to a TMS or an MT. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:LocalyzerUploadTranslatedFiles.jpg|30px]] '''[[Upload translated files]]''' - Upload files which were translated for a prep kit sent to translation for one locale. The files may have been sent to a TMS. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:DeactivateLastTranslationKitIcon.jpg|30px]] '''Deactivate last translation kit''' - deactivate the last translation kit that was sent. A translation kit cannot be deactivated if any part of it has been imported.

[[File:ResetAllTranslationKitsIcon.jpg|30px]] '''Reset all translation kits''' - this is used as a reset for the project.

[[File:CreateProjectBaselineIcon.jpg|30px]] '''Create project baseline''' - Set the baseline so that the database can keep track of translation changes and imports. While creating and configuring the project, it does not have a baseline.

= String Manager =

== Introduction video ==
Click on the image below to watch a String Manager introductory video:
[[File:String Manager Video.jpg|200px|center|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]

== Overview ==
[Admin, Manager, Developer, Translator]

[[File:String Manager.jpg|500px|center]]

String manager provides visibility into each key/value pair managed by Localyzer. A link for a specific resource points the browser to GitHub, GitLab or Bitbucket repository/project/branch/key-value pair. Typically, only developers will have access to their repositories and modify source strings.

'''Developers''' create and maintain the '''source''' strings, and if some strings need to be changed, only developers can change them. Users without access to the repository can copy the link and send it to the development team with some explanation, via Slack, Teams, Email, etc.

'''Localyzer''' makes changes to the '''target files''' with translations, pseudo-translation, context files, or LocalyzerQA type files. Developers should not modify those, especially outside of the branch where Localyzer pushed them, for fear of merge conflicts.

== Search ==

From the search box input text, find strings that match by
* their values
* their keys
* their filename
* their description

== Filter ==
Filtering is based on attributes of the key value pairs:
* to be sent
* sent and are not yet translated
* translated
* to be reviewed (or not)
* reviewed (or not)
* have context (or not)

== Sort ==

Sort strings based on
* the text itself
* the key
* the filename
* the time it was found.

* In the screen shot above, strings that match 'model' and are 'to be sent' are displayed.

Strings can be set 'to be reviewed', or 'reviewed', or neither. Certain strings will be marked 'to be reviewed' by the system. Filtering allows to select strings based on the status of the string.

== Expanded view ==

To see the expanded view of a key/value pair, click on the right down arrow.

[[File:StringManagerExpandedView.png|center|500px]]

* The top label shows the string value
* File and line number: The location of the string
* String key: the key for that string
* Source reviewed: a yes/no flag to indicate if the string was reviewed
* Source review recommended: a yes/no flag to indicate that string may be rewritten
* Do not translate: if set, the translation must match the source string
* String length min/max: If set, the source and translated strings number of characters must be within the boundaries. Click the arrow to set the boundaries
* Prompt: The specific string prompt, passed to the translation connection. See [[Prompting]].
* Translation status: The string was translated, is being translated, has not been translated in how many locales
** Note: To see which are those locales, hover over the numbers

== Multi String Selection ==

To select specific strings, click on the multistring selector, then click each string:

[[File:Multiselection.png|center|500px]]

To help with the selection, use filter and search.

=== Send selected string to translation ===

Once strings are selected, click '''Send to translation''', pick the locales (all, some), and click '''Send selected strings'''.

[[File:MultiselectionTranslation.png|center|500px]]

=== Context Capture (See below) ===

== Context Capture ==

For project whose [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS has an InContext server]], context can be acquired in 3 different ways and shown in the String Manager.

=== Webapp Context Capture ===
Project must be configured with a context locale, say 'la' for Latin. This will create a set of resource files in the context locale, - like 'la' (Latin). To capture the context, run the application in the Context Locale (la) and use the [[InContext_Installation#Chrome_Extension_Installation|Lingoport Google Chrome extension]] to capture the context. The context will be pushed to the InContext Server associated with the TMS.

=== Figma ===
Use the Figma extension with the [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin|Enable Context Screenshots]] option set, on a project whose TMS as an InContext Server.

Each string will then be sent to Command Center with the design element as the context. The context PNG will be stored in the InContext Server.

=== Add Screenshots ===
Another option is to use the multi string selector '''or''' the context indicator to add a screen shot as a context for those selected strings.

'''Multi selector and Context'''
* Click on the multi selector (the list list icon)
* Select the strings
* Click on 'Assign Context Image'
* Add an image
* Click 'Upload'

[[File:Multi Select Screenshot.png|500px|center]]

'''Context Indicator''' for an individual string association:
* Click on the context selector
* Add an image
* Click 'Upload'

== Context Viewing ==
When context has been associated with a string, the context indicator will show up as 'blue'. Otherwise, it will stay 'grey'. To view a context, click on the indicator. The context will pop up.

[[File:Show Context.png| 500px|center]]

Filter those strings which do or don't have context, as above.

== Sending Context to Translation ==
Context works for projects whose TMS has been configured with an InContext Server and PXML (see below). When sending files to translation, the PXML file will have an lrm_incontext element with the URL to the context for that string, held in the InContext Server.

Here is an example of Trados Enterprise showing the context:
[[File:Context All results - dogs.jpg|center |500px]]

=== PXML ===
When sending translation with context, best is to send them as PXML files.

* [[PXML | PXML]]

=== Prompting ===
Prompting is passing textual data for the project files to be translated. Prompting can be at the System level, the Project level, and the String level:

See: [[Prompting]]

Prompting can then be used by an LLM, optionally with Context, so that the translation is of better quality.

=== ChatGPT / LLM ===
When sending to an LLM configured with InContext Server, the context will be passed as an automatic prompt for better quality translation, as showing a string on an application screenshot helps an LLM disambiguate the meaning and potential translation for a UI string.

= Issues =
[Admin, Manager, Developer, Translator]

[[File:Issues.jpg|500px|center]]

The Issues icon [[File:IssuesIcon.jpg|60px]] opens the Issues page and will show all the Globalyzer and Localyzer issues. Once the issues page is open, the issues can be searched, filtered and sorted.

[[File:IssuesDetail.jpg|500px|center]]
Selecting an issue in the list will show more detail about the issue, including its status, type and priority.
*'''Go to line in source code''' - will take the user to the line of code in the repository, for users with repository access.
*'''Learn more about this issue''' - will open up documentation about the issue.
*'''Comments''' - any comments can be added about Globalyzer issues. They will remain after further analyses.

= Project logs =
[Admin, Manager, Developer, Translator]

[[File:ProjectLogs.jpg|500px|center]]

The Console Logs icon [[File:LogsIcon.jpg|60px]] opens up the logs to show when the project has been analyzed. Selecting any of the lines will open the log and show more detail.

[[File:ProjectLogDetail.jpg|500px|center]]

In this example:
* The user making the change is '''testAdmin'''
* The version of Command Center is given
* One setting in the '''General Settings''' was changed
** Tags were modified on the project: '''FTP''' to '''FTP''' and '''Build 5'''

= Edit Project configuration =
[Admin, Manager]

[[File:EditProjectConfiguration.jpg|500px|center]]

The Edit icon [[File:ConfigureIcon.jpg|60px]] will open the Edit Project Configuration page. There are several icons on the left side of the page.

[[File:ValidateProjectIcon.jpg|30px]] - validate the Localyzer configuration finds the resource files.

[[File:DuplicateProjectIcon.jpg|30px]] - make a copy of this project

[[File:CleanProjectWorkspaceIcon.jpg|30px]] - refresh the project

[[File:DeleteProjectIcon.jpg|30px]] - remove the project from Command Center

[[General Settings]]

[[Data Source Settings]]

[[Access Settings]]

[[Globalyzer Settings]]

[[Localyzer Settings]]

== Edit a project ==

There are multiple ways to get to edit a project.

[[File:EditProject1.jpg|500px|center]]

First, from the Projects page, hover over the project and the Edit button will appear.

[[File:EditProject2.jpg|500px|center]]

Second, select the project name (or the Globalyzer or Localyzer icon) to go to the Overview, Globalyzer or Localyzer page. Select the Configure button on the top to get to the Edit Project Configuration page.

[[File:EditProjectConfiguration.jpg|500px|center]]

From this page, any of the settings can be changed.

When changes are made and saved, a notice appears at the top of the screen about the project being updated. The project does not run until it is manually run or by an automated task.

Individual Project Tasks

2026-04-06T21:40:00Z

Olibouban: /* Globalyzer */

= Introduction =
[[File:ProjectOverview2.jpg|500px|center]]
When a user selects a project name from the Projects page, the Project Overview page comes up with a summary of the project. There are a number of tabs on the top of the page. The tab that is selected is highlighted. For this example the Overview button [[File:OverviewIconSelected.jpg|60px]] is highlighted for the Project Overview page.

* '''Overview''' - a summary of the project, showing the data source, history, and a summary of Globalyzer and Localyzer configuration
* '''Globalyzer''' - a detail of the Globalyzer information including the number of issues found
* '''Localyzer''' - a detail of the Localyzer information including the locales and translation status
* '''Issues''' - detailed information about the Globalyzer and Localyzer issues
* '''Logs''' - report of the various actions performed on the project.
* '''Configure''' - allows the user to modify the project.

= Analyze Project =
[Admin, Manager]

[[File:InProcessAnalyzeProject.jpg|500px|center]]

The Analyze Project icon [[File:AnalyzeProjectIcon.jpg|30px]] will run the project. When the button is selected, the icon will be shown twirling and a message will come up in the upper left about the job processing.

= Overview =
[Admin, Manager, Developer, Translator]

[[File:ProjectOverview2.jpg|500px|center]]

Once a project is created, selecting its name will open the Project Overview. Note that the Overview tab [[File:OverviewIconSelected.jpg|60px]] on the top is highlighted. The Overview page is a project summary page, showing the Globalyzer and Localyzer summaries and the Project History. Any of the analysis lines are selectable and will open the corresponding logs.

The Analyze project button [[File:AnalyzeProjectIcon.jpg|30px]] will run the project.

= Globalyzer =
[Admin, Manager, Developer, Translator]

[[File: GlobalyzerReport.jpg|500px|center]]

The Globalyzer Icon [[File:GlobalyzerIcon2.jpg|60px]] opens the Globalyzer Report page with the details of the Globalyzer analysis.

* '''Total Remaining Issues''' - all the issues that Globayzer has identified. This card is selectable and will take you to the Issues page.
* '''Total Issues Fixed''' - how many issues have been fixed since the project was created.
* '''Total Issues Density''' - number of issues divided by the number of lines of code that were scanned.
* '''Issues Types Breakdown''' - What types of issues were found.
* '''Issues Priorities Breakdown''' or '''Issues Severities Breakdown'''- A list of the severity of the issues. This can be toggled in the Advanced Settings.
* '''Issue Scans Breakdown''' - The rulesets used and the items scanned for.

=== Project Definition File ===
To create a Globalyzer project, a Project Definition File must exist in a repository, either that of the project, typically under lingoport/LiteProjectDefinition.xml or as a System file.

Samples:
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using an LLM ]

= Localyzer =

[Admin, Manager, Developer, Translator]

[[File:LocalyzerReport.jpg|500px|center]]

The Localyzer Icon [[File:LocalyzerIcon2.jpg|60px]] opens up the Localyzer Report page. The Localyzer page has a number of icons on the left side for actions that can be done.

[[File:SendKitToTranslation.jpg|30px]] '''Send kit to translation''' - send the latest prep kit to be translated at the specified Translation Management System or Machine Translation engine.

[[File:CheckImportIcon.jpg|30px]] '''Check Import''' - Check the translation management system to see if translations are available to import. If previous translations passed the incoming checks but failed on pushing to the repository, Check Import will try again pushing to the repository those checked files.

[[File:LocalyzerDownloadFilesToTranslate.jpg|30px]] '''[[Download files to translate]]''' - Download the files for a translation kit. Those files may have been sent to a TMS or an MT. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:LocalyzerUploadTranslatedFiles.jpg|30px]] '''[[Upload translated files]]''' - Upload files which were translated for a prep kit sent to translation for one locale. The files may have been sent to a TMS. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:DeactivateLastTranslationKitIcon.jpg|30px]] '''Deactivate last translation kit''' - deactivate the last translation kit that was sent. A translation kit cannot be deactivated if any part of it has been imported.

[[File:ResetAllTranslationKitsIcon.jpg|30px]] '''Reset all translation kits''' - this is used as a reset for the project.

[[File:CreateProjectBaselineIcon.jpg|30px]] '''Create project baseline''' - Set the baseline so that the database can keep track of translation changes and imports. While creating and configuring the project, it does not have a baseline.

= String Manager =

== Introduction video ==
Click on the image below to watch a String Manager introductory video:
[[File:String Manager Video.jpg|200px|center|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]

== Overview ==
[Admin, Manager, Developer, Translator]

[[File:String Manager.jpg|500px|center]]

String manager provides visibility into each key/value pair managed by Localyzer. A link for a specific resource points the browser to GitHub, GitLab or Bitbucket repository/project/branch/key-value pair. Typically, only developers will have access to their repositories and modify source strings.

'''Developers''' create and maintain the '''source''' strings, and if some strings need to be changed, only developers can change them. Users without access to the repository can copy the link and send it to the development team with some explanation, via Slack, Teams, Email, etc.

'''Localyzer''' makes changes to the '''target files''' with translations, pseudo-translation, context files, or LocalyzerQA type files. Developers should not modify those, especially outside of the branch where Localyzer pushed them, for fear of merge conflicts.

== Search ==

From the search box input text, find strings that match by
* their values
* their keys
* their filename
* their description

== Filter ==
Filtering is based on attributes of the key value pairs:
* to be sent
* sent and are not yet translated
* translated
* to be reviewed (or not)
* reviewed (or not)
* have context (or not)

== Sort ==

Sort strings based on
* the text itself
* the key
* the filename
* the time it was found.

* In the screen shot above, strings that match 'model' and are 'to be sent' are displayed.

Strings can be set 'to be reviewed', or 'reviewed', or neither. Certain strings will be marked 'to be reviewed' by the system. Filtering allows to select strings based on the status of the string.

== Expanded view ==

To see the expanded view of a key/value pair, click on the right down arrow.

[[File:StringManagerExpandedView.png|center|500px]]

* The top label shows the string value
* File and line number: The location of the string
* String key: the key for that string
* Source reviewed: a yes/no flag to indicate if the string was reviewed
* Source review recommended: a yes/no flag to indicate that string may be rewritten
* Do not translate: if set, the translation must match the source string
* String length min/max: If set, the source and translated strings number of characters must be within the boundaries. Click the arrow to set the boundaries
* Prompt: The specific string prompt, passed to the translation connection. See [[Prompting]].
* Translation status: The string was translated, is being translated, has not been translated in how many locales
** Note: To see which are those locales, hover over the numbers

== Multi String Selection ==

To select specific strings, click on the multistring selector, then click each string:

[[File:Multiselection.png|center|500px]]

To help with the selection, use filter and search.

=== Send selected string to translation ===

Once strings are selected, click '''Send to translation''', pick the locales (all, some), and click '''Send selected strings'''.

[[File:MultiselectionTranslation.png|center|500px]]

=== Context Capture (See below) ===

== Context Capture ==

For project whose [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS has an InContext server]], context can be acquired in 3 different ways and shown in the String Manager.

=== Webapp Context Capture ===
Project must be configured with a context locale, say 'la' for Latin. This will create a set of resource files in the context locale, - like 'la' (Latin). To capture the context, run the application in the Context Locale (la) and use the [[InContext_Installation#Chrome_Extension_Installation|Lingoport Google Chrome extension]] to capture the context. The context will be pushed to the InContext Server associated with the TMS.

=== Figma ===
Use the Figma extension with the [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin|Enable Context Screenshots]] option set, on a project whose TMS as an InContext Server.

Each string will then be sent to Command Center with the design element as the context. The context PNG will be stored in the InContext Server.

=== Add Screenshots ===
Another option is to use the multi string selector '''or''' the context indicator to add a screen shot as a context for those selected strings.

'''Multi selector and Context'''
* Click on the multi selector (the list list icon)
* Select the strings
* Click on 'Assign Context Image'
* Add an image
* Click 'Upload'

[[File:Multi Select Screenshot.png|500px|center]]

'''Context Indicator''' for an individual string association:
* Click on the context selector
* Add an image
* Click 'Upload'

== Context Viewing ==
When context has been associated with a string, the context indicator will show up as 'blue'. Otherwise, it will stay 'grey'. To view a context, click on the indicator. The context will pop up.

[[File:Show Context.png| 500px|center]]

Filter those strings which do or don't have context, as above.

== Sending Context to Translation ==
Context works for projects whose TMS has been configured with an InContext Server and PXML (see below). When sending files to translation, the PXML file will have an lrm_incontext element with the URL to the context for that string, held in the InContext Server.

Here is an example of Trados Enterprise showing the context:
[[File:Context All results - dogs.jpg|center |500px]]

=== PXML ===
When sending translation with context, best is to send them as PXML files.

* [[PXML | PXML]]

=== Prompting ===
Prompting is passing textual data for the project files to be translated. Prompting can be at the System level, the Project level, and the String level:

See: [[Prompting]]

Prompting can then be used by an LLM, optionally with Context, so that the translation is of better quality.

=== ChatGPT / LLM ===
When sending to an LLM configured with InContext Server, the context will be passed as an automatic prompt for better quality translation, as showing a string on an application screenshot helps an LLM disambiguate the meaning and potential translation for a UI string.

= Issues =
[Admin, Manager, Developer, Translator]

[[File:Issues.jpg|500px|center]]

The Issues icon [[File:IssuesIcon.jpg|60px]] opens the Issues page and will show all the Globalyzer and Localyzer issues. Once the issues page is open, the issues can be searched, filtered and sorted.

[[File:IssuesDetail.jpg|500px|center]]
Selecting an issue in the list will show more detail about the issue, including its status, type and priority.
*'''Go to line in source code''' - will take the user to the line of code in the repository, for users with repository access.
*'''Learn more about this issue''' - will open up documentation about the issue.
*'''Comments''' - any comments can be added about Globalyzer issues. They will remain after further analyses.

= Project logs =
[Admin, Manager, Developer, Translator]

[[File:ProjectLogs.jpg|500px|center]]

The Console Logs icon [[File:LogsIcon.jpg|60px]] opens up the logs to show when the project has been analyzed. Selecting any of the lines will open the log and show more detail.

[[File:ProjectLogDetail.jpg|500px|center]]

In this example:
* The user making the change is '''testAdmin'''
* The version of Command Center is given
* One setting in the '''General Settings''' was changed
** Tags were modified on the project: '''FTP''' to '''FTP''' and '''Build 5'''

= Edit Project configuration =
[Admin, Manager]

[[File:EditProjectConfiguration.jpg|500px|center]]

The Edit icon [[File:ConfigureIcon.jpg|60px]] will open the Edit Project Configuration page. There are several icons on the left side of the page.

[[File:ValidateProjectIcon.jpg|30px]] - validate the Localyzer configuration finds the resource files.

[[File:DuplicateProjectIcon.jpg|30px]] - make a copy of this project

[[File:CleanProjectWorkspaceIcon.jpg|30px]] - refresh the project

[[File:DeleteProjectIcon.jpg|30px]] - remove the project from Command Center

[[General Settings]]

[[Data Source Settings]]

[[Access Settings]]

[[Globalyzer Settings]]

[[Localyzer Settings]]

== Edit a project ==

There are multiple ways to get to edit a project.

[[File:EditProject1.jpg|500px|center]]

First, from the Projects page, hover over the project and the Edit button will appear.

[[File:EditProject2.jpg|500px|center]]

Second, select the project name (or the Globalyzer or Localyzer icon) to go to the Overview, Globalyzer or Localyzer page. Select the Configure button on the top to get to the Edit Project Configuration page.

[[File:EditProjectConfiguration.jpg|500px|center]]

From this page, any of the settings can be changed.

When changes are made and saved, a notice appears at the top of the screen about the project being updated. The project does not run until it is manually run or by an automated task.

Individual Project Tasks

2026-04-06T21:39:20Z

Olibouban: /* Globalyzer */

= Introduction =
[[File:ProjectOverview2.jpg|500px|center]]
When a user selects a project name from the Projects page, the Project Overview page comes up with a summary of the project. There are a number of tabs on the top of the page. The tab that is selected is highlighted. For this example the Overview button [[File:OverviewIconSelected.jpg|60px]] is highlighted for the Project Overview page.

* '''Overview''' - a summary of the project, showing the data source, history, and a summary of Globalyzer and Localyzer configuration
* '''Globalyzer''' - a detail of the Globalyzer information including the number of issues found
* '''Localyzer''' - a detail of the Localyzer information including the locales and translation status
* '''Issues''' - detailed information about the Globalyzer and Localyzer issues
* '''Logs''' - report of the various actions performed on the project.
* '''Configure''' - allows the user to modify the project.

= Analyze Project =
[Admin, Manager]

[[File:InProcessAnalyzeProject.jpg|500px|center]]

The Analyze Project icon [[File:AnalyzeProjectIcon.jpg|30px]] will run the project. When the button is selected, the icon will be shown twirling and a message will come up in the upper left about the job processing.

= Overview =
[Admin, Manager, Developer, Translator]

[[File:ProjectOverview2.jpg|500px|center]]

Once a project is created, selecting its name will open the Project Overview. Note that the Overview tab [[File:OverviewIconSelected.jpg|60px]] on the top is highlighted. The Overview page is a project summary page, showing the Globalyzer and Localyzer summaries and the Project History. Any of the analysis lines are selectable and will open the corresponding logs.

The Analyze project button [[File:AnalyzeProjectIcon.jpg|30px]] will run the project.

= Globalyzer =
[Admin, Manager, Developer, Translator]

[[File: GlobalyzerReport.jpg|500px|center]]

The Globalyzer Icon [[File:GlobalyzerIcon2.jpg|60px]] opens the Globalyzer Report page with the details of the Globalyzer analysis.

* '''Total Remaining Issues''' - all the issues that Globayzer has identified. This card is selectable and will take you to the Issues page.
* '''Total Issues Fixed''' - how many issues have been fixed since the project was created.
* '''Total Issues Density''' - number of issues divided by the number of lines of code that were scanned.
* '''Issues Types Breakdown''' - What types of issues were found.
* '''Issues Priorities Breakdown''' or '''Issues Severities Breakdown'''- A list of the severity of the issues. This can be toggled in the Advanced Settings.
* '''Issue Scans Breakdown''' - The rulesets used and the items scanned for.

To create a Globalyzer project, a Project Definition File must exist in a repository, either that of the project, typically under lingoport/LiteProjectDefinition.xml or as a System file.

Samples:
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]
* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using an LLM ]

= Localyzer =

[Admin, Manager, Developer, Translator]

[[File:LocalyzerReport.jpg|500px|center]]

The Localyzer Icon [[File:LocalyzerIcon2.jpg|60px]] opens up the Localyzer Report page. The Localyzer page has a number of icons on the left side for actions that can be done.

[[File:SendKitToTranslation.jpg|30px]] '''Send kit to translation''' - send the latest prep kit to be translated at the specified Translation Management System or Machine Translation engine.

[[File:CheckImportIcon.jpg|30px]] '''Check Import''' - Check the translation management system to see if translations are available to import. If previous translations passed the incoming checks but failed on pushing to the repository, Check Import will try again pushing to the repository those checked files.

[[File:LocalyzerDownloadFilesToTranslate.jpg|30px]] '''[[Download files to translate]]''' - Download the files for a translation kit. Those files may have been sent to a TMS or an MT. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:LocalyzerUploadTranslatedFiles.jpg|30px]] '''[[Upload translated files]]''' - Upload files which were translated for a prep kit sent to translation for one locale. The files may have been sent to a TMS. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:DeactivateLastTranslationKitIcon.jpg|30px]] '''Deactivate last translation kit''' - deactivate the last translation kit that was sent. A translation kit cannot be deactivated if any part of it has been imported.

[[File:ResetAllTranslationKitsIcon.jpg|30px]] '''Reset all translation kits''' - this is used as a reset for the project.

[[File:CreateProjectBaselineIcon.jpg|30px]] '''Create project baseline''' - Set the baseline so that the database can keep track of translation changes and imports. While creating and configuring the project, it does not have a baseline.

= String Manager =

== Introduction video ==
Click on the image below to watch a String Manager introductory video:
[[File:String Manager Video.jpg|200px|center|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]

== Overview ==
[Admin, Manager, Developer, Translator]

[[File:String Manager.jpg|500px|center]]

String manager provides visibility into each key/value pair managed by Localyzer. A link for a specific resource points the browser to GitHub, GitLab or Bitbucket repository/project/branch/key-value pair. Typically, only developers will have access to their repositories and modify source strings.

'''Developers''' create and maintain the '''source''' strings, and if some strings need to be changed, only developers can change them. Users without access to the repository can copy the link and send it to the development team with some explanation, via Slack, Teams, Email, etc.

'''Localyzer''' makes changes to the '''target files''' with translations, pseudo-translation, context files, or LocalyzerQA type files. Developers should not modify those, especially outside of the branch where Localyzer pushed them, for fear of merge conflicts.

== Search ==

From the search box input text, find strings that match by
* their values
* their keys
* their filename
* their description

== Filter ==
Filtering is based on attributes of the key value pairs:
* to be sent
* sent and are not yet translated
* translated
* to be reviewed (or not)
* reviewed (or not)
* have context (or not)

== Sort ==

Sort strings based on
* the text itself
* the key
* the filename
* the time it was found.

* In the screen shot above, strings that match 'model' and are 'to be sent' are displayed.

Strings can be set 'to be reviewed', or 'reviewed', or neither. Certain strings will be marked 'to be reviewed' by the system. Filtering allows to select strings based on the status of the string.

== Expanded view ==

To see the expanded view of a key/value pair, click on the right down arrow.

[[File:StringManagerExpandedView.png|center|500px]]

* The top label shows the string value
* File and line number: The location of the string
* String key: the key for that string
* Source reviewed: a yes/no flag to indicate if the string was reviewed
* Source review recommended: a yes/no flag to indicate that string may be rewritten
* Do not translate: if set, the translation must match the source string
* String length min/max: If set, the source and translated strings number of characters must be within the boundaries. Click the arrow to set the boundaries
* Prompt: The specific string prompt, passed to the translation connection. See [[Prompting]].
* Translation status: The string was translated, is being translated, has not been translated in how many locales
** Note: To see which are those locales, hover over the numbers

== Multi String Selection ==

To select specific strings, click on the multistring selector, then click each string:

[[File:Multiselection.png|center|500px]]

To help with the selection, use filter and search.

=== Send selected string to translation ===

Once strings are selected, click '''Send to translation''', pick the locales (all, some), and click '''Send selected strings'''.

[[File:MultiselectionTranslation.png|center|500px]]

=== Context Capture (See below) ===

== Context Capture ==

For project whose [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS has an InContext server]], context can be acquired in 3 different ways and shown in the String Manager.

=== Webapp Context Capture ===
Project must be configured with a context locale, say 'la' for Latin. This will create a set of resource files in the context locale, - like 'la' (Latin). To capture the context, run the application in the Context Locale (la) and use the [[InContext_Installation#Chrome_Extension_Installation|Lingoport Google Chrome extension]] to capture the context. The context will be pushed to the InContext Server associated with the TMS.

=== Figma ===
Use the Figma extension with the [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin|Enable Context Screenshots]] option set, on a project whose TMS as an InContext Server.

Each string will then be sent to Command Center with the design element as the context. The context PNG will be stored in the InContext Server.

=== Add Screenshots ===
Another option is to use the multi string selector '''or''' the context indicator to add a screen shot as a context for those selected strings.

'''Multi selector and Context'''
* Click on the multi selector (the list list icon)
* Select the strings
* Click on 'Assign Context Image'
* Add an image
* Click 'Upload'

[[File:Multi Select Screenshot.png|500px|center]]

'''Context Indicator''' for an individual string association:
* Click on the context selector
* Add an image
* Click 'Upload'

== Context Viewing ==
When context has been associated with a string, the context indicator will show up as 'blue'. Otherwise, it will stay 'grey'. To view a context, click on the indicator. The context will pop up.

[[File:Show Context.png| 500px|center]]

Filter those strings which do or don't have context, as above.

== Sending Context to Translation ==
Context works for projects whose TMS has been configured with an InContext Server and PXML (see below). When sending files to translation, the PXML file will have an lrm_incontext element with the URL to the context for that string, held in the InContext Server.

Here is an example of Trados Enterprise showing the context:
[[File:Context All results - dogs.jpg|center |500px]]

=== PXML ===
When sending translation with context, best is to send them as PXML files.

* [[PXML | PXML]]

=== Prompting ===
Prompting is passing textual data for the project files to be translated. Prompting can be at the System level, the Project level, and the String level:

See: [[Prompting]]

Prompting can then be used by an LLM, optionally with Context, so that the translation is of better quality.

=== ChatGPT / LLM ===
When sending to an LLM configured with InContext Server, the context will be passed as an automatic prompt for better quality translation, as showing a string on an application screenshot helps an LLM disambiguate the meaning and potential translation for a UI string.

= Issues =
[Admin, Manager, Developer, Translator]

[[File:Issues.jpg|500px|center]]

The Issues icon [[File:IssuesIcon.jpg|60px]] opens the Issues page and will show all the Globalyzer and Localyzer issues. Once the issues page is open, the issues can be searched, filtered and sorted.

[[File:IssuesDetail.jpg|500px|center]]
Selecting an issue in the list will show more detail about the issue, including its status, type and priority.
*'''Go to line in source code''' - will take the user to the line of code in the repository, for users with repository access.
*'''Learn more about this issue''' - will open up documentation about the issue.
*'''Comments''' - any comments can be added about Globalyzer issues. They will remain after further analyses.

= Project logs =
[Admin, Manager, Developer, Translator]

[[File:ProjectLogs.jpg|500px|center]]

The Console Logs icon [[File:LogsIcon.jpg|60px]] opens up the logs to show when the project has been analyzed. Selecting any of the lines will open the log and show more detail.

[[File:ProjectLogDetail.jpg|500px|center]]

In this example:
* The user making the change is '''testAdmin'''
* The version of Command Center is given
* One setting in the '''General Settings''' was changed
** Tags were modified on the project: '''FTP''' to '''FTP''' and '''Build 5'''

= Edit Project configuration =
[Admin, Manager]

[[File:EditProjectConfiguration.jpg|500px|center]]

The Edit icon [[File:ConfigureIcon.jpg|60px]] will open the Edit Project Configuration page. There are several icons on the left side of the page.

[[File:ValidateProjectIcon.jpg|30px]] - validate the Localyzer configuration finds the resource files.

[[File:DuplicateProjectIcon.jpg|30px]] - make a copy of this project

[[File:CleanProjectWorkspaceIcon.jpg|30px]] - refresh the project

[[File:DeleteProjectIcon.jpg|30px]] - remove the project from Command Center

[[General Settings]]

[[Data Source Settings]]

[[Access Settings]]

[[Globalyzer Settings]]

[[Localyzer Settings]]

== Edit a project ==

There are multiple ways to get to edit a project.

[[File:EditProject1.jpg|500px|center]]

First, from the Projects page, hover over the project and the Edit button will appear.

[[File:EditProject2.jpg|500px|center]]

Second, select the project name (or the Globalyzer or Localyzer icon) to go to the Overview, Globalyzer or Localyzer page. Select the Configure button on the top to get to the Edit Project Configuration page.

[[File:EditProjectConfiguration.jpg|500px|center]]

From this page, any of the settings can be changed.

When changes are made and saved, a notice appears at the top of the screen about the project being updated. The project does not run until it is manually run or by an automated task.

Individual Project Tasks

2026-04-06T21:37:43Z

Olibouban: /* Globalyzer */

= Introduction =
[[File:ProjectOverview2.jpg|500px|center]]
When a user selects a project name from the Projects page, the Project Overview page comes up with a summary of the project. There are a number of tabs on the top of the page. The tab that is selected is highlighted. For this example the Overview button [[File:OverviewIconSelected.jpg|60px]] is highlighted for the Project Overview page.

* '''Overview''' - a summary of the project, showing the data source, history, and a summary of Globalyzer and Localyzer configuration
* '''Globalyzer''' - a detail of the Globalyzer information including the number of issues found
* '''Localyzer''' - a detail of the Localyzer information including the locales and translation status
* '''Issues''' - detailed information about the Globalyzer and Localyzer issues
* '''Logs''' - report of the various actions performed on the project.
* '''Configure''' - allows the user to modify the project.

= Analyze Project =
[Admin, Manager]

[[File:InProcessAnalyzeProject.jpg|500px|center]]

The Analyze Project icon [[File:AnalyzeProjectIcon.jpg|30px]] will run the project. When the button is selected, the icon will be shown twirling and a message will come up in the upper left about the job processing.

= Overview =
[Admin, Manager, Developer, Translator]

[[File:ProjectOverview2.jpg|500px|center]]

Once a project is created, selecting its name will open the Project Overview. Note that the Overview tab [[File:OverviewIconSelected.jpg|60px]] on the top is highlighted. The Overview page is a project summary page, showing the Globalyzer and Localyzer summaries and the Project History. Any of the analysis lines are selectable and will open the corresponding logs.

The Analyze project button [[File:AnalyzeProjectIcon.jpg|30px]] will run the project.

= Globalyzer =
[Admin, Manager, Developer, Translator]

[[File: GlobalyzerReport.jpg|500px|center]]

The Globalyzer Icon [[File:GlobalyzerIcon2.jpg|60px]] opens the Globalyzer Report page with the details of the Globalyzer analysis.

* '''Total Remaining Issues''' - all the issues that Globayzer has identified. This card is selectable and will take you to the Issues page.
* '''Total Issues Fixed''' - how many issues have been fixed since the project was created.
* '''Total Issues Density''' - number of issues divided by the number of lines of code that were scanned.
* '''Issues Types Breakdown''' - What types of issues were found.
* '''Issues Priorities Breakdown''' or '''Issues Severities Breakdown'''- A list of the severity of the issues. This can be toggled in the Advanced Settings.
* '''Issue Scans Breakdown''' - The rulesets used and the items scanned for.

To create a Globalyzer project, a Project Definition File must exist in a repository, either that of the project, typically under lingoport/LiteProjectDefinition.xml or as a System file.

Samples:
* [[ https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml | Using Globalyzer Server Rules ]]
* [[ https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml | Using an LLM ]]

= Localyzer =

[Admin, Manager, Developer, Translator]

[[File:LocalyzerReport.jpg|500px|center]]

The Localyzer Icon [[File:LocalyzerIcon2.jpg|60px]] opens up the Localyzer Report page. The Localyzer page has a number of icons on the left side for actions that can be done.

[[File:SendKitToTranslation.jpg|30px]] '''Send kit to translation''' - send the latest prep kit to be translated at the specified Translation Management System or Machine Translation engine.

[[File:CheckImportIcon.jpg|30px]] '''Check Import''' - Check the translation management system to see if translations are available to import. If previous translations passed the incoming checks but failed on pushing to the repository, Check Import will try again pushing to the repository those checked files.

[[File:LocalyzerDownloadFilesToTranslate.jpg|30px]] '''[[Download files to translate]]''' - Download the files for a translation kit. Those files may have been sent to a TMS or an MT. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:LocalyzerUploadTranslatedFiles.jpg|30px]] '''[[Upload translated files]]''' - Upload files which were translated for a prep kit sent to translation for one locale. The files may have been sent to a TMS. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

[[File:DeactivateLastTranslationKitIcon.jpg|30px]] '''Deactivate last translation kit''' - deactivate the last translation kit that was sent. A translation kit cannot be deactivated if any part of it has been imported.

[[File:ResetAllTranslationKitsIcon.jpg|30px]] '''Reset all translation kits''' - this is used as a reset for the project.

[[File:CreateProjectBaselineIcon.jpg|30px]] '''Create project baseline''' - Set the baseline so that the database can keep track of translation changes and imports. While creating and configuring the project, it does not have a baseline.

= String Manager =

== Introduction video ==
Click on the image below to watch a String Manager introductory video:
[[File:String Manager Video.jpg|200px|center|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]

== Overview ==
[Admin, Manager, Developer, Translator]

[[File:String Manager.jpg|500px|center]]

String manager provides visibility into each key/value pair managed by Localyzer. A link for a specific resource points the browser to GitHub, GitLab or Bitbucket repository/project/branch/key-value pair. Typically, only developers will have access to their repositories and modify source strings.

'''Developers''' create and maintain the '''source''' strings, and if some strings need to be changed, only developers can change them. Users without access to the repository can copy the link and send it to the development team with some explanation, via Slack, Teams, Email, etc.

'''Localyzer''' makes changes to the '''target files''' with translations, pseudo-translation, context files, or LocalyzerQA type files. Developers should not modify those, especially outside of the branch where Localyzer pushed them, for fear of merge conflicts.

== Search ==

From the search box input text, find strings that match by
* their values
* their keys
* their filename
* their description

== Filter ==
Filtering is based on attributes of the key value pairs:
* to be sent
* sent and are not yet translated
* translated
* to be reviewed (or not)
* reviewed (or not)
* have context (or not)

== Sort ==

Sort strings based on
* the text itself
* the key
* the filename
* the time it was found.

* In the screen shot above, strings that match 'model' and are 'to be sent' are displayed.

Strings can be set 'to be reviewed', or 'reviewed', or neither. Certain strings will be marked 'to be reviewed' by the system. Filtering allows to select strings based on the status of the string.

== Expanded view ==

To see the expanded view of a key/value pair, click on the right down arrow.

[[File:StringManagerExpandedView.png|center|500px]]

* The top label shows the string value
* File and line number: The location of the string
* String key: the key for that string
* Source reviewed: a yes/no flag to indicate if the string was reviewed
* Source review recommended: a yes/no flag to indicate that string may be rewritten
* Do not translate: if set, the translation must match the source string
* String length min/max: If set, the source and translated strings number of characters must be within the boundaries. Click the arrow to set the boundaries
* Prompt: The specific string prompt, passed to the translation connection. See [[Prompting]].
* Translation status: The string was translated, is being translated, has not been translated in how many locales
** Note: To see which are those locales, hover over the numbers

== Multi String Selection ==

To select specific strings, click on the multistring selector, then click each string:

[[File:Multiselection.png|center|500px]]

To help with the selection, use filter and search.

=== Send selected string to translation ===

Once strings are selected, click '''Send to translation''', pick the locales (all, some), and click '''Send selected strings'''.

[[File:MultiselectionTranslation.png|center|500px]]

=== Context Capture (See below) ===

== Context Capture ==

For project whose [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS has an InContext server]], context can be acquired in 3 different ways and shown in the String Manager.

=== Webapp Context Capture ===
Project must be configured with a context locale, say 'la' for Latin. This will create a set of resource files in the context locale, - like 'la' (Latin). To capture the context, run the application in the Context Locale (la) and use the [[InContext_Installation#Chrome_Extension_Installation|Lingoport Google Chrome extension]] to capture the context. The context will be pushed to the InContext Server associated with the TMS.

=== Figma ===
Use the Figma extension with the [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin|Enable Context Screenshots]] option set, on a project whose TMS as an InContext Server.

Each string will then be sent to Command Center with the design element as the context. The context PNG will be stored in the InContext Server.

=== Add Screenshots ===
Another option is to use the multi string selector '''or''' the context indicator to add a screen shot as a context for those selected strings.

'''Multi selector and Context'''
* Click on the multi selector (the list list icon)
* Select the strings
* Click on 'Assign Context Image'
* Add an image
* Click 'Upload'

[[File:Multi Select Screenshot.png|500px|center]]

'''Context Indicator''' for an individual string association:
* Click on the context selector
* Add an image
* Click 'Upload'

== Context Viewing ==
When context has been associated with a string, the context indicator will show up as 'blue'. Otherwise, it will stay 'grey'. To view a context, click on the indicator. The context will pop up.

[[File:Show Context.png| 500px|center]]

Filter those strings which do or don't have context, as above.

== Sending Context to Translation ==
Context works for projects whose TMS has been configured with an InContext Server and PXML (see below). When sending files to translation, the PXML file will have an lrm_incontext element with the URL to the context for that string, held in the InContext Server.

Here is an example of Trados Enterprise showing the context:
[[File:Context All results - dogs.jpg|center |500px]]

=== PXML ===
When sending translation with context, best is to send them as PXML files.

* [[PXML | PXML]]

=== Prompting ===
Prompting is passing textual data for the project files to be translated. Prompting can be at the System level, the Project level, and the String level:

See: [[Prompting]]

Prompting can then be used by an LLM, optionally with Context, so that the translation is of better quality.

=== ChatGPT / LLM ===
When sending to an LLM configured with InContext Server, the context will be passed as an automatic prompt for better quality translation, as showing a string on an application screenshot helps an LLM disambiguate the meaning and potential translation for a UI string.

= Issues =
[Admin, Manager, Developer, Translator]

[[File:Issues.jpg|500px|center]]

The Issues icon [[File:IssuesIcon.jpg|60px]] opens the Issues page and will show all the Globalyzer and Localyzer issues. Once the issues page is open, the issues can be searched, filtered and sorted.

[[File:IssuesDetail.jpg|500px|center]]
Selecting an issue in the list will show more detail about the issue, including its status, type and priority.
*'''Go to line in source code''' - will take the user to the line of code in the repository, for users with repository access.
*'''Learn more about this issue''' - will open up documentation about the issue.
*'''Comments''' - any comments can be added about Globalyzer issues. They will remain after further analyses.

= Project logs =
[Admin, Manager, Developer, Translator]

[[File:ProjectLogs.jpg|500px|center]]

The Console Logs icon [[File:LogsIcon.jpg|60px]] opens up the logs to show when the project has been analyzed. Selecting any of the lines will open the log and show more detail.

[[File:ProjectLogDetail.jpg|500px|center]]

In this example:
* The user making the change is '''testAdmin'''
* The version of Command Center is given
* One setting in the '''General Settings''' was changed
** Tags were modified on the project: '''FTP''' to '''FTP''' and '''Build 5'''

= Edit Project configuration =
[Admin, Manager]

[[File:EditProjectConfiguration.jpg|500px|center]]

The Edit icon [[File:ConfigureIcon.jpg|60px]] will open the Edit Project Configuration page. There are several icons on the left side of the page.

[[File:ValidateProjectIcon.jpg|30px]] - validate the Localyzer configuration finds the resource files.

[[File:DuplicateProjectIcon.jpg|30px]] - make a copy of this project

[[File:CleanProjectWorkspaceIcon.jpg|30px]] - refresh the project

[[File:DeleteProjectIcon.jpg|30px]] - remove the project from Command Center

[[General Settings]]

[[Data Source Settings]]

[[Access Settings]]

[[Globalyzer Settings]]

[[Localyzer Settings]]

== Edit a project ==

There are multiple ways to get to edit a project.

[[File:EditProject1.jpg|500px|center]]

First, from the Projects page, hover over the project and the Edit button will appear.

[[File:EditProject2.jpg|500px|center]]

Second, select the project name (or the Globalyzer or Localyzer icon) to go to the Overview, Globalyzer or Localyzer page. Select the Configure button on the top to get to the Edit Project Configuration page.

[[File:EditProjectConfiguration.jpg|500px|center]]

From this page, any of the settings can be changed.

When changes are made and saved, a notice appears at the top of the screen about the project being updated. The project does not run until it is manually run or by an automated task.

Project Tags & Tokens

2026-04-06T20:15:50Z

Olibouban: /* View Tags */

= Introduction =

Command Center projects can have a number of tags in order to organize and filter projects based on tags. A user has access to a set of projects as assigned by an Administrator or a Manager. A user can then filter projects based on tags.

= View Tags =
[Admin, Manager, Developer, Translator]

Tags are accessible from the Global Settings page.

[[File:ViewTags.jpg|600px|center]]

Tags and their associated tokens can be viewed by all users. Administrator and Manager users can edit, modify and delete tags.
== Copy to Clipboard ==
[Administrator, Manager, Developer, Translator]

[[File:CopyToClipboard1.jpg|600px|center]]

[[File:CopyToClipboard2.jpg|600px|center]]

The tags have a Copy to Clipboard feature that copies the token associated with the tag. The feature can be accessed either:
# From the Manage Tags page
# Selecting the tag and then the Copy to Clipboard icon on the Tag page.

When the button is selected a message Token copied! comes up.

= Create and Configure Tags =
[Administrator, Manager]

[[File:EditTags.jpg|600px|center]]

The Administrator or Manager user can select the [[File:CreateIcon.jpg|20px]] (Create new tag) button on the Manage Tags page to add new tags.

A name is required and the tag can be associated with any of the projects. A token is generated with a possible expiration date.

= Search and Sort Tags =
[Administrator, Manager, Developer, Translator]

[[File:SearchTags.jpg|600px|center]]

[[File:SortTags.jpg|600px|center]]

The tags can sort by ascending or descending for tag name or number of projects.

[[System_Logs_%26_Events|Next: System Logs & Events]]

Project Tags & Tokens

2026-04-06T20:15:14Z

Olibouban: /* Introduction */

= Introduction =

Command Center projects can have a number of tags in order to organize and filter projects based on tags. A user has access to a set of projects as assigned by an Administrator or a Manager. A user can then filter projects based on tags.

= View Tags =
[Admin, Manager, Developer, Translator]

[[File:ViewTags.jpg|600px|center]]

Tags and their associated tokens can be viewed by all users. Administrator and Manager users can edit, modify and delete tags.
== Copy to Clipboard ==
[Administrator, Manager, Developer, Translator]

[[File:CopyToClipboard1.jpg|600px|center]]

[[File:CopyToClipboard2.jpg|600px|center]]

The tags have a Copy to Clipboard feature that copies the token associated with the tag. The feature can be accessed either:
# From the Manage Tags page
# Selecting the tag and then the Copy to Clipboard icon on the Tag page.

When the button is selected a message Token copied! comes up.

= Create and Configure Tags =
[Administrator, Manager]

[[File:EditTags.jpg|600px|center]]

The Administrator or Manager user can select the [[File:CreateIcon.jpg|20px]] (Create new tag) button on the Manage Tags page to add new tags.

A name is required and the tag can be associated with any of the projects. A token is generated with a possible expiration date.

= Search and Sort Tags =
[Administrator, Manager, Developer, Translator]

[[File:SearchTags.jpg|600px|center]]

[[File:SortTags.jpg|600px|center]]

The tags can sort by ascending or descending for tag name or number of projects.

[[System_Logs_%26_Events|Next: System Logs & Events]]

File:DeleteUser.jpg

2026-04-06T20:09:32Z

Olibouban: Olibouban uploaded a new version of File:DeleteUser.jpg

Users & Teams

2026-04-06T20:07:01Z

Olibouban: /* Edit User */

=Introduction=

[[File: CCUserTeams.jpg|600px|center]]

= View Users =
[Administrator, Manager, Developer, Translator]

[[File:ViewUsers.jpg|600px|center]]

All users can view the users in the system as well as their full name and role. Only the administrator user has the ability to add and update users, although individual users can update their own information.

The columns of the Manage Users Page are:
*Username
*Full Name
*Role
*Email
*Time zone (if set)

=Create and Configure Users =
[Administrator]

==Create User==
The Administrator user can select the [[File:CreateIcon.jpg|20px]] (Create new user) button on the Manage Users page to add new users.

[[File:CreateUser.jpg|600px|center]]

The Administrator sets up the username and password, sets the role and then assigns projects and teams to the user. If role of the user is Manager, then the Administrator also assigns the Data Source Credentials.

==Edit User==

In the list of users, the Administrator can edit any user and make any changes to their information. An Edit button appears when hovering over a user entry in the list.

[[File:EditUser.jpg|600px|center]]

Alternatively, the Administrator can first click on the username and from the View User page, click the Edit button.

[[File:EditUser2.jpg|600px|center]]

==Delete User==

[[File:DeleteUser.jpg|600px|center]]

The Edit user page has a Delete button to remove the user.

[[File:DeleteUser2.jpg|600px|center]]

The administrator can also select users and a Delete icon appears at the top of the list to delete all selected users. Alternatively, the administrator can select users and create a team with those users.

=Search and Sort Users =
Any user can select the [[File:SearchIcon.jpg|30px]] (Search icon).

[[File:SearchUsers.jpg|600px|center]]

When leaving the Search panel, the list returns to its original order.

Any user can select the [[File:SortIcon.jpg|30px]] (Sort icon). The users can be sorted on any string. Case does not matter. In this example, all the users from testco were searched for.

[[File:SortUsers.jpg|600px|center]]

Users can be sorted in ascending or descending order by username, role or the full name. When leaving the Sort panel, the list retains its new order.

= View Teams =
[Administrator, Manager, Developer, Translator]

[[File:ViewTeams.jpg|700px|center]]

All users can view the teams in the system as well as the number of projects and users. Only the administrator user has the ability to add and update teams.

= Create and Configure Teams =
[Administrator]

==Create Team==
The Administrator user can select the [[File:CreateIcon.jpg|20px]] (Create new team) button on the Manage Teams page to add new teams.

[[File:CreateTeam.jpg|600px|center]]

The Administrator creates the team name and chooses the members and projects associated with the team.

==Edit Team==

[[File:EditTeam.jpg|600px|center]]

In the list of teams, the Administrator can edit any team and make any changes to their information. An Edit button appears when hovering over a team entry in the list.

[[File:EditTeam2.jpg|600px|center]]

Alternatively, the Administrator can select Username and an Edit team button appears.

==Delete Team==

[[File:DeleteTeam.jpg|600px|center]]

When the Administrator selected the Edit button for a team, the page that comes up has an Delete button.

[[File:DeleteTeam2.jpg|600px|center]]

The Administrator can also select teams and a Delete icon appears at the top of the list to delete the selected teams.

= Search and Sort Teams =
[Administrator, Manager, Developer, Translator]

[[File:SearchTeams.jpg|600px|center]]

A search can be done of all the teams. In this example, all teams with 'team' in the name was searched for.

[[File:SortTeams.jpg|600px|center]]

Teams can be sorted in ascending or descending order by the team name, the number of projects and the number of users. In this example, the teams are sorted in descending order for the number of projects.

[[Data_Source_Credentials|Next: Data Source Credentials]]

File:EditUser2.jpg

2026-04-06T20:04:10Z

Olibouban: Olibouban uploaded a new version of File:EditUser2.jpg

File:CreateUser.jpg

2026-04-06T19:57:17Z

Olibouban: Olibouban uploaded a new version of File:CreateUser.jpg

File:CCUserTeams.jpg

2026-04-06T19:55:09Z

Olibouban: Olibouban uploaded a new version of File:CCUserTeams.jpg

Command Center Release Notes

2026-04-06T16:04:38Z

Olibouban: /* Fixes */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with ChatGPT

=== XTM Context ===
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is editable again.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-06T16:03:56Z

Olibouban: /* UI Improvements */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with ChatGPT

=== XTM Context ===
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
* 9286 - String Manager Context Indicator icon update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is not editable any longer. It must be.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Individual Project Tasks

2026-04-06T16:00:06Z

Olibouban: /* Expanded view */

Command Center Release Notes

2026-04-06T15:59:18Z

Olibouban: /* XTM Context */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with ChatGPT

=== XTM Context ===
* 9251 - Pass [[XTM_Cloud#XTM_and_Context|Context]] the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues
* 9285 - Added option for JSON file patterns
* 9286 - String Manager Context Indicator update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is not editable any longer. It must be.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-06T15:58:41Z

Olibouban: /* Globalyzer */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
* 9241 - Globalyzer Scanning with ChatGPT

=== XTM Context ===
* 9251 - Pass Context the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues
* 9285 - Added option for JSON file patterns
* 9286 - String Manager Context Indicator update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is not editable any longer. It must be.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

XTM Cloud

2026-04-06T15:58:11Z

Olibouban: /* XTM and Context */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the [[About_InContext_Translation|InContext Server]] if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* resx: keys must be the same as the data <code>name</code>
* properties: keys must be the same as the key in the .properties file
* Android strings.xml: keys must be the same as the string <code>name</code>
* iOS .string: keys must be the same as the key in the .string file.

The XTM configuration (filter/parser) must '''ignore''' [[JSON_Resource_Bundles#Typical_with_Keys_for_Comments|JSON comments]].

XTM Cloud

2026-04-06T15:57:58Z

Olibouban: /* XTM and Context */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the [[About_InContext_Translation|InContext Server]] if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* resx: keys must be the same as the data <code>name</code>
* properties: keys must be the same as the key in the .properties file
* Android strings.xml: keys must be the same as the string <code>name</code>
* iOS .string: keys must be the same as the key in the .string file.

The XTM configuration (filter/parser) must ignore [[JSON_Resource_Bundles#Typical_with_Keys_for_Comments|JSON comments]].

XTM Cloud

2026-04-06T15:57:27Z

Olibouban: /* XTM and Context */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the [[About_InContext_Translation|InContext Server]] if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: Keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* resx: Keys must be the same as the data <code>name</code>
* properties: Keys must be the same as the key in the .properties file
* Android strings.xml: Keys must be the same as the string <code>name</code>
* iOS .string: Keys must be the same as the key in the .string file.

The XTM configuration (filter/parser) must ignore [[JSON_Resource_Bundles#Typical_with_Keys_for_Comments|JSON comments]].

XTM Cloud

2026-04-06T15:56:29Z

Olibouban: /* XTM and Context */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the InContext Manager if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: Keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* resx: Keys must be the same as the data <code>name</code>
* properties: Keys must be the same as the key in the .properties file
* Android strings.xml: Keys must be the same as the string <code>name</code>
* iOS .string: Keys must be the same as the key in the .string file.

The XTM configuration (filter/parser) must ignore [[JSON_Resource_Bundles#Typical_with_Keys_for_Comments|JSON comments]].

XTM Cloud

2026-04-06T15:56:12Z

Olibouban: /* XTM and Context */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the InContext Manager if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: Keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* resx: Keys must be the same as the data <code>name</code>
* properties: Keys must be the same as the key in the .properties file
* Android strings.xml: Keys must be the same as the string <code>name</code>
* iOS .string: Keys must be the same as the key in the .string file.

The configuration must ignore [[JSON_Resource_Bundles#Typical_with_Keys_for_Comments|JSON comments]].

XTM Cloud

2026-04-06T15:55:39Z

Olibouban: /* XTM and Context */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the InContext Manager if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: Keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* resx: Keys must be the same as the data <code>name</code>
* properties: Keys must be the same as the key in the .properties file
* Android strings.xml: Keys must be the same as the string <code>name</code>
* iOS .string: Keys must be the same as the key in the .string file.

The configuration must ignore JSON comments (see: [[JSON_Resource_Bundles#Typical_with_Keys_for_Comments]]).

XTM Cloud

2026-04-06T15:50:08Z

Olibouban: /* XTM and Context */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the InContext Manager if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: Keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* resx: Keys must be the same as the data <code>name</code>
* properties: Keys must be the same as the key in the .properties file
* Android strings.xml: Keys must be the same as the string <code>name</code>
* iOS .string: Keys must be the same as the key in the .string file.

XTM Cloud

2026-04-06T15:49:45Z

Olibouban: /* XTM and ICU Message Format */

= Configuring XTM Connection =
== Set the Host URL and other credentials==

[[File:SetUpXTM2.jpg|center|700px]]

== Set up the callback URL and proxy ==

[[File:SetUpXTM3.jpg|center|700px]]

== Configure the Locale Code Set ==

[[File:SetUpFTP4.jpg|center|700px]]

These are a list of possible locales. In general, these can be left as the default values.

== Name the Translation Memory System Connection ==

[[File:SetUpFTP5.jpg|center|700px]]

The Name cannot have a space or a variety of special characters.

= XTM Highlights and Issue =

==LRM Resource Types Supported by XTM==

XTM supports the following LRM resource types:
* .html, .htm
* .json
* .po
* .properties
* .resx
* .rc
* .rxml
* .strings
* strings.xml
* .txt
* .yaml, .yml

XTM does not support the following LRM resource types:
* .rjs
* .msg

==XTM Special Instructions - parameters (e.g. %d, etc)==
XTM expects parameters in '''.strings''' resource files to be numbered.
If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import.
To avoid the error, number of the parameters in the base resource file.
 
For example, if you have the following in a .strings resource file:
"Test.Key" = "Test %d and %d";
It should be changed to:
"Test.Key" = "Test %1$d and %2$d";

Note: a single parameter must be numbered. For example:
"Test.Key_Single" = "Test %1$d";

== XTM and ICU Message Format ==

We reported an issue to XTM around ICU message formats. The issue is that for certain file type, such as JSON files, when a string has an ICU message format, the original file is renamed and this in turns does not get returned via the XTM API integration. In effect, those files must then be re-renamed back to the original files (as for all files which do not have ICU message format for any string value), and imported by hand.

The XTM page on this refers directly to a file from Lingoport, as you can tell by the name of file starting with '''LID'''<digits> - '''LID''' is for '''L'''ocalyzer '''ID'''.

* https://xtm-cloud.atlassian.net/wiki/spaces/EXKB/pages/3273492815/How+to+configure+plurals+in+XTM+Cloud#Supported-file-formats

The work-around in this case may be to upload the files from Localyzer. See:
* [[Upload translated files]]

== XTM and Context ==
Localyzer can pass the context from the InContext Manager if captured prior to sending a prep kit to XTM.

'''XTM support''' must enable this functionality. Furthermore, the XTM configuration must follow the key convention:

* JSON: Keys must be in the form <code>level1.level2.level3</code> as per the tree structure of the incoming file.
* RESX: Keys must be the same as the data <code>name</code>
* properties: Keys must be the same as the key in the .properties file
* Android strings.xml: Keys must be the same as the string <code>name</code>
* iOS .string: Keys must be the same as the key in the .string file.

Command Center Release Notes

2026-04-06T15:41:19Z

Olibouban: /* String Prompting */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Ceter
* 9241 - Globalyzer Scanning with ChatGPT

=== XTM Context ===
* 9251 - Pass Context the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from [[Individual_Project_Tasks#Expanded_view| String Manager]].
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues
* 9285 - Added option for JSON file patterns
* 9286 - String Manager Context Indicator update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is not editable any longer. It must be.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-06T15:40:35Z

Olibouban: /* Do Not Translate (DNT) */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Ceter
* 9241 - Globalyzer Scanning with ChatGPT

=== XTM Context ===
* 9251 - Pass Context the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from String Manager.
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In [[Individual_Project_Tasks#Expanded_view|String Manager]], a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues
* 9285 - Added option for JSON file patterns
* 9286 - String Manager Context Indicator update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is not editable any longer. It must be.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>

Command Center Release Notes

2026-04-06T15:40:12Z

Olibouban: /* Min/Max String Length */

= Upcoming =
== Version 4.2.z (May 2026??) ==

===Globalyzer===
* 8669 - Performance Improvement on Globalyzer Analysis in Command Ceter
* 9241 - Globalyzer Scanning with ChatGPT

=== XTM Context ===
* 9251 - Pass Context the XTM way, associate images with keys

=== String Prompting ===
In 4.1, [[Prompting]] was done at the Translation Connection and the Project level. In this release, prompting is also available at the [[Prompting#String_Level_Prompting|string level]] from String Manager.
* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
* 9061 - Enhancement: Prompting - ChatGpt
* 9258 - Enhancement: Prompting - String Manager key
* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

=== Min/Max String Length ===
Minimum and maximum string lengths can be set from [[Individual_Project_Tasks#Expanded_view|String Manager]].

If a repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.

If a translation comes back outside of the min/max boundaries, it will raise a Localyzer issue.

* 9047 - Enhancement: PXML file - display the min/max, if defined, for a key
* 9048 - Enhancement: Store Min/Max per key-import fails if string length is outside boundary
* 9091 - Enhancement: Resource Issues - include violation of min/max on target files
* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

=== Do Not Translate (DNT) ===
In String Manager, a string can have the DNT set:
* If the repository strings have a different value than the source string, it will raise an issue
* If a translation comes back with a different value than the source string, it will raise an issue

* 8349 - Enhancement: CC String Manager - add Do Not Translate comment
* 9260 - Call to PortalTask.getReplaceDoNotTranslateTask() for setting/unsetting DNT flag
* 9261 - 2 new issues associated with 'DoNotTranslate' check.
* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

=== ChatGPT ===
* 9266 - Support gpt-5.2 and gpt-5.2_mini models
* 9273 - Support changes to ChatGptTaskContext

=== Signed Commits ===
Git signed commits use cryptographic signatures to verify that a commit comes from a trusted author and hasn’t been tampered with. They add a layer of authenticity and integrity to version control by allowing others to validate the identity of the committer.
The [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub|GPG key]] needs to be created from the container.
The Git Data Source configuration needs to set the 'Signed Commit' flag.
* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

=== Command Center API ===
* 9108 - API to trigger a project [[Command_Center_API_Reference#Command_Center_Analysis|analysis]]
* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project|duplicate project]]

=== UI Improvements===
* 9219 - No email option for API users
* 9282 - Option to show or not informational issues
* 9285 - Added option for JSON file patterns
* 9286 - String Manager Context Indicator update
* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

=== ICU Message Format - CLRD Updates ===
The rules for ICU message format have been updated. New Cardinal Rules imply more selectors for some locales, for example 'many' added to French, Spanish, and Italian!
See: https://www.unicode.org/cldr/charts/48/supplemental/language_plural_rules.html
* 7696 - Update to icu4j from 57.1 to 69.1 which will change plural rules
* 9254 - ICU Format import fails if target file has additional selectors that contain parameters
* 9257 - MT-for plural ICU Msg Format, the base resource file should have all the 6 plurals
* 9263 - MT and ICUMessagePattern - Plural rules/Selects are translated if content text is the same
* 9268 - New base resource critical error (MISSING_PLURALS_MT)

=== Fixes ===
* 9264 - WS Project ID is not editable any longer. It must be.

= Supported Version =

== Version 4.1.2 (December 2025) ==

=== Figma2Dev ===

Localyzer Figma plugin has been allowing translation and viewing translated designs in Figma.

In this release, we are adding the ability to '''generate developer resource files,''' source and/or target files - e.g. JSON, resx, properties, etc. - from a Figma design on-boarded with Localyzer using the Localyzer Figma Plugin.

* '''Generate''' the keys to be used by developers and '''view''' them in Figma [9133, 9167, 9129 ]
* Generate the developer resource files [8949, 9128,9157, 9152, 9153, 9154, 9110]
* Configure Figma commit messages [9073]

See:
> Full Webinar (52'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Short Demo (5'): https://www.youtube.com/watch?v=bC-z0Wllm1A&t
> Wiki:
* https://wiki.lingoport.com/Create_a_Figma_project
* https://wiki.lingoport.com/Create_a_Localyzer_only_project#Figma_to_Dev

Figma enhancements:
* Figma project specific creation / edit [9064]
* Figma Lingoport Pluging is now handling '''variable tables''' [9166, 9167, 9194, 9200] See: [[Figma_API_Project#Modes_and_Variable_Tables]]
* Figma Lingoport Plugin improved performance
* Passing images and associating context for prompting (see below, Prompting) See: [[Figma_API_Project#Context]]

===Prompting for LLM ===

Localyzer enables translation via an MT, a TMS, or directly via an LLM. To better leverage TMS using LLMs or LLMs, Localyzer provides the ability to prompt the GenAI.

* Use Context (images) to prompt for translation [9102, 9121, 9122,9082, 9179]
* Configure, set prompt for translation [9163, 9058, 9059, 9060, 9061, 9165]
* Token count [9150]
* Internal setting [9140, 9088]
* TMS with PXML and LLM Connection Configuration [9057, 9141, 9161, 9162, 9164, 9184, 9185]
* Prompt for LLM and PXML project [9163, 9164, 9165 9171,9172, 9173, 9186, 9189]

See:
> Short Demo (7'): https://www.youtube.com/watch?v=jNvdx1lkTo4
> Wiki: https://wiki.lingoport.com/Prompting

=== Major UI Redesign, Useability, and Performance Improvements ===
* New create project by type
* Refactored duplicate Project
* Refactored project edit
* Refactored locale setting
* Updated System Settings
* etc.
> [9045, 9046, 9047, 9048, 9131, 9115, 9116, 9124, 9125, 9134,9148, 9160, 9096]

===InContext Server 2.0.20 ===
* [[Command_Center_API_Reference#Associate_a_Screenshot_Context_with_a_String | API to associate context ]] with a key/value pair
* Ability to delete a context from the API [9152]

=== Miscellaneous ===
* Improved large log handling [9127]
* Improved merging and performance for large JSON file [9069]
* Late kit and notify changes notifications [9105]

= Historic Versions =

== Version 3.1.35 (June 2025) ==

=== Major Localyzer Context Update ===

* '''Webapp Context''' Capture
** See a short [https://www.youtube.com/watch?v=89lu6Zz165Y video]

* '''Figma Context''' Capture [8925, 8926, 8925] for Localyzer
** The Figma plugin version 13 and above allows each design element to be captured and associated with the strings in that element. See [[Figma_API_Project#Set_up_the_Lingoport_Localyzer_Figma_plugin | Figma Configuration]]
** Better filtering of strings to translate [8930]
** See a short [https://www.youtube.com/watch?v=gc3eKjmrDOs video]

* '''Screenshot''' Association to Localyzer Strings [8927, 8781, 8911]
** From String Manager, the ability to select the set of strings associated with a screenshot and [[Individual_Project_Tasks#Context_Capture|upload that screenshot]]
** See a short [https://www.youtube.com/watch?v=yGPO5Qft9NI video]

* [[Individual_Project_Tasks#Sending_Context_to_Translation|Context View]] in '''Trados Enterprise,''' Trados Accelerate, Trados Team [RWS]

* Context View in '''Trados Studio''' [RWS]

* Localyzer [[PXML|PXML]] file format (Preview XML) [8937, 8938, 9000]
** A [[Machine_Translation_and_Translation_Management_System#InContext_Server_and_TMS_Connections|TMS configuration]] can now convert resource files into a PXML file
** With one PXML format as opposed to many resource file formats, only one configuration for those files are necessary on the translation side
** PXML files include the URL to the context whenever applicable; Other string attributes are upcoming

=== Major Localyzer String Manager Improvements ===

* '''String Select''' [8781, 8911]
** Ability to [[Individual_Project_Tasks#Multi_String_Selection|select which strings to be sent to what locale(s)]] from String Manager
** Hover over a string's ''sent, to be sent, outstanding'' indicators to see the associated locales for each category

* A number of tacks were taken to improve the '''responsiveness''' in String Manager
** Better request database handling [8956]
** New Advanced Setting option to run String Refresh right after Analysis [8983]
** HTTP/2

=== UI Improvements ===
* Better indicators of possible actions to take (Analyze, Send to translation, Baselining, etc.) [9006]
* Improved icons [9006]
* Separate System Events from Logs [8994]
* Globalyzer issue expanded view show more lines of code by default, new layout of the expanded view [8810]
* Option to disable running daily analysis [9009]

=== InContext Server v. 2.0.9 ===

* Now serving files [8926, 8922, 8923, 8924] captured from
** the Google Chrome extension for Webapp
** the Figma context
** the screenshot association

=== LocalyzerQA V 1.7.3 ===

* LocalyzerQA now shows the actual string from the file in the repository on 'Error: Not Found', so it's easier to see how to correct it. [8889, 8890, 8999]

== Command Center version 3.0.19 (March 2025) ==

=== TMS Integration ===

* '''[[TSS]]''' Custom Integration [8837]
** A customer request to add a custom integration (TSS) to their translation system with a new internal system handling translations (TI)

* '''Trados Enterprise''' and FTP '''[[Localyzer_Settings#Include.2FExclude_-_Reference_material|Reference Material]]''' [8829]
** Reference material in repositories can be passed to the translation projects. Reference material are specified in the project configuration.

=== New: Download/Upload Feature ===

* '''[[Download_files_to_translate|Download files to translate]]''' from Command Center to your computer [8870]
* '''[[Upload_translated_files|Upload translated files]]''' to Command Center from your computer [8870]

This feature allows for a more manual process, for instance if a TMS cannot return translated files via the normal integration, for whatever reason. It allows the translation without a full TMS, and some fast corrections without going back to an LSP.

'''Note''': UI Icon changes to better reflect action on prep kits and other actions on the overall project, in particular with the addition of this feature.

=== New: Moving Command Center from a non SSO to an SSO System ===
* New easy to use [[Command_Center_Installation#Moving_from_a_non_SSO_to_an_SSO_configuration|scripts]] have been added to help move Command Center over to SSO.

=== New: Create Baseline Visibility ===
Starting with this release, the Create Baseline button only shows up when baselining might be necessary. Before tracking file via baselining, please make sure that the Localyzer project configuration is correct: One way is to Edit the project and click the validate button. Another way could be to look at the Localyzer page and/or the string manager.
See: [[Baseline]]

=== Other enhancements ===
* JSON fix: Fixed an issue for special cases when objects were being split
* Proxy support for AWS S3 data sources
* Proxy support for XTM TMS
* API Enhancement: [8895] [[Command_Center_API_Reference#Command_Center_Project_Get_Locales|getLocales]], retrieves locales for given project with an API user
* API Enhancement: [8901] [[Command_Center_API_Reference|API calls]] all return a JSON payload with a 'code' status
* Ignore empty files: [8780] do not send files without key/value pairs or empty files / blank files
* Show example XML file: [8893] New log output to verify if the correct [[LRM_XML_Support|xmlParser.xml]] system file is used.
* Reduce calls to XTM: [8897] For improved security, allows for connection with less privileges, to the detriment of validation of <code>template</code> and <code>customer</code>
* Handle properties '''keys''' with <code>\:</code>, <code>\=</code> [8898] : Typically, a properties key value pair separator is either <code>:</code> or <code>=</code>. If it has a <code>\=</code> or <code>\:</code> in the '''key''', it must not be construed as a separator.
* Minor bug fixes [8868, 8883, 8879, 8869, 8865, 8876, 8850, 8867]

=== Security Fixes ===

CVE security issues were fixed, including the following high priorities:
* log4j-core.2.3.2
** CVE-2021-44228
** CVE-2017-5645

* snakeyaml 1.30
** CVE-2022-25857
** CVE-2022-1471

*json 20080701
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

*json 20140107
** GHSA-rm7j-f5g5-27vv⁠
** CVE-2023-5072⁠
** CVE-2022-45690⁠
** CVE-2022-45689⁠
** CVE-2022-45688⁠

= Historic Versions =

== Command Center 2.2.28 Release Notes (October 2024) ==
=== TMS Integrations ===
* [[ Machine_Translation_and_Translation_Management_System#View_TMS_Connections | Smartling ]] Integration using the Smartling API
* Click on the [[ Smartling#Smartling_and_Context |Smartling context link ]] showing in the 'Instructions' pane above the string to translate to see the context (see below)
* Lingoport is a Smartling Partner

=== New Features ===
==== Context in String Manager ====
To make use of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: [[About_InContext_Translation |Incontext Server]].
* Web application context accessible from String Manager
* Filter strings with or without context in String Manager

==== Schedule Translations ====
* [[Optional_Localyzer_Settings#Schedule_translations |Schedule]] sending files to be translated in Localyzer project advanced settings

=== Improvements ===
* Added commit author email and name in Git [[ Data_Source_Credentials#Edit_Credentials | Data Source configuration ]]
* Map between unique file names (starting in LID) and repository file names in log files
* [[ Projects_page#Search_Projects | Project Search ]]Find Localyzer project based on target locales
* Improved TFS data source support
* Better definition of Command Center developer v. translator roles
* [[Command_Center_API_Reference | Command Center API Reference]]: added [[ Command_Center_API_Reference#List_Command_Center_users | list users by role]] and [[Command_Center_API_Reference#Add_Users_to_a_Team| add users to a team ]]
* [[ Command_Center_API_Reference#Command_Center_Project_Status | Globalyzer Issue Density ]] added to Project Status API Output
* When translated files failed to be pushed to the repo (protected branch, no write privilege), click [[ Individual_Project_Tasks#Localyzer | 'Check import' ]] after the repo has been fixed to import files previously translated

== Command Center 2.1.24 Release Notes (July 2024) ==
=== TMS Integrations ===
* [https://www.trados.com/product/enterprise/ RWS Trados Enterprise ] Integration Improvements using the Trados Enterprise API
* [https://translated.com/welcome Translated ] Integration as a new TMS
* Update the XTM token for one, many, or all XTM configurations
* Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

=== UI/UX Improvements ===
* UI Performance Improvement: Project Page, String Manager, etc.
* UI Improvements, such as labels for icons, layout, sorting, etc.
* Improved ChatGPT logs and icons for Globalyzer issues
* Globalyzer Issues filtering by Rule Set
* Filtering and chips improvement: better filtering layout and "and" and "or" between chips
* Easier linking from items on one page to other items on another
* Ability to add or replace the locales for one project from another project's locales
* Deletion of Issues Comments

=== Miscellaneous ===
* Post-Import Processing: A new system file type that allows for processing once the translated files are imported
* Advanced Settings option to keep the prep kit tag in the translated files, for traceability

== Command Center 2.0.13 Release Notes (April 2024) ==
=== Overall performance improvements ===
* Localyzer analysis performance improvements
* Issue search/filtering performance improvements
* Project page searching, filtering, sorting performance improvements

=== Introducing '''Localyzer String Manager'''! ===
[[File:String Manager Video.jpg|200px|link=https://www.youtube.com/watch?v=lO1THJAhXSc&ab_channel=Lingoport]]
Introduction video

* '''Show each individual string''' coming from the source resource files (resx, json, properties, etc.)
* Easy '''navigation to the resource''' in the repository, for those with access privileges, such as developers
* '''Filter''' based on those which are
** strings '''to be sent''': check the content before it's sent to translation, verify grammar, spelling as desired
** strings '''send to translation''', not yet returned
** '''fully translated''' strings
* Mark strings:
** Not reviewed
** To be reviewed
** Reviewed
* Filter by the review state (see above)
* Sort by filename, strings, keys, time created
* Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
* Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
* Clean up and restart from scratch
[[ Individual_Project_Tasks#String_Manager | String Manager ]]

=== Updated Projects Page ===
* Faster project page refresh, deep performance improvement
* Infinite scrolling
* Improved filtering
* Improved sorting, now includes sort by
** Group name
** Project name
** Module name
** Globalyzer issue density
** Localyzer percent complete
** Project status
** Time since last changed

== Command Center 1.2.8 Release Notes (March 2024) ==

* Complete overhaul of the [[Individual_Project_Tasks#Issues | Issues page]], especially around Globalyzer issues, including:
** Performance
** Comments
** Filtering - New Filter selector; issues by scan; by Status; by Priority
** Search - On issue text, on code line, on file name, on comments
** Improved navigation from the Globalyzer page to the issues page
** Issue detail
** Status and status change
** Code lines above and below issue line
** Migration from EOL Jenkins/Dashboard
** Display either as priority or as severity
* Simplified '''debug scripts execution'''
* '''Post import processing''' ability
* Improved ChatGPT processing on large number of issues
* '''Android pluralization''' support
* PO pluralization support
* '''Edit''' a Command Center project configuration while a project is running
* Allow project '''validation''' prior to saving the project configuration
* '''Sort the locales''' alphabetically when editing a project
* '''Delete all queued jobs''' ability
* Improved session management

== Command Center 1.1.38 Release Notes (February 2024) ==

* '''Relaxing ICU message format issues''': Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
* '''Check Send''': from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
* '''Reset Project''': ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
* '''Scheduling WorldServer import''': Fixed an issue on the scheduler for WorldServer
* '''TMS/MT Connection Renaming''': ability to rename a connection and reflect the change automatically in all the projects using that connection
* '''Indicate the last SHA for system files''' so it makes it clear which version of the system files are on Command Center

==Command Center 1.1.35 Release Notes (January 2024)==
* '''[https://www.youtube.com/watch?v=DiuQLUla2bA InContext Translation Support]''' When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See [[ About InContext Translation ]]. Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
* '''Analysis Performance Improvements'''
* '''Pseudo-localization, trackback, instrumentation Performance Improvements'''
* '''Start Tracking''': After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
* '''Troubleshooting File System''': A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
* '''System Environment Variables''': For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
* '''DITA Sample Transform''': see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
* '''Advanced Localyzer Settings'''

* Fixed an issue around casing between the repository locales and the TMS or MT locale.

==Command Center 1.1.32 Release Notes (December 2023)==
* '''[[ AWS S3 Data Source Credential ]]''' Support. See also [[ Git to AWS S3 System ]]
* '''[[ Gerrit Data Source Credential ]]''' enhancement for slashes in project URL
* '''Trados Enterprise''' TMS support
* '''[[ LocalyzerQA ]]''' support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
* '''Changing TMS''' for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
* '''[[ API_Reference#Pseudo-localize_a_Command_Center_Project | Pseudo-Localization Remote Calling ]]'''
* '''New Version Indicator''': Command Center indicates when a new version is available.
* Better logging on project configuration changes
* Enhancement in TMS management - internal file configuration.
* Enhancement in Queue management - interaction between queue and maintenance mode.
* Enhancement to Globalyzer and Localyzer handling of issues
* Fix issue on Toggle UI elements
* Fix issue in Saving projects

==Command Center 1.1.11 Release Notes (October 2023)==
* '''XTM''' TMS integration support
* '''WorldServer''' TMS integration support
* '''Custom''' Data Source
* [[ Gerrit Data Source Credential ]]
* [[ GitLab_Pull_Requests_and_Commit_Analysis | GitLab Merge Request ]]
* Alpha '''ChatGPT Translation Support'''
* Alpha '''ChatGPT Globalyzer Support'''

In addition to the Underlying Localyzer engine features:
* [[ Localyzer_Release_Notes#Localyzer_9.2_.28Korea.29_release_-_Fall_2023 | Localyzer 9.2 Korea ]]
* [[ Localyzer_Release_Notes#Localyzer_9.1_.28Joetsu.29_release_-_Feb_2023 | Localyzer 9.1 Joetsu ]]

==Command Center 1.0.154 Release Notes (September 2023)==
The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including
* Administration of the system
* Configuration and on-boarding of individual projects
* Search on project, search on issues
* Filtering on projects, filtering on issues
* Sort on projects, sort on issues
* Improved reporting and logging
* Improved performance

Below are some of the major features in Command Center:

<ul>
<li>Support for SAML/SSO:
The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP.
This allows seamless integration with third party identity providers.
</li>
<li>Support for Globalyzer 6.8.0:
Command Center allows for fast and easy Globalyzer project creation.
For information on Globalyzer, please see: [[About_Globalyzer | Globalyzer]]
</li>
<li>Support for Localyzer 9.2.0:
Command Center allows for fast and easy Localyzer project creation.
For information on Localyzer, please see: [[About_Localyzer | Localyzer]]
</li>
<li>Figma Integration:
Use Command Center to translate Figma designs.
</li>
<li>Project Tagging:
Projects can be organized and filtered using tags.
</li>
<li>API calls:
Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
</li>
<li>Execution Queue:
See what is in the execution queue, delete from the queue, interrupt a running job.
</li>
<li>Improved Issue Management:
The user interface for issues has been entirely redesigned.
</li>
<li>Space and System Requirements Improvements:
In Command Center, no files are pushed to the database as was the case with Dashboard. 
A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
</li>
<li>Access to Code:
Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.
</li>
</ul>