You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The sethome not support áéíőúűáéóüö characters #1742
Are you saying that it takes accented/umlauted characters and turns them to underscores?
Does this show up as so in the user's data file?
Now, I'm not familiar with what language you're likely using, but I figure that in most languages, you can go without the accents/umlauts, however incorrect. With that being said, I also am not entirely sure how easy it would be to implement support for these characters, I believe the files would just need to be encoded in UTF8 if they're not.
Just my initial input to get some info out of you!
Replacing the diacritics with underscores is intentional; without this, the YAML would break when reloading the user's data. The only way to work around this is to not add the diacritics and just type the undecorated vowels.
Replacing the diacritics with underscores is intentional; without this, the YAML would break when reloading the user's data. The only way to work around this is to not add the diacritics and just type the undecorated vowels.
Hello!
After five (almost six) years we have talked about this on discord and you said:
It's likely possible to support accented characters now since we do save the contents of configs in UTF-8 - leave a comment on the original issue and we can revisit it
So here I am - hoping that it could be solved.
It would be so much better for the users we would be so happy.
Thanks.
Activity
DrewAMitchell commentedon Jan 2, 2018
Are you saying that it takes accented/umlauted characters and turns them to underscores?
Does this show up as so in the user's data file?
Now, I'm not familiar with what language you're likely using, but I figure that in most languages, you can go without the accents/umlauts, however incorrect. With that being said, I also am not entirely sure how easy it would be to implement support for these characters, I believe the files would just need to be encoded in UTF8 if they're not.
Just my initial input to get some info out of you!
mdcfe commentedon Jan 2, 2018
Replacing the diacritics with underscores is intentional; without this, the YAML would break when reloading the user's data. The only way to work around this is to not add the diacritics and just type the undecorated vowels.
mcnagynorbi commentedon Dec 6, 2023
Hello!
After five (almost six) years we have talked about this on discord and you said:
So here I am - hoping that it could be solved.
It would be so much better for the users we would be so happy.
Thanks.
mdcfe commentedon Dec 6, 2023
Reopening as a feature request, since we should now be safe to store home names as UTF-8
Allow unicode characters as userdata file is now written in UTF-8