Figma Plugin and Localyzer Project - Revision history

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

2026-04-14T14:19:00Z

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

← Older revision	Revision as of 14:19, 14 April 2026
(No difference)

Olibouban: /* Modes and Variable Tables */

2025-11-17T20:54:17Z

Modes and Variable Tables

← Older revision		Revision as of 20:54, 17 November 2025
Line 74:		Line 74:
	* https://help.figma.com/hc/en-us/articles/15343816063383-Modes-for-variables		* 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'.		'''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]]		[[File:FigmaVariableTable.png\|center\|700px]]

Olibouban: /* Modes and Variable Tables */

2025-11-17T19:00:53Z

Modes and Variable Tables

← Older revision		Revision as of 19:00, 17 November 2025
Line 79:		Line 79:

	* '1': Once translation is returned, if the Variable Table option is enabled, a new page with 'Var Table' shows.		* '1': Once translation is returned, if the Variable Table option is enabled, a new page with 'Var Table' shows.
	* '2': Select ~~which~~ 'mode', ~~here locale'~~ in which to view the application		* '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'		* '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.		* '4': Each column is a 'mode', here a locale. This table provides one view with the source strings, the keys, the translated strings.

Olibouban: /* Modes and Variable Tables */

2025-11-17T18:59:57Z

Modes and Variable Tables

← Older revision		Revision as of 18:59, 17 November 2025
Line 78:		Line 78:
	[[File:FigmaVariableTable.png\|center\|700px]]		[[File:FigmaVariableTable.png\|center\|700px]]

	* '1': In the ~~Figma Localyzer Plugin~~,		* '1': Once translation is returned, if the Variable Table option is enabled, a new page with 'Var Table' shows.
	* '2': Select which 'mode', here locale' in which to view the application		* '2': Select which 'mode', here locale' in which to view the application
	* '3': To open the table with the variables, click on 'Variable Table'		* '3': To open the table with the variables, click on 'Variable Table'

Olibouban: /* Modes and Variable Tables */

2025-11-17T18:58:40Z

Modes and Variable Tables

← Older revision		Revision as of 18:58, 17 November 2025
Line 75:		Line 75:

	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'.		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': In the Figma Localyzer Plugin,
			* '2': Select which 'mode', here locale' 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 =		= Verification of the setup, actions =

Olibouban: /* Context */

2025-11-17T18:51:30Z

Context

← Older revision		Revision as of 18:51, 17 November 2025
Line 68:		Line 68:

	== Context ==		== 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 has an InContext server.		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.

	~~The setup is now complete~~.

	== Modes and Variable Tables ==		== Modes and Variable Tables ==

Olibouban: /* Context */

2025-11-17T18:50:55Z

Context

← Older revision		Revision as of 18:50, 17 November 2025
Line 71:		Line 71:

	The setup is now complete.		The setup is now complete.

			== 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'.

	= Verification of the setup, actions =		= Verification of the setup, actions =

Olibouban at 19:55, 3 November 2025

2025-11-03T19:55:52Z

← Older revision		Revision as of 19:55, 3 November 2025
Line 46:		Line 46:

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

	~~= Set up a repository / branch =~~
	~~Next, set up a repository / branch with the following at the top level:~~
	* figma/locales/en/translation.json
	~~For example:~~
	* https://github.com/Acme/Figma/blob/main/figma/locales/en/translation.json
	** GitHub is used
	** the repository is Acme
	** the branch is main



	~~Add a first key/value in the translation.json file, such as <code>"start": "start"</code>~~

	= Create a Command Center Figma Project =		= Create a Command Center Figma Project =

Olibouban: /* From Command Center Localyzer to Translation */

2025-11-03T19:55:03Z

From Command Center Localyzer to Translation

← Older revision		Revision as of 19:55, 3 November 2025
Line 33:		Line 33:
	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.		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		The translated files will be stashed in the repository under their respective locale directory, for example
	* <code>locales/fr/translation.json</code>		* <code>figma/locales/fr/translation.json</code>
	* <code>locales/ja/translation.json</code>		* <code>figma/locales/ja/translation.json</code>

	=== From Command Center back to Figma ===		=== From Command Center back to Figma ===

Olibouban: /* From Figma to Command Center Localyzer */

2025-11-03T19:54:49Z

From Figma to Command Center Localyzer

← Older revision		Revision as of 19:54, 3 November 2025
Line 26:		Line 26:
	=== From Figma to Command Center Localyzer===		=== 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		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>locales/en/translation.json</code>		* <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.		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 ===		=== From Command Center Localyzer to Translation ===