On Wed, 9 Jul 2003, Timwi wrote:
Thanks again for your input. Now that my Wikipedia
test server works
fine (yay!), I was able to test my own patch.
Which reminds me, did you get CVS working?
Note that if you pulled the tree anonymously, you have pull a fresh copy
as a developer and commit from the new tree. Cryptic commands at bottom of
http://sourceforge.net/cvs/?group_id=34373
PHP seems to have very different operator precedence
than both Perl and
C. (This is my first time doing PHP, does it show? :) ) It does not seem
to be possible to do this:
return $var == $value ? $one : $two . $three;
without parentheses.
?: probably should _never_ be used without parentheses, since it's such a
confusing sonuva.
There's only one final decision left that I need
someone to make: How do
we parse the following input?
''line 1
line 2''
There are three possibilities with my patch as it is now:
1) <em>line 1
<p>
line 2</em> (incorrect HTML)
That would be bad. ;)
2) ''line 1
<p>
line 2'' (shows author what's wrong)
This is current behavior.
3) line 1
<p>
line 2 (least confusing to readers, but author may
wonder why '' ... '' didn't
work)
I don't think I like this one.
Of course other things are possible, e.g.
4) <em>line 1</em>
<p>
<em>line 2</em>
but that requires slightly more work (especially for line 2).
I don't think things like '' should cross block-level boundaries like
paragraph breaks (though they probably should cross line breaks in source
text that are in the same block). It's easy to mysteriously plunge an
entire page into italics by mistake like that, and hard to track down the
problem. Localizing the effects localizes the trouble, and makes it
easier to take isolated segments and move them around within and between
pages without breaking formatting.
Another possible rendering is:
<p><em>line 1</em></p>
<p>line 2<em></em></p>
in which we treat '' as a toggle which is reset at the end of a block.
-- brion vibber (brion @
pobox.com)