Lingoport Wiki - Recent changes [en]

Command Center Release Notes

Olibouban — Tue, 14 Apr 2026 19:50:19 GMT

← Older revision		Revision as of 19:50, 14 April 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	= Upcoming =		= Upcoming =
	== Version 4.2.z (May 2026??) ==		== Version 4.2.z (''Expected'' May 2026) ==

	===Globalyzer===		===Globalyzer===
Line 6:		Line 6:
	* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples\| ChatGPT]]		* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples\| ChatGPT]]

	=== XTM Context ===		=== Localyzer ===

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

	=== String Prompting ===		==== 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]].		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		* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
Line 16:		Line 18:
	* 9169 - Create a LRM command to insert a string prompt for a unique instrument key		* 9169 - Create a LRM command to insert a string prompt for a unique instrument key

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

Line 28:		Line 30:
	* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys		* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys

	=== Do Not Translate (DNT) ===		==== Do Not Translate (DNT) ====
	In [[Individual_Project_Tasks#Expanded_view\|String Manager]], a string can have the DNT set:		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 the repository strings have a different value than the source string, it will raise an issue
Line 38:		Line 40:
	* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up		* 9262 - DNT key has 'translate="1"' instead of "0" in PXML prep kit file if vendor has InContext set up

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

	=== Signed Commits ===		==== 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.		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 [[Signed_Commit#Create_GPG_keys_and_associate_it_with_GitHub\|GPG key]] needs to be created from the container.
Line 48:		Line 50:
	* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]		* 8507 - Feature Request: GPG Support for Git [[Signed Commit]]

	=== ~~Command Center~~ API ===		==== 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]]		* 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]]		* 9302 - API changes to [[Command_Center_API_Reference#Duplicate_Command_Center_Project\|duplicate project]]

	=== UI Improvements===		==== UI Improvements====
	* 9219 - No email option for API users		* 9219 - No email option for API users
	* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''		* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
Line 59:		Line 73:
	* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.		* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.

	=== ~~ICU Message Format - CLRD Updates~~ ===		==== Fixes ====
	~~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!~~		* 9264 - WorldServer Project ID is editable again.
	~~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 =		= Supported Version =

Figma API Project

Olibouban — Tue, 14 Apr 2026 14:19:00 GMT

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

New page

= 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

Olibouban — Thu, 09 Apr 2026 14:17:08 GMT

ChatGPT only Scanning

← Older revision		Revision as of 14:17, 9 April 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	== ChatGPT Use in Globalyzer ==		== ChatGPT Use in Globalyzer ==

	~~=== Enabling~~ ChatGPT ~~Support for~~ a Globalyzer ~~Project~~ ===		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.		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.
Line 14:		Line 19:
	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.		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 ====		=== 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:		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"		* True positive "Orange"
Line 21:		Line 26:
	[[File:IssuesChatgptIcons.png\|1024px\|center]]		[[File:IssuesChatgptIcons.png\|1024px\|center]]

	==== Issues Page Individual Issue ChatGPT Indicators ====		=== 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.		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.
Line 27:		Line 32:
	[[File:IssuesAiPredictive.png\|1024px\|center]]		[[File:IssuesAiPredictive.png\|1024px\|center]]

	==== AI Prediction Reason ====		=== AI Prediction Reason ===

	*Currently In Progress		*Currently In Progress



	=== Cost of Incorporation ===		=== Cost of Incorporation ===
Line 44:		Line 51:
	\| AI Prediction Reason\|\| TBD \|\| TBD \|\| TBD \|\| TBD \|\| TBD \|\| TBD \|\| TBD \|\| TBD \|\| TBD		\| 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.

Create a Globalyzer only project

Olibouban — Thu, 09 Apr 2026 14:07:38 GMT

Setting

← Older revision		Revision as of 14:07, 9 April 2026
(6 intermediate revisions by the same user not shown)
Line 34:		Line 34:

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

	==== Samples====		==== Samples====
	* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/sample/LiteProjectDefinition.xml Using Globalyzer Server Rules ]		* [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~~ ]		* [https://github.com/Lingoport/CommandCenterConfig/blob/main/globalyzer/PureLLM/LiteProjectDefinition.xml Using only ChatGPT]

	== Setting ==		== Setting ==
Line 63:		Line 66:
	<nowiki>https://github.com/Acme/MyProject</nowiki>		<nowiki>https://github.com/Acme/MyProject</nowiki>

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

	then the entry for Project Definition File would be:		then the entry for Project Definition File would be:

	/lingoport/~~PDF~~.xml		/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.		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.

Command Center Release Notes

Olibouban — Mon, 06 Apr 2026 21:51:20 GMT

Globalyzer

← Older revision		Revision as of 21:51, 6 April 2026
(One intermediate revision by the same user not shown)
Line 4:		Line 4:
	===Globalyzer===		===Globalyzer===
	* 8669 - Performance Improvement on Globalyzer Analysis in Command Center		* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
	* 9241 - Globalyzer Scanning with ChatGPT		* 9241 - Globalyzer Scanning with [[Create_a_Globalyzer_only_project#Samples\| ChatGPT]]

	=== XTM Context ===		=== XTM Context ===

Create a Globalyzer only project

Olibouban — Mon, 06 Apr 2026 21:49:31 GMT

Globalyzer Settings

← Older revision		Revision as of 21:49, 6 April 2026
(2 intermediate revisions by the same user not shown)
Line 35:		Line 35:
	= Globalyzer Settings =		= 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]]		[[File:GzLitePDF.png\|center\|600px]]

Individual Project Tasks

Olibouban — Mon, 06 Apr 2026 21:46:38 GMT

Project Definition File

← Older revision	Revision as of 21:46, 6 April 2026
(4 intermediate revisions by the same user not shown)
(No difference)

Project Tags & Tokens

Olibouban — Mon, 06 Apr 2026 20:15:50 GMT

View Tags

← Older revision		Revision as of 20:15, 6 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	= Introduction =		= Introduction =

	~~[[File: CCTags~~.~~jpg\|600px\|center]]~~		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 =		= View Tags =
	[Admin, Manager, Developer, Translator]		[Admin, Manager, Developer, Translator]

			Tags are accessible from the Global Settings page.

	[[File:ViewTags.jpg\|600px\|center]]		[[File:ViewTags.jpg\|600px\|center]]

File:DeleteUser.jpg

Olibouban — Mon, 06 Apr 2026 20:09:32 GMT

Olibouban uploaded a new version of File:DeleteUser.jpg

New page

Users & Teams

Olibouban — Mon, 06 Apr 2026 20:07:01 GMT

Edit User

← Older revision		Revision as of 20:07, 6 April 2026
Line 28:		Line 28:

	==Edit User==		==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]]		[[File:EditUser.jpg\|600px\|center]]

	~~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~~.

			Alternatively, the Administrator can first click on the username and from the View User page, click the Edit button.


	[[File:EditUser2.jpg\|600px\|center]]		[[File:EditUser2.jpg\|600px\|center]]

	~~The Administrator can also select the Username and the next page will have a button to Edit User~~

	==Delete User==		==Delete User==

File:EditUser2.jpg

Olibouban — Mon, 06 Apr 2026 20:04:10 GMT

Olibouban uploaded a new version of File:EditUser2.jpg

New page

File:CreateUser.jpg

Olibouban — Mon, 06 Apr 2026 19:57:17 GMT

Olibouban uploaded a new version of File:CreateUser.jpg

New page

File:CCUserTeams.jpg

Olibouban — Mon, 06 Apr 2026 19:55:09 GMT

Olibouban uploaded a new version of File:CCUserTeams.jpg

New page

Command Center Release Notes

Olibouban — Mon, 06 Apr 2026 16:04:38 GMT

Fixes

← Older revision		Revision as of 16:04, 6 April 2026
(One intermediate revision by the same user not shown)
Line 54:		Line 54:
	=== UI Improvements===		=== UI Improvements===
	* 9219 - No email option for API users		* 9219 - No email option for API users
	* 9282 - Option to show or not informational issues		* 9282 - Option to show or not informational issues in Localyzer ''Advanced Localyzer Settings''
	* 9285 - Added option for JSON file patterns		* 9285 - Added option for JSON file patterns in Localyzer Edit > ''Resource File Configuration''
	* 9286 - String Manager Context Indicator update		* 9286 - String Manager Context Indicator icon update
	* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.		* 9303 - Added "Learn more about this issue" on Localyzer issues, in the same way as Globalyzer issues.


	=== ICU Message Format - CLRD Updates ===		=== ICU Message Format - CLRD Updates ===
Line 70:		Line 69:

	=== Fixes ===		=== Fixes ===
	* 9264 - WS Project ID is ~~not~~ editable ~~any longer. It must be~~.		* 9264 - WS Project ID is editable again.

	= Supported Version =		= Supported Version =

Individual Project Tasks

Olibouban — Mon, 06 Apr 2026 16:00:06 GMT

Expanded view

← Older revision		Revision as of 16:00, 6 April 2026
Line 121:		Line 121:
	* Source review recommended: a yes/no flag to indicate that string may be rewritten		* 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		* Do not translate: if set, the translation must match the source string
	* String ~~Length~~: If set, the source and translated strings number of characters must be within the boundaries. Click the arrow to set the boundaries		* 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]].		* 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		* Translation status: The string was translated, is being translated, has not been translated in how many locales

Command Center Release Notes

Olibouban — Mon, 06 Apr 2026 15:59:18 GMT

XTM Context

← Older revision		Revision as of 15:59, 6 April 2026
(One intermediate revision by the same user not shown)
Line 3:		Line 3:

	===Globalyzer===		===Globalyzer===
	* 8669 - Performance Improvement on Globalyzer Analysis in Command ~~Ceter~~		* 8669 - Performance Improvement on Globalyzer Analysis in Command Center
	* 9241 - Globalyzer Scanning with ChatGPT		* 9241 - Globalyzer Scanning with ChatGPT

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

	=== String Prompting ===		=== String Prompting ===

XTM Cloud

Olibouban — Mon, 06 Apr 2026 15:58:11 GMT

XTM and Context

← Older revision		Revision as of 15:58, 6 April 2026
(7 intermediate revisions by the same user not shown)
Line 67:		Line 67:
	The work-around in this case may be to upload the files from Localyzer. See:		The work-around in this case may be to upload the files from Localyzer. See:
	* [[Upload translated files]]		* [[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]].

Command Center Release Notes

Olibouban — Mon, 06 Apr 2026 15:41:19 GMT

String Prompting

← Older revision		Revision as of 15:41, 6 April 2026
(2 intermediate revisions by the same user not shown)
Line 10:		Line 10:

	=== String Prompting ===		=== 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.		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		* 9059 - Enhancement: Prompting - String Manager key including new Portal Task
	* 9061 - Enhancement: Prompting - ChatGpt		* 9061 - Enhancement: Prompting - ChatGpt
Line 17:		Line 17:

	=== Min/Max String Length ===		=== Min/Max String Length ===
	Minimum and maximum string lengths can be set from String Manager.		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 repository string for that key, source or translated, is outside the min/max bound, it will raise a Localyzer issue.
Line 27:		Line 27:
	* 9091 - Enhancement: Resource Issues - include violation of min/max on target files		* 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		* 9271 - Enhancement - Portal task for replacing min/max boundaries for a list of instrument keys


	=== Do Not Translate (DNT) ===		=== Do Not Translate (DNT) ===
	In String Manager, a string can have the DNT set:		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 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		* If a translation comes back with a different value than the source string, it will raise an issue

Individual Project Tasks

Olibouban — Mon, 06 Apr 2026 15:39:21 GMT

Expanded view

← Older revision		Revision as of 15:39, 6 April 2026
Line 115:		Line 115:
	[[File:StringManagerExpandedView.png\|center\|500px]]		[[File:StringManagerExpandedView.png\|center\|500px]]

			* The top label shows the string value
	* File and line number: The location of the string		* File and line number: The location of the string
	* String key: the key for that string		* String key: the key for that string
	* Source reviewed: a yes/no flag to indicate if the string was reviewed		* 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		* 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: 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		* 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		** Note: To see which are those locales, hover over the numbers