MW Other approaches

From Bjoern Hassler's website
Jump to: navigation, search
The "Mediawiki accessibility project"

General considerations - Mirroring - file size extension - email interface - W:Mediawiki OER export - [Edit]

1 Mediawiki[edit]

http://en.wikipedia.org/wiki/Wikipedia:Tools/Editing_tools

1.1 http://en.wikipedia.org/wiki/Wikipedia:Text_editor_support[edit]

1.1.1 Command line tools[edit]

QUote from http://en.wikipedia.org/wiki/Wikipedia:Text_editor_support:

  • There are also command line tools that allow you to download articles, edit them using your favorite text editor, and upload the edited articles back into the Wikipedia (or into any MediaWiki server). This bypasses the need for a web browser. These are (at least):
    • mvs, a Perl program available from CPAN. There's more information at [1]. ... issues with UTF8 ... Unfortunately, mvs uses the name of the local file as the title of the page for the wiki remote server. If you need title pages in UTF-8 for Russian, Japanese or Arabic for example, you won't be able to upload such files. It seems that Mediawiki::Client as well as Perl libraries are not enough advanced in the management of UTF-8 characters to be fully operational, even if your terminal and shell are correctly set for UTF-8. But see Debian bug reports.
    • http://en.wikipedia.org/wiki/Meta:pywikipedia is an extensive library and set of utilities for doing innumerable things with wikipedia. It can also do something as simple as editing wikipedia pages. ... good utf support ...

1.1.2 Wikipediafs[edit]

Quote from http://en.wikipedia.org/wiki/Wikipedia:Text_editor_support: Users of POSIX-compliant operating systems like Linux or Mac OS X also can use the virtual filesystem Wikipedia filesystem based on Python and FUSE. It allows the user to treat articles of any Mediawiki-based implementation like real files. This software (version 0.3) was not easy to install since it required the installation of several other software.

Emacs support for the WikipediaFS is provided by wikipediafs.el.

Wikipediafs. http://wikipediafs.sourceforge.net/ http://wikipediafs.sourceforge.net/README.txt

2 Eclipse plug-in[edit]

See MWEclipse.
The Wikipedia Editor plugin Eclipse Wikipedia Editor is available for Eclipse (cross-platform). With an automatically updating outline of the article. It has many features which are very helpful for editing wikipedia. It also downloads articles directly from Wikipedia and has highlighting.


3 Mediawiki svn[edit]

This page http://www.emacswiki.org/emacs/WikiDownload offers some interesting ways of getting hold of the emacs wiki:

4 Emacs and mediawiki[edit]

In particular http://en.wikipedia.org/wiki/Wikipedia-mode offers a download and instructions for adding syntax highlighting to mediawiki files.

5 How to set up specific editors for Wikipedia editing[edit]

http://en.wikipedia.org/wiki/Wikipedia:Text_editor_support


5.1 GNU Emacs[edit]

Quote from http://en.wikipedia.org/wiki/Wikipedia:Text_editor_support: There are a couple of Emacs major modes available for editing Wikipedia articles:

  • wikipedia-mode.el is a simple major mode that mostly provides syntax highlighting for wikipedia markup.
  • wikipedia.el is a much more advanced major mode which provides WYSIWYG editing of wikipedia articles. Note, however, that it is developed using the current CVS version of GNU Emacs, may not be compatible with older versions, and has been effectively discontinued because it's not being actively maintained. Also, the mode was in the alpha stage of development when it was orphaned, so use it at your own risk.

Quote from http://en.wikipedia.org/wiki/Wikipedia:Text_editor_support: Since Wikipedia articles use line breaks|don't use line breaks, you may want to install screen-lines.el, which redefines movement commands to work in terms of screen lines as opposed to text lines, or install longlines.el, which implements "word wrap" functionality for Emacs (longlines.el is now part of GNU Emacs). Installation instructions are longlines-mode|here.

wikipediafs.el can be used along with one of the aforementionned major modes, when using the virtual Wikipedia filesystem.


5.2 jEdit[edit]

For jEdit (Java-supporting OSes) there is a plugin available at http://www.djini.de/software/mwjed/ . Apart from providing syntax highlighting for wikipedia markup, it can communicate directly with the Wikipedia website using the HttpClient component from the Jakarta Project.

5.3 Kate / KWrite[edit]

For Kate (for GNU/Linux KDE desktop), rules for syntax highlighting are provided by the XML file de:Media:Wikimedia.xml. It recognizes HTML tags and entities, wiki control characters, links, section titles, tables and <nowiki> sections.

To install this template, copy it to ~/.kde/share/apps/katepart/syntax/ for per user settings or $(PREFIX)/share/apps/katepart/syntax/ for global settings. There's also an import tool : Settings → Configure Kate → Highlighting → Download.

5.4 SubEthaEdit[edit]

A syntax highlighting mode is available for SubEthaEdit (Mac OS X) as well. After downloading the mode bundle, drop it in /Library/Application Support/SubEthaEdit/Modes/ (system-wide) or ~/Library/Application Support/SubEthaEdit/Modes/ (user-specific). You may need to create the final two directories by hand. The mode will be automatically selected for files with a .wiki or .wikipedia extension.

5.5 TextMate[edit]

A "MediaWiki" bundle is available in the TextMate (cross-platform) bundle subversion repository. To learn how to load this bundle, see the TextMate manual page about installing more bundles. The bundle for now (8 August 2006) only does syntax highlighting, but the ability to fetch and post articles is coming soon.

5.6 NoteTab[edit]

A Clip Library plugin for the NoteTab (Windows) text editor contains some functions to automate Wiki markup.


6 Other wikis[edit]

http://blogs.law.harvard.edu/doc/2008/12/30/outlining-in-mediawiki/ has the following comments (among others):

Regarding http://wiki.developer.mindtouch.com/MindTouch_Deki

Look at MindTouch Deki (originally a MediaWiki fork), which has two useful characteristics here: (a) its API is completely separate from its’ frontend (the frontend is just an API client), so you could use any editor of your choice and a simple REST API; and (b) the markup language is XHTML, so you can use any editor of your choice and don’t have to worry about wikitext. You can also edit just one section (as defined in your outline by headings) at a time.

Plus, a built-in scripting language (DekiScript) lets you massage your data in any way you want. Some potential uses - include sections of a page from another page; templating; pulling data from other sources, processing and displaying - a.k.a. the Web 2.0 ‘mashup’.

Regarding http://ikiwiki.info/

Doc, you might want to check out Ikiwiki, which you might call “the wiki that gets along with your other software” or maybe “the lazy wiki that makes other software do most of the work”. Ikiwiki uses a revision control system as the back end. So any application with a hook to commit into the revision control system will update the wiki, too–auto-freaking-magically. The other k3wl thing about ikiwiki is that you can add any input format by writing a plugin — so you can have the wiki work from your outliner’s native format. So that means the critical path from where you are now to total outliner/wiki smoothness is (1) a revision control hook for your outliner and (2) an ikiwiki plugin to handle your outliner’s native format.

7 More[edit]

http://www.mediawiki.org/wiki/Talk:Alternative_parsers