On 01/11/2010 12:01 PM, Nino Novak wrote:
>> The Rich Editor was requested by a lot of people who are working on
>> the OOoWiki.  Switching it off will take away a useful tool for a lot
>> of pwople working on the Wiki.
> 
> And how many people do actually use it? 
> Could this be made transparent?

Obviously quite a few must be using the RE since the problem with the
diff is enough for you to notice. :-)

Transparent?  How do you mean... a list of specific users who have
enabled this extension?  Theoretically possible, but it would require an
SQL Query be done against the User table in the database.  Is it
necessary?  Is it a good idea to provide a list of users using the RE?
Not really for the same reason I'm not happy about digging out email
addresses of spammers.  We have an obligation to maintain a high level
of privacy and data protection for the users, and I'm not willing to
compromise that... not even in the slightly grey areas.

If the information is not available in the main MediaWiki interface (via
SpecialPages) or available with accepted extensions, then I consider it
"off limits".  In this case, even as an admin, you cannot see what
options a user has set on his or her profile.


> Do they know that they break the diff functionality by using RE?
> (For me, this is still a showstopper)

As I said before.. they "break" the diff on the first time a page is
edited with the RE.  The RE does a Tidy on the page contents (in many
cases, a much needed Tidy).  Once the Tidy is done the first time, the
diff is usable on subsequent edits.

That said, I've just raised this question in a couple of places with the
FCKEditor guys... maybe there is a setting, or some way of limiting the
Tidy on editing with the RE.  Maybe there is a better way of managing
this diff issue.

C.
-- 
Clayton Cornell       [email protected]
OpenOffice.org Documentation Project co-lead
Sun Microsystems, Hamburg, Germany

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to