""There is a lot of bad hardware out there," writes Chen, "and there are a lot of compatibility hacks to deal with it." There's hardware that spouts nonsense or does things that it says it absolutely won't (Chen cites the example of a USB device that drew more power than it promised it would.) Still, the vast majority can be dealt with behind the scenes with code that can repair or ignore corrupted values."
"The device local string is specified to be encoded in UTF-8. However, Chen explains, "the Microsoft Wireless Notebook Presenter Mouse 8000 reports its name as Microsoft⟪AE⟫ Wireless Notebook Presenter Mouse 8000, encoding the registered trademark symbol ® not as UTF-8 as required by the specification but in code page 1252." "What's even worse is that a bare ⟪AE⟫ is not a legal UTF-8 sequence, so the string wouldn't even show up as corrupted; it would get rejected as invalid.""
Windows Bluetooth stack contains a hardcoded reference to the Microsoft Wireless Notebook Presenter Mouse 8000 to work around a severe device bug. Many devices produce incorrect or nonstandard behavior, and compatibility hacks often repair or ignore corrupted values at the driver level. The Mouse 8000 reported its local name using a Windows-1252 encoded registered trademark symbol instead of UTF-8 as the specification requires. The bare ⟪AE⟫ byte sequence is not a legal UTF-8 sequence and would be rejected as invalid, so Windows implemented an extreme special-case to accept that device.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]