This entry is only for me to check what happens to HTML I type in, and how it's stored in MT's database. Here goes...
entities followed by the actual symbol:
right angle bracket; > >
left angle bracket; < <
ampersand; & &
angle brackets; ><>< ><><
writing an entity by encoding the ampersand; > & < should be the code to display < & >
basic tags; strong text
paragraphs, with <p> tags;
This is a sentence of text. The sentence is a building block of the paragraph. This is a sentence of text. The sentence is a building block of the paragraph.
this text is formatted using the <pre> tag. It also contains html
this text is formatted using the <code> tag. It also contains html
this text is formatted using the <code> tag. It also contains html. Finally it has a lang="html" attribute.
this text is formatted using the <blockquote> tag. It also contains html, and a cite url attribute
now to get really funky:
Japanese, straight text;
Romanji 日本語 カタカナ
日本語 fat letters Japanese romanji
Japanese wrapped in a <p> tag with lang="ja";
Romanji 日本語 カタカナ
日本語 fat letters Japanese romanji
I'll publish with "convert line breaks" and see what happens. Read on for the results...
This seems a lot better than the Geeklog system of converting all code to entities, entities' ampersands to ampersand entities, marking apostrophies and line breaks as \' and \r, and using a code tag for block level html that you want to display as code. Much better!
When I want to display HTML I just have to entity all the angle brackets in tags, and entity the ampersands when I want to display entity codes. Just like usual. The result is also much more portable - stripping Geeklog's cruft out of my old articles has taken ages!