[mapserver-users] Re: mapserver and i18n

[Michael Smith]

I would do this on the backend. Pass a language variable to your data query

DATA "geom from data where lang='%lang%'"
LABELITEM "%LANG%HIGHWAY"

And have one mapfile and just have your translations in PostGis/Oracle/etc.

Mike


-- 
Michael Smith
US Army Corps of Engineers
Remote Sensing/GIS Center
Hanover, NH 





On 10/6/10 1:56 PM, "Stephen Woodbridge" <woodbri at swoodbridge.com> wrote:

> On 10/6/2010 12:54 PM, Bart van den Eijnden wrote:
>> I don't agree with you here Steve.
>> 
>> Also look at the INSPIRE language parameter, it's up to the service
>> (View Service, WMS) to translate, not the client. Think of layer
>> titles in WMS GetCapabilities.
>> 
>> The way I've been doing it is to duplicate my datasets behind
>> Mapserver, but that's not an ideal situation.
>> 
>> Best regards, Bart
>> 
> 
> Hi Bart,
> 
> Thanks for this feedback. I will look into that.
> 
> While I have implemented multilingual driving directions, but I'm far
> from being very knowledgeable with regards to most of the i18n issues.
> 
> So do you have any recommendations or ideas for how mapserver should
> deal with this? Would something like creating an additional mapping
> table for terms solve this problem? Maybe something like the following
> in a mapfile:
> 
> TRANSLATIONS
>    TERM "Highway"
>      en_US.UTF-8 "Highway"
>      en_UK.UTF-8 "Autoroute"
>      ...
>    END
>    TERM ...
>    END
> END
> 
> or something along these lines, with the idea the mapserver use this to
> deal with user requests appropriately.
> 
> -Steve W
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users