-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
write_html fails with latest plotly.min.js version 2.17.1 #4019
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
Comments
Thanks @johannesloibl! This must be an artifact of the switch from @archmoj |
That said, I wonder if #4022 does this one better by fixing even more problems? |
Author of #4022 here, since HTML pages generated by plotly.py have
by default (see _html.py), for me it makes sense to support the full palette of Unicode by exporting files in utf-8 (as claimed). |
Thanks @rxxg - looking at this in more detail, seems like #4022 and #4021 each address part of the issue: #4021 handles the new part about the plotly.js change to including unicode in the bundle, while #4022 is about other unicode content in the plot. So we need both of these. And while it could be considered a breaking change that the plotly.js bundle is no longer pure ASCII, we never made that an explicit contract, it was an accidental requirement of the usage here. UTF-8 is more efficient and the generally accepted as the standard at this point so on second thought I'd prefer we fix these cases rather than enforce an ASCII-only bundle. |
Thanks folks! I've merged both the PRs and I'm just waiting on another fix related to webpack to release 5.12.1 ... hopefully this week. |
The latest plotly.min.js version 2.17.1 contains special characters which are not supported by the Windows cp1252 default codec.
E.g.
\u25c4
(https://www.fileformat.info/info/unicode/char/25c4/index.htm).Reproducible example (Win 10, 64bit, plotly 5.12):
This produces following error:
The text was updated successfully, but these errors were encountered: