הלוואי שהיה קל לדווח על בעיות בכל שפה.
@Astinson can you please clarify what you need here? Shall we just configure a Content Translation campaign id (also known as "cta"), as we did for Wiki for Human Rights? Or something else?
Tue, Feb 25
Sun, Feb 23
I started a discussion in the Langcom about this.
Sat, Feb 22
Thu, Feb 20
Wed, Feb 19
Thanks. I added a few trivial improvements to the messages themselves.
Tue, Feb 18
Mon, Feb 17
Just change the English. Translators will notice the change and update the translations.
Sun, Feb 16
Thu, Feb 13
Wed, Feb 12
This is implemented in the latest monthly reports. Somewhat manual, but good as a start. Feedback is welcome.
Mon, Feb 10
Sun, Feb 9
Wed, Feb 5
Tue, Feb 4
Thu, Jan 30
Wed, Jan 29
I had a quick conversation with @daniel about this. This is the closest thing I could find to a Phab task for implementing the Dependency engine :)
First of all, I really appreciate the effort to harmonize the names across different wikis. Thanks for starting this.
Jan 27 2020
It's indeed quite possible that it't intended, but it shouldn't be :)
Jan 24 2020
Jan 22 2020
Jan 21 2020
And what are the languages for which it's possible to use real codes? Languages in Names.php? Something else?
I confirm. I saw it myself, and heard complaints from multiple people.
... Maybe, as a workaround until this is properly fixed in Blink, these wikis can define a font other than Georgia for their heading in Common.css?
Jan 20 2020
Here, as in T103066, I'd say that the really right solution is having better semantics in the text, and this is outside the scope of CX.
I've tried to reproduce, and here's what happens:
I agree with declining, but I'd add a slightly different rationale: It should be done, but not by Content Translation. Content Translation should be responsible for adapting only the most obvious and least ambiguous things, like links and images. Template adaptation is very non-obvious, and it is done by Content Translation, but that, too, should be refactored (see T243150 for an initial proposal).
Jan 19 2020
Jan 18 2020
Thanks. I don't see this problem on MacOS. This may be a problem with Windows. Does this happen in all browsers on Windows—Firefox, Internet Explorer, Edge? Does this work better on other websites?
On which browser does it happen?
Jan 17 2020
This is an extreme setting. No other wiki has such huge numbers.
Jan 15 2020
Thanks for the clarification! I updated the documentation.
Jan 14 2020
Maybe I'm missing something, but I cannot actually select the current year in the form. It's 2020 now, and it's grayed out:
Jan 13 2020
I've just reproduced this by translating the article GAZelle from English to Hebrew: https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Amire80/%D7%92%D7%90%22%D7%96%D7%90%D7%9C&oldid=27056000
Jan 11 2020
This happened today in the Hebrew Wikipedia.
Jan 10 2020
Is this just the branch cutting, which usually happens on Tuesdays? Or does it also affect the time of the actual deployment?
Jan 9 2020
Yeah, possibly related, but I'm not sure it's the same.
I'm working on integrating it with the Language team monthly reports.
Thanks for the explanation. As I noted in the description, I wasn't sure whether the truncating of the link before <ref> happens in VE or in Parsoid. I'm pretty sure that it happens somewhere.