Skip to content
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 my runtime environment is a Chinese encoding environment, the list of error messages returned is garbled #456

Open
GodMeowIceSun opened this issue May 31, 2024 · 4 comments

Comments

@GodMeowIceSun
Copy link

input

image

critical code

image

result

image

individual opinion

There is a problem with different character sets, so I think the output content of the default character set should be provided.

GodMeowIceSun added a commit to GodMeowIceSun/antisamy that referenced this issue May 31, 2024
@GodMeowIceSun
Copy link
Author

This issue occurs when I use dependencies in Maven, but it no longer exists after I compile locally

@GodMeowIceSun
Copy link
Author

No, it's not that there's no problem with local compilation, but rather that getErrorMessages has been called multiple times

GodMeowIceSun added a commit to GodMeowIceSun/antisamy that referenced this issue May 31, 2024
@GodMeowIceSun
Copy link
Author

After applying changes and compiling locally, There's no garbled code left.

result

image

@davewichers
Copy link
Collaborator

davewichers commented Nov 19, 2024

Per @kwwall - I suppose the correct thing to do to address this is for someone to correct all the AntiSamy properties files and XML files as per the Oracle JDK 9 document that @GodMeowIceSun referenced, and use UTF-8 instead of ISO-8859-1. (And if that doesn't work, use a system property like I suggested earlier in the thread for: #457

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants