LRM Fixing Issues - Revision history

Llawson: /* Why, when I prep a kit, do I get a report called "BaseFileSearchErrors.xml"? */

2020-09-25T17:39:12Z

Why, when I prep a kit, do I get a report called "BaseFileSearchErrors.xml"?

← Older revision		Revision as of 17:39, 25 September 2020
Line 196:		Line 196:
	* '''DUPLICATE_KEY''' - there is a duplicate string key in the base resource file. Remove the duplicate and run --prep-kit again.		* '''DUPLICATE_KEY''' - there is a duplicate string key in the base resource file. Remove the duplicate and run --prep-kit again.
	* '''EMPTY_KEY''' - the value has no corresponding key. Either remove the value from the file or add the appropriate key.		* '''EMPTY_KEY''' - the value has no corresponding key. Either remove the value from the file or add the appropriate key.
	* '''FILE_TOO_BIG''' - a base resource file cannot be larger than 16 megabytes. You will need to break up your resource file into multiple files and ~~then~~ run --prep-kit again.		* '''FILE_TOO_BIG''' - a base resource file cannot be larger than 16 megabytes. You will need to break up your resource file into multiple files and run --prep-kit again.
	* '''UNKNOWN_FILE_FORMAT''' - the base resource file could not be parser. You will need to fix the format and ~~the~~ run --prep-kit again.		* '''ICU_MSGFORMAT''' - the base resource file has an invalid ICU Message Format. You will need to fix the format and run --prep-kit again. For more info about ICU Message Formatting syntax visit https://unicode-org.github.io/icu/userguide/format_parse/messages/
			* '''UNKNOWN_FILE_FORMAT''' - the base resource file could not be parser. You will need to fix the format and run --prep-kit again.

	=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===		=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===

Llawson: /* Modified text does not seem to be recognized as a change in my base resource file. What is wrong? */

2019-04-23T21:12:56Z

Modified text does not seem to be recognized as a change in my base resource file. What is wrong?

← Older revision		Revision as of 21:12, 23 April 2019
Line 201:		Line 201:
	=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===		=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===
	Modified text can only be detected if there has been a baseline created for the project. In this way, LRM can detect any modifications to file text. The Jenkins nightly Notification job for a project automatically calls the create baseline command. This command can also be called on the command line. See [[LRM_Commands_Reference#Create_a_project_baseline\| Create Project Baseline]] for more information.		Modified text can only be detected if there has been a baseline created for the project. In this way, LRM can detect any modifications to file text. The Jenkins nightly Notification job for a project automatically calls the create baseline command. This command can also be called on the command line. See [[LRM_Commands_Reference#Create_a_project_baseline\| Create Project Baseline]] for more information.

			== Misc ==

			=== Why are there files in my repository that end in ''_LRMLQA''? ===
			These are the LRM instrumented files that were created during the ''instrument resource files'' command.
			See [[LRM_Instrumentation#LRM_Instrumentation\|LRM Instrumented Files]] for more information.

Llawson: /* Modified text does not seem to be recognized as a change in my base resource file. What is wrong? */

2019-04-23T19:56:13Z

Modified text does not seem to be recognized as a change in my base resource file. What is wrong?

← Older revision		Revision as of 19:56, 23 April 2019
Line 200:		Line 200:

	=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===		=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===
	Modified text can only be detected if there has been a baseline created for the project. In this way, LRM can detect any modifications to file text. The Jenkins nightly Notification job for a project automatically calls the create baseline command. This command can also be called on the command line.		Modified text can only be detected if there has been a baseline created for the project. In this way, LRM can detect any modifications to file text. The Jenkins nightly Notification job for a project automatically calls the create baseline command. This command can also be called on the command line. See [[LRM_Commands_Reference#Create_a_project_baseline\| Create Project Baseline]] for more information.

Llawson: /* Modified text does not seem to be recognized as a change in my base resource file. What is wrong? */

2019-04-23T19:49:58Z

Modified text does not seem to be recognized as a change in my base resource file. What is wrong?

← Older revision		Revision as of 19:49, 23 April 2019
Line 200:		Line 200:

	=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===		=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===
	Modified text can only be detected if there has been a baseline created for the project. In this way, LRM can detect any modifications to file text. The Jenkins nightly job for a project automatically calls the create baseline command. This command can also be called on the command line.		Modified text can only be detected if there has been a baseline created for the project. In this way, LRM can detect any modifications to file text. The Jenkins nightly Notification job for a project automatically calls the create baseline command. This command can also be called on the command line.

Llawson: /* Modified text does not seem to be recognized as a change in my base resource file. What is wrong? */

2019-04-23T19:48:56Z

Modified text does not seem to be recognized as a change in my base resource file. What is wrong?

← Older revision		Revision as of 19:48, 23 April 2019
Line 200:		Line 200:

	=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===		=== Modified text does not seem to be recognized as a change in my base resource file. What is wrong? ===
	Modified text can only be detected if there has been ~~at least one prep kit.~~		Modified text can only be detected if there has been a baseline created for the project. In this way, LRM can detect any modifications to file text. The Jenkins nightly job for a project automatically calls the create baseline command. This command can also be called on the command line.
	~~When the prep kit command is invoked,~~ a 'baseline~~' is~~ created in the ~~database~~. In this way, LRM can detect any modifications to file text. ~~It is important, after creating~~ a project~~, to always invoke~~ the ~~prep kit~~ command ~~even if~~ the ~~project is 100% translated~~.

Llawson: /* How can I tell if my LRM project is setup correctly? */

2019-04-23T18:25:48Z

How can I tell if my LRM project is setup correctly?

@@ Line 9: / Line 9: @@
 /var/lib/jenkins/Lingoport_Data/LRM/<GroupName>/reports/<ProjectName>/ProjectInspect_de_de.xml
 /var/lib/jenkins/Lingoport_Data/LRM/<GroupName>/reports/<ProjectName>e/ProjectInspect_fr_fr.xml
 Process completed successfully.
 </pre>
@@ Line 27: / Line 28: @@
    </results>
 </LRMProjectInspectResults>
 </pre>

Olibouban: /* How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project? */

2018-03-14T18:55:29Z

How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project?

← Older revision		Revision as of 18:55, 14 March 2018
Line 57:		Line 57:

	===How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project?===		===How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project?===
			LRM is written in Java and the encodings available to the system are Java based, even if your environment is not Java.

	The supported encodings vary between different implementations of the Java platform. For example, the list of supported encodings supported by Java SE 8 is found here ''http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html''. The encoding that should be copied into the project definition xml is located under column '''"''Canonical Name for java.nio API''"'''. Every implementation of Java is required to support the following encodings.		The supported encodings vary between different implementations of the Java platform. For example, the list of supported encodings supported by Java SE 8 is found here ''http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html''. The encoding that should be copied into the project definition xml is located under column '''"''Canonical Name for java.nio API''"'''. Every implementation of Java is required to support the following encodings.
	* US-ASCII		* US-ASCII

Olibouban: /* When we generate the first prep kit with LRM, will all the base locale resource files be extracted, or only those base locale resource files that have corresponding localized files that have not been translated? */

2018-03-14T17:08:38Z

When we generate the first prep kit with LRM, will all the base locale resource files be extracted, or only those base locale resource files that have corresponding localized files that have not been translated?

← Older revision		Revision as of 17:08, 14 March 2018
Line 94:		Line 94:
	===When we generate the first prep kit with LRM, will all the base locale resource files be extracted, or only those base locale resource files that have corresponding localized files that have not been translated?===		===When we generate the first prep kit with LRM, will all the base locale resource files be extracted, or only those base locale resource files that have corresponding localized files that have not been translated?===

	For the first prep kit, only those base locale resource files that have corresponding localized files that have not been translated are sent out for translation. This includes missing keys or missing files.		For the '''first prep kit''', only those base locale resource files that have corresponding localized files that have not been translated are sent out for translation. This includes missing keys or missing files.

	~~Note-~~After the first prep kit, LRM is able to detect modified text as well as missing keys and missing files. It's always a good idea that the prep kit command is executed after creating a project in order for the files to get into the system in order to monitor text changes.		'''After the first prep kit''', LRM is able to detect modified text as well as missing keys and missing files. It's always a good idea that the prep kit command is executed after creating a project in order for the files to get into the system in order to monitor text changes.

	For example let's say you have a project with:		For example let's say you have a project with:

Olibouban: /* How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project? */

2018-03-14T17:04:17Z

How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project?

← Older revision		Revision as of 17:04, 14 March 2018
Line 57:		Line 57:

	===How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project?===		===How do I fix "Error 218 - invalid base file encoding" and "Error 219 - invalid localized file encoding" when updating or creating my project?===
	The supported encodings vary between different implementations of the ~~java~~ platform. For example, the list of supported encodings supported by Java SE 8 is found here ''http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html''. The encoding that should be copied into the project definition xml is located under column '''"''Canonical Name for java.nio API''"'''. Every implementation of Java is required to support the following encodings.		The supported encodings vary between different implementations of the Java platform. For example, the list of supported encodings supported by Java SE 8 is found here ''http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html''. The encoding that should be copied into the project definition xml is located under column '''"''Canonical Name for java.nio API''"'''. Every implementation of Java is required to support the following encodings.
	* US-ASCII		* US-ASCII
	* ISO-8859-1		* ISO-8859-1

Olibouban at 17:03, 14 March 2018

2018-03-14T17:03:08Z

← Older revision		Revision as of 17:03, 14 March 2018
Line 43:		Line 43:
	<extension>.properties</extension>		<extension>.properties</extension>
	</pre>		</pre>
	* Verify that it is a supported extension. [[~~LRM_Fixing_Issues#What_extensions_are_supported_by_LRM.3F~~\| ~~See~~ Supported ~~extensions above~~]]		* Verify that it is a supported extension. See [[Supported_Resource_Bundles\|Supported Resource Bundles]].

	===How do I fix "Error 215 - incorrect pattern for extension" when updating or creating my project?===		===How do I fix "Error 215 - incorrect pattern for extension" when updating or creating my project?===