Le 20/06/2014 12:41, Paolo Cavallini a écrit :
Il 20/06/2014 11:15, René-Luc Dhont ha scritto:
It's probably due to different encoding in desktop (Latin1), server (UTF-8) and
data
(Latin1)
good catch, thanks.
I think we should handle this more gracefully, however. For the end user this
woul
Il 20/06/2014 11:15, René-Luc Dhont ha scritto:
> It's probably due to different encoding in desktop (Latin1), server (UTF-8)
> and data
> (Latin1)
good catch, thanks.
I think we should handle this more gracefully, however. For the end user this
would
be very difficult to solve.
All the best.
Le 20/06/2014 11:07, Paolo Cavallini a écrit :
Il 20/06/2014 10:51, René-Luc Dhont ha scritto:
Does the issue still exist ?
I take a look at the map application and roads are well rendering.
Yes, the underlying issue is still there. I kind of solved for that application
simply using an INT f
Il 20/06/2014 10:51, René-Luc Dhont ha scritto:
> Does the issue still exist ?
>
> I take a look at the map application and roads are well rendering.
Yes, the underlying issue is still there. I kind of solved for that application
simply using an INT field, and applying labels to it.
All the best
Hi Paolo,
Does the issue still exist ?
I take a look at the map application and roads are well rendering.
Regards,
Le 19/06/2014 12:50, Paolo Cavallini a écrit :
Hi all.
Apparently items whose classification name includes high ASCII (àèé etc.) are
drawn
and shown in the legend, but not on t
Hi all.
Apparently items whose classification name includes high ASCII (àèé etc.) are
drawn
and shown in the legend, but not on the map:
http://213.136.126.133:8080/www/index.php/view/map/?repository=abidjan&project=abidjan_demo
see e.g. Routes > Voies revêtues
Unsure whether it is a server or