-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
When exporting the data the columns are not translated #20830
Comments
Hi @Chardonneaur, it seems like when using CSV, TSV or RSS types of exports the translations should already be there. Have you tried those and it didn't work? Or you used different type of export where it's not supported (XML, JSON)? If it was the first three and the translations didn't appear, could you provide replication steps and which report you exported etc? Thanks! |
@Chardonneaur Could you answer @michalkleiner questions? Otherwise we may close this one, as it's not fully clear what exactly you are asking for. |
@Chardonneaur simply attaching |
@sgiehl yes but for a normal human being, when clicking on the export button, while we are in the French UI, it should output translated columns without having to add a parameter within the url. That's the thing that I would like to stress. It is is a UX issue. |
So you are looking for an option in the export overlay, that can be checked to enable/disable the column translation. right? |
Well, it shouldn't even be an option. If I am using Matomo with a French User Interface, the export should show the columns translated in French and not in English. |
We could maybe also automatically add that to HMTL exports as well. But for XML and JSON exports this won't be supported. |
Hello,
When i export the data from Matomo, let's imagine that my interface is in French, then, the columns are not translated.
It would be nice to directly include the following parameter: &translateColumnNames=1
or to include it within the User Interface before we click on the export button.
The text was updated successfully, but these errors were encountered: