The mystery is solved when you look at the actual HTML that is generated...
So, the “<b></b>” portion of the tip is being sent in the output stream, but the web browser is simply rendering it as raw HTML—by bolding an empty space on the page.
So, of course the user does not see the “<b></b>” tags on the screen.
OK, so the tip string is being sent to the output stream, but Documents-R-Us wants to convert HTML special characters into a format that is rendered properly in their tips. So we want to send “<” in order for the user to see the actual <
character in the browser, and “>” to produce the >
character.
How would you accomplish this?