Le 17/06/2019 à 21:45, Nick Wilson (Quiddity) a écrit :

On Mon, Jun 17, 2019 at 11:43 AM Sylvain Chiron <chironsylvain@orange.fr mailto:chironsylvain@orange.fr> wrote:

When translating messages 22, 23 and 24 on the main feedback page, I get
the following mesage:
“
Error saving translation: This namespace is reserved for content page
translations. The page you are trying to edit does not seem to
correspond any page marked for translation.
”

I’ve kept my translations of these messages into French in a text file
so please don’t translate again.

Hi Sylvain This error message comes from an occasional bug that is suspected to be related to the JobQueue. TLDR: Wait a few minutes and try again - that usually solves it. Other workarounds, and bug details, are in https://phabricator.wikimedia.org/T221119

Indeed it works now. Thanks :).

I also want to say that I would be glad to translate the testing app if it can help. But if you don’t plan to make it translatable, then you should wrap the button labels with <tvar> in the wiki page (so that I don’t have to think about whether or not I must translate it).

And I’ve got another remark by the way. It’s that I prefer page links to direct translation links :/ for the following reasons: — often it does not select the right target language, because either I’m not initially logged in (my browser cookies are reset at each new session, because I feel that otherwise cookies are more useful to web service providers than to web users) or your link specifies another target language, and changing the target language is just as long as clicking ‘Translate this page’ from the original page; — it’s often good to see what the page looks like while you’re translating it and even before you begin (i.e. look at the big thing before helping on it, get some context information; I’m not just an automatic translation tool, I’m somewhat interested in the thing); — from the translation interface you can only access the original version, while from the page you can access the translated version and the translation interface (e.g. when translating Page to French you have a link to Page but not to Page/fr; but from Page you have a link to Page/fr and a link to translate into your usual language); — the page link is more readable (the least important but still a bonus).

But well, do what you like — set a place to discuss/vote what the best is, or simply continue to give your links. Anyway now that you’ve read my feelings I should no longer be disturbed by direct translation links. I’m sorry to be an anxious guy.

Cheers,

My bad concerning the links. I usually give you the one without the language parameter but I skipped that one. Sorry.

On Tue, Jun 18, 2019 at 2:40 AM Nick Wilson (Quiddity) < nwilson@wikimedia.org> wrote:

On Mon, Jun 17, 2019 at 2:51 PM Sylvain Chiron chironsylvain@orange.fr wrote:

...

And I’ve got another remark by the way. It’s that I prefer page links to direct translation links :/ for the following reasons:

Those are good points! I think the Tech/News standard email setup works best, by providing both the page link, and the direct translation link (with no language specified in the URL) for those who prefer to get straight into the task. E.g. https://lists.wikimedia.org/pipermail/translators-l/2019-June/004881.html but I agree that the page link is probably the most important. (I'm not involved with the Research test app, so I'll leave those questions for Benoît. :)

---

Translators-l mailing list Translators-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/translators-l