Tomasz Wegrzanowski wrote:
On Sat, Nov 30, 2002 at 12:23:08PM -0800, Brion VIBBER
wrote:
Tomasz Wegrzanowski wrote:
Please restore old meaning of <pre> which
suppressed interpretation
of wiki markup ! (for Polish Wikipedia at least, I don't care much
whether others will have broken markup)
I don't remember it ever working differently; I was not aware that the
behavior had been changed. Changing it again now would of course
probably break other code...
It always worked differently.
Well, it's worked the present way at least since January on the English
wiki as far as I know. I'll drop a note on the English and general lists
to warn about plans of changing it back.
If you don't want to mess with code too much, just
insert something like:
if ($language eq "pl")
{
$text =~ s/<pre>/<pre><nowiki>/g;
$text =~ s/<\/pre>/<\/nowiki><\/pre>/g;
}
I would much prefer that the markup work consistently the same
throughout the 'pedia in all languages.
Second, <pre> on wiki has always been meant for
listing code,
so it makes no sense at all to use wiki markup inside <pre>.
And third, <nowiki> is extremely low level markup. Introducing
more low level markup is not right direction.
Hmm, come to think of it, there's no good reason to use <pre> separately
-- putting a space in the first line does preformatting for wikitext.
In future, some higher level mechanism like <code
name="hello.cpp"></code>
may be implemented, to get rid of <pre> and <nowiki> and give some extras
like downloading examples listed in arcticle, searching for code etc.
But as for now let <pre> keep its old meaning.
Something like that might also be nice for citing texts.
And don't do any more changes to markup in future
without telling
people about that.
I'll just point out we had a test server running for *months* with the
new software and a copy of the Polish wiki precisely to check for things
that might need to be fixed or changed.
Human testing is always unreliable - people take most efford to check things
they suspect might be broken, like translation. They don't check things they
don't expect to break.
This is software -- expect everything to break. :)
-- brion vibber (brion @
pobox.com)