Problem: Rendering of this page would not if extended characters beyond FoxPro's active CodePage are present in the Markdown text. This includes Emojii or different character set languages.

Solution: Turn off default UTF-8 encoding for the threads page and explicitly encode each of the text elements on the page. The Markdown block is internally encoded by the .NET Markdown parser and the a new switch to return UTF-8 encoded HTML from the parser from .NET:

<%= (MarkdownParser.Parse(lcMarkdown,.t.) %>

The key is not using the default UTF-8 encoding.

Note: We're still limited in FoxPro to what FoxPro can store inside of a Table for a given character set. Emoji work because they are encoded in output, but things like Chinese characters are simply not available in the Western Codepage so can't be stored 😦.

This is a test message with emojii and extended characters.

Emojii:

😃 😄

Extended Chars:

// code with extended characters (within the FoxPro Western Code)
var feets = "Kalte Füsse Test Messagë";