Comment 10 for bug 210484

Alexander,

Why do you say that this is not a network-manager issue? essids are just raw values with no concept of encoding, so it doesn't make sense for (e.g.) wireless-tools to try to do a charset conversion on them. Instead, tools that expect UTF8 input (which is likely the case for network-manager, since GNOME libs are heavily UTF8-oriented) should take care to convert non-UTF8 bytes to some representable form (without assuming anything about the encoding).

I think the network-manager task should be reopened here...