Re: [Phpwiki-talk] transform.php

[<ho...@sb...>]

Jeff,

my net connection is down and maybe will remain so for another week (aaarrggh). 
I cannot send emails from my regular address, so I can't post to phpwiki-talk. 
Could you please forward this email?

[turning transform.php into a bona fide parser]
> 1. It would help guarantee correctness of generated HTML.

I doubt that you will be able to ensure HTML4 compliance. As far as I have 
tested out, "correct" markup will produce correct HTML. Why deal with stuff 
like double-intended lists without a single list first? Wrong markup produces 
wrong HTML - simple enough.

> 2. It would make extensions to the markup such as Reini's
> <code></code> blocks cleaner to implement.

Block stuff could easily be fitted into the current transform.php with some 
minor modifications. I have already thought about that. (About block markup 
itself: I guess you know where I stand ;o)

> 3. I've starting thinking about how to colorize (or otherwise) mark
> the transformed text to highlight diffs.  It's not easy to fit a
> colorizing scheme into the current transform code

Hm, if you think of the one diff-mode where you have the two versions side by 
side, it should be fairly easy to implement. Using some variation of the 
current diff-mode might be hard to implement, I agree.

> all the ways I've thought of to do this would surely not
> receive the Arno seal of code simplicity.

:o) Well, I'd also argue that the diff stuff is not fundamental to wiki, and 
that the current diff is good enough for 95% of all cases. But I'm also 
interested to learn about the different ideas you had!

> To change topics slightly, a personal peeve I have with the current
> markup, is this thing about having to put entire paragraphs (& list items,
> etc...) on one line.

I think this is a frequent complaint. Maybe we should deal with this. Your 
simple solution (everything keeps current mode until a newline or another mode-
markup is encountered) seems straightforward and easy to implement. I'm not 
sure if it's a good idea, but maybe (if modifications are small) we could add 
this as option?

> (I don't see any reason why italicization and boldizization shouldn't be
> able to span these continuation lines as well.)

Because, "errors" are then contained to one line? The thing I really like about 
wiki markup is, that no matter what I (or others!!) do on line 3, line 4 will 
always be shown as I have meant it to be displayed. Furthermore, currently if 
there's only one '' in the line, italics won't even be opened. It needs an open 
and close tag to be recognized by the regexp.

/Arno