[postgis-users] i18n

[Paul Ramsey]

Just a quick followup on this:
- A quick grep of printf's in the postgis code revealed basically no 
english that is not part of a standard output (GML tags for example). 
Only exceptions are in debugging statements used mainly by programmers.
So most of our user-facing english in the code is actually in GEOS 
exception strings, I would guess. Other than that, it is all documentation.
Paul

Jose Moran wrote:

> ----- Original Message -----
> From: "Paul Ramsey" <pramsey at refractions.net>
> To: "PostGIS Users" <postgis-users at postgis.refractions.net>
> Sent: Thursday, June 23, 2005 11:02 AM
> Subject: [postgis-users] i18n
> 
> 
> 
>>Since we are talking about languages, I have some questions to the
>>community:
>>
>>- Should I worry that we are losing international users because of our
>>generally English-only web site (occasional submitted translations
>>notwithstanding?)
> 
> That would be a good characteristic, al least for peoplo who do not have
> English as first Language, like me :)
> 
> 
> 
>>- Would a more open web site, with translation support, actually be
>>maintained regularly, or would I risk creating a multi-lingual ghetto,
>>where only the English site is up to date, and the rest are in various
>>stages of disrepair?
> 
> just to say...big job man!,
> 
> 
> 
>>- At a code level, should we consider applying i18n to PostGIS itself?
>>The number of strings/errors we produce is low, and PgSQL handles most
>>of the core language issues, but should we try and be complete?
>>
> 
> I guess yes, but not if this makes slow move forward to other features in
> Postgis.
> 
> 
> Saludos
> José
> 
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users