About Localyzer - Revision history

Rdaly: /* What about sequencing - when translations are returned in a different order? */

2022-08-25T20:21:55Z

What about sequencing - when translations are returned in a different order?

← Older revision		Revision as of 20:21, 25 August 2022
Line 73:		Line 73:

	[[Components Diagram\|A Typical Localyzer Deployment]]		[[Components Diagram\|A Typical Localyzer Deployment]]

	~~[[File:Lrm-icon.png]]~~

	==Does Localyzer work for my Environment?==		==Does Localyzer work for my Environment?==

Rdaly: /* What does Localyzersend when resource files are modified? */

2022-08-25T20:17:25Z

What does Localyzersend when resource files are modified?

← Older revision		Revision as of 20:17, 25 August 2022
Line 56:		Line 56:
	'''Absolutely'''. Localyzer helps automate tasks. It also shows the status of the state of translation within the source code itself. It helps different software development cultures, in particular those applying Agile processes, by facilitating the tracking, sending, and receiving of resource kits. Non Agile processes do still benefit from Localyzer.		'''Absolutely'''. Localyzer helps automate tasks. It also shows the status of the state of translation within the source code itself. It helps different software development cultures, in particular those applying Agile processes, by facilitating the tracking, sending, and receiving of resource kits. Non Agile processes do still benefit from Localyzer.

	==What does ~~Localyzersend~~ when resource files are modified? ==		==What does Localyzer send when resource files are modified? ==
	Localyzer projects can be on-boarded as either '''full file''' or '''changes only'''. Localyzer defaults to 'changes only' for most resource file types, but this can be modified in the <code>config_lrm_info.properties</code> configuration file.		Localyzer projects can be on-boarded as either '''full file''' or '''changes only'''. Localyzer defaults to 'changes only' for most resource file types, but this can be modified in the <code>config_lrm_info.properties</code> configuration file.

Rdaly: /* What does Localyzer check for? */

2022-08-25T20:15:31Z

What does Localyzer check for?

← Older revision		Revision as of 20:15, 25 August 2022
Line 48:		Line 48:
	== What does Localyzer check for? ==		== What does Localyzer check for? ==

	See [https://sandbox.lingoport.com/coding_rules?repositories=lrm \| This list of coding rules] for more details.		See [https://sandbox.lingoport.com/coding_rules?repositories=lrm This list of coding rules] for more details.

	== Does Localyzer Compete with Translation Products? ==		== Does Localyzer Compete with Translation Products? ==

Olibouban: /* Licensing */

2022-04-26T20:54:53Z

Licensing

← Older revision		Revision as of 20:54, 26 April 2022
Line 106:		Line 106:
	* what files to on-board		* what files to on-board

	=== Licensing ===		== Licensing ==
	[[Localyzer_License]]		[[Localyzer_License]]

Olibouban at 20:54, 26 April 2022

2022-04-26T20:54:39Z

← Older revision		Revision as of 20:54, 26 April 2022
Line 105:		Line 105:
	* which branch to hook Localyzer to		* which branch to hook Localyzer to
	* what files to on-board		* what files to on-board

			=== Licensing ===
			[[Localyzer_License]]

Olibouban: /* What Does the Localyzer Do? */

2021-11-08T18:43:45Z

What Does the Localyzer Do?

← Older revision		Revision as of 18:43, 8 November 2021
Line 9:		Line 9:
	The [[Terms_and_Definitions#LingoportDashboard\|Dashboard]] permission settings allows a granular presentation of the [[Terms_and_Definitions#LRMProject\|Localyzer project]] so management, development, and/or the translation vendor can all benefit from the status.		The [[Terms_and_Definitions#LingoportDashboard\|Dashboard]] permission settings allows a granular presentation of the [[Terms_and_Definitions#LRMProject\|Localyzer project]] so management, development, and/or the translation vendor can all benefit from the status.

	== What Does ~~the~~ Localyzer Do? ==		== What Does Localyzer Do? ==
	* Localyzer provides a translation '''status''' for [[Terms_and_Definitions\|resource files]].		* Localyzer provides a translation '''status''' for [[Terms_and_Definitions\|resource files]].
	* Localyzer facilitates and helps '''automate passing resource files from the development environment to the [[Terms_and_Definitions\|translation vendor]] and back'''.		* Localyzer facilitates and helps '''automate passing resource files from the development environment to the [[Terms_and_Definitions\|translation vendor]] and back'''.

Rdaly at 21:08, 9 July 2021

2021-07-09T21:08:30Z

← Older revision		Revision as of 21:08, 9 July 2021
Line 72:		Line 72:


	[[Components Diagram\|A Typical ~~LRM~~ Deployment]]		[[Components Diagram\|A Typical Localyzer Deployment]]

	[[File:Lrm-icon.png]]		[[File:Lrm-icon.png]]

Rdaly: /* What does the Resource Manager send when resource files are modified? */

2021-07-09T20:00:34Z

What does the Resource Manager send when resource files are modified?

← Older revision		Revision as of 20:00, 9 July 2021
Line 56:		Line 56:
	'''Absolutely'''. Localyzer helps automate tasks. It also shows the status of the state of translation within the source code itself. It helps different software development cultures, in particular those applying Agile processes, by facilitating the tracking, sending, and receiving of resource kits. Non Agile processes do still benefit from Localyzer.		'''Absolutely'''. Localyzer helps automate tasks. It also shows the status of the state of translation within the source code itself. It helps different software development cultures, in particular those applying Agile processes, by facilitating the tracking, sending, and receiving of resource kits. Non Agile processes do still benefit from Localyzer.

	==What does ~~the Resource Manager send~~ when resource files are modified? ==		==What does Localyzersend when resource files are modified? ==
	~~LRM~~ projects can be on-boarded as either '''full file''' or '''changes only'''. ~~LRM~~ defaults to 'changes only' for most resource file types, but this can be modified in the <code>config_lrm_info.properties</code> configuration file.		Localyzer projects can be on-boarded as either '''full file''' or '''changes only'''. Localyzer defaults to 'changes only' for most resource file types, but this can be modified in the <code>config_lrm_info.properties</code> configuration file.

	* '''Full file''': when some strings in a file need to be sent for translation, the entire file is sent		* '''Full file''': when some strings in a file need to be sent for translation, the entire file is sent
	* '''Changes only''': When some strings in a file need to be sent for translation, only the part of the file with those strings is sent.		* '''Changes only''': When some strings in a file need to be sent for translation, only the part of the file with those strings is sent.

	In ~~LRM~~ parlance, the set of files sent to be translated is called a '''prep kit'''. Each prep kit has a '''kit number''' associated with it.		In Localyzer parlance, the set of files sent to be translated is called a '''prep kit'''. Each prep kit has a '''kit number''' associated with it.

	==What about sequencing - when translations are returned in a different order?==		==What about sequencing - when translations are returned in a different order?==

Rdaly: /* Does LRM work for my Environment? */

2021-07-09T19:59:47Z

Does LRM work for my Environment?

← Older revision		Revision as of 19:59, 9 July 2021
Line 76:		Line 76:
	[[File:Lrm-icon.png]]		[[File:Lrm-icon.png]]

	==Does ~~LRM~~ work for my Environment?==		==Does Localyzer work for my Environment?==

	Lingoport team members help potential customers determine how ~~LRM~~ will fit into their environment. To that end, Lingoport typically asks for ~~LRM~~ relevant information.		Lingoport team members help potential customers determine how Localyzer will fit into their environment. To that end, Lingoport typically asks for Localyzer relevant information.

	=== Basic Information ===		=== Basic Information ===
Line 89:		Line 89:

	=== Demo ===		=== Demo ===
	Lingoport team members routinely present actual [[Terms_and_Definitions#onboarding\|on-boarded]] ~~LRM~~ projects in a Dashboard for a specific potential project, so that a potential customer can see how ~~LRM~~ works with their own files. There are a few alternatives to proceed.		Lingoport team members routinely present actual [[Terms_and_Definitions#onboarding\|on-boarded]] Localyzer projects in a Dashboard for a specific potential project, so that a potential customer can see how Localyzer works with their own files. There are a few alternatives to proceed.
	==== Send sample files to Lingoport ====		==== Send sample files to Lingoport ====
	An efficient way to '''demonstrate''' ~~LRM~~ fit is to send Lingoport some sample files in a directory structure. Those sample files may be a small subset of the actual development resource files, provided they show:		An efficient way to '''demonstrate''' Localyzer fit is to send Lingoport some sample files in a directory structure. Those sample files may be a small subset of the actual development resource files, provided they show:
	* the format and the idiosynchrasies of the file content		* the format and the idiosynchrasies of the file content
	* the naming of the files		* the naming of the files
Line 103:		Line 103:
	* an account to be granted r/w privileges		* an account to be granted r/w privileges
	* a URL to the repository		* a URL to the repository
	* which branch to hook ~~LRM~~ to		* which branch to hook Localyzer to
	* what files to on-board		* what files to on-board

Rdaly: /* What about sequencing - when translations are returned in a different order? */

2021-07-09T19:58:46Z

What about sequencing - when translations are returned in a different order?

← Older revision		Revision as of 19:58, 9 July 2021
Line 65:		Line 65:

	==What about sequencing - when translations are returned in a different order?==		==What about sequencing - when translations are returned in a different order?==
	If <code>messages.properties, errors.properties, and resources.properties</code> were sent for translation in prep kit #17 with a total of 243 strings to be translated in French, ~~LRM~~ is expecting back from the French translation the same 243 translated strings (based on their keys) from <code>messages.properties, errors.properties, and resources.properties</code>, as sent in prep kit 17. This may be different than the same files in prep kit 23, or what files currently reside in the repository for that project.		If <code>messages.properties, errors.properties, and resources.properties</code> were sent for translation in prep kit #17 with a total of 243 strings to be translated in French, Localyzer is expecting back from the French translation the same 243 translated strings (based on their keys) from <code>messages.properties, errors.properties, and resources.properties</code>, as sent in prep kit 17. This may be different than the same files in prep kit 23, or what files currently reside in the repository for that project.

	When files are modified, the delta (either full file or changes only) from the previous kit number is sent. ~~LRM~~ handles the order in which the translations are returned. For instance, if ~~LRM~~ sends kits 101, 102, and 103 before any is returned, and 102 is returned in French before 101, 103 is returned in Russian, then 101 is returned in French, then 103, etc., ~~LRM~~ handles those sequencing. If 103 is returned before 102 in Japanese, 103 translations will be kept even if 102 contains the same strings.		When files are modified, the delta (either full file or changes only) from the previous kit number is sent. Localyzer handles the order in which the translations are returned. For instance, if Localyzer sends kits 101, 102, and 103 before any is returned, and 102 is returned in French before 101, 103 is returned in Russian, then 101 is returned in French, then 103, etc., Localyzer handles those sequencing. If 103 is returned before 102 in Japanese, 103 translations will be kept even if 102 contains the same strings.

	[[Sequencing Example\|A detailed example of sequencing]]		[[Sequencing Example\|A detailed example of sequencing]]