mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: NFO isn't parsed as UTF-8 / Special Characters not displayed correctly #4771
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Wortex17 on GitHub (Apr 7, 2023).
Originally assigned to: @Shadowghost on GitHub.
Please describe your bug
I have added some additional metadata via local NFOs (to augment fetcher data, I am not using the NFO saver)
In this case, I added japenese characters to the originaltitle.
These are displayed as question marks in the client.
Note that the japanese characters fetched from the provider e.g. IMDB are displayed fine - this is only an issue when overwritten via local NFOs
Sample:
Update:
I noticed that when editing the data inside jellyfin metadata editor it works fine. Exporting with NFO saver also works with (albeit, the files charset is OEM-US not UTF-8) but reimporting it again (even though its the same file it exported) will break it again.
Could be confirmable/reproducible via an unit test for export-import with japanese characters or emojis
Jellyfin Version
10.8.0
if other:
No response
Environment
Jellyfin logs
No response
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
Code of Conduct
@jellyfin-bot commented on GitHub (Aug 5, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@Wortex17 commented on GitHub (Aug 13, 2023):
Still happening
@helmutheinz commented on GitHub (Sep 24, 2023):
Confirm this bug with Jellyfin on fresh installed Debian Server (DEB-package install, no docker) and editing NFO Files containing german Umlauts (e.g. äöüß). Notepad++ was used as editor and shows encoding OEM-US.
@Wortex17 commented on GitHub (Nov 1, 2023):
I can see this was moved to "insufficient data", but no further information was requested - anything we can do to help?
@felix920506 commented on GitHub (Nov 1, 2023):
We are waiting for a volunteer to test this
@Wortex17 commented on GitHub (Nov 23, 2023):
I'm sorry if I misunderstand, but test what exactly? I don't see any PR to be tested etc. and while I' offer myself as volunteer, I don't know what data you might need.
Edit: Removed referenc to mising label doc in https://jellyfin.org/docs/general/contributing/issues/#issue-labels as this is not an issue label, but your internal process, my bad.
Still, currently this communicates as "there's nothing you can contribute" and I just wnat to make sure that this is true.
@Optimus1008 commented on GitHub (Feb 28, 2024):
I just switched to generating nfo files on my server and got the same problem... but since I'm german all umlaute (öäü) and the "Eszett" (ß) get also replaced by a question mark since the current encoding doesn't support these characters... which is a bummer as they appear many times in the German language...
@Shadowghost commented on GitHub (Feb 28, 2024):
I did check the server code when the issue was filed and the files should be opened in UTF-8 mode, so not sure what else can be done. I will take a look over the weekend again, maybe I missed something.
@sjorge commented on GitHub (Feb 28, 2024):
I can't reproduce this either, I have a lot of tvshow.nfo hint files for my anime e.g. mine for Acchi Kocchi is
I wonder if it is because whatever tool/editor write the file did not write it with utf-8 encoding.
@Shadowghost commented on GitHub (Feb 28, 2024):
Would be interesting if someone with bad files can check their encoding. If it is wrong, there isn't much we can do.
@Optimus1008 commented on GitHub (Feb 28, 2024):
just deleted all NFOs and let Jellyfin regenerate them... for now, it seems okay, but I'll check again at another time... already checked if, for some reason, any other service (tdarr, sonarr) may cause this, but with no luck... maybe it really was a one-time error... weird nonetheless...
@Wortex17 commented on GitHub (Mar 5, 2024):
While trying to reproduce the issue, I noticed that this was likely the cause of my original issue:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/9153
So it was Notepad++'s fault, as it looked like it saves it as utf8 but never actually does
I'll try to find time to verify the mentioned export+import route, because i didn't document if i had touched the exported nfo with npp in any way in between (I shouldn't have, but lets see)
@jellyfin-bot commented on GitHub (Jul 4, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (Jul 25, 2024):
This issue was closed due to inactivity.