[Bugs] #2023 HIGH: non-UTF-8 SSIDs not rendered in Neighbourhood (was: non-ASCII SSIDs not rendered in Neighbourhood)

[Sugar Labs Bugs]

#2023: non-UTF-8 SSIDs not rendered in Neighbourhood
-----------------------+----------------------------------------------------
    Reporter:  cgaray  |          Owner:  tch                        
        Type:  defect  |         Status:  assigned                   
    Priority:  High    |      Milestone:  Unspecified by Release Team
   Component:  sugar   |        Version:  0.84.x                     
    Severity:  Major   |       Keywords:  sugar-love                 
Distribution:          |   Status_field:  Needinfo                   
-----------------------+----------------------------------------------------
Changes (by fran):

  * status_field:  Unconfirmed => Needinfo


Comment:

 It looks like the problem is the use of encodings other than UTF-8 (of
 which ASCII is a strict subset). Cgaray's SSID is named 'asunci\xf3n' -
 this is 'asunción' in Latin-1, but invalid UTF-8, hence the UnicodeError
 in the log above.

 This is more complicated than the purely cosmetic bug #2099 - it looks
 like NetworkManager is itself choking on the non-UTF-8 SSID, since D-Bus
 requires UTF-8 strings. (Cgaray, are you still able to connect to the
 network, even though the SSID doesn't render?)

 There's also no reliable way to consistently detect which encoding is in
 use, so while it's important that Sugar/NetworkManager be able to
 _connect_ to non-UTF-8 SSIDs, it's unlikely that SSIDs with other
 encodings will ever be rendered properly in the interface without
 compromising Unicode support.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/2023#comment:7>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system