-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Download to CSV shows a special Chinese characters #2922
Comments
Please provide a minimal working example to reproduce this. Not just a line of code w/o any context. |
@ThiefMaster here is the application log:
And the
|
We need a minimal reproducible example demonstrating that the issue is in Werkzeug. We can't debug Apache Superset or this complicated example. This also looks like an encoding issue either during writing the file or opening in Excel, which is not handled by Werkzeug. |
+1, the current issue with Werkzeug refers to Superset-specific code and they won't be able to repro/fix. Though we may get lucky and they might point to some 3.x breaking change they knew might cause this kind of issue. In any case, it'd be good to get to the specifics of where the behavior is different from what you'd expect in Werkzeug itself. |
This is strange. To reproduce the issue, I did the following:
|
Right, though the "minimal reproducible example" would figure out exactly what in exact method/feature we're using from Werkzeug that has changed behavior over those versions, and remove all the related Superset-specific logic. Without knowing what cause the change of behavior, it's hard to even assert that the |
Download to CSV shows a special Chinese characters
This bug is related to Apache Superset. When I try to download a CSV query containing non-English characters, I get special Chinese characters as shown in the attached example: apache/superset#29506. Even setting the export configuration as follows:
This behavior didn't exist in Werkzeug
version 2.3.8
, but starting fromversion 3.x
we encountered this error.Environment:
The text was updated successfully, but these errors were encountered: