Create a Localyzer only project - Revision history

Olibouban: /* Figma to Dev */

2025-11-26T21:42:18Z

Figma to Dev

← Older revision		Revision as of 21:42, 26 November 2025
Line 155:		Line 155:
	In this example, the source and target files <code>more.json</code> will have key/value pairs added from the Localyzer Figma project.		In this example, the source and target files <code>more.json</code> will have key/value pairs added from the Localyzer Figma project.

	Please follow the recommendations as to when to setup the Figma2Dev configuration and when to switch to a new ~~target~~ developer file:		Please follow the recommendations as to when to setup the Figma2Dev configuration and when to switch to a new destination (generated) developer file:
	* [[Figma_to_Dev_Generation_Details#Recommendation]]		* [[Figma_to_Dev_Generation_Details#Recommendation]]

Olibouban: /* Figma to Dev */

2025-11-26T21:41:51Z

Figma to Dev

← Older revision		Revision as of 21:41, 26 November 2025
Line 154:		Line 154:

	In this example, the source and target files <code>more.json</code> will have key/value pairs added from the Localyzer Figma project.		In this example, the source and target files <code>more.json</code> will have key/value pairs added from the Localyzer Figma project.

			Please follow the recommendations as to when to setup the Figma2Dev configuration and when to switch to a new target developer file:
			* [[Figma_to_Dev_Generation_Details#Recommendation]]

	In terms of when development resource files are generated, on the source and target locales, please refer to		In terms of when development resource files are generated, on the source and target locales, please refer to

Olibouban: /* Figma to Dev */

2025-11-12T20:52:19Z

Figma to Dev

← Older revision		Revision as of 20:52, 12 November 2025
Line 154:		Line 154:

	In this example, the source and target files <code>more.json</code> will have key/value pairs added from the Localyzer Figma project.		In this example, the source and target files <code>more.json</code> will have key/value pairs added from the Localyzer Figma project.

			In terms of when development resource files are generated, on the source and target locales, please refer to
			* [[Figma to Dev Generation Details]]

	Click ''Next''		Click ''Next''

Olibouban: /* Validation */

2025-10-29T17:02:18Z

Validation

← Older revision		Revision as of 17:02, 29 October 2025
Line 191:		Line 191:

	If the validation steps shows the correct information, click ''Create'' to finalize the process and create the Localyzer project.		If the validation steps shows the correct information, click ''Create'' to finalize the process and create the Localyzer project.

			[[File:LzCreateProject.png\|600px\|center]]

			Run analyze as the next step and check the Localyzer tab.

Olibouban: /* Advanced Localyzer Settings */

2025-10-29T16:57:11Z

Advanced Localyzer Settings

@@ Line 158: / Line 158: @@
 = Advanced Localyzer Settings=
 '''Localyzer Issue Detection'''
@@ Line 178: / Line 180: @@
 [[File:CC Schedule Translation.jpg|400px|center]]

Olibouban: /* Figma to Dev */

2025-10-29T16:51:24Z

Figma to Dev

← Older revision		Revision as of 16:51, 29 October 2025
Line 156:		Line 156:

	Click ''Next''		Click ''Next''

			= Advanced Localyzer Settings=

			'''Localyzer Issue Detection'''

			Selecting the '''Detect prep kit reasons''' and '''Detect informational reasons''' will report more Localyzer issues on the Localyzer report page.

			'''Prep kit configuration'''

			* '''Send changes only''' - By default this is set. After a file has been fully translated, then only the changes will be sent to translation.
			* '''Send separate translation kits for each locale''' - this is unset. When prep kits to be translated are sent to a Translation Management System or Machine Translator, they are sent in one large zip package unless this value is set. Prep kits are returned individually.
			* '''Replace post edit text directly in file''' - this is unset and will not change the translated files unless it is checked.
			* '''Global tags (comma separated)''' - what is this?

			'''Custom Git Commit Message'''
			All of these options allow the user to customize the Git Commit messages for various processes.

			==Schedule translations==
			Files can be scheduled to be sent to translation either every n days or every n weeks on a specific day.
			For example, below is a schedule to sent files to translation every 2 weeks on a Friday:

			[[File:CC Schedule Translation.jpg\|400px\|center]]

Olibouban: /* Figma to Dev */

2025-10-29T16:50:15Z

Figma to Dev

← Older revision		Revision as of 16:50, 29 October 2025
Line 149:		Line 149:
	If a repository file will be used to receive key/value pairs from a Localyzer Figma project, select which Figma project to use and what source file is the destination for the source strings. If the Figma project has translations, the corresponding target files will be generated as well, based on the on-boarding.		If a repository file will be used to receive key/value pairs from a Localyzer Figma project, select which Figma project to use and what source file is the destination for the source strings. If the Figma project has translations, the corresponding target files will be generated as well, based on the on-boarding.
	* Note: For Localyzer Figma project creation, see: [[Create_a_Figma_project]]		* Note: For Localyzer Figma project creation, see: [[Create_a_Figma_project]]


	[[File:LzF2D.png\|center\|600px]]		[[File:LzF2D.png\|center\|600px]]

			In this example, the source and target files <code>more.json</code> will have key/value pairs added from the Localyzer Figma project.

			Click ''Next''

Olibouban: /* Figma to Dev */

2025-10-29T16:48:47Z

Figma to Dev

← Older revision		Revision as of 16:48, 29 October 2025
Line 148:		Line 148:
	= Figma to Dev =		= Figma to Dev =
	If a repository file will be used to receive key/value pairs from a Localyzer Figma project, select which Figma project to use and what source file is the destination for the source strings. If the Figma project has translations, the corresponding target files will be generated as well, based on the on-boarding.		If a repository file will be used to receive key/value pairs from a Localyzer Figma project, select which Figma project to use and what source file is the destination for the source strings. If the Figma project has translations, the corresponding target files will be generated as well, based on the on-boarding.
			* Note: For Localyzer Figma project creation, see: [[Create_a_Figma_project]]

	[[File:LzF2D.png\|center\|600px]]		[[File:LzF2D.png\|center\|600px]]

Olibouban: /* Include/Exclude/Reference Patterns */

2025-10-29T16:46:45Z

Include/Exclude/Reference Patterns

← Older revision		Revision as of 16:46, 29 October 2025
Line 145:		Line 145:
	== Special On-Boarding ==		== Special On-Boarding ==
	* [[DITA Project Configuration \| DITA Project Configuration ]]		* [[DITA Project Configuration \| DITA Project Configuration ]]

			= Figma to Dev =
			If a repository file will be used to receive key/value pairs from a Localyzer Figma project, select which Figma project to use and what source file is the destination for the source strings. If the Figma project has translations, the corresponding target files will be generated as well, based on the on-boarding.

			[[File:LzF2D.png\|center\|600px]]

Olibouban: /* Include/Exclude/Reference Patterns */

2025-10-29T16:41:05Z

Include/Exclude/Reference Patterns

← Older revision		Revision as of 16:41, 29 October 2025
Line 135:		Line 135:

	If all the resource files are under a folder called <code>locales</code> then the Include Patterns would be <code>/locales/</code>		If all the resource files are under a folder called <code>locales</code> then the Include Patterns would be <code>/locales/</code>
	If there is a file such as <code>config.json<code> which is not a resource file, then the Exclude Patterns would look like <code>**/config.json</code>		If there is a file such as <code>config.json</code> which is not a resource file, then the Exclude Patterns would look like <code>**/config.json</code>

	Reference files are specific to Trados Enterprise and provide information or instruction about the translation steps.		Reference files are specific to Trados Enterprise and provide information or instruction about the translation steps.