Difference between revisions of "User:Siebrand"

From translatewiki.net
Jump to navigation Jump to search
(→‎Bugs: P2 BUG: not all changed messages recognised as changed with poimport.php (silently skipped) or giving "inconsistent request" from Special:Importtranslations)
Line 60: Line 60:
 
* P1 BUG: caching for language stats incomplete:
 
* 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)
 
** 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: not all changed messages recognised as changed with poimport.php (silently skipped) or giving "inconsistent request" from Special:Importtranslations. Example file in /home/siebrand/bug/it_out-statusnet.po, 3 messages with issues: [StatusNet:1e7e4d0e2e2185d196df893fffdbfdb3887772e1-Unknown language " s"./it|1]], [[StatusNet:A24dc3f56de91dea3b4cd8ecc3dbe904528d45b6-Search results for " 1$s" on 2/it|2]], [[StatusNet:1ec76e8bcb7156d5affd60a0cabd0e6a79b7e7fc-No such document " s"/it|3]].
 
* P2 BUG: import of gettext for out-statusnet appears to ignore codeMap for no <=> nb. New messages for 'nb' are imported into 'nb', while 'no' is expected.
 
* P2 BUG: import of gettext for out-statusnet appears to ignore codeMap for no <=> nb. New messages for 'nb' are imported into 'nb', while 'no' is expected.
 
* P2 BUG: import and fuzzy translations for an updated message in Special:Translate/manage for out-freecol leads to "Exception: Unhandled action fuzzy", and nothing being processed.
 
* P2 BUG: import and fuzzy translations for an updated message in Special:Translate/manage for out-freecol leads to "Exception: Unhandled action fuzzy", and nothing being processed.

Revision as of 22:50, 9 February 2010

Last 3 days (Top 7)

Loading map...

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 simplici lingua Latina conferre potest.
MediaWiki-2020-icon.svg This user helps translating MediaWiki.
Openstreetmap logo.svg This user helps translating OpenStreetMap.
Logo-OpenLayers.png This user helped translating OpenLayers.
Okawix logo.png This user helped translating okawix.
MantisBT logo square.png This user helps translating MantisBT.
Fudforum.png This user helps translating FUDforum.
StatusNet logo.png This user helped translating StatusNet.
Nocc.png This user helped translating NOCC.
Icon-PediaPress.png This user helped translating mwlib.rl.
Wikia Logo.png This user helped translating wikia.
Users by language

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.

Goals for MediaWiki localisation 2010

As stated in my posting An update on localisation in MediaWiki

  1. core-mostused 99%: 170 or more (now: 153 - threshold 89%)
  2. core 90%: 105 or more (now: 82 - threshold 74%)
  3. wikimedia extensions 90%: 65 or more (now: 32 - threshold 48%)
  4. extensions 65%: 50 or more (now: 40 - threshold 48%)

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

Tactical requirements

  1. get a dedicated server and get it hosted (got the server, need to install and migrate)
  2. easier commit and review mechanism (possibly transifex)
  3. 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)
    • Achievo
    • Aviary (license?)
    • CiviCRM
    • Creative Commons
    • DimDim
    • KDE
    • OAuth
    • OpenID
    • Pidgin
    • Webmin/Virtualmin/Usermin
    • openSUSE
    • wxWidgets
    • ...

Todo

  • Target languages with previous activity, but not anymore. Try to re-activate the translators for those languages. Need volunteers that will take this up in a structured way.

Bugs

  • P1 bugzilla:21768: Cannot export gettext plural. Plural rules should be added automatically from a database[] 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: 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
    • Imports ignored messages
    • 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.
      • I set the time to 30 seconds, which worked for importing FUDforum changes, but I guess it should be just as long as it needs. Didn't work for fuzzying and importing one message of FreeCol in one go.
  • 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: not all changed messages recognised as changed with poimport.php (silently skipped) or giving "inconsistent request" from Special:Importtranslations. Example file in /home/siebrand/bug/it_out-statusnet.po, 3 messages with issues: [StatusNet:1e7e4d0e2e2185d196df893fffdbfdb3887772e1-Unknown language " s"./it|1]], 2, 3.
  • P2 BUG: import of gettext for out-statusnet appears to ignore codeMap for no <=> nb. New messages for 'nb' are imported into 'nb', while 'no' is expected.
  • P2 BUG: import and fuzzy translations for an updated message in Special:Translate/manage for out-freecol leads to "Exception: Unhandled action fuzzy", and nothing being processed.
  • P2 BUG: aliasvar is supported on the input side for MW extensions, but not properly exported (see Wikilog extension special page aliases).
  • P2 BUG: notices thrown: PHP Notice: Undefined index: <key> when adding PageTranslation
  • P2 BUG: notices thrown: PHP Notice: Undefined variable: ret and 'edit conflict' reported when a page translation page contains uneven numbers of open and close "translate" tags.
  • P2 BUG: make translatable page empty, and try to mark the latest version for translation: PHP Fatal error: Class 'TPsection' not found in tag/TPParse.php on line 92
  • P2 bugzilla:21771: Undefined property: GettextFormatWriter::$owndata
  • P2 bugzilla:21786 in page translation, line breaks are not maintained. This is an issue translating the Potlatch help page.
  • P2 BUG: The plural checks for FUDforum fail. After translating the correct format, the check for variables is still triggered and report it is not being used.
  • 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 bugzilla:21788: equal message keys in different namespaces may lead to confusing results (in case of fuzzying for example)
  • P2 BUG: Alias translation fatal error: Exception: Something missing from values: Array [1]
  • P3 bugzilla:21789: Special:TranslationStats does not process page translation entries correctly {like group "page|translating:intro")
  • P3 bugzilla:21790: Special:AdvancedTranslate does not see "a_b" and "a b" (underscore difference) as a conflict. It should.
  • P3 BUG: ajax editing does not work properly with Opera (positioning, not closing)
  • P3 bugzilla:21769: Undefined index: HEADERS in /var/www/w/extensions/Translate/ffs/Gettext.php on line 98
  • P3 BUG: false positive on plural parameter in language which should ignore plural example

Feature requests

  • P1 FEATURE: start using YAML config method for MantisBT
  • P1 FEATURE: YAML config support for gettext products (StatusNet in particular)
  • P1 FEATURE: branch support for MantisBT (1_1, 1_2)
  • P2 FEATURE: update TMs run time
  • P2 FEATURE: Special:ImportTranslations is too slow. User should be able to get 1000+ translations imported in one go. Use job queue to queue the imports and process them later? Currently with 45-60 seconds processing time, only 25-30 translations are dealt with. That's way too slow.
  • P2 FEATURE: 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.
  • P2 FEATURE: OpenStreetMap checks for variables ("template inclusion style").
  • 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.
  • P2 FEATURE: allow customisation (or addition) to page translation groups. This way it is possible to add advice/direction/explanation of what this page is about, or used for. It may not be a regular page, for example.
  • P2 FEATURE: update page translation sections without fuzzying derivatives (for typo/grammar updates)
  • P2 FEATURE: allow derivative name in page translation to be changed (KDE translators feature request)
  • P2 FEATURE: tool to track changes in English messages with web processing to enable '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 language edit in UI (hard from an architectural point of view)
  • P2 FEATURE: user defined fallback languages (in software; feature request shot?)
  • 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)
  • P2 FEATURE: Special page for reviewing recent changes to a language (like review in Special:Translate, duplicates removed)
  • 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:15866: Translate's export to file for MediaWiki core should auto-rebuild the language file
  • P2 bugzilla:18000: Whitespace following fuzzy marks should be removed during fuzzy mark removal
  • P2 bugzilla:21534: Add checker for balanced HTML
  • 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: 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)
  • 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: 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: 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: update Special:Translate view when using ajax translate (will be heavy on the server, I think)
  • P3 FEATURE: redesign Special:Translate standard view to only show main product groups, and show details on sub pages (it's getting too big)
  • 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: install some kind of nag feature that will randomly encourage users to validate their e-mail address
  • Done Done P2 FEATURE: bring cursor to edit screen after inserting suggestion from TM

Links

Pages in my namespace: