Resource File(s) Format - Revision history

Olibouban at 15:16, 28 December 2023

2023-12-28T15:16:11Z

← Older revision		Revision as of 15:16, 28 December 2023
Line 15:		Line 15:

	[[What are the Localyzer locales \|<== Back to Step 6: What are the Localyzer locales?]]		[[What are the Localyzer locales \|<== Back to Step 6: What are the Localyzer locales?]]

	~~[[DITA Project Configuration \| DITA Project Configuration ]]~~

	== Using Custom Resource File Types ==		== Using Custom Resource File Types ==
Line 90:		Line 88:

	Custom Transform Scripts are added to the system in '''Settings -> System Files -> Custom Scripts'''.		Custom Transform Scripts are added to the system in '''Settings -> System Files -> Custom Scripts'''.

			== Special On-Boarding ==
			* [[DITA Project Configuration \| DITA Project Configuration ]]

Olibouban at 15:14, 28 December 2023

2023-12-28T15:14:14Z

← Older revision		Revision as of 15:14, 28 December 2023
Line 16:		Line 16:
	[[What are the Localyzer locales \|<== Back to Step 6: What are the Localyzer locales?]]		[[What are the Localyzer locales \|<== Back to Step 6: What are the Localyzer locales?]]

			[[DITA Project Configuration \| DITA Project Configuration ]]

	== Using Custom Resource File Types ==		== Using Custom Resource File Types ==

Olibouban: /* File Name Pattern */

2023-10-09T14:50:27Z

File Name Pattern

← Older revision		Revision as of 14:50, 9 October 2023
Line 29:		Line 29:
	* <code>v</code> is for variant, as in ''tw''		* <code>v</code> is for variant, as in ''tw''

	The '''File name pattern''' determines how Localyzer parses locale information from the filename. Both the file name pattern and the file location pattern can be used together, but only one or the other is required. The pattern must contain <code>l</code>, <code>c</code>, and <code>v</code>, or <code>LCID</code>. The pattern cannot contain <code>/</code>, <code>\\</code>, or any letter other than <code>l</code>, <code>c</code>, or <code>v</code>, or the continuous string <code>LCID</code>. The pattern may contain <code>*</code> as a wildcard to indicate “the rest of the file name,” but it must be the very first character of the pattern. Below are some example file name patterns with a hypothetical properties file that they could map to:		The '''File name pattern''' determines how Localyzer parses locale information from the repository filename. Both the file name pattern and the file location pattern can be used together, but only one or the other is required. The pattern must contain <code>l</code>, <code>c</code>, and <code>v</code>, or <code>LCID</code>. The pattern cannot contain <code>/</code>, <code>\\</code>, or any letter other than <code>l</code>, <code>c</code>, or <code>v</code>, or the continuous string <code>LCID</code>. The pattern may contain <code>*</code> as a wildcard to indicate “the rest of the file name,” but it must be the very first character of the pattern. Below are some example file name patterns with a hypothetical properties file that they could map to:

	<code>*-l_c-v</code> -> <code>file1-zh_hant-tw.properties</code>		<code>*-l_c-v</code> -> <code>file1-zh_hant-tw.properties</code>

Olibouban: /* File Name Pattern */

2023-10-09T14:49:33Z

File Name Pattern

← Older revision		Revision as of 14:49, 9 October 2023
Line 26:		Line 26:
	In this following section, the codes used in the file name pattern are based on:		In this following section, the codes used in the file name pattern are based on:
	* <code>l</code> is for language, as in ''de'' or ''fr'' or ''zh''		* <code>l</code> is for language, as in ''de'' or ''fr'' or ''zh''
	* <code>c</code> is for country, as in ''DE'' or ''FR'' or ''~~Hant~~''		* <code>c</code> is for country, as in ''DE'' or ''FR'' or ''hant''
	* <code>v</code> is for variant, as in ''tw''		* <code>v</code> is for variant, as in ''tw''

Olibouban: /* File Name Pattern */

2023-10-09T14:49:14Z

File Name Pattern

← Older revision		Revision as of 14:49, 9 October 2023
Line 27:		Line 27:
	* <code>l</code> is for language, as in ''de'' or ''fr'' or ''zh''		* <code>l</code> is for language, as in ''de'' or ''fr'' or ''zh''
	* <code>c</code> is for country, as in ''DE'' or ''FR'' or ''Hant''		* <code>c</code> is for country, as in ''DE'' or ''FR'' or ''Hant''
	* <code>v</code> is for variant, as in ''TW''		* <code>v</code> is for variant, as in ''tw''

	The '''File name pattern''' determines how Localyzer parses locale information from the filename. Both the file name pattern and the file location pattern can be used together, but only one or the other is required. The pattern must contain <code>l</code>, <code>c</code>, and <code>v</code>, or <code>LCID</code>. The pattern cannot contain <code>/</code>, <code>\\</code>, or any letter other than <code>l</code>, <code>c</code>, or <code>v</code>, or the continuous string <code>LCID</code>. The pattern may contain <code>*</code> as a wildcard to indicate “the rest of the file name,” but it must be the very first character of the pattern. Below are some example file name patterns with a hypothetical properties file that they could map to:		The '''File name pattern''' determines how Localyzer parses locale information from the filename. Both the file name pattern and the file location pattern can be used together, but only one or the other is required. The pattern must contain <code>l</code>, <code>c</code>, and <code>v</code>, or <code>LCID</code>. The pattern cannot contain <code>/</code>, <code>\\</code>, or any letter other than <code>l</code>, <code>c</code>, or <code>v</code>, or the continuous string <code>LCID</code>. The pattern may contain <code>*</code> as a wildcard to indicate “the rest of the file name,” but it must be the very first character of the pattern. Below are some example file name patterns with a hypothetical properties file that they could map to:

Olibouban: /* File Name Pattern */

2023-10-09T14:48:55Z

File Name Pattern

← Older revision		Revision as of 14:48, 9 October 2023
Line 24:		Line 24:

	=== File Name Pattern ===		=== File Name Pattern ===
			In this following section, the codes used in the file name pattern are based on:
			* <code>l</code> is for language, as in ''de'' or ''fr'' or ''zh''
			* <code>c</code> is for country, as in ''DE'' or ''FR'' or ''Hant''
			* <code>v</code> is for variant, as in ''TW''

	The '''File name pattern''' determines how Localyzer parses locale information from the filename. Both the file name pattern and the file location pattern can be used together, but only one or the other is required. The pattern must contain <code>l</code>, <code>c</code>, and <code>v</code>, or <code>LCID</code>. The pattern cannot contain <code>/</code>, <code>\\</code>, or any letter other than <code>l</code>, <code>c</code>, or <code>v</code>, or the continuous string <code>LCID</code>. The pattern may contain <code>*</code> as a wildcard to indicate “the rest of the file name,” but it must be the very first character of the pattern. Below are some example file name patterns with a hypothetical properties file that they could map to:		The '''File name pattern''' determines how Localyzer parses locale information from the filename. Both the file name pattern and the file location pattern can be used together, but only one or the other is required. The pattern must contain <code>l</code>, <code>c</code>, and <code>v</code>, or <code>LCID</code>. The pattern cannot contain <code>/</code>, <code>\\</code>, or any letter other than <code>l</code>, <code>c</code>, or <code>v</code>, or the continuous string <code>LCID</code>. The pattern may contain <code>*</code> as a wildcard to indicate “the rest of the file name,” but it must be the very first character of the pattern. Below are some example file name patterns with a hypothetical properties file that they could map to:

Rdaly at 22:31, 13 September 2023

2023-09-13T22:31:43Z

← Older revision		Revision as of 22:31, 13 September 2023
Line 82:		Line 82:
	*<code>xml</code> - <code>%[ds]\|%\d+\$[ds]\|%\{\w+\}</code>		*<code>xml</code> - <code>%[ds]\|%\d+\$[ds]\|%\{\w+\}</code>

	=== Custom Transform Scripts ===		== Custom Transform Scripts ==

	Custom Transform Scripts are added to the system in '''Settings -> System Files -> Custom Scripts'''.		Custom Transform Scripts are added to the system in '''Settings -> System Files -> Custom Scripts'''.

Rdaly at 22:31, 13 September 2023

2023-09-13T22:31:12Z

← Older revision		Revision as of 22:31, 13 September 2023
Line 81:		Line 81:
	*<code>strings</code> - <code>%d\|%s\|%\d+\$s\|%\d+\$d\|%\{\w+\}</code>		*<code>strings</code> - <code>%d\|%s\|%\d+\$s\|%\d+\$d\|%\{\w+\}</code>
	*<code>xml</code> - <code>%[ds]\|%\d+\$[ds]\|%\{\w+\}</code>		*<code>xml</code> - <code>%[ds]\|%\d+\$[ds]\|%\{\w+\}</code>

			=== Custom Transform Scripts ===

			Custom Transform Scripts are added to the system in '''Settings -> System Files -> Custom Scripts'''.

Rdaly: /* Parameters */

2023-09-13T22:27:59Z

Parameters

← Older revision		Revision as of 22:27, 13 September 2023
Line 70:		Line 70:

	=== Parameters ===		=== Parameters ===

			The '''Parameters''' column is a regex pattern that defines how Localyzer parses parameters out of the messages within files. Below are the parameters patterns used in some of the default resource types as examples:

			*<code>js</code> - <code>\{\d+\}\|%[ds]</code>
			*<code>json</code> - <code>\{\w+\}\|%[ds]</code>
			*<code>msg</code> - <code>%\d+%\|%[ds]</code>
			<code>po</code> - <code>%\d[ds]\|%\d+</code>
			*<code>properties</code> - <code>\{\w+\}\|%[ds]</code>
			*<code>rc</code> - <code>%\d+</code>
			*<code>strings</code> - <code>%d\|%s\|%\d+\$s\|%\d+\$d\|%\{\w+\}</code>
			*<code>xml</code> - <code>%[ds]\|%\d+\$[ds]\|%\{\w+\}</code>

Rdaly: /* Encoding */

2023-09-13T22:26:24Z

Encoding

← Older revision		Revision as of 22:26, 13 September 2023
Line 64:		Line 64:

	=== Encoding ===		=== Encoding ===

			The file encoding by which to read and write the files. For example: UTF-8

			UTF-8 is the most common encoding value. Select UTF-8 for the encoding unless instructed otherwise.

	=== Parameters ===		=== Parameters ===