On Fri, Mar 26, 2010 at 16:30, Roan Kattouw roan.kattouw@gmail.com wrote:
and the inserted strings? 2) How/where could a wiki customize the special character insert menu,
The entire toolbar can be customized using site JS. There are examples at http://usability.wikimedia.org/wiki/Toolbar_customization ; these currently don't mention how to add/modify special characters entries, I'll add examples for that as well.
Whatever they mention, i couldn't understand a word of it, and i do know some HTML and JS.
There are several buttons which are essential to me and which disappeared from the new default toolbar, such as nowiki, strikeout and some others. If i had a convenient way to add them, i wouldn't complain, but that [[Toolbar customization]] page is completely unreadable to anyone but the dedicated developers.
And the embed file (picture) button inserts
this: "[[Example.jpg]]", without any "File:" or "Image:"!
That's a bug, thanks for reporting it.
I reported this bug some time ago via "beta feedback". It seems completely trivial, but it's still not fixed. I rarely insert images, so i can live with it, but many other editors do and i have no idea how they live with it.
Not too early for live deployment?
Your list consists of a trivial bug (missing File: prefix), a feature (protecting Opera users from text corruption) and the disabling of an unrelated feature that's not slated to go live in April, so I wouldn't say it's too early.
I'm sorry, but it is too early to force this on editors. On the technical Village Pump in the Hebrew Wikipedia, for example, the attitude towards the beta ranges from indifferent to negative, and not because of RTL problems, but simply because for people who only read Wikipedia this is inessential and for editors it is rather harmful.
True, some people may have enabled the beta and stuck to it, but what about all those that didn't enable it at all or enabled it and returned to Monobook? Do you have any numbers about people who use the beta and actually edit Wikipedia and not just read it?
You should ask for more feedback from the community via sitenotice or watchlist notice before enabling it for everyone.