Known Issues
"<" Character is not rendered: Because PWStyleHTMLField interprets all text entered as HTML, the "<" character, which signifies the beginning of a tag in HTML, is not rendered. Furthermore, any text entered after a "<" character and before a closing ">" character is not rendered. To enter the "<" character, you must escape it as described in the Usage section of the documentation.

Avoid pure blue text: PWStyleHTMLField uses the color &c0000FF for link text. If you format text with that color and also format it in bold and underline styles, bad things could happen.

Format text in a body font: To get the best results, use one of the fonts you specify for the body font as the main font in your styled text.

Don't type in link text: Typing in the middle of a link breaks the PWStyleHTMLField's internal reference to the URL. Typing at the end of a link such that it extends the link style does the same thing.

Linux issues: PWStyleHTMLField relies on RTFData for some of its functionality. Because of problems with RTFData in Linux implementations of Real Studio, some features do not work correctly when running in Linux. These include translating colors to HTML (some colors in the blue range work fine, others toward the red end of the spectrum do not), and displaying non-default paragraph alignments.

Cocoa issues: At the time of this writing, PWStyleHTMLField does not work in Real Studio's beta Cocoa releases. There are problems with TextArea class functionality that PWStyleHTMLField depends on which prevent it from working under Cocoa builds. (This is the state of matters as of the release of Real Studio 2011 R1.)

Problems handling multi-byte text: Because PWStyleHTMLField relies on RTF support in REALbasic/Real Studio, an RTF bug means that PWStyleHTMLField cannot properly handle multi-byte languages such as Chinese.