[Geoprisma-dev] gettext under Windows

[Etienne Dube]

Fine, then I'll go with option #2 and commit the change.

I think Ext i18n is an interesting way of doing things, it has the 
advantage of making widgets (almost, if we exclude Globals.xslt) fully 
self-contained in their directories and skip the need to compile the .po 
files (yay). Maybe we can switch over one or two widgets to this system 
during the code sprint (after that it'll get repetitive and I guess we 
can spend the time we have together on more challenging issues!)

Etienne


On 01/03/2011 9:50 AM, Alexandre Dube wrote:
> I would go with option #2.
>
> Since we're discussing i18n here, what about 
> http://trac.osgeo.org/geoprisma/ticket/168 ?  To my eye, the getText 
> dependency could be avoided completely if we followed the Ext and 
> GeoExt i18n way.  We wouldn't drop the getText support entirely since 
> it's still very useful to customize i18n text regarding the data we 
> use (resource title, user-custom text for widgets, etc.) but the 
> 'default GeoPrisma widget i18n' could be entirely managed on client-side.
>
> Thoughts ?  Do you think this could be a nice thing to work on during 
> the sprint ?
>
> Alexandre
>
> On 11-03-01 09:35 AM, Etienne Dube wrote:
>> Hi,
>>
>> We have noticed a problem with the gettext library under PHP 5.3.5 
>> and Windows Server 2008 (x64). Details are in the ticket: 
>> http://trac.osgeo.org/geoprisma/ticket/193
>>
>> A possible solution would be to replace the default gettext that 
>> comes with PHP (which relies on the GNU gettext library) with an 
>> alternate, pure PHP implementation, namely php-gettext 
>> (https://launchpad.net/php-gettext/). I've tested it successfully by 
>> implementing a new subclass of Locale.
>>
>> Now the question is whether we make this new class (namely 
>> PhpGetTextLocale) as the default in Setting.php (by changing the 
>> LOCALE_CLASS constant), or leave GetTextLocale with the GNU gettext 
>> implementation as the default. php-gettext is licensed under the 
>> GPLv2, whereas GeoPrisma has a "Modified BSD License" (which is 
>> GPL-compatible according to 
>> http://en.wikipedia.org/wiki/BSD_licenses) so legally it should be 
>> fine. However, Yves pointed out to me that including a GPLv2 lib 
>> would prevent the use of GeoPrisma in some contexts that the BSD 
>> license allows for, namely in proprietary, non-free software.
>>
>> So the two options would be:
>>
>> 1 - Make the new PhpGetTextLocale the default in Setting.php and 
>> distribute php-gettext with GeoPrisma (in the lib/ directory). The 
>> old GetTextLocale would still be there if someone wants to use the 
>> GNU gettext implementation.
>>
>> 2 - Include the PhpGetTextLocale class but leave the existing 
>> GetTextLocale class as the default and don't distribute php-gettext 
>> with GeoPrisma. Users who want to use php-gettext would have to 
>> download the library themselves and override the default setting 
>> using the SettingImpl class.
>>
>> I'm neutral on that one, since both options are acceptable for our 
>> needs. Any opinions on that?
>>
>> Thanks,
>>
>> Etienne
>>
>
>


-- 
Etienne Dubé
Developer

Boréal Informations Stratégiques
101, Du Moulin, bureau 202-A
Magog (Québec)
J1X 4A1
Canada

Tel. :  514.313.5951 #1131
Email: etienne.dube at boreal-is.com