How do I make Windows 7 display SSID Unicode characters correctly in the Network panel?
up vote
-1
down vote
favorite
On Windows 7 Unicode characters are displayed correctly everywhere except on the Wifi settings and network options panel. More specifically it's the SSID of my home network that has an "é" (French acute accent on e) character in it that is replaced by jumbled characters (not the usual empty rectangles).
Other operating systems (android, OS X, even Linux) don't have this problem with my Wifi so I am 95% it has something to do with Windows.
Curiously enough I haven't been able to find a solution to this ultra-specific problem online so I now turn to you guys!
It's not that big a problem at all but for some reason it's driving me batty and I'm curious as to what is causing the issue.
kind regards
windows-7 networking unicode
add a comment |
up vote
-1
down vote
favorite
On Windows 7 Unicode characters are displayed correctly everywhere except on the Wifi settings and network options panel. More specifically it's the SSID of my home network that has an "é" (French acute accent on e) character in it that is replaced by jumbled characters (not the usual empty rectangles).
Other operating systems (android, OS X, even Linux) don't have this problem with my Wifi so I am 95% it has something to do with Windows.
Curiously enough I haven't been able to find a solution to this ultra-specific problem online so I now turn to you guys!
It's not that big a problem at all but for some reason it's driving me batty and I'm curious as to what is causing the issue.
kind regards
windows-7 networking unicode
Are you sure this is Unicode? It can also be extended ASCII, and the use of different codepages will result in different characters to be shown. Actually, I think this issue would not appear on Unicode at all.
– Tobias Knauss
Dec 30 '15 at 8:15
«even Linux» — funny sentence, with regard to a «toolbox-OS». I do know what the problem though: the systems you mentioned, GNU/Linux, Android which is Linux based, and OS X which is a unix — they use UTF8. Windows is the single OS which uses deprecated UTF16 by default. So, encoding mismatch is what breaks it. I don't know if there's a way to fix that (except of using aside app) though.
– Hi-Angel
Jan 13 '16 at 16:44
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
On Windows 7 Unicode characters are displayed correctly everywhere except on the Wifi settings and network options panel. More specifically it's the SSID of my home network that has an "é" (French acute accent on e) character in it that is replaced by jumbled characters (not the usual empty rectangles).
Other operating systems (android, OS X, even Linux) don't have this problem with my Wifi so I am 95% it has something to do with Windows.
Curiously enough I haven't been able to find a solution to this ultra-specific problem online so I now turn to you guys!
It's not that big a problem at all but for some reason it's driving me batty and I'm curious as to what is causing the issue.
kind regards
windows-7 networking unicode
On Windows 7 Unicode characters are displayed correctly everywhere except on the Wifi settings and network options panel. More specifically it's the SSID of my home network that has an "é" (French acute accent on e) character in it that is replaced by jumbled characters (not the usual empty rectangles).
Other operating systems (android, OS X, even Linux) don't have this problem with my Wifi so I am 95% it has something to do with Windows.
Curiously enough I haven't been able to find a solution to this ultra-specific problem online so I now turn to you guys!
It's not that big a problem at all but for some reason it's driving me batty and I'm curious as to what is causing the issue.
kind regards
windows-7 networking unicode
windows-7 networking unicode
asked Dec 29 '15 at 22:43
Pajeet B.
21
21
Are you sure this is Unicode? It can also be extended ASCII, and the use of different codepages will result in different characters to be shown. Actually, I think this issue would not appear on Unicode at all.
– Tobias Knauss
Dec 30 '15 at 8:15
«even Linux» — funny sentence, with regard to a «toolbox-OS». I do know what the problem though: the systems you mentioned, GNU/Linux, Android which is Linux based, and OS X which is a unix — they use UTF8. Windows is the single OS which uses deprecated UTF16 by default. So, encoding mismatch is what breaks it. I don't know if there's a way to fix that (except of using aside app) though.
– Hi-Angel
Jan 13 '16 at 16:44
add a comment |
Are you sure this is Unicode? It can also be extended ASCII, and the use of different codepages will result in different characters to be shown. Actually, I think this issue would not appear on Unicode at all.
– Tobias Knauss
Dec 30 '15 at 8:15
«even Linux» — funny sentence, with regard to a «toolbox-OS». I do know what the problem though: the systems you mentioned, GNU/Linux, Android which is Linux based, and OS X which is a unix — they use UTF8. Windows is the single OS which uses deprecated UTF16 by default. So, encoding mismatch is what breaks it. I don't know if there's a way to fix that (except of using aside app) though.
– Hi-Angel
Jan 13 '16 at 16:44
Are you sure this is Unicode? It can also be extended ASCII, and the use of different codepages will result in different characters to be shown. Actually, I think this issue would not appear on Unicode at all.
– Tobias Knauss
Dec 30 '15 at 8:15
Are you sure this is Unicode? It can also be extended ASCII, and the use of different codepages will result in different characters to be shown. Actually, I think this issue would not appear on Unicode at all.
– Tobias Knauss
Dec 30 '15 at 8:15
«even Linux» — funny sentence, with regard to a «toolbox-OS». I do know what the problem though: the systems you mentioned, GNU/Linux, Android which is Linux based, and OS X which is a unix — they use UTF8. Windows is the single OS which uses deprecated UTF16 by default. So, encoding mismatch is what breaks it. I don't know if there's a way to fix that (except of using aside app) though.
– Hi-Angel
Jan 13 '16 at 16:44
«even Linux» — funny sentence, with regard to a «toolbox-OS». I do know what the problem though: the systems you mentioned, GNU/Linux, Android which is Linux based, and OS X which is a unix — they use UTF8. Windows is the single OS which uses deprecated UTF16 by default. So, encoding mismatch is what breaks it. I don't know if there's a way to fix that (except of using aside app) though.
– Hi-Angel
Jan 13 '16 at 16:44
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Windows 7 cannot display unicode ssid's. Last time I checked you would have change source code.
New contributor
@Mureinik "It cannot be done" is a valid answer :)
– bertieb
Nov 15 at 15:13
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Windows 7 cannot display unicode ssid's. Last time I checked you would have change source code.
New contributor
@Mureinik "It cannot be done" is a valid answer :)
– bertieb
Nov 15 at 15:13
add a comment |
up vote
0
down vote
Windows 7 cannot display unicode ssid's. Last time I checked you would have change source code.
New contributor
@Mureinik "It cannot be done" is a valid answer :)
– bertieb
Nov 15 at 15:13
add a comment |
up vote
0
down vote
up vote
0
down vote
Windows 7 cannot display unicode ssid's. Last time I checked you would have change source code.
New contributor
Windows 7 cannot display unicode ssid's. Last time I checked you would have change source code.
New contributor
New contributor
answered Nov 15 at 3:20
Shawn
1
1
New contributor
New contributor
@Mureinik "It cannot be done" is a valid answer :)
– bertieb
Nov 15 at 15:13
add a comment |
@Mureinik "It cannot be done" is a valid answer :)
– bertieb
Nov 15 at 15:13
@Mureinik "It cannot be done" is a valid answer :)
– bertieb
Nov 15 at 15:13
@Mureinik "It cannot be done" is a valid answer :)
– bertieb
Nov 15 at 15:13
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1019506%2fhow-do-i-make-windows-7-display-ssid-unicode-characters-correctly-in-the-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you sure this is Unicode? It can also be extended ASCII, and the use of different codepages will result in different characters to be shown. Actually, I think this issue would not appear on Unicode at all.
– Tobias Knauss
Dec 30 '15 at 8:15
«even Linux» — funny sentence, with regard to a «toolbox-OS». I do know what the problem though: the systems you mentioned, GNU/Linux, Android which is Linux based, and OS X which is a unix — they use UTF8. Windows is the single OS which uses deprecated UTF16 by default. So, encoding mismatch is what breaks it. I don't know if there's a way to fix that (except of using aside app) though.
– Hi-Angel
Jan 13 '16 at 16:44