Thanks, Legal Department
Another reason why I have 0 respect for anyone working in legal departments for businesses. They are unnecessary and make things worse to justify their existence.
NotKyloRen@lemmy.zip 3 weeks ago
The answer:
The device local name string is specified to be encoded in UTF-8. However, 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.
Thanks, Legal Department, for sticking a ® in the descriptor and messing up the whole thing.
There is a special table inside the Bluetooth drivers of “Devices that report their names wrong (and the correct name to use)”. If the Bluetooth stack sees one of these devices, and it presents the wrong name, then the correct name is substituted.
That table currently has only one entry.
Thanks, Legal Department
Another reason why I have 0 respect for anyone working in legal departments for businesses. They are unnecessary and make things worse to justify their existence.
When I was doing bids for consulting work, our legal department earned its keep many times over.
vinnymac@lemmy.world 3 weeks ago
While I don’t know this is the case, I can say from experience that in large enterprise organizations compliance departments will and do actively prevent the release of features and even commits if they don’t comply.
While that’s not an excuse for challenging them, I could definitely see a stressed out mid level just trying to make there manager happy and move on with life.
NotKyloRen@lemmy.zip 3 weeks ago
Good explanation. Thank you.