Dashboard encoding problem

[Luka Lazovic]

Hi, 

I have a problem when creating widget on Dashboard, where Serbian Latin letters (ć, š, ž, č) are replaced with special characters. Mapstore and Geoserver are hosted on Windows with Tomcat. How can I solve this problem? I have tried many different solutions but they did not give an effect.

Best Regards,

Luka Lazovic

[Lorenzo Natali]

Hi,

I don't have tried with MapStore Binary of 2021.02.00 on windows creating a dashboard with a text widget, copy and paste (ć, š, ž, č) in a text widget and saved as a new dashboard. Also title of the dashboard was (ć, š, ž, č).

I refersh the page but I didn't noticed anything. It works correctly to me. 

Maybe the data coming from GeoServer?

[Luka Lazovic]

Hi Lorenzo,

It was problem with Java, I needed to add JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 into system variables.

Best Regards,

Luka

[Lorenzo Natali]

Great!

Thank you for providing your solution.

[Florent Gravin]

Hello there,

I wonder if you managed to make those encodings working in the print as well ?

Putting " í, á, é, š, č,....." in the title of the print removes the  č but displays well the í, á, é, š

I put 
env:
- name: JAVA_OPTS
value: -Xms512m -Xmx512m -XX:MaxPermSize=128m -Dgeorchestra.datadir=/etc/georchestra -DPRINT_BASE_URL=pdf -Dfile.encoding=UTF-8
- name: HOST
value: 0.0.0.0
- name: JAVA_TOOL_OPTIONS
value: -Dfile.encoding=UTF-8

in the Mapstore container.
I wonder if it's because MapfishPrint would have been built without the option or something like that ? Or a font issue ?  It's also weird that all the char work but the č

Do you guys have the same issue ?

Thanks

[Lorenzo Natali]

Did you try to follow this thread?

https://github.com/mapfish/mapfish-print/issues/49#issuecomment-17812911

They suggest to use the variable, configure server.xml in tomcat and to modify the font in config.yml

--
You received this message because you are subscribed to the Google Groups "mapstore-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapstore-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapstore-users/c803c7f7-30c7-4e3e-967b-d314ab82ecbbn%40googlegroups.com.

[Florent Gravin]

Thanks Lorenzo for the hint, it helped me.

Still not able to fix it though.

I added JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 but it's not better.

I tried the DejaVu.ttf font but still nothing

I put fontEncoding: Identity-H in the config.yml but now i'm getting an error 

Error on printing: Error while generating PDF: java.nio.charset.UnsupportedCharsetException: Identity-H at java.base/java.nio.charset.Charset.forName(Charset.java:529) at com.itextpdf.text.pdf.PdfEncodings.convertToBytes(PdfEncodings.java:186) at 

com.itextpdf.text.pdf.Type1Font.<init>(Type1Font.java:277) at

So the last thing is the the 

<Connector

URIEncoding="UTF-8"

But i couldn't update that from the https://github.com/geosolutions-it/MapStore2/blob/15c079322f4ce44f73f957bd145a1bf209c695f2/binary/tomcat/conf/server.xml#L69
The server.xml deploy within the image is different.

So I tried to update the server.xml directly in the image, shutdown and restart tomcat, but still have the error.

Don't know if anyone was able to figure that out.

Thanks for the help anyway

[Shai Sussman]

I have a similar problem that occurs only on WINDOWS (not on ubuntu)

see the image below, the text in the bar chart is not displayed correctly I am guessing this has got to do with wrong encoding.

I am not familiar with where EXACTLy do I need to set the variable in the JAVA_TOOL_OPTIONS?

can you provide me step by step where I need to make this modification as I am not familiar with modifying JAVA environment?

[Lorenzo Natali]

Hi Shai, 

this issue you are reporting is not releated to printing. 

That labels are handled by plotlyJS and/or GeoServer(that is probably returning the labels ton the client in that way) and/or the proxy 

So I suggest to write another thread. 

I can suggest to see first the encoding and the response from GeoServer in developer tools to gather more information about the possible cause of this issue.