Localization support added into Jamfile-engine.

* Added possibility to localize projects driven by Jamfile-engine in
  the easy way. Targets "catkeys", "catalogs", "catlogsinstall",
  "bindcatalogs" introduced.
* This contribution was made by Peter Polacik during working on GCI 2011
  tasks. Thank you!

data/develop/Jamfile

@@ -1,4 +1,4 @@
-## Haiku Generic Jamfile v1.0 ##
+## Haiku Generic Jamfile v1.0.1 ##
 
 ## Fill in this file to specify the project being created, and the referenced
 ## Jamfile-engine will do all of the hard work for you.  This handles both
@@ -17,6 +17,10 @@ NAME =  ;
 #	DRIVER: Kernel Driver
 TYPE =  ;
 
+# Specify the application MIME signature, if you plan to use localization
+# 	features. String format x-vnd.<VendorName>-<AppName> is recommended.
+APP_MIME_SIG =  ;
+
 # Specify the source files to use
 #	Full paths or paths relative to the Jamfile can be included.
 # 	All files, regardless of directory, will have their object
@@ -36,6 +40,9 @@ RSRCS =  ;
 #	-	if your library follows the naming pattern of:
 #		libXXX.so or libXXX.a you can simply specify XXX
 #		library: libbe.so entry: be
+#
+#	-	for localization support add following libs:
+#		locale localestub
 #		
 #	- 	if your library does not follow the standard library
 #		naming scheme you need to specify the path to the library
@@ -65,6 +72,13 @@ LOCAL_INCLUDE_PATHS =  ;
 #	NONE, SOME, FULL
 OPTIMIZE =  ;
 
+# Specify the codes for languages you are going to support in this 
+# 	application. The default "en" one must be provided too. "jam catkeys"
+# 	will recreate only locales/en.catkeys file. Use it as template for
+# 	creating other languages catkeys. All localization files must be
+# 	placed in "locales" sub-directory.
+LOCALES =  ;
+
 # Specify any preprocessor symbols to be defined.  The symbols will not
 #	have their values set automatically; you must supply the value (if any)
 #	to use.  For example, setting DEFINES to "DEBUG=1" will cause the