-
-
Notifications
You must be signed in to change notification settings - Fork 30
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 calling the html serializer pass an encoding #239
Conversation
@ale-rt thanks for creating this Pull Request and helping to improve Plone! TL;DR: Finish pushing changes, pass all other checks, then paste a comment:
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically. Happy hacking! |
@jenkins-plone-org please run jobs |
@@ -120,7 +121,9 @@ def parseTree(self, result): | |||
return None | |||
|
|||
try: | |||
return getHTMLSerializer(result, pretty_print=False) | |||
return getHTMLSerializer( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's beyond the scope of this fix, but I was doing a transform yesterday and changed getHTMLSerializer
from repoze.xmliter
with lxml.etree.HTMLParser
. Should we actually move to that one?
repoze.itertools
does not look much taken care of 😓
And actually it is just a tiny wrapper to lxml
...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks a nice idea to get rid of a dependency.
I created #240. I added the milestone 6.1 there, I would avoid doing that change for Plone 6.0 right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I could not reproduce problems in a client project, so it probably depends on how exactly you use plone.app.theming. Anyway, with your code I see no problems either, so LGTM. I have released |
Ah, thank you! I encountered encoding problems here with the package |
You see this currently on https://classic.demo.plone.org/de/folder_contents in the german toolbar: @mauritsvanrees maybe we can get a 6.0.11.1 release with this update here? |
I am surprised that this is only a problem in folder contents, and not on view. |
6.0.11.1 is available on dist.plone.org: |
Fixes #238
Without passing the encoding the test fails with: