Last modified: 2014-04-15 00:19:52 UTC
We would like to have VisualEditor enabled on some part of svwiktionary. Suggested namespace: User namespace. Rationale: We're doing a proof-reading project[1] where we'll need to do lots of style edits (mainly update italics and bold). The idea is to extract useful information from the dictionary/thesaurus "Ord för ord"[2] and create new entries and improve existing ones using the information. [1] https://sv.wiktionary.org/wiki/Wiktionary:Projekt/Ord_f%C3%B6r_ord [2] http://runeberg.org/ordforord/
Thank you for your interest in Visual Editor. [ Adding James Forrester and Trevor Pascal as CC to get feedback on this matter. ]
https://www.mediawiki.org/wiki/VisualEditor#Timeline says "VisualEditor may be offered to users at non-Wikipedia projects, such as Commons or Wiktionary, after deployment to the Wikipedias has completed. No timeline has been set for this."
I was thinking that it might be possible to enable it on svwiktionary earlier, since I thought it would be low-risk to enable it for the user namespace only, not adding any new requirements. Anyway, I take that as a "no" in the short-term (this year).
I was just providing info about what's written in public; James and the VE development team has the final word and is free to change plans. :)
Sorry for the slow reply – we can do this if wanted. Just user namespace is entirely possible if that's what you want. Will do a patch now.
Change 97711 had a related patch set uploaded by Jforrester: Enable VisualEditor as opt-in on svwikitionary https://gerrit.wikimedia.org/r/97711
Change 97711 merged by jenkins-bot: Enable VisualEditor as opt-in on svwiktionary https://gerrit.wikimedia.org/r/97711
This is now live - you can opt in to test VisualEditor using the Beta Features link in your personal tools at the top of the page, or through the Preferences link in the "Beta Features" tab. If there are any issues, please shout!
I noticed that it's enabled in the main namespace too, but that doesn't make sense. We use lots of templates and very well-defined lists that just don't work well with VisualEditor. Can you please disable it for the main namespace? If possible, you could enable it for the project namespace instead (but not on pages with __NEWSECTIONLINK__).
(In reply to comment #9) > I noticed that it's enabled in the main namespace too, but that doesn't make > sense. We use lots of templates and very well-defined lists that just don't > work well with VisualEditor. > > Can you please disable it for the main namespace? Hmm, that's odd; it's configured for just the User namespace, per this bug – will investigate why it's working elsewhere too. > If possible, you could enable it for the project namespace instead (but not > on pages with __NEWSECTIONLINK__). Not sanely possible - we don't enable VisualEditor on pages which are signed, as that's what Flow is for, and too much of the project namespace is randomly signed (even with an expensive check for __NEWSECTIONLINK__), sorry. :-(
Change 98871 had a related patch set uploaded by Jforrester: Disable VisualEditor in content namespaces on svwiktionary https://gerrit.wikimedia.org/r/98871
Change 98871 merged by jenkins-bot: Disable VisualEditor in content namespaces on svwiktionary https://gerrit.wikimedia.org/r/98871
This should now be fixed; sorry for the mis-configuration.
