[Geoserver-users] WMS GetLegendGraphic i18n

GeoServer GeoServer User
1

Hello :slight_smile:

I recently started using GeoServer and am currently trying to learn the ropes. My new project has been using GeoServer for some time now. They currently are on version 2.5. Now I received the task to add internationalization to the legend drawn from the style of a layer. I could do it with custom functions but I would prefer a native way over building my own mechanism. I found this mailing list entry: http://osgeo-org.1560.x6.nabble.com/SLD-and-Internationalization-td5054597.html which seems to address my issue exactly. But as I can find no mention of this in the documentation I am not sure if this made it into the application as of yet.

Does anyone know if the SLD i18n was implemented? And if so, which parameter do I have to set to define the locale for the getLegendGraphic (http://docs.geoserver.org/stable/en/user/services/wms/get_legend_graphic/legendgraphic.html#get-legend-graphic) request?

Cheers,
Michael

2

Hi Michael,
indeed there is some support for it, but it’s not well documented (I will try to add some documentation ASAP).
You can use the parameter LANGUAGE to choose a particular locale, then you can use the following syntax in SLD to specify some of the metadata in several languages:

Basso-Basso Basso-Basso Low-Low Faible-Faible Niedriges-Niedriges

The text directly inside Title is the default (when no language parameter is specified). The text in a Localized tag is used when LANGUAGE is equal to the lang attribute value.

This syntax can be used for the following SLD Title and Abstract tags.

Regards,
Mauro

···

2015-09-11 0:50 GMT+02:00 Michael Colin <Colin_Michael@anonymised.com>:

Hello :slight_smile:

I recently started using GeoServer and am currently trying to learn the ropes. My new project has been using GeoServer for some time now. They currently are on version 2.5. Now I received the task to add internationalization to the legend drawn from the style of a layer. I could do it with custom functions but I would prefer a native way over building my own mechanism. I found this mailing list entry: http://osgeo-org.1560.x6.nabble.com/SLD-and-Internationalization-td5054597.html which seems to address my issue exactly. But as I can find no mention of this in the documentation I am not sure if this made it into the application as of yet.

Does anyone know if the SLD i18n was implemented? And if so, which parameter do I have to set to define the locale for the getLegendGraphic (http://docs.geoserver.org/stable/en/user/services/wms/get_legend_graphic/legendgraphic.html#get-legend-graphic) request?

Cheers,
Michael

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

3

Hello Mauro,

thank you very much for the quick reply. This helped me use the built-in way rather than writing my own solution via an extension, though the extension was pretty much ready to go at that point.

I noticed one rather big issue for some applications though:
“lang” really only specifies the lang, not the country. If I try to use the locale instead, e.g. es_ES, it will simply not work. Or maybe I just tried it the wrong way, who knows. But if not, wouldn’t it be an easy fix to allow for any kind of string as input to lang instead of the current solution? Luckily for my purposes this isn’t an issue.

A few other things that came up with my test cases:
Localized doesn’t seem to accept a namespace. In my example the following wouldn’t work whereas the 2nd snipped worked:

<?xml version="1.0" encoding="UTF-8"?><sld:StyledLayerDescriptor xmlns="[http://www.opengis.net/sld](http://www.opengis.net/sld)" xmlns:sld="[http://www.opengis.net/sld](http://www.opengis.net/sld)" ....

sld:TitleDesign
<sld:Localized lang=“es”>Diseño
<sld:Localized lang=“pt”>Design
<sld:Localized lang=“ru”>Точность сетки
</sld:Title>
working:
sld:TitleDesign
Diseño
Design
Точность сетки
</sld:Title>

When uploading a style through the GUI it is not encoded as UTF8 and the internationalised values are mangled. I had to upload them manually into the styles directory instead.

Thank you once again and have a good day :slight_smile:

Cheers,
Michael

From: Mauro Bartolomeoli <maurobartolomeoli@…84…>
To: Michael Colin <Colin_Michael@…7234…>
Cc: GeoServer Mailing List List geoserver-users@lists.sourceforge.net
Date: 11/09/2015 05:40 PM
Subject: Re: [Geoserver-users] WMS GetLegendGraphic i18n

Hi Michael,
indeed there is some support for it, but it’s not well documented (I will try to add some documentation ASAP).
You can use the parameter LANGUAGE to choose a particular locale, then you can use the following syntax in SLD to specify some of the metadata in several languages:

Basso-Basso Basso-Basso Low-Low Faible-Faible Niedriges-Niedriges

The text directly inside Title is the default (when no language parameter is specified). The text in a Localized tag is used when LANGUAGE is equal to the lang attribute value.

This syntax can be used for the following SLD Title and Abstract tags.

Regards,
Mauro

2015-09-11 0:50 GMT+02:00 Michael Colin <Colin_Michael@…7234…>:
Hello :slight_smile:

I recently started using GeoServer and am currently trying to learn the ropes. My new project has been using GeoServer for some time now. They currently are on version 2.5. Now I received the task to add internationalization to the legend drawn from the style of a layer. I could do it with custom functions but I would prefer a native way over building my own mechanism. I found this mailing list entry: http://osgeo-org.1560.x6.nabble.com/SLD-and-Internationalization-td5054597.html which seems to address my issue exactly. But as I can find no mention of this in the documentation I am not sure if this made it into the application as of yet.

Does anyone know if the SLD i18n was implemented? And if so, which parameter do I have to set to define the locale for the getLegendGraphic (http://docs.geoserver.org/stable/en/user/services/wms/get_legend_graphic/legendgraphic.html#get-legend-graphic) request?

Cheers,
Michael

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

4

Hi Michael,
thank you for your feedbacks on the functionality: can you open a JIRA issue with your observations?

Thanks
Mauro

···

2015-09-15 3:52 GMT+02:00 Michael Colin <Colin_Michael@anonymised.com>:

Hello Mauro,

thank you very much for the quick reply. This helped me use the built-in way rather than writing my own solution via an extension, though the extension was pretty much ready to go at that point.

I noticed one rather big issue for some applications though:
“lang” really only specifies the lang, not the country. If I try to use the locale instead, e.g. es_ES, it will simply not work. Or maybe I just tried it the wrong way, who knows. But if not, wouldn’t it be an easy fix to allow for any kind of string as input to lang instead of the current solution? Luckily for my purposes this isn’t an issue.

A few other things that came up with my test cases:
Localized doesn’t seem to accept a namespace. In my example the following wouldn’t work whereas the 2nd snipped worked:

<?xml version="1.0" encoding="UTF-8"?><sld:StyledLayerDescriptor xmlns="[http://www.opengis.net/sld](http://www.opengis.net/sld)" xmlns:sld="[http://www.opengis.net/sld](http://www.opengis.net/sld)" ....

sld:TitleDesign
<sld:Localized lang=“es”>Diseño
<sld:Localized lang=“pt”>Design
<sld:Localized lang=“ru”>Точность сетки
</sld:Title>
working:
sld:TitleDesign
Diseño
Design
Точность сетки
</sld:Title>

When uploading a style through the GUI it is not encoded as UTF8 and the internationalised values are mangled. I had to upload them manually into the styles directory instead.

Thank you once again and have a good day :slight_smile:

Cheers,
Michael

From: Mauro Bartolomeoli <maurobartolomeoli@anonymised.com>
To: Michael Colin <Colin_Michael@anonymised.com4…>
Cc: GeoServer Mailing List List <geoserver-users@lists.sourceforge.net>
Date: 11/09/2015 05:40 PM
Subject: Re: [Geoserver-users] WMS GetLegendGraphic i18n

Hi Michael,
indeed there is some support for it, but it’s not well documented (I will try to add some documentation ASAP).
You can use the parameter LANGUAGE to choose a particular locale, then you can use the following syntax in SLD to specify some of the metadata in several languages:

Basso-Basso Basso-Basso Low-Low Faible-Faible Niedriges-Niedriges

The text directly inside Title is the default (when no language parameter is specified). The text in a Localized tag is used when LANGUAGE is equal to the lang attribute value.

This syntax can be used for the following SLD Title and Abstract tags.

Regards,
Mauro

2015-09-11 0:50 GMT+02:00 Michael Colin <Colin_Michael@anonymised.com>:
Hello :slight_smile:

I recently started using GeoServer and am currently trying to learn the ropes. My new project has been using GeoServer for some time now. They currently are on version 2.5. Now I received the task to add internationalization to the legend drawn from the style of a layer. I could do it with custom functions but I would prefer a native way over building my own mechanism. I found this mailing list entry: http://osgeo-org.1560.x6.nabble.com/SLD-and-Internationalization-td5054597.html which seems to address my issue exactly. But as I can find no mention of this in the documentation I am not sure if this made it into the application as of yet.

Does anyone know if the SLD i18n was implemented? And if so, which parameter do I have to set to define the locale for the getLegendGraphic (http://docs.geoserver.org/stable/en/user/services/wms/get_legend_graphic/legendgraphic.html#get-legend-graphic) request?

Cheers,
Michael

Geoserver-users mailing list
Geoserver-users@anonymised.comforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

5

Hi Michael,

···

On Tue, Sep 15, 2015 at 3:52 AM, Michael Colin <Colin_Michael@anonymised.com> wrote:

Localized doesn’t seem to accept a namespace. In my example the following wouldn’t work whereas the 2nd snipped worked:

<?xml version="1.0" encoding="UTF-8"?><sld:StyledLayerDescriptor xmlns="[http://www.opengis.net/sld](http://www.opengis.net/sld)" xmlns:sld="[http://www.opengis.net/sld](http://www.opengis.net/sld)" ....

sld:TitleDesign
<sld:Localized lang=“es”>Diseño
<sld:Localized lang=“pt”>Design
<sld:Localized lang=“ru”>Точность сетки
</sld:Title>

The closing Localized tags in your snippet are wrong, they should be </sld:Localized> (qualified): perhaps this is why the example doesn’t work? Or maybe it’s just a typo in your e-mail…

–

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts! Visit
[http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:     +39 0584 1660272

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_it](http://twitter.com/geosolutions_it)

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility  for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
6

Good Morning Stefano,

thank you for pointing that out, but that only is a typo in the email. I added the sld back in for the example. We use a code generator to create a few of our styles and it generated the sld prefix into the xml whether I wanted it to or not, so this has gotten to be a painful issue I’ll have to work around.

I’ll open the Jira later on, gotta get this functionality done first.

Cheers,
Michael

From: Stefano Costa <stefano.costa@…1107…>
To: Michael Colin <Colin_Michael@…7234…>
Cc: Mauro Bartolomeoli <maurobartolomeoli@…84…>, GeoServer Mailing List List geoserver-users@lists.sourceforge.net
Date: 15/09/2015 05:47 PM
Subject: Re: [Geoserver-users] WMS GetLegendGraphic i18n

Hi Michael,

On Tue, Sep 15, 2015 at 3:52 AM, Michael Colin <Colin_Michael@…7234…> wrote:
Localized doesn’t seem to accept a namespace. In my example the following wouldn’t work whereas the 2nd snipped worked:

<?xml version="1.0" encoding="UTF-8"?><sld:StyledLayerDescriptor xmlns="[http://www.opengis.net/sld](https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opengis.net_sld&d=BQMFaQ&c=p0oa49nxxGtbbM2qgM-GB4r4m9OlGg-sEp8sXylY2aQ&r=A3KdcnVyFqLMOOqCdo2429zd-IRYbqVdYcNdu2zOiik&m=3G3IhVc0OiXsvLHMjZaW2vyx3O4BjKjrgm7-0Sl5v-8&s=ncyEGol8WVISAXYSzEqWDYeExv0g3MEVMO-sAX5OWKs&e=)" xmlns:sld="[http://www.opengis.net/sld](https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opengis.net_sld&d=BQMFaQ&c=p0oa49nxxGtbbM2qgM-GB4r4m9OlGg-sEp8sXylY2aQ&r=A3KdcnVyFqLMOOqCdo2429zd-IRYbqVdYcNdu2zOiik&m=3G3IhVc0OiXsvLHMjZaW2vyx3O4BjKjrgm7-0Sl5v-8&s=ncyEGol8WVISAXYSzEqWDYeExv0g3MEVMO-sAX5OWKs&e=)" ....

sld:TitleDesign
<sld:Localized lang=“es”>Diseño
<sld:Localized lang=“pt”>Design
<sld:Localized lang=“ru”>Точность сетки
</sld:Title>

The closing Localized tags in your snippet are wrong, they should be </sld:Localized> (qualified): perhaps this is why the example doesn’t work? Or maybe it’s just a typo in your e-mail…

–
Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.