-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
export files - wrong file name #1475
Comments
the same problem when the user downloads the PDF file (printer tool) |
@rldhont here i'm talking about with wrong file name (PDF output) related to printer tool |
it's a very annoying situation for the users... please, can you try to fix it? |
@josemvm I think this issue a lizmap issue not wfsOutputExtension one. |
@rldhont yes, i think so too, that's why i keep it here |
@rldhont this issue is about the when the user downloads the printer output (PDF, JPG, PNG or SVG), lizmap doesn't assume the special characters |
??? |
This code is about excluding the restricted composers to the available composers. |
somewhere into the code the name of the printer output file is formed based on the concatenation of the |
hi
lizmap exports the files with wrong file name encoding (e.g.:
export_Bocas_de_Incêndio.xxx
in case ofBocas de Incêndio
/layer name in lizmap).#500 (comment)
thanks for your attention
The text was updated successfully, but these errors were encountered: