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
Always display IDN host names as Unicode characters
Actual behaviour
Sometimes IDN host names are displayed as punycode
Detailed description
In the above example, the host name (and instance name) should be displayed as "bawü.social", but it is displayed in punycode: "xn--baw-joa.social".
This is confusing for most unexperienced users.
There are several places, where the domain name is displayed as punycode, e.g. in big on the about page, but also at the left sidebar in the footer, as account name on the account page (e.g. https://bawü.social/@lfdi); in some situations the domain name is displayed correctly with unicode chars.
In some places Unicode domains are displayed correctly. With 4.0 the issue is more noticeable because on the "about" page the hostname is displayed large in punycode.
Examples
Specifications
Mastodon 4.0.2
The text was updated successfully, but these errors were encountered:
Steps to reproduce the problem
Expected behaviour
Always display IDN host names as Unicode characters
Actual behaviour
Sometimes IDN host names are displayed as punycode
Detailed description
In the above example, the host name (and instance name) should be displayed as "bawü.social", but it is displayed in punycode: "xn--baw-joa.social".
This is confusing for most unexperienced users.
There are several places, where the domain name is displayed as punycode, e.g. in big on the about page, but also at the left sidebar in the footer, as account name on the account page (e.g. https://bawü.social/@lfdi); in some situations the domain name is displayed correctly with unicode chars.
In some places Unicode domains are displayed correctly. With 4.0 the issue is more noticeable because on the "about" page the hostname is displayed large in punycode.
Examples
Specifications
Mastodon 4.0.2
The text was updated successfully, but these errors were encountered: