Issues and features

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.

Primarily for translatewiki.net

Bugs

• P2 BUG: Update Translating:How to start
• 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]
• P3 BUG: Javascript performance issue in Special:LanguageStats.

Features

• P1 (system setup) Run rakkauspipe as a daemon (with init scripts) instead of in screen
• 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.
• P2 FEATURE: Badges (or some kind of honours) for experienced and active translators
• P3: Ditch Special:AdvancedTranslate and have the special features act as normal message groups.
• 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
• P3 FEATURE: install lucene search
• P3 FEATURE: OpenID logins

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'

Things potentially relevant for all users of Translate extension

• See also TODO markers in the source code.
• See /www/w/logs/warn.doxygen for issues with code documentation.

Bugs

• P1 BUG: exhaustive documentation. See Roadmap/Documentation.
• 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)
• P2 BUG: Self-suggestions from TM in review recent changes.
• P2 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 BUG: JavaFFS doesn't parse fuzzy tags from source files, leads to information loss when the files are modified outside the wiki.
• P2 BUG: fuzzy.php gives a database error if no input given
• P3 BUG: export.php needs much memory for executing external programs. Move the memory limit closer to the execution.
• P3 BUG bugzilla:31281 Check blacklist should be configurable in message group configuration

Feature requests

• P2 FEATURE: allow translation of messages in mediawiki namespace that belong to message groups
• P2 FEATURE: allow easy branch support for all supported products
• P2 FEATURE: allow easy creation of arbitrary meta message groups out of a array of message group IDs.
• 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
• P2 FEATURE: notifications for updated message groups (also on meta level)
• P2 FEATURE: allow translation pop-up for additional languages to make life easier for users working on multiple localisations (usually pairs like nl/nl-informal, de/de-formal, zh-hans/zh-hant, sr-ec/sr-el, etc.).

• P3 bugzilla:18721: Add configuration variable for limiting the languages displayed on Special:Translate
• 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: validate structure of message group definitions (=YAML files)
• P3 FEATURE: use text alignment to enhance translation memory.

Gettext Support

1. WBN: interactive plural help
   • detect if message uses plural
   • alert the user about it
   • provide previews of the translation with different numbers

Page translation

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

• 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: derivatives of translatable pages should have __ NOEDITSECTION __ because they cannot be edited anyway. Also makes them a bit cleaner.

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

MediaWiki i18n

• All reported MediaWiki i18n issues
• Check all action- messages for actual possible use cases; remove if not used
• Check all uses of 'colon-separator'. Many are expected to be invalid.
• Check all uses of 'comma-separator'. Some are expected to be invalid. Especially check for a text list that is not listified (a, b, c and d).

More information needed or uncertain issues

• P3 FEATURE: view warnings in a language - basically all fuzzy tagged (over all groups for quick update of out of date translations)