Talk:Tech/News

Archives

---

Talk:Tech/News/Archives

Browsers

Hi, Johan. Is that right that from January 1 there are a lot of new browsers that do not allow to read or edit Wikimedia sites, for example Android below 4.4, and there was no announcement with browsers list in the News? Thank you. IKhitron (talk) 13:27, 8 January 2020 (UTC)

Hi IKhitron, thanks for asking – I had missed this. After looking around I guess that what you're referring to is related to phab:T238038. The browsers in question would've seen the warning message, which refers to January 1, but nothing has actually happened since December 9, which is when the pageview rate showing the warning went from 10% to 100% for these browsers. So in practice, the change happened in early December, and protocol-level support is to be dropped but it hasn't happened. I'll mention it in the next newsletter. /Johan (WMF) (talk) 17:24, 8 January 2020 (UTC)

Thank you. IKhitron (talk) 17:30, 8 January 2020 (UTC)

Thanks, Johan, but I think there must be a link to browsers list. IKhitron (talk) 15:35, 9 January 2020 (UTC)

There's no exhaustive browser list, unfortunately, as far as I can tell – the most common browsers affected are, as you've noted, on Android below 4.4. I have added a link to the browser recommendations, which is the most up-to-date information for the bigger platforms. /Johan (WMF) (talk) 16:09, 9 January 2020 (UTC)

I'm trying to get better stats – will add them if I get them in time. /Johan (WMF) (talk) 16:15, 9 January 2020 (UTC)

Bot to start translations

Hi. Can I propose that, to simplify translating each week's edition, a bot (mine) automatically fill in prepared translations for the phrases that are included every week, such as "Recent changes" and "Problems". Doing this automatically would both save translators from needing to translate the messages each week, and allow for standard translations of such messages to be established. Thoughts? (If there is support here, and I'll start coding and file a request for approval; for now I just want to see what people would think). Thanks, --DannyS712 (talk) 07:00, 10 January 2020 (UTC)

My first reaction is positive, but I haven't had time to think it through, of course. As long as the translation memory works these are fairly standardised and easy to use for returning translators. Something that immediately comes to mind is that we don't want to end up with a bunch of translations every week where nothing but the pre-translated messages are available in that language. I'll point translators this way to make sure they're aware of your suggestion. /Johan (WMF) (talk) 07:07, 10 January 2020 (UTC)

I personally wouldn't have anything against implementing the suggestion. Saederup92 (talk) 07:22, 10 January 2020 (UTC)

Maybe using templates for common parts of newsletters issues? --Wargo (talk) 11:10, 10 January 2020 (UTC)

I think it will be some problem for delivering the newsletter. Stryn (talk) 11:48, 10 January 2020 (UTC)

It would need change to module to prepare the mailing. But, here, on wiki translation and reading will work in known way. --Wargo (talk) 11:54, 10 January 2020 (UTC)

I have been thinking of implementing templates for several months. Indeed, currently, it is impossible to see if a regular message have changed (ok, we can look at the memory translation percentage), and it is hard to improve a regular translation because translators ever use the most used translation memory… With templates, we would see history of each message and last translation would be used! —Pols12 (talk) 22:02, 12 January 2020 (UTC)