. . .
So, is there anything the Admins can do about it?
. . . )
Sort of. Every HTML document should include a declaration about what character set is intended to be used to render the text. LotusTalk is using ISO-8859-1, also known as Latin1 because it’s intended to render Latin letters and Western European languages (and not much else). So the hex code for the checkered flag cited in your original example isn’t in that character set; LotusTalk sent it as plain text and your browser rendered it as symbols, numbers and letters.
A better character set (and the preferred standard) is Unicode encoded as UTF-8. This character set and encoding generally has room for every possible character in every language. For UTF-8 web pages to render correctly, the HTML document has to be encoded
- “saved” might be a more familiar term - in UTF-8. Since LotusTalk lets users submit text for display through an editor presented from within the page, the Admin would have to ensure that
text was being correctly encoded in UTF-8 also.
Once the web page is encoded in UTF-8 and that fact is declared in the HTML, it is up to your browser to render the text properly. A few browsers do this reasonably well (IE, Firefox) but many don’t. The LotusTalk admin can’t control what browser you use or how well it renders the specified character set. So it takes everyone’s cooperation to get things rendered as intended.
- you should change the site character set/encoding to Unicode/UTF-8.
- you should use a browser that can display the entire Unicode/UTF-8 character set correctly.