LRM Properties Support - Revision history

Llawson: /* Example of Project Definition File */

2017-09-18T20:24:36Z

Example of Project Definition File

@@ Line 60: / Line 60: @@
 If a unique file extension is a valid properties file, then the ''&lt;parser-type&gt;'' should be ''properties'' in the project definition file.
-== Example of Project Definition File ==
+== Example of Project Definition for Resources ==
- <?xml version="1.0" encoding="UTF-8"?>
+     <resources-extensions>
        <resource-extension>
           '''<extension>properties</extension>'''
@@ Line 104: / Line 86: @@
        </resource-extension>
     </resources-extensions>

Llawson: /* .properties uses the properties parser type */

2017-09-01T15:50:54Z

.properties uses the properties parser type

← Older revision		Revision as of 15:50, 1 September 2017
Line 55:		Line 55:

	=== .properties uses the ''properties'' parser type===		=== .properties uses the ''properties'' parser type===
	When defining a project ~~with~~ .properties ~~extension~~, there is no need to define a ''<parser-type>'' as the ''properties'' parser will always be used.		When defining a project containing LRM Standard .properties resource files, there is no need to define a ''<parser-type>'' as the ''properties'' parser will always be used.

	=== unique file extension needs to define ''properties'' parser type ===		=== unique file extension needs to define ''properties'' parser type ===
	If a unique file extension is a valid properties file, then the ''<parser-type>'' should be ''properties'' in the project definition file.		If a unique file extension is a valid properties file, then the ''<parser-type>'' should be ''properties'' in the project definition file.

Llawson: /* Example of Project Definition File */

2017-08-31T23:21:44Z

Example of Project Definition File

← Older revision		Revision as of 23:21, 31 August 2017
Line 49:		Line 49:

	# bind and validation errors		# bind and validation errors

			== ''properties'' parser type ==
			=== valid properties syntax ===
			Files that use the ''properties'' parser are expected to have valid properties syntax

			=== .properties uses the ''properties'' parser type===
			When defining a project with .properties extension, there is no need to define a ''<parser-type>'' as the ''properties'' parser will always be used.
			=== unique file extension needs to define ''properties'' parser type ===
			If a unique file extension is a valid properties file, then the ''<parser-type>'' should be ''properties'' in the project definition file.

	== Example of Project Definition File ==		== Example of Project Definition File ==

Llawson: /* Example of Project Definition File */

2017-08-31T21:56:49Z

Example of Project Definition File

← Older revision		Revision as of 21:56, 31 August 2017
Line 96:		Line 96:
	<dirset>		<dirset>
	<includes>		<includes>
	<include-dir>/src/</include-dir>		<include-dir-file>/src/</include-dir-file>
	</includes>		</includes>
	<excludes>		<excludes>

Llawson: /* How to setup LRM for .properties files as well as file extensions using the properties parser type */

2017-08-31T20:21:39Z

How to setup LRM for .properties files as well as file extensions using the properties parser type

← Older revision		Revision as of 20:21, 31 August 2017
Line 1:		Line 1:
	== How to setup LRM for .properties files as well as file extensions using the properties parser type ==		== How to setup LRM for .properties files as well as file extensions using the ''properties'' parser type ==
	The encoding of a .properties file is ISO-8859-1, also known as Latin-1. All non-Latin-1 characters must be entered by using Unicode escape characters, e. g. \uHHHH where HHHH is a hexadecimal index of the character in the Unicode character set. This allows for using .properties files as resource bundles for localization. A non-Latin-1 text file can be converted to a correct .properties file by using the native2ascii tool that is shipped with the JDK or by using a tool, such as po2prop, that manages the transformation from a bilingual localization format into .properties escaping.		The encoding of a .properties file is ISO-8859-1, also known as Latin-1. All non-Latin-1 characters must be entered by using Unicode escape characters, e. g. \uHHHH where HHHH is a hexadecimal index of the character in the Unicode character set. This allows for using .properties files as resource bundles for localization. A non-Latin-1 text file can be converted to a correct .properties file by using the native2ascii tool that is shipped with the JDK or by using a tool, such as po2prop, that manages the transformation from a bilingual localization format into .properties escaping.
	For more information, please refer to : http://en.wikipedia.org/wiki/.properties		For more information, please refer to : http://en.wikipedia.org/wiki/.properties


	== Naming Conventions ==		== Naming Conventions ==

Llawson: /* Example of .properties */

2017-08-31T20:21:23Z

Example of .properties

← Older revision		Revision as of 20:21, 31 August 2017
Line 23:		Line 23:
	The bold file is the base file (U.S. English in this instance) translated into German, Spanish, French, Russian, and Chinese.		The bold file is the base file (U.S. English in this instance) translated into German, Spanish, French, Russian, and Chinese.

	== Example of .properties==		== Example of .properties or a file extension using the ''properties'' parser type ==
	<pre>		<pre>
	byTheFollowingAdministrator= by the following administrator: {0}		byTheFollowingAdministrator= by the following administrator: {0}

Llawson: /* Example of Project Definition File */

2017-08-31T20:09:54Z

Example of Project Definition File

Show changes

Llawson: /* Example of Project Definition File */

2017-08-31T19:43:29Z

Example of Project Definition File

@@ Line 118: / Line 118: @@
           <!--Default pattern for properties is '![CDATA[\{\d+\}|%[ds]]]'-->
           <parameter-regex-pattern><![CDATA[\{\w+\}|%[ds]]]></parameter-regex-pattern>
-           </resource-extension>
+      </resource-extension>
     </resources-extensions>
     <dirset>

Llawson at 18:44, 31 August 2017

2017-08-31T18:44:51Z

← Older revision		Revision as of 18:44, 31 August 2017
Line 1:		Line 1:
	== How to setup LRM for .properties ==		== How to setup LRM for .properties files as well as file extensions using the properties parser type ==
	The encoding of a .properties file is ISO-8859-1, also known as Latin-1. All non-Latin-1 characters must be entered by using Unicode escape characters, e. g. \uHHHH where HHHH is a hexadecimal index of the character in the Unicode character set. This allows for using .properties files as resource bundles for localization. A non-Latin-1 text file can be converted to a correct .properties file by using the native2ascii tool that is shipped with the JDK or by using a tool, such as po2prop, that manages the transformation from a bilingual localization format into .properties escaping.		The encoding of a .properties file is ISO-8859-1, also known as Latin-1. All non-Latin-1 characters must be entered by using Unicode escape characters, e. g. \uHHHH where HHHH is a hexadecimal index of the character in the Unicode character set. This allows for using .properties files as resource bundles for localization. A non-Latin-1 text file can be converted to a correct .properties file by using the native2ascii tool that is shipped with the JDK or by using a tool, such as po2prop, that manages the transformation from a bilingual localization format into .properties escaping.
	For more information, please refer to : http://en.wikipedia.org/wiki/.properties		For more information, please refer to : http://en.wikipedia.org/wiki/.properties

Rdaly: /* Example of Project Definition File */

2017-02-02T16:20:48Z

Example of Project Definition File

Show changes