Please Ma'am, this isn't the fault of this website. Here is a typical post from elsewhere which highlights what the problem actually is:

<quote>

Content-Type
Source: HTTP/1.0 (RFC1945)
The HTTP content type may be extended to give the character set. As an HTTP/1.0 header, this unfortunately breaks older browsers. As a META tag, it causes Netscape Navigator to load the appropriate charset before displaying the page. E.g.

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-2022-JP">

It is now recommended to always use this tag, even with the previously-default charset ISO-8859-1. Failure to do so may cause display problems where, for instance, the document uses UTF-8 punctuation characters but is displayed in ISO or ASCII charsets

</quote>

Which implies that if the "previously-default charset" is being used, older systems will probably display that webpage correctly whereas newer systems which use the new default (which I think may be UTF-8) will display incorrectly.

Even if you post your stories elsewhere they will may the same problem until the proper <META ...> tag is added to the webpage displaying the story.

Please please don't blame the volunteers here for something that isn't their fault!

All the best
VV