User talk:Kim Bruning

Voctrain
Omegawiki-based Vocabulary trainer. Uses a flashcard system to help the user learn vocabulary from any language to any language supported by Omegawiki. Created for University of Bamberg.

Licensed GPL 2.0 or later.

Contact kim at bruning dot xs4all dot nl for inquiries.

Minimal developer documentation for .php files
Your language.i18n.php file should contain a single array called $messages

...with each key being a language. English is considered default by most civilisations.

A list of accepted language codes can be found at (among others): http://svn.wikimedia.org/svnroot/mediawiki/branches/wikidata/languages/Names.php

You can also provide documentation under the fake language code "qqq"

For any of these per-language arrays, there are no limits to what you can use as values. For keys, at least the following limitations apply:
 * MUST NOT contain any special characters or spaces
 * MAY contain underscores, but MUST NOT have more than 2 underscores in a row.
 * Technically, unicode is permitted. Most people stick to just latin letters and numbers though
 * may contain a prefix (probably the name of your application) (this used to be a requirement. Currently betawiki is implementing namespaces, so possibly you can skip the prefix).
 * Prefix might not even be allowed to have a capital first letter (according to Nikerabbit)
 * key limitation (Translate specific): should start with lower case Latin character. (hence the prefix limitation above)

Here's a quick routine to convert an arbitrary text to a valid key that is still readable (this does not 100% ensure there will be no key collisions, but should be usable enough). YMMV:

If you'd like to have language fallbacks, you have to implement and maintain them yourself, Betawiki doesn't support them. (You could snarf the fallbacks off of mediawiki though).