> 3. Publishing wiki sourcecode in wiki and make it
editable
just like
wikipedia articles.
I don't know if this works but we can try.
Source is fragile enough that I'd be very wary of this.
That, and I
really do want a better editor than Mozilla when
working
with code. ;)
> Probably the
> first step is publishing "language.php"s and probably
sysop
applies them.
The current format of those files (a bunch of arrays and a
class
definition in a PHP source file!) is horrible, arcane,
and
very very
fragile. (About half the updates I get submitted to me
ends
up with a
missing comma, an extra quotation mark, whatever, and
hence
syntax
error. And that includes the ones I make myself!)
What we need is a human-friendly interface for editing the
messages,
being able to compare all or selected language versions
of
each one
side-by-side. The ability to incrementally and safely
update 99% of this
stuff without waiting for a developer's
intervention will
be a big help
for newer language sections being established.
I totally agree with that. Then why don't we employ wiki to
improve the sourcecode? Also, I don't know if it will work.
Then why don't we try?