Command Center Release Notes

From Lingoport Wiki
Jump to: navigation, search

Upcoming Version 4.0.z (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:

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 improvement

  • 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.13

  • 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]

Supported Version

Version 3.1.35 (June 2025)

Major Localyzer Context Update

  • Webapp Context Capture
  • 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 Configuration
    • Better filtering of strings to translate [8930]
    • See a short 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 upload that screenshot
    • See a short video
  • Context View in Trados Enterprise, Trados Accelerate, Trados Team [RWS]
  • Context View in Trados Studio [RWS]
  • Localyzer PXML file format (Preview XML) [8937, 8938, 9000]
    • A 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

  • 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.8

  • 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 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

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 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] getLocales, retrieves locales for given project with an API user
  • API Enhancement: [8901] 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 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 template and customer
  • Handle properties keys with \:, \= [8898] : Typically, a properties key value pair separator is either : or =. If it has a \= or \: 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

  • Smartling Integration using the Smartling API
  • Click on the 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: Incontext Server.

  • Web application context accessible from String Manager
  • Filter strings with or without context in String Manager

Schedule Translations

  • Schedule sending files to be translated in Localyzer project advanced settings

Improvements


Command Center 2.1.24 Release Notes (July 2024)

TMS Integrations

  • RWS Trados Enterprise Integration Improvements using the Trados Enterprise API
  • 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!

 String Manager Video.jpg
 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

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 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)

  • 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
  • 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)

In addition to the Underlying Localyzer engine features:


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:

  • 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.
  • Support for Globalyzer 6.8.0: Command Center allows for fast and easy Globalyzer project creation. For information on Globalyzer, please see: Globalyzer
  • Support for Localyzer 9.2.0: Command Center allows for fast and easy Localyzer project creation. For information on Localyzer, please see: Localyzer
  • Figma Integration: Use Command Center to translate Figma designs.
  • Project Tagging: Projects can be organized and filtered using tags.
  • API calls: Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
  • Execution Queue: See what is in the execution queue, delete from the queue, interrupt a running job.
  • Improved Issue Management: The user interface for issues has been entirely redesigned.
  • 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.
  • 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.