Internationalization/tool evaluation - Revision history

Ivangan: /* Writing our own tools */

2008-03-14T19:54:03Z

‎Writing our own tools

2008-03-14T19:51:00Z

‎Problems, Ideas, Further Development

2008-03-14T19:48:41Z

‎Other tools to watch

2008-03-14T19:24:30Z

‎Writing our own tools

2008-03-14T19:20:19Z

‎Problems, Ideas, Further Development

2008-03-14T19:19:40Z

‎Problems, Ideas, Further Development

2008-03-14T19:13:39Z

‎Other tools to watch

2008-03-14T19:09:37Z

‎Other tools to watch

2006-06-03T06:11:24Z

2006-05-31T16:50:13Z

added page to our category

@@ Line 160: / Line 160: @@
 Drawbacks
 * can be a lot of work
-Efficient use of time would be to combine NLSO-WEB for web interface with a custom written module for source code/po file translation which could be executed on the client's computer, anybody interested in putting such a project together? [http://comchatter.com/contact.php Contact Ivan via this form]
+Efficient use of time would be to combine NLSO-WEB for web interface with a custom written module for source code/po file translation which could be executed on the client's computer, anybody interested in putting such a project together? [http://comchatter.com/contact.php Contact Ivan via this link]
 = Problems, Ideas, Further Development =

← Older revision		Revision as of 19:51, 14 March 2008
Line 175:		Line 175:
	* NLSO-WEB has autodetection of the client browser language settings and uses primary / alternate langauge policy to maximize the usability of the site		* NLSO-WEB has autodetection of the client browser language settings and uses primary / alternate langauge policy to maximize the usability of the site
	* NLSO-WEB can be easily introduced to an existing website which uses PHP & Mysql, so much of what's suggested here is already available in one library, it also includes IP to country system and considerable Geo-Data		* NLSO-WEB can be easily introduced to an existing website which uses PHP & Mysql, so much of what's suggested here is already available in one library, it also includes IP to country system and considerable Geo-Data
		+
		+	Using NLSO-WEB to provide a back-end & support pages combined with a client module is the best way to create applications that share translations, then localized versions could become a thing of the past

@@ Line 142: / Line 142: @@
 * [http://po4a.alioth.debian.org/ po4a] (The po4a (po for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation.)
 * xml2po
-* [http://sourceforge.net/projects/nlso NLSO] (for Windows) volunteers needed to rewrite this for Lazarus IDE, this would also open it up to Apple OS & Linux,[http://comchatter.com/contact.php Contact Ivan via this form for more info]
+* [http://sourceforge.net/projects/nlso NLSO] (for Windows) volunteers needed to rewrite this for Lazarus IDE, Could also be achieved using Eiffel, this would also open it up to Apple OS & Linux,[http://comchatter.com/contact.php Contact Ivan via this form for more info]
 * [http://sourceforge.net/projects/nlso-web NLSO-WEB] (for Web design)
 * [http://comchatter.com/nlso ComChatter.com/nlso] (the new home of nlso), a site built using NLSO principles

@@ Line 160: / Line 160: @@
 Drawbacks
 * can be a lot of work
 = Problems, Ideas, Further Development =

@@ Line 170: / Line 170: @@
 * Unicode problem (maybe a collaboration with the Unicode group can help)
-NLSO-WEB already supports UTF-8 format & presents it correctly
+* NLSO-WEB already supports UTF-8 format & presents it correctly
-NLSO-WEB had the database of language data online and it can be updated by authorized users via the browser
+* NLSO-WEB had the database of language data online and it can be updated by authorized users via the browser
-NLSO-WEB has autodetection of the client browser language settings and uses primary / alternate langauge policy to maximize the usability of the site
+* NLSO-WEB has autodetection of the client browser language settings and uses primary / alternate langauge policy to maximize the usability of the site
-NLSO-WEB can be easily introduced to an existing website which uses PHP & Mysql, so much of what's suggested here is already available in one library, it also includes IP to country system and considerable Geo-Data
+* NLSO-WEB can be easily introduced to an existing website which uses PHP & Mysql, so much of what's suggested here is already available in one library, it also includes IP to country system and considerable Geo-Data

← Older revision		Revision as of 19:19, 14 March 2008
Line 169:		Line 169:
	* A 2nd database can be placed on the user's pc and autoupdate Eiffel and the additional content one may have when needed (when a new version of Eiffel or a new tool is available for example), with this system one doesn't need to download every time a new file containing some information already downloaded before		* A 2nd database can be placed on the user's pc and autoupdate Eiffel and the additional content one may have when needed (when a new version of Eiffel or a new tool is available for example), with this system one doesn't need to download every time a new file containing some information already downloaded before
	* Unicode problem (maybe a collaboration with the Unicode group can help)		* Unicode problem (maybe a collaboration with the Unicode group can help)
		+
		+	NLSO-WEB already supports UTF-8 format & presents it correctly
		+	NLSO-WEB had the database of language data online and it can be updated by authorized users via the browser
		+	NLSO-WEB has autodetection of the client browser language settings and uses primary / alternate langauge policy to maximize the usability of the site
		+	NLSO-WEB can be easily introduced to an existing website which uses PHP & Mysql, so much of what's suggested here is already available in one library, it also includes IP to country system and considerable Geo-Data

@@ Line 143: / Line 143: @@
 * xml2po
 * [http://nlso-objects.sourceforge.net/ NLSO] (for Windows)
 * Kartouche

← Older revision		Revision as of 06:11, 3 June 2006
Line 1:		Line 1:
−	~~[[Category:Projects]]~~
	[[Category:Internationalization]]		[[Category:Internationalization]]

← Older revision		Revision as of 16:50, 31 May 2006
Line 1:		Line 1:
		+	[[Category:Projects]]
		+	[[Category:Internationalization]]
		+
	In this section it will be discussed which tool should be taken for the i18n work.		In this section it will be discussed which tool should be taken for the i18n work.