Hi,
>
>
> Thoughts ?
I don't know how OpenLayers.i18n works, but an i18n abstraction with (optional)
langfiles is imho the way to go.
Please note, that the approach like with simplePrint is already lang-file
capable
//example:
File with statments like this:
GeoExt.ux.SimplePrint.prototype.layoutText = 'translated text...';
From a technical point of view, the ExtJS approach (and the one used with
printing) is great, as overwriting the strings in the prototype is very fast
and efficient.
From a translators point of view, an extra class which standard i18n support
like gettext/xgettext/poedit would be more appreciable. I prefer to use a style
like this:
...
title : this.i18n._('string to be translated'),
...
as i18n object i use:
http://svn.tine20.org/svn/trunk/tine20/Tinebase/js/Locale.js
http://svn.tine20.org/svn/trunk/tine20/Tinebase/js/Locale/Gettext.js
and as langhelper:
http://svn.tine20.org/svn/trunk/tine20/langHelper.php
finaly this leads to translation reports like this:
http://www.tine20.org/langStats/
cu
Cornelius
Dipl.-Phys. Cornelius Weiss
Tine 2.0 Lead Developer
Metaways Infosystems GmbH
Pickhuben 2, D 20457 Hamburg
E-Mail: [email protected]
Web: http://www.metaways.de
Tel: +49 (0)40 317031-545
Fax: +49 (0)40 317031-945
Mobile: +49 (0)170 3322254
--- Tine 2.0 - Open Source Groupware and CRM -> www.tine20.org ---
Metaways Infosystems GmbH - Sitz: D-22967 Tremsbüttel
Handelsregister: Amtsgericht Ahrensburg HRB 4508
Geschäftsführung: Hermann Thaele, Lüder-H.Thaele
_______________________________________________
Dev mailing list
[email protected]
http://www.geoext.org/cgi-bin/mailman/listinfo/dev
