User:Siebrand

{{#display_point:52.092397, 5.057801| service=googlemaps2| height=250| width=215}}

Babel user information nl-N Deze gebruiker heeft het Nederlands als moedertaal. en-3 This user has advanced knowledge of English. de-1 Dieser Benutzer beherrscht Deutsch auf grundlegendem Niveau. fr-1 Cet utilisateur dispose de connaissances de base en français. af-1 Hierdie gebruiker het basiese kennis van Afrikaans. la-1 Hic usor simplice Latinitate contribuere potest. This user helps translating MediaWiki. This user helps translating OpenStreetMap. This user helps translating OpenLayers. This user helps translating Okawix. This user helps translating MantisBT. This user helps translating FUDforum. This user helps translating StatusNet. This user helps translating NOCC. This user helps translating Mwlib.rl. This user helps translating Wikia. This user helps translating WikiReader. This user helps translating Shapado. This user helps translating iHRIS.

I am a staff member of translatewiki.net, and contracted by the Wikimedia Foundation to work on this project for one day a week from 1 October 2009 to 31 September 2010. I would highly appreciate other entities also sponsoring me for a number of hours a week to keep this project going. Please contact me for a proposal.

For MediaWiki we (Raymond and I) try to commit translated messages once every day, most of the time in the evening (CET). We do not have any other products (yet) that are running live in a very exposed environment. Translations for other supported products are commited less often - this can range from days apart to weeks or months apart.

Please do not request things from me directly, but use Support. This will ensure centralised processing of everything, also when I am not active here.

For my other main accounts, see the Dutch language Wikipedia, Wikimedia Commons and OmegaWiki. Please keep translatewiki.net related issues on translatewiki.net.

[modificar] Goals for MediaWiki localisation 2010

As stated in my posting An update on localisation in MediaWiki

1. core-mostused 99%: 170 or more (now: 166 - threshold 97%)
2. core 90%: 105 or more (now: 81 - threshold 77%)
3. wikimedia extensions 90%: 65 or more (now: 38 - threshold 60%)
4. extensions 65%: 50 or more (now: 39 - threshold 49%)

Threshold is the percentage of localisation for which the goal would be reached.

[modificar] Important stuff

1. easier commit and review mechanism (possibly transifex)
2. get many other open source projects in translatewiki.net and consolidate l10n efforts and translation communities (makes open source localisation work more efficiently and gives more challenges to translators)
   • openSUSE (follow-up on 2010-06-06)
   • wxWidgets (follow-up on 2010-06-06)
   • Creative Commons
   • DimDim
   • OpenID - have to look into this a little further about what we can do for them.
   • Pidgin
   • Webmin/Virtualmin/Usermin
   • PHP documentation - have to wait a bit until the KDE guys have had some experience.
   • ...

[modificar] Todo

• Target languages with previous activity, but not any more. Try to re-activate the translators for those languages. Need volunteers that will take this up in a structured way.
• Test gettext new style groups

Here is a list of issues and feature requests. This is not a road map nor does it contain any big visions, but concrete bugs and feature requests.

[modificar] Primarily for translatewiki.net

[modificar] Bugs

• P1 BUG: magic and special page aliases export broken for MediaWiki extensions
  • Spent the evening investigating this. export-magic.php takes hideously long because it loops through every extension available, and then every language available for that group - causing ~400 message loads for ~400 extensions... ~160,000 message loads per export! I think it would make more sense to do it the other way round, resulting in only 400 message loads and a very efficient process. RobertL 21:40, 12 July 2010 (UTC)
• P1 BUG: caching messages from mediawiki namespace is too slow (about two minutes per language) and the site is jammed if those need to be rebuilt
• P2 BUG: The variable checks for FUDforum fail. This should trigger variable not used, but does not.
• P2 bugzilla:21787: magic words localisation does not support 2 extensions with the same magic word. (in this case #default in ParserFunctions and CategoryTests - also cannot add StringFunctions because of duplicates). Needs a solution, one way or another. Just make one page per magic word, and put those in the MediaWiki namespace?
• P2 BUG: Alias translation fatal error if first special page alias translation is the same as an element in the fallback chain: Exception: Something missing from values: Array [1]
• P2 BUG: aliasvar is supported on the input side for MW extensions, but not properly exported (see Wikilog extension special page aliases).

[modificar] Features

• P1 (system setup) Run {tm-server,rakkauspipe} as a daemon (with init scripts) instead of in screen
• P1 FEATURE: branch support for MantisBT (1.2, master/1.3)
• P2 FEATURE: Add support for community instructions for a message group. Implement with editable page in the same namespace as the translations for the message group. Key name something like "translate-group-community-desc-[group-id". Add this information below a "hr", just as the URL for groups. Display a message with a link to the forementioned page at all times. Mind that group ids for translatable pages contain "|", so that needs to be handled.
• P3 FEATURE: need report on inactive languages. Report all language codes that have had fewer than 25 edits in the past 3 months (bot edits excluded - not that difficult addition to scripts/languagestats.php)
• P3 FEATURE: install some kind of nag feature that will randomly encourage users to validate their e-mail address
• P3 FEATURE: need report on previous contributors (100+ edits) that have not contributed in the past 3 months (commandline script probably, because this will be too heavy to load in a web page - also check if we can e-mail?)
• P3 FEATURE: allow url config word in mediawiki-defines.txt. First try to match a current group name and then use that URL, if not, use the value as a URL

[modificar] Other

• P1 Improve content of Help us and make translatable page.
• P2 Document all processes regarding supported products (setup, update, commit) in the README.txt files in SVN.
• P3 Update scripts for statistics, preferably into one main script with some parameters, and run stats under 'betawiki' instead of 'siebrand'

[modificar] Things potentially relevant for all users of Translate extension

[modificar] Bugs

• P1 BUG: exhaustive documentation. See Documentation plan.
• P1 BUG: Special:Translate/manage issues
  • bugzilla:21785: Breaks message index when keys are added. Needs to rebuild changed groups for consistency; otherwise leads to PHP Fatal error: Call to a member function getNamespace() on a non-object in /var/www/w/extensions/Translate/utils/TranslationHelpers.php on line 78

    SM: I think this may not be happening anymore. There is a translation editor with reduced functionality, but no more fatals.

  • import and fuzzy will never be done in 10 seconds, after which it times out. Have to perform it multiple times to fuzzy one message. Unacceptable.
• P1 BUG: caching for language stats incomplete:
  • updating/adding/removing an English message should invalidate all cached entries for the group (live message groups like MediaWiki:Betawiki-messages, adding a message to MantisBT and running createMessageIndex.php for example)
• P1 BUG: Special:ImportTranslations is too slow.
  • User should be able to get 1000+ translations imported in one go. Currently with 45-60 seconds processing time, only 25-30 translations are dealt with.
• P2 bugzilla:21788: equal message keys in different namespaces may lead to confusing results with fuzzy.php
• P2 BUG: timezone cutting is wrong for graphs when scale!=days. First item in graphs is too low.
• P2 BUG: when trying to save an empty page in the translation editor, a pop-up window appears with text that is not localised ("Creating new, empty pages is not allowed (emptypage)")
• P3 BUG: Automatic selection is broken in Special:ImportTranslations if wgEnableMWSuggest is not enabled. In addition it's broken in Chrome for file selection input
• P3 BUG: ajax editing does not work properly with Opera (details needed)

[modificar] Feature requests

• P1: Facility for reviewing translations
  • Also recent changes to translations?
• P2 FEATURE: allow easy branch support for all supported products
• P2 FEATURE: create Special:GroupStats with run-time stats for an extension group. I have a prototype, but I am unable to finish it. Just do not know how to get to the right data. Please ask me if you can make it work.
• P2 FEATURE: allow easy creation of arbitrary meta message groups out of a array of message group IDs.

This will need some restructuring, since message collection assumes all have the same namespace

• P2 FEATURE: tool to track changes in English messages with web processing to enable 'incompatible with lower branch' tagging
• P2 FEATURE: allow prefix on Special:LanguageStats to only show groups starting with IDs that start with the prefix.
• P2 FEATURE: multiple language edit in UI (hard from an architectural point of view)
• P2 FEATURE: user defined fallback languages (in software; feature request shot?)
• P2 FEATURE: the buttons in the translation editor need title/tooltip to let users know they have shortcuts.
• P2 FEATURE: allow more elaborate validation process with stages "untranslated", "fuzzy", "translated", and "proofread". Should also implement tagging rights on a per language basis, and allowing 'language managers' to distribute "proofread rights", so only experienced and trusted users will be able to mark "proofread" for particular languages. This will add some overhead to the proofreading process, but will also reduce duplicate proofreading. Should allow for mass tagging per 10/25/50 messages in review mode to make the reviewer's life easier.
• P2 bugzilla:21534: Add checker for balanced HTML
• P2 FEATURE: add checker for variables of type "%(varname)s" as used in Mwlib.rl
• P2 FEATURE: add checkers for variables of type "%s"/"%d" and "%#$s"/%#$d" as used in StatusNet
• P2 FEATURE: notifications for updated message groups (also on meta level)

• P3 FEATURE: currently labels in graphs are group IDs. Change that to group labels
• P3 bugzilla:18721: Add configuration variable for limiting the languages displayed on Special:Translate
• P3 FEATURE: Fill a message in all languages with all available non-fuzzied content from another message (should definitely use job queue, default edit message containing source, and use job queue). Add as fuzzy should be optional.
• P3 FEATURE: Allow Special:TranslationStats to show stats on a per namespace basis also, instead of per group(s)
• P3 FEATURE: view warnings in a language (over all groups for quick update of out of date translations)
• P3 FEATURE: ignore trailing whitespace on export (or ignore it on save - or both)
• P3 FEATURE: update Special:Translate view when using ajax translate
• P3 FEATURE: install some kind of 'remind me' functionality that allows users to activate a 'nag me' feature that will send them e-mail
• P3 FEATURE: allow click through to source code on a project basis if the information is available in the source files (example)
• P3 FEATURE: allow importance rating of messages to help translators decide what messages to translate first.
• P3 FEATURE: validate structure of message group definitions (=YAML files)

[modificar] Gettext Support

• P1 bugzilla:21768: Cannot export gettext plural. Plural rules should be added automatically from a database[2] kept in the extension if not already present.
• P1 BUG: If gettext "Plural-Forms" is added, as was done for StatusNet, "Exception: Plural not found, expecting 2" is thrown.
• P1 BUG: YAML configured gettext groups have keys but no message text

[modificar] Page translation

See also http://userbase.kde.org/User:Annew/Translate_Issues

• P2 BUG: marked pages cannot be moved or deleted

Implementation idea: Use the jobqueue for move/delete actions and add success/failure messages to the same or different log as in the P2 feature logging of translation actions

Moving is in testing state

• P2 BUG: it is possible to cause duplicate section ids and later on a database error by editing the section markers manually
• P3 BUG: The "outdated translations are shown like this" banner appears even when there are no outdated translation in that page
• P1 FEATURE: Fuzzied page translation message should be replaced by the source language part. We never realised this before, but it was seen in UserBase that page links can break on retags, etc. Page consistency must be preserved, and that can only happen if outdated parts are not in the aggregate.

Need to dicuss this one.

• P2 FEATURE: allow derivative name in page translation to be changed (KDE translators feature request)

[modificar] Related extensions and other code

• P2 BUG: LQT ondiscussionpage bug
• P2 FEATURE: pull more data out of cldr (time zone translations, country name translations)
• P2 FEATURE: CLDR should probably use cdb (Robert will work on this, he said)

[modificar] More information needed or uncertain issues

• P2: Tag untranslated with 'having suggestion' and allow selection of this on (meta) group level (see Drupal l10n feature). This gives translators the opportunity to make a flying start.

Where do these suggestions come from?

TM - from an offline job, jobqueue, or whatever.

• P2 FEATURE: add "\n" to the problematic checks for FreeCol. In MediaWiki a newline does not mean anything,^{(see discussion)} In FreeCol, or in any other project using GetText for reading localized resources generated from files in .po/.pot format, a newline does mean something and is exported as "\n". The number of "\n" in source should be equal to that in destination.

  Does not having this cause any problems?

  No it just upsets the formatting the developers intended.

  Note that a translation may need to use more newlines than in the source language (for example for usage help text of command-line tools used in *nix/Linux shells or even under Windows console, where line length is limited typically to 79 characters), so the number of newlines will not match on purpose.

  It is just important to make sure that resources edited in one language in translatewiki.net will preserve the intended newlines. However, translatewiki.net can control that the number of leading or trailing newlines are preserved, as well as the number of leading or trailing spaces (excluding other line-leading or line-trailing spaces in the middle of the resource). Some other translation projects, when viewing or comparing messages, are displaying leading/trailing whitespaces with light colored bullets or arrows in their GUI, and this is probably a good idea.

  The same could be done for tabs and form feeds and other controls (even if, when editing the messages, they are themselves converted to the "\t, \n, \f, \xa0" syntax for "easier" identification by the user modifying them).

[modificar] Links

Pages in my namespace: