BBO Discussion Forums: Corrupt character in the alert string - BBO Discussion Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Corrupt character in the alert string

#1 User is offline   sekica 

  • Pip
  • Group: Members
  • Posts: 6
  • Joined: 2014-August-29

Posted 2021-June-08, 03:00

When I click on the 3H bid on this hand


I get some corrupt characters at the beginning of the string.

The string should be "It's ogust ...", but the single quote is replaced with something else.

I noticed this on some other alerts too, it only started happening lately.

Thank you for looking into it.

#2 User is offline   mycroft 

  • Secretary Bird
  • PipPipPipPipPipPipPipPip
  • Group: Advanced Members
  • Posts: 6,129
  • Joined: 2003-July-12
  • Gender:Male
  • Location:Calgary, Canada

Posted 2021-June-08, 08:50

The string actually says "It's ogust...", not "it is ogust..."

You've been caught by "typecode bug", possibly (especially if the bidder is using BBOAlert (and editing in Word-equivalent) or cut-and-paste from Werd) triggered by "Microsoft smart quotes".

The apostrophe is converted to some odd bytecode which, when resolved in your browser's font and BBO's codepage, becomes resolvable as some other odd characters.

This is a very common problem, and not local to BBO - and not completely resolvable. Best hope is that BBO uses Unicode, and people who cut-and-paste to do their Alerts do likewise. The chance that their system isn't set up to do that is very high, and the chance they don't even know what they're doing ("it looks right to me"), given that this is a *very ugly* and *very technical* problem, is also very high.
When I go to sea, don't fear for me, Fear For The Storm -- Birdie and the Swansong (tSCoSI)

Share this topic:

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users