Idea (and warning probably not a good one) regarding the UI for i18n. What
about if we had a single page, or maybe even a separate app that was
devoted to doing i18n of all configuration strings. It could be designed to
make it easy to batch updates, etc.. .perhaps we can even utilize existing
apps that already do this for code.
Then in the existing ui we wouldn't add much expect for some global
dropdown that selects the language. And perhaps if we wanted to provide a
nicer integration for those text fields that correspond to i18nized fields
we could add a little link titled "translate" that would forward to the
i18n page with that field selected.
Just a random thought.
On Fri, Feb 22, 2013 at 2:36 AM, Andrea Aime
<[email protected]>wrote:
> On Fri, Feb 22, 2013 at 10:32 AM, Mauro Bartolomeoli <
> [email protected]> wrote:
>
>>
>> Hi Andrea. For this 2 specific cases, I was thinking of a simple approach
>> that could be implemented as a first step to add some form of
>> internationalization.
>> For GetFeatureInfo, it would be useful to have different templates (with
>> a prefix or suffix in the name) depending on a request parameter.
>> For GetMap the env variable substitution in SLD could be used to build a
>> different PropertyName for labeling (currently this doesn't seem to be
>> feasible, I think because env variable substitution can only produce a
>> Literal and not a PropertyName). I was thinking of something like this:
>>
>> <Label>
>> <ogc:PropertyName>
>> <ogc:Function name="Concatenate">
>> <ogc:Literal>STATE_</ogc:Literal>
>> <ogc:Function name="env">
>> <ogc:Literal>lang</ogc:Literal>
>> <ogc:Literal>EN</ogc:Literal>
>> </ogc:Function>
>> </ogc:Function>
>> </ogc:PropertyName>
>> </Label>
>>
>
> We do have the "property" function that can be used for the purpose, and
> that would work for GetMap.
> For GetFeatureInfo in HTML format we could roll out FTL templates and
> inject the language in the HTML
> template.
>
> However, for any other GetFeatureInfo output format (text, gml, json)
> we're toast, there is no templating,
> and for GetFeature it's the same.
> Now that I think about it, we might also have problems with
> GetLegendGraphics, the titles are coming from
> the rule titles right? But afaik there is no way to specify multiple
> titles in different languages in an SLD.
>
> Cheers
> Andrea
>
> --
> ==
> Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
> information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
