Page MenuHomePhabricator

Trondtr (Trond Trosterud)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Thursday

  • Clear sailing ahead.

User Details

User Since
Nov 27 2015, 11:48 PM (437 w, 3 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Trondtr [ Global Accounts ]

Recent Activity

Dec 18 2015

Trondtr added a comment to T120837: Publish button does not become active when editing the translation.

After a meeting today with Runa and Niklas, it turned out that I had an old .js page under my user page area (having to do with author counting of WP pages). After deleting it, all pages tested so far work. I will return with more info, but at present it seems that my bug (the grau button not turning green for nb->nn) is solved.

Dec 18 2015, 1:47 PM · LE-CX7-Sprint 4, ContentTranslation-Release7, ContentTranslation, Essential-Work
Trondtr added a comment to T106415: Better announce the lack of Machine Translation.
Dec 18 2015, 1:46 PM · OKR-Work, Design, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

After a meeting today with Runa and Niklas, it turned out that I had an old .js page under my user page area (having to do with author counting of WP pages). After deleting it, all pages tested so far work. I will return with more info, but at present it seems that my bug (the grau button not turning green for nb->nn) is solved.

Dec 18 2015, 1:45 PM · Design, Essential-Work, ContentTranslation

Dec 14 2015

Trondtr added a comment to T106415: Better announce the lack of Machine Translation.

This is the list of Apertium language pairs. Pairs under "Trunk" and "Staging" should be useful. Whether the "Nursery" ones will be useful or not is in itself an interesting question, I would like to give it a go, but I also fear Wikpedia "language collectors" use this as a way to add better minority language content than they would have been able to do without it (and hence publish without any proofreading).

Dec 14 2015, 10:59 PM · OKR-Work, Design, ContentTranslation
Trondtr added a comment to T106415: Better announce the lack of Machine Translation.

This is a setup for Apertium, so we are restricted to Apertium language pair (and in general, I assume, to open source solutions). Statistical MT is in any case not that good for language production. Language pairs not in Apertium may be added, though. If an apertium pair is broken, the intermediate answer is to roll back the svn to the last working version. But since the source code is open, the best way is probably just to get a password, go in and participate in the work.

Dec 14 2015, 10:53 PM · OKR-Work, Design, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Comment to User:SThelen.Aqua:
I am glad to hear that you get the translation published by clicking twice on the green (gray?) button.
For the record: I have tried to press the gray button twice (many times), and the only solid correspondence I find is "gray button after first paragraph translated = gray button no matter how many times I press or how much or little I translate".
Here is my last try, checked a minute ago, button staying gray:
https://no.wikipedia.org/wiki/Limonesisk_kreol

Dec 14 2015, 12:41 PM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T120837: Publish button does not become active when editing the translation.

yes, sometimes (appr in 20% of the cases) I am able to publish ("green button"), and sometimes I am not. Unfortunately, I have not been able to spot any correlating factor (I have tried varying article type). But as long as I do not know what causes the problem it is also hard to look for it. I also have not got any feedback from others in this thread as to whether they are able to replicate my results, or whether nb-no works for them.

Dec 14 2015, 10:20 AM · LE-CX7-Sprint 4, ContentTranslation-Release7, ContentTranslation, Essential-Work

Dec 8 2015

Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

So, I turned off the Enable AdBlock, and the success rate went up from 0% to 20%:

Dec 8 2015, 8:58 PM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

New list of pages not translatable nb->nn:

Dec 8 2015, 8:46 PM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Failed articles: I have reportet appr 7-10 of them, more to come.

Dec 8 2015, 1:52 PM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Here is the procedure:

  1. I choose text + title for the translated article
  2. I click the "Start a new translation"
  3. The page I arrive at has the original to the left, an empty field to the right, and a grey "Publish translation" button
  4. I click the paragraphs, one by one, and get translations from Apertium. Now, things go good or bad:

GOOD:
After my first click, I get translated text, and the grey button turn green. Now I know I may continue, I will be able to publish in the end.
BAD:
After my first click, I get translated text, but the grey button does NOT turn green. Now I know I have to abandon this translation. No matter what I do, I will not be able to translate on any point. The button will stay gray, and nothing will happend when I press the grey button.

Dec 8 2015, 1:51 PM · Design, Essential-Work, ContentTranslation

Dec 7 2015

Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

I try to publish on nn. Today (when I had the presentation) I managed to publish one. At the moment my success rate for publishing is appr 20% (8 out of 10 attempts just give a grey "publish translation" button. You see my translations here:

Dec 7 2015, 7:59 PM · Design, Essential-Work, ContentTranslation

Dec 6 2015

Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Update again: Well, definitely not ashamed, but baffled, perhaps. The improved behaviour turned out to be short-lived. Even with JavaScript _on_ and adblock off, I get the same unpredictable behaviour as before, even with the "fail" percentage rising, Tonight I have still not found a single page working (getting translation). Examples of failed pages:
https://no.wikipedia.org/wiki/Narve_Skarpmoen
https://no.wikipedia.org/wiki/Grensevakt

Dec 6 2015, 9:51 PM · Design, Essential-Work, ContentTranslation

Dec 1 2015

Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Update: (... still do not know whether I should be ashamed or still baffled): When testing earlier, I have tried both with and without the adblock filter, both ways with bad results (but in hindsight, I cannot promise I restarted the browser). Looking at the "warning, adblock" above, I again turned it off, and ensured that JavaScript was on. After that I translated perhaps 6 articles, All worked, except one (which also worked when I tried it a second time). In Chrome, I had had JavaScript _on_ the whole time (with the earlier reported sad results), now I am not able to repeat them. I will thus comtinue translating, and report possible errors. At the moment they are hard to find.

Dec 1 2015, 10:15 PM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Ok, Show JavaScript --

Dec 1 2015, 7:33 PM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Ok, Show JavaScript --

Dec 1 2015, 7:33 PM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

As far as I have seen, it is a 1-1 relation between the "PT" button turning green when clicking the first paragraph, and the possibility of publishing anything. I cannot understand that you "do not doo any checks whether the publishing will actually succeed before you click the button " -- since even though "you" do not do it, evidently the computer does (green = I may continue translating the article; grey = I better give in -- this generalisation holds 100%).

Dec 1 2015, 7:27 PM · Design, Essential-Work, ContentTranslation

Nov 30 2015

Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

I am assuming you mean "Start translation" and "Cancel" buttons on the page selection dialog on Special:CX,

Yes, I do, on this page:
https://nn.wikipedia.org/wiki/Spesial:Innhaldsomsetjing
Here I choose the page, and press "Start a new translation".
Then I get the page (two columns), I click (doubleclick, actually) to the right to get the first paragraph. In the good cases, the button "Publiser omsetjing" ("publish translation") turns grean, and I can go on.
In the bad cases, it stays gray, and I give in.
In this special case (article "Barnas supershow") it turned green, and I thought I could save the article for my demo.
So I pressed the "Alle omsetjingar" ("All translations") in the upper left corner, and got back to this page:
https://nn.wikipedia.org/wiki/Spesial:Innhaldsomsetjing
But when I then tried the same article again (starting over by suggesting the same article + translating the first paragraph on the two-column page), the "Publiser omsetjing" did not turn green.

Nov 30 2015, 11:51 PM · Design, Essential-Work, ContentTranslation

Nov 28 2015

Trondtr added a comment to T116908: Investigate CX saving/recovery failures.

It is not: I found the correct bug for that: https://phabricator.wikimedia.org/T114621. Sorry.

Nov 28 2015, 12:02 PM · LE-CX7-Sprint 4, MW-1.27-release (WMF-deploy-2015-11-17_(1.27.0-wmf.7)), ContentTranslation, MW-1.27-release (WMF-deploy-2015-12-08_(1.27.0-wmf.8)), Patch-For-Review, Essential-Work, ContentTranslation-Release7
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

While looking at this, I thought I could prepare for my presentation by finding "green" (translatable) articles in beforehand. So, I found this one: https://no.wikipedia.org/wiki/Barnas_supershow. (translating no->nn) Checked the first paragraph, link is green, good. I then pressed "Interrupt" ("Avbryt"), and then started again, with the same article. This time it did not turn green, but stayed gray. Is it my interrupted article which blocks the second attempt? If so, a notification telling just that would have helped.

Nov 28 2015, 11:53 AM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T114621: Get ContentTranslation to anticipate and handle AbuseFilter warnings and blocks.

Comment to Pginer-WMF: This is great !! I intend to demo this tool on a week-long course in Apertium MT next monday (7.12.), and really hope for a more enlightened workaround by then. The unpredictability is the worst (standing in front of the audience and desperately click myself through lists in order to find a "green" article).

Nov 28 2015, 11:46 AM · Design, Essential-Work, ContentTranslation
Trondtr added a comment to T116908: Investigate CX saving/recovery failures.

I take it that the problem of the PUBLISH TRANSLATION button staying gray is not part of this bug?

Nov 28 2015, 11:39 AM · LE-CX7-Sprint 4, MW-1.27-release (WMF-deploy-2015-11-17_(1.27.0-wmf.7)), ContentTranslation, MW-1.27-release (WMF-deploy-2015-12-08_(1.27.0-wmf.8)), Patch-For-Review, Essential-Work, ContentTranslation-Release7
Trondtr added a comment to T106415: Better announce the lack of Machine Translation.

There are several ways of showing possible language pairs: One is via a table, andother is by listing pairs (e.g. ordered according to target language) rather than by listing singleton languages. So, the following list could be a good idea:
Target language: source language 1, source language 2, etc.
...
Philosophy: I can understand more languages than I can write text for. I thus decide on the target language and investigate what pairs there are. Clicking on e.g. "source language 2" above will give the pairs "source language 2 -> target language"

Nov 28 2015, 12:22 AM · OKR-Work, Design, ContentTranslation