-
Notifications
You must be signed in to change notification settings - Fork 41
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
[Bug]: Files displays broken encoding when ⚰ is added to Markdown file #766
Comments
I cannot reproduce that, but haven't tried the community docker image yet. Any chance you can share a copy of such a file here as an attachment for checking the file encoding directly? |
The file is fine, I thoroughly checked the encoding.
Only when I edit the file and the editor saves it, then the encoding gets messed up. I removed the symbol that triggers the bug, but still:
I restored the file.
By the way, the bug is not triggered by every character beyond U+00FF. With the € U+20AC it works fine. Same with ✄ U+2704. But with ⚰ U+26B0 it breaks.
|
Ah, you are using a different app then, let me move the issue |
Bug description
After upgrading nextcloud to 26.0.5, I noticed that some Markdown files are shown with broken encoding in the editor. They were fine in many nextcloud versions up to 23.0.12. I updated in steps to 26.0.5. I also updated to 27.0.2, but the bug persists.
All files are encoded in UTF-8.
I've tracked it down to: when I add a character ⚰ (U+26B0) it breaks.
With äöü in the file, it displays correctly.
With äöü⚰ in the file, it displays as äöü⚰
The files on the filesystem are fine. It's a problem with the nextcloud files editor.
I've used docker images nextcloud:23-fpm .. nextcloud:27-fpm
Steps to reproduce
test äöü
⚰
. Still looking finetest äöü ⚰
Expected behavior
The file show display correctly as it did in older nextcloud versions.
Installation method
Community Docker image
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
Other
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: