They wanted the mouse to have a name like "Microsoft® Wireless Notebook Presenter Mouse 8000" but they accidentally used the wrong encoding and the name was invalid. Because they already made thousands of devices without properly testing them, the "obvious" solution was to patch the Bluetooth stack on every single computer in the world to fix this issue. It's the only Bluetooth device released in computer history that requires this.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago (3 children)

I bet that same workaround is probably implemented in Linux as well.

  • source
  • hideshow 3 child comments
  • [–] 16 points 1 year ago (2 children)

    Linux would probably handle it gracefully.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 19 points 1 year ago (1 child)

    Wouldn't surprise me if it doesn't check the UTF-8 validity at all and just lets the apps get broken UTF-8 where most of the time nothing horrible happens. That or they just strip invalid characters.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 1 year ago

    Yeah, this seems to be a display name, not some technical identifier. Microsoft cares about displaying it correctly, because it's their product, but I doubt anyone else does...

  • source
  • parent