The only normal characters that should change anything are:

dash, star, underscore, colon, tilde, pipe

Indention in the source is rendered

Code and other advanced things are not handled here

also, if you put more than two newlines in a row in the source, add a <br>

2001/12/08 12:32 US/Pacific (via web):
What would each of these characters do for you?

For me:

I am not sure what you mean by indentation of the source is rendered. I rather like using blank lines between paragraphs. Even indented paragraphs should have blank lines between them for legibility purposes.

(...a bit later...)

OK, I think I found a use for the tilde. The escape character. So typing something like ~StructuredTextThatIsSimpleAndWorks will result in StructuredTextThatIsSimpleAndWorks, instead of the hyperlink. Likewise, ~~ will display just ~, while things like '~ will display the single quote. This lets you "inline" a Python reference without having to worry about improper quoting. Think of it as being similar to C's or Python's \ character.

Samuel A. Falvo II

2001/12/08 12:46 US/Pacific (via web):
dashes: list items only, I understand the point about building headers with it, but I think list items is enough for this

star: this should be only for italics and bolds, no list items, nothing else

underscore: underline

colon: maybe this should be kept off the list. i was thinking of urls here

tilde: i figure its another character a very rarely use why not use it for something, how about making this the italic character?

pipe: another one i rarely use (except in unix commands). probably for tables?

by indention I mean they way indenting two spaces makes the line before a header, indention 4 spaces makes the line before a lower header,

but my version would simple use tables (or better style sheets) to space things out. I hate when something becomes a header when I didn't do anything to it.


2001/12/08 12:47 US/Pacific (via web):
no, i think backslash is better for escapeing, seems more universal than tilde

*(OK, backslash it is then. I like that idea as well. -- Samuel A. Falvo II)*

2001/12/08 12:51 US/Pacific (via web):
OK, I see what you're getting at. I agree with everything here. Colons can be used as markup for URLs? as long as the URL can be unambiguously identified. For example, is a pretty unique use of a colon in almost any context, as it always fits the pattern of .*:.*@.* . Likewise for more "normal" URLs? as well: :// is pretty rare to find in anything except a URL. :)