LRM Android Support - Revision history

Llawson: /* Example of Project Definition for Resources */

2021-03-09T00:33:55Z

Example of Project Definition for Resources

← Older revision		Revision as of 00:33, 9 March 2021
Line 57:		Line 57:

	== Example of Project Definition for Resources ==		== Example of Project Definition for Resources ==
	The following is an example of xml resource file definitions. See [[Supported_Resource_Bundles#Resource_Extensions\| resource extensions]] for more information.		The following is an example of xml resource file definitions. See [[Supported_Resource_Bundles#Resource_Extensions\| resource extensions]] for more information on extensions. The project defintion can also be setup [[On_Boarding_a_project_with_both_LRM_and_Globalyzer#Resource_File_types\| using Jenkins]]

	<resource-extensions>		<resource-extensions>

Llawson: /* Example strings.xml File For Android */

2021-03-09T00:30:46Z

Example strings.xml File For Android

← Older revision		Revision as of 00:30, 9 March 2021
Line 18:		Line 18:

	== Example strings.xml File For Android==		== Example strings.xml File For Android==

			For information on Android string resources see https://developer.android.com/guide/topics/resources/string-resource

	<?xml version="1.0" encoding="utf-8"?>		<?xml version="1.0" encoding="utf-8"?>

Llawson: /* Example strings.xml File For Android */

2021-03-09T00:29:07Z

Example strings.xml File For Android

← Older revision		Revision as of 00:29, 9 March 2021
Line 26:		Line 26:
	<string name="person_activity_title">Person</string>		<string name="person_activity_title">Person</string>
	<string name="label_person_tree_button">View This Tree</string>		<string name="label_person_tree_button">View This Tree</string>
	<string name="~~label_person_other~~">~~Other~~</~~string~~>		<!-- Array Support -->
	<~~string name="label_person_name"~~>~~Name~~</~~string~~>		<string-array name="planets_array">
	<~~string name="label_person_details"~~>~~Details~~</string>		<item>Mercury</item>
	<!-- ~~Fact detail:~~ -->		<item>Venus</item>
	<~~string~~ name="~~fact_detail_sub_header_reason~~"~~>Reason This Information Is Correct</string~~>		<item>Earth</item>
	<~~string name~~="~~fact_detail_footer_modified~~">~~Modified~~</~~string~~>		<item>Mars</item>
	<~~string name~~="~~fact_detail_send_email_chooser~~">~~Choose an Email Client</string>~~		</string-array>
	~~<string name="fact_detail_send_email_error_no_client">Email app not~~ found</~~string~~>		<!-- Plural Support -->
	~~<string name="fact_name_label">Name~~</~~string~~>		<plurals name="numberOfSongsAvailable">
			<item quantity="one">%d song found.</item>
			<item quantity="other">%d songs found.</item>
			</plurals>
	</resources>		</resources>

	== ''xml'' parser type using AndroidParser.xml format definition ==		== ''xml'' parser type using AndroidParser.xml format definition ==
	=== valid Android xml syntax ===		=== valid Android xml syntax ===

Llawson: /* Example of Project Definition for Resources */

2017-09-18T20:21:40Z

Example of Project Definition for Resources

← Older revision		Revision as of 20:21, 18 September 2017
Line 52:		Line 52:

	== Example of Project Definition for Resources ==		== Example of Project Definition for Resources ==
	The following is an example ~~of the definition~~ of xml ~~resources~~.		The following is an example of xml resource file definitions. See [[Supported_Resource_Bundles#Resource_Extensions\| resource extensions]] for more information.

	<resource-extensions>		<resource-extensions>
	<resource-extension>		<resource-extension>

Llawson: /* Example of Project Definition for Resources */

2017-09-18T20:20:08Z

Example of Project Definition for Resources

← Older revision		Revision as of 20:20, 18 September 2017
Line 52:		Line 52:

	== Example of Project Definition for Resources ==		== Example of Project Definition for Resources ==
			The following is an example of the definition of xml resources.
	<resource-extensions>		<resource-extensions>
	<resource-extension>		<resource-extension>

Llawson: /* Example of Project Definition File */

2017-09-18T20:19:26Z

Example of Project Definition File

@@ Line 51: / Line 51: @@
 </ul>
-== Example of Project Definition File ==
+== Example of Project Definition for Resources ==
- <?xml version="1.0" encoding="UTF-8" standalone="no"?>
+   <resource-extensions>
      <resource-extension>
       '''&lt;!-- parser-type not needed since .xml is a standard LRM extension that maps to the xml parser type --&gt;'''
@@ Line 100: / Line 79: @@
      </resource-extension>
    </resource-extensions>

Llawson: /* xml parser type using AndroidParser.xml format definition */

2017-09-01T19:06:14Z

xml parser type using AndroidParser.xml format definition

← Older revision		Revision as of 19:06, 1 September 2017
Line 39:		Line 39:
	== ''xml'' parser type using AndroidParser.xml format definition ==		== ''xml'' parser type using AndroidParser.xml format definition ==
	=== valid Android xml syntax ===		=== valid Android xml syntax ===
	Files that use the ''xml'' parser and the AndroidParser.xml format definition are expected to have valid Android xml file syntax		Files that use the ''xml'' parser and the [[LRM_XML_Support#AndroidParser.xml_structure\|AndroidParser.xml]] format definition are expected to have valid Android xml file syntax

	=== Android .xml uses the ''xml'' parser type===		=== Android .xml uses the ''xml'' parser type===

Llawson: /* Example of Project Definition File */

2017-09-01T16:15:46Z

Example of Project Definition File

← Older revision		Revision as of 16:15, 1 September 2017
Line 37:		Line 37:
	</resources>		</resources>

			== ''xml'' parser type using AndroidParser.xml format definition ==
			=== valid Android xml syntax ===
			Files that use the ''xml'' parser and the AndroidParser.xml format definition are expected to have valid Android xml file syntax

			=== Android .xml uses the ''xml'' parser type===
			When defining a project containing LRM Standard Android.xml resource files, there is no need to define a ''<parser-type>'' as the ''xml'' parser will always be used along with the AndroidParser.xml format definition.

			=== unique file extension needs to define ''xml'' parser type. Xml format definition defaults to Android ===
			If a unique file extension is a valid Android xml file, then:
			<ul>
			<li>In the Project definition xml file, ''<parser-type>'' should be ''xml'' </li>
			<li>There is no need to copy over a format definition because the default definition is for Android syntax.
			</ul>

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

Llawson: /* Example of Project Definition File */

2017-08-31T21:55:59Z

Example of Project Definition File

← Older revision		Revision as of 21:55, 31 August 2017
Line 61:		Line 61:
	<default-locale>en</default-locale>		<default-locale>en</default-locale>
	<resource-extensions>		<resource-extensions>
	'''~~<resource~~-extension>'''		<resource-extension>
			'''<!-- parser-type not needed since .xml is a standard LRM extension that maps to the xml parser type -->'''
	'''<extension>xml</extension>'''		'''<extension>xml</extension>'''
	'''<file-name-pattern/>'''		'''<file-name-pattern/>'''
Line 70:		Line 71:
	'''<localized-file-encoding>UTF-8</localized-file-encoding>'''		'''<localized-file-encoding>UTF-8</localized-file-encoding>'''
	'''<parameter-regex-pattern><![CDATA[%d\|%s\|%d+$s\|%d+$d\|%\{w+\}]]></parameter-regex-pattern>'''		'''<parameter-regex-pattern><![CDATA[%d\|%s\|%d+$s\|%d+$d\|%\{w+\}]]></parameter-regex-pattern>'''
	'''</~~resource~~-~~extension~~>'''		</resource-extension>
			<resource-extension>
			'''<!-- parser-type is required because .myext is not a standard LRM extension -->'''
			'''<extension>''myext''</extension>'''
			'''''<!-- There is no need to copy over a parser.xml because the default xml parser is for Android files -->'''''
			'''''<parser-type>xml</parser-type>'''''
			'''<file-name-pattern/>'''
			'''<use-pattern-on-dflt-locale>0</use-pattern-on-dflt-locale>'''
			'''<file-location-pattern>*-l-c-v</file-location-pattern>'''
			'''<use-location-pattern-on-dflt-locale>0</use-location-pattern-on-dflt-locale>'''
			'''<base-file-encoding>UTF-8</base-file-encoding>'''
			'''<localized-file-encoding>UTF-8</localized-file-encoding>'''
			'''<parameter-regex-pattern><![CDATA[%d\|%s\|%d+$s\|%d+$d\|%\{w+\}]]></parameter-regex-pattern>'''
			</resource-extension>
	</resource-extensions>		</resource-extensions>
	<dirset>		<dirset>
	<includes>		<includes>
	<include-dir>/</include-dir>		<include-dir-file>**/string.xml</include-dir-file>
			<include-dir-file>*/.myext</include-dir-file>
	</includes>		</includes>
	<excludes>		<excludes>
	<exclude-dir-file>**/~~integration.xml</exclude-dir-file>~~		<exclude-dir-file>/source/bin/</exclude-dir-file>
	~~<exclude-dir-file>**/logging.xml</exclude-dir-file>~~		</excludes>
	~~<exclude-dir-file>/values-eo/</exclude-dir-file>~~
	~~<exclude-dir-file>/values-xx/</exclude-dir-file>~~
	~~<exclude-dir-file>/LRMScans/</exclude-dir-file>~~
	<exclude-dir-file>/~~GlobalyzerScans~~/</exclude-dir-file>
	</excludes>
	</dirset>		</dirset>
	</lrmconf>		</lrmconf>

Rdaly: /* Naming Conventions */

2017-02-02T18:11:35Z

Naming Conventions

← Older revision		Revision as of 18:11, 2 February 2017
Line 1:		Line 1:
	== Naming Conventions ==		== Naming Conventions ==
	Android resources ~~bundles~~ are named <code>strings.xml</code>. Typically, an Android application will have one <code>strings.xml</code> base file located under a directory named <code>values</code>. The corresponding translated resource bundle will be also named <code>strings.xml</code> and located under a directory named <code>values-fr</code> (for French) at the same level as <code>values</code>.		Android resources files are named <code>strings.xml</code>. Typically, an Android application will have one <code>strings.xml</code> base file located under a directory named <code>values</code>. The corresponding translated resource bundle will be also named <code>strings.xml</code> and located under a directory named <code>values-fr</code> (for French) at the same level as <code>values</code>.

	For example, for a few locales, the directory structure and file names would be:		For example, for a few locales, the directory structure and file names would be: