Thank you very much! Now I must learn how to use
Once Stable Version went into development, I thought
it a better solution than Protect Section. I hope the
final version will prove as useful as I believe it
will. Proofread page is a good way to verify edits,
but en.WS does not have a large enough percentage of
our texts scanned to really depend on that for the
average edit. Currently we still use full protection
and must have admins fix interwiki links and any other
notes on left on the talk page.
--- ThomasV <thomasV1(a)gmx.de> wrote:
I am pleased to announce that bug 7957 is now fixed.
In fact, I did
not know of that bug before you sent your message to
the mailing list :-)
Tim recently gave me svn access, so I hope that in
the future I will
be able to provide more software enhancements for
Considering Protect Section, it was never enabled
because some people
at the foundation considered that it gives too much
power to admins.
However, I believe that using ProofreadPage makes it
I wrote ProtectSection in order to protect texts
against clever vandals
(or ignorant goodwilling contributors) who make
corrections that look
ok but are not. However, the best way to tell apart
vandalism is to have access to the scanned text.
Birgitte SB wrote:
Labled Section Transclution (at least en and he)
DjVu support for ProofreadPage (general)
DynamicPageList (at least en and de)
WikiTeX (general for sheet music)
Those are the main ones I am watching for. Also
Stable Versions but that should be a priority
of Wikisource. If Stable Version never happens,
might want revive Protect Section as substitute.
Wikisource-l mailing list
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around