Page MenuHomePhabricator

Re-enable Special:AdvancedTranslate on translatewiki.net
Open, Stalled, Needs TriagePublic

Description

Please Enable Special:AdvancedTranslate on translatewiki so we can translate namespaces and special pages aliases and magic words for new languages and newly deployed extensions such as Flow.

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Krenair changed the edit policy from "All Users" to "Custom Policy".Aug 16 2015, 7:31 PM
Krenair removed subscribers: Jdforrester-WMF, Krenair.
Krenair changed the edit policy from "Custom Policy" to "All Users".EditedAug 16 2015, 7:50 PM

That was to try to prevent you from adding me to subscribers again. If you do not stop it, I will ask a Phabricator admin to disable your account altogether.

Krenair removed a subscriber: Krenair.Aug 16 2015, 7:52 PM
Mjbmr added a subscriber: Krenair.Aug 16 2015, 7:52 PM

@Krenair for what? creating a ticket?

Reedy added a subscriber: Reedy.EditedAug 16 2015, 8:55 PM

Disabled in https://phabricator.wikimedia.org/rGTWN63c90e2932b562a6ffa7ccca5f74698359dacd4b as it was throwing exceptions

@siebrand or @Nikerabbit Any chance of you posting a stack trace?

Any chance of you posting a stack trace?

The blocker is T42706#1411172.

Krenair for what? creating a ticket?

Please don't add subscribers who have clearly stated that they do not want to be subscribed to a task.

Krenair removed a subscriber: Krenair.Aug 17 2015, 4:46 PM
Mjbmr added a comment.Aug 17 2015, 5:48 PM

@mmodell I didn't, they were unless automatically by comment.

Maybe there is a bug, as someone who removed themself from subscribers shouldn't be added back automatically by @mentions. Hmm...

Maybe there is a bug, as someone who removed themself from subscribers shouldn't be added back automatically by @mentions. Hmm...

Filed ages ago: T76993

MarcoAurelio added a subscriber: MarcoAurelio.

@Nikerabbit mentioned this at TNW support. It would be useful to have AdvancedTranslate back and working. It's easier to translate from there rather than having to upload patches to gerrit, something that not all users know how to do. Do you foresee if it'd be complicated? Regards.

Do you foresee if it'd be complicated?

Yes.

@siebrand @Nikerabbit I have created this initiative at Meta to somewhat try to replace AdvancedTranslate until the tool is avalaible again. After they're translated, I'll upload those to gerrit so they can be merged. Best regards.

Dalba added a subscriber: Dalba.Oct 21 2015, 4:45 AM
Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptNov 6 2015, 1:23 PM
Liuxinyu970226 renamed this task from Enable Special:AdvancedTranslate on translatewiki to Re-enable Special:AdvancedTranslate on translatewiki.Nov 6 2015, 1:24 PM

Clarified the title, as this special page was enabled on TWN, but removed in May 2015.

Nemo_bis renamed this task from Re-enable Special:AdvancedTranslate on translatewiki to Re-enable Special:AdvancedTranslate on translatewiki.net.Nov 6 2015, 2:29 PM

I want to change https://translatewiki.net/wiki/MediaWiki:Sp-translate-data-SpecialPageAliases/sa this page. Can someone tell me what is the procedure ?

revi added a subscriber: revi.Nov 19 2015, 2:41 PM
Varg added a comment.Nov 19 2015, 7:56 PM

Hi
I am admin in Gilaki wikipedia and translating in wikimedia to my language.

But I cant find whereI could translate namespaces. Ho I could tranlate namespaces?

I have confused here! Please help me.

But I cant find whereI could translate namespaces. Ho I could tranlate namespaces?

See:

If that page is unclear, please tell us why so that we can improve.

Robby added a subscriber: Robby.Dec 21 2015, 7:11 PM
Restricted Application removed a subscriber: Mjbmr. · View Herald TranscriptDec 21 2015, 7:11 PM
Varg added a comment.Dec 22 2015, 12:10 PM

I am so confused. :|
What should I do for translate namespaces? :(

@Varg: See T109235#1818384.
People can only help if clear and specific questions are asked. See http://catb.org/~esr/faqs/smart-questions.html#explicit

MarcoAurelio awarded a token.

Any updates for this? This would be a wonderful tool to have back. Thanks.

No work on this is currently scheduled or planned.

I do agree, it would be great to support namespace and magic word translations.

Can I suggest that some time and resources be allocated to re-enable this
if at all possible? Thanks.

Can I suggest that some time and resources be allocated to re-enable this
if at all possible?

Given T42706: Fatal error in Special:AdvancedTranslate for special pages aliases, if someone reviewed all extensions for invalid translations and submitted patches to fix them, then things would be easier.

@Nemo_bis: Reviewing all extensions is a massive work. Maybe a bot could fetch those incorrect data so we can fix it? What about re-enabling them at translatewiki.net for some users so they can test and debug?

I don't have interest bringing the old code back. It does not fit into our streamlined process. This part should be rewritten so that it integrates with Special:Translate and our import/export workflows with adequate automatic verification (since these things can break MediaWiki badly).

This plan would work in tandem with the plans of moving magic words and namespace aliases to JSON format and have sane fallback handling.

MediaWiki now supports editcontentmodel and JSON. Would that make this task
easier?

Reviewing all extensions is a massive work. Maybe a bot could fetch those incorrect data so we can fix it?

I don't know. Perhaps an interested person can test Special:AdvancedTranslate on their own test wiki to reproduce the errors and log their sources.

MediaWiki now supports editcontentmodel and JSON. Would that make this task easier?

Not much I would say. Just dropping translators a big JSON blob even with a JSON editor is not very friendly.

I think better would be to have one item per page, then no JSON is needed. Some syntax for adding multiple items is needed. The simplest ones (comma separator or newline separator) don't even need a customized editor. JsonFFS would be easy to amend to convert these to/from arrays.

Hardest part is ensuring proper format:

  • spaces vs. underscores
  • first letter case
  • the preferred form first
  • keeping old translations as aliases

First two could be normalized by MediaWiki core itself, latter two could be masked by only showing the first item, automatically keeping the rest when exporting.

And finally, ensuring that special page name translations are unique (but then there are exceptions), and that some but not all magic word translations are unique... I am not sure how that could be done within our side.

Anyway, just some thoughts.

This comment was removed by Liuxinyu970226.
Elitre added a subscriber: Elitre.Nov 30 2016, 4:48 PM

Change 385797 had a related patch set uploaded (by Zoranzoki21; owner: Zoranzoki21):
[translatewiki@master] Re-enable Special:AdvancedTranslate on translatewiki.net

https://gerrit.wikimedia.org/r/385797

Change 385797 abandoned by Zoranzoki21:
Re-enable Special:AdvancedTranslate on translatewiki.net

Reason:
No work

https://gerrit.wikimedia.org/r/385797

Liuxinyu970226 changed the task status from Open to Stalled.Oct 23 2017, 4:00 AM
Liuxinyu970226 triaged this task as Lowest priority.
Liuxinyu970226 added a subscriber: Zoranzoki21.

@Zoranzoki21 sadly it's not possible to simple attaching a patch at the moment, maybe waiting for 2030 to redo it?

Liuxinyu970226 raised the priority of this task from Lowest to Needs Triage.Oct 23 2017, 4:00 AM

@Nikerabbit Maybe dropping a big JSON blob is not very editor friendly, but the current system is not very user friendly either. In order to mitigate the possible issues, I suggest that we enable the JSON editor and let only some experienced users in translatewiki.net edit those files (via a new usergroup or an abusefilter maybe?). Would that work for now, until we can have integration with the Translate extension? FWIW, is anyone or any team (Global-Collaboration ?) working on this right now? If not, any plans? Thanks.

There is no "JSON editor". Some work will always be needed to have these even synced to and from in translatewiki.net, even without a special editor.

For your second question about who is working on this, the answer is nobody. Currently I am the only person whose responsibilities include supporting translatewiki.net and most of my time goes to on-going maintenance to keep things running.

For your second question about who is working on this, the answer is nobody. Currently I am the only person whose responsibilities include supporting translatewiki.net and most of my time goes to on-going maintenance to keep things running.

I am very upset by this fact. Wikimedia projects depend critically on the performance of TWN, and it seems to me that it is vital to have a "spare engineer" for support this (already only so that you can go on vacation). @Amire80 - Who needs to be asked why this position is not reserved?

There is no "JSON editor".

MediaWiki does support now JSON content model files. As far as I remember, it lints the file before saving it so some mistakes can be avoided. That's what I meant.

Reedy added a comment.Nov 17 2017, 5:55 PM

For your second question about who is working on this, the answer is nobody. Currently I am the only person whose responsibilities include supporting translatewiki.net and most of my time goes to on-going maintenance to keep things running.

I am very upset by this fact. Wikimedia projects depend critically on the performance of TWN, and it seems to me that it is vital to have a "spare engineer" for support this (already only so that you can go on vacation). @Amire80 - Who needs to be asked why this position is not reserved?

twn is a volunteer run project, it technically has nothing to do with the WMF. The WMF doesn't really dedicate any resources to keeping it running.

MediaWiki does support now JSON content model files. As far as I remember, it lints the file before saving it so some mistakes can be avoided. That's what I meant.

That is true, but it is not integrated with the functionality of Translate.

The WMF doesn't really dedicate any resources to keeping it running.

Cf. open questions at https://lists.wikimedia.org/pipermail/wikitech-l/2017-July/088418.html

Fito added a subscriber: Fito.Dec 31 2017, 8:10 PM

This makes the current UI confusing:

  1. Go to https://translatewiki.net/wiki/MediaWiki:Sp-translate-data-MagicWords/ce
  2. See "DO NOT EDIT THIS PAGE DIRECTLY! Use Special:AdvancedTranslate."
  3. Click "Special:AdvancedTranslate."
  4. Get "No such special page" instead and have no idea what to do.

(See https://phabricator.wikimedia.org/T196784#4269063 why I ended up there.)

There is no current UI. Those pages are not in use. These changes must currently be requested in Phabricator, translatewiki.net support page or directly as Gerrit patches.