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

	<!--	All units must have a parent category. The example below defines the 
		unit category "Length" which has the base unit "Meter".

		NOTE: A category consists of the following
			1) package	- This will determine it's placement in the library.
			2) name		- The name of the category and should NOT be subject to locale.
			3) base		- The name of the base unit and assumes that they are in the
					  same package. This too should NOT be subject to locale.
			4) displayName	- The name that is shown to the user, this can and probably
		    			  should be subject to locale.
			5) description	- The description of this category that is availible to the user,
					  this can and probably should be subject to locale.
	-->
	<Category package="library.Sample.unit" 
		  name="Length" 
		  base="Meter" 
		  displayName="i18n:DisplayName" 
		  description="i18n:Description">
		
		<!-- 	If one of the Unit or Unit Categories attributes should be subject to locale (e.g. 
		    	availible in mulitple translations) the following <messages> tag should be included 
		     	for each locale. Each messages tag should include the attribute "lang", where it's 
			value is the java locale that is supported by that block. In the case below we have 
			two <message> block, the first defaults to "us" because no "lang" is specifeid while 
			the second defines the translation to be used in the Japanese locale.

			The actual matching is done between the text that follows the "i18n:" above and the 
			value of the "key" attribute below. So in the "us" local, "i18n:DisplayName" will be 
			shown to the user as "Length" while in the "ja" local is will be shown as "長さ". 
			It is expected that the text will be utf-8, this will also accept unicode (/uXXXX).
		-->
		<messages>
			<term key="DisplayName">Length</term>
			<term key="Description">Distance between two ends.</term>
		</messages>
		<messages lang="ja">
			<term key="DisplayName">\u9adf\uff77\u7e3a\ufffd</term>
			<term key="Description">2 \u8f64\uff79\u9ae2\u8599\ufffd\u970d\u665e\u5c6c\u7e32\ufffd</term>
		</messages>
	</Category>

	<!--	The examples below show how to define a unit, the base "Meter" and another unit "Length"

		NOTE: A unit consists of the following:
			1) package	- This will determine it's placement in the library.
			2) name		- The name of the unit and should NOT be subject to locale.
			3) category	- The name of the category that this unit belongs to, it is 
		       			  assumed that the unit and its category are in the same 
				  	  package. This to should NOT be subject to locale.
			4) factor	- The value that dictates how this unit relates to the base
					  in the case of the base unit this is always 1.
			5) displayName	- The name that is shown to the user, this can and probably
		    			  should be subject to locale.
			6) symbol	- The common symbol that is also shown to the user..
			7) tags		- A series of comma separated strings that allow the end user
					  to easily filter through the units. The most common will be
					  metric, SI, english, etc... but these could also include
					  tags specific to the customer like the company name.
			8) description	- The description of this unit that is availible to the user,
					  this can and probably should be subject to locale.
	-->
	<Unit package="library.Sample.unit" 
	      name="Meter" 
	      category="Length" 
	      factor="1" 
	      displayName="i18n:DisplayName" 
	      symbol="i18n:Symbol"  
	      tags="i18n:Tags" 
	      description="i18n:Description">

		<messages>
			<term key="DisplayName">Meter</term>
			<term key="Symbol">m</term>
			<term key="Tags">SI, metric</term>
			<term key="Description">The meter is the length of the path travelled by light in vacuum during a time interval of 1/299,792,458 of a second.</term>
		</messages>
		<messages lang="ja">
			<term key="DisplayName">\u7e5d\uff61\u7e5d\uff7c\u7e5d\u533b\u039d</term>
			<term key="Symbol">m</term>
			<term key="Tags">SI, SI Base</term>
			<term key="Description">\u9adf\uff77\u7e3a\u8f14\ufffd\u870a\u5005\uff7d\u962a\ufffd1 \u7e5d\uff61\u7e5d\uff7c\u7e5d\u533b\u039d\u7e3a\uff6f\u7e32\ufffd99 792 458 \u86fb\ufffd\ufffd 1 \u9058\u5075\ufffd\u8b4e\u308b\u4fe3\u7e3a\uff6b\u8708\u5ce8\u2032\u9035\u6ebd\uff69\uff7a\u8373\uff6d\u7e67\u5243\uff7c\u6634\uff4f\u7e67\u7396\uff77\u665e\u5c6c\u7e3a\uff67\u7e3a\u5436\ufffd</term>
		</messages>
	</Unit>

	<!--	The example below shows an additonal non-base unit. Note that the factor shows that 
	        1 foot is equal to 0.3048 of the base unit, which in this case in the meter. It should 
		also be noted that this unit definition does not use any localization, It is as simple 
		as a single unit definition can get.
	-->
	<Unit package="library.Sample.unit" 
	      name="Foot" 
	      category="Length" 
	      factor="0.3048" 
	      displayName="Foot" 
       	      symbol="ft"  
	      tags="Non SI, English" 
	      description="A unit of length, found in a number of different systems. The international foot is 0.3048 meters.">
	</Unit>

</fiper_Units>
