Closed SoSheolH closed 1 month ago
Can you provide the problematic track please? So that I can catch and debug the issue.
@TheQwertiest If this is the same bug I've fixed, it has to do with multi byte characters.
This commit should point you to the right direction. https://github.com/s0hv/foo_discord_rich/commit/2140d2c08907c878d812f892657232eab5294493
@s0hv could you please describe the problem that you were fixing with your commit? I've tried using various multibyte UTF8 chars (e.g. emoji) and it worked fine for me (discord didn't reject it, that is)
@TheQwertiest I might've misremembered the thing I fixed. It was related to the text being too short instead of too long. Discussion related to that can be found here but I'm currently unable to test if the character mentioned in the thread causes problems for long strings as well https://github.com/s0hv/foo_discord_rich/discussions/6#discussioncomment-4947883
Thanks! This actually reproduced the issue for me - seems that emoji handling is different from kanji...
@SoSheolH Reading your description more carefully, it seems that the problem is not with the original version of foo_discord_rich (this repo), but with s0hv's fork (perhaps in image upload implementation?).
Thus I'm closing this issue as invalid, since there's nothing to be done.
Have an album where metadata fields include both the original Mandarin and English versions in brackets, and despite enabling UTF-8 in Windows, the plugin refuses to update my status and spits out the following in the console: