Views
From translatewiki.net
2009-06-25: Please translate the messages for the Wikimedia license change!
2009-06-20: Many new messages were added to products recently. Please check your untranslated messages. (Other news...)
|
| <slippymap lat="52.092397" lon="5.057801" z="8" w="215" h="250" layer="osmarender" marker="1" /> | ||||||||
|
I am a staff member of this project and project lead of the Language project
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 and Translating:Tasks. 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.
Contents |
[edit] Goals for MediaWiki localisation 2009
As stated in my posting An update on localisation in MediaWiki
- core-mostused 98%: 130 or more (now: 113 - threshold 93%)
- core 90%: 90 or more (now: 75 - threshold 75%)
- wikimedia extensions 90%: 50 or more (now: 30 - threshold 59%)
- extensions 65%: 30 or more (now: 30 - threshold 67%)
Threshold is the percentage of localisation for which the goal would be reached.
[edit] Tactical requirements
- get AJAX support in Special:Translate (no more tabs)
- hook translatewiki.net up to a Transifex server (easy commit and project/language lead final say)
- 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)
Done (although needs further integration into UI) get terminology and TM support (huge productivity and consistency gains - possibly hard feature, but OMG this would be so sweet)
[edit] Todo
- Reminders to translators with low percentages translated. At arn:.
[edit] Bugs
- P1 BUG: equal message keys in different namespaces may lead to confusing results [1]
- 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)
- meta group cache stats should be invalidated when edits made to member groups
- P2 BUG: 'undo' on a message shows latest revision content, not previous content
- P3 BUG: missing link in MediaWiki and extensions like [[Special:AbuseFilter/$3|filter $3]] is not considered problematic[2]
- P3 BUG: percentage in Special:LanguageStats have trailing 0 stripped (or not added), which disturbs the layout
- Done P2 BUG: Special:Magic export fails when local underlying page is not present. Gives HTML output in form.
[edit] Feature requests
- P1 FEATURE: inline editing of messages (using AJAX) (see how this is done in Pootle)
- P1 FEATURE: branch support for Mantis (1_1, 1_2)
- P2 FEATURE: branch support for MediaWiki extensions - basically for any file format supported.
- 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: tool to track changes in English messages with web processing to enable fuzzying and 'incompatible with lower branch' tagging
- P2 FEATURE: add "\n" to the problematic checks for FreeCol. In MediaWiki a newline does not mean anything, in FreeCol it does and is exported as "\n". Number of "\n" in source should be equal to that in destination.
- P2 FEATURE: Multiple message edit in UI (hard from an architectural point of view)
- P2 FEATURE: Multiple language edit in UI (hard from an architectural point of view)
- P2 FEATURE: user defined fallback languages
- P2 FEATURE: when messages contain !!FUZZY!!, add additional translation hint.
- P2 FEATURE: add standard support for localisation of Magic words in MediaWiki extensions
- P2 FEATURE: I wonder if we should pull more data out of cldr (time zone translations, country name translations)
- P2 FEATURE: Special page for reviewing recent changes to a language (like review in Special:Translate, duplicates removed)
- P3 FEATURE: Add links to mediawiki.org in special:translate. like this. (by Alnokta)
- P3 FEATURE: enable gettext file submission through web UI, based on user group rights
- P3 FEATURE: quotation consistency checking on language level (Niklas input: big chances for a lot of false positives)
- P3 FEATURE: ignore trailing whitespace on export (or ignore it on save - or both)
- Done P2 FEATURE: Make it possible to blacklist messages from sanity checks, as some just should not be reported/checked (example)
- Done P3 FEATURE: make it possible to ignore plural warnings on a language code basis in problematic checks.
- Done P2 FEATURE: if a fall back language has been set, new translations will be filled with the contents of the fallback language. This should preferably be made configurable at user level in Special:Preferences (history).
[edit] Links
- Special:TranslationChanges: changed in the last 24 hours
- Pages in my namespace: