tree 976917305b2efae7dc262bb5674988a48cb73fd9
parent da21ed1b92e56b7927c9d40c97ae6300f91518f9
author Quang Anh Luong <qal@google.com> 1686110657 +0000
committer Android (Google) Code Review <android-gerrit@google.com> 1686110657 +0000

Revert "Prioritize alternate charset when de-translating SSIDs"

Revert submission 23579364

Reason for revert: It seems more likely that actual UTF-8 SSIDs will be misinterpreted as GBK, than GBK being misinterpreted as UTF-8. This is because GBK (and the other common extended ASCII charsets like EUC-KR) has valid characters mapped to nearly every 2-byte sequence, which means any UTF-8 string with an even number of bytes has a high likelyhood of being interpreted as GBK.

The use of the "is UTF-8" bit is also not guaranteed (and seems to be uncommon), so the lack of it is not a good indication that the SSID is not UTF-8. Thus to be on the safe side, we should revert back to preferring UTF-8 over the alternate charset (which is also consistent with the OEM GBK solutions). 
 
Reverted changes: /q/submissionid:23579364

Change-Id: Idd0f3bd5a9cd9d6c0ebf577c885c46b35b3342d4