User Details
- User Since
- Jan 25 2019, 12:59 AM (103 w, 2 d)
- Availability
- Available
- LDAP User
- VulpesVulpes825
- MediaWiki User
- VulpesVulpes825 [ Global Accounts ]
Sep 27 2020
Vue 3.0 is officially released.
Sep 22 2020
@Jdlrobson It shows the correct logo, thank you for your patch.
Sep 19 2020
Sep 18 2020
Sep 17 2020
Sep 8 2020
Maybe just rename variantname-kk to ‘unconverted’, which is what Chinese does in https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/languages/i18n/zh.json. This should help reduce confusion.
Adding MediaWiki-Language-converter since it is the part of the core that is responsible for language conversion. Adding Platform Engineering assume they are the current maintainer of language converter.
Aug 31 2020
Aug 28 2020
I do not believe this is an issue and the limit should not be changed. For example, the three character caption only mention the name and nothing else. Such caption is bad and meaningless as it does not provide any information at all, like is it a portrait, a photograph, a drawing?
Aug 27 2020
Right now the project logo variant change is supported and working for both logged in and logged out users on Chinese Wikipedia (not the beta cluster one). So please do not worry to much.
We probably need to extend wgLogos to support language variants of logos.
That will be great, which can also solve the issue that current logo delivery logic: both Traditional and Simplified needed to be served and then Traditional version is replaced by Simplified version using Common.css. This causes Traditional version never being used, create an unnecessary delivery, which the bandwidth can adds up if serving huge amount of users.
Aug 25 2020
Changing the title as the wordmark and tagline as been uploaded and deployed via patch 621542.
@alexhollender: This means that the common.css in beta cluster is not updated with the variant part.
Aug 24 2020
@alexhollender, you mean the current project-logo? Currently, since MediaWiki does not currently support variant changes for logos in the core, Chinese Wikipedia relies on its Common.css for the variant change. I am very inventive to mark this task as a duplicate of T260908, as I have already upload both of the wordmark and tagline for Chinese Wikipedia when I fix the error caused by T258552.
Community as stated clearly that the Simplified Chinese logo will be dropped, thus reopening the task.
Aug 23 2020
As Chinese Wikisource has both Simplified/Traditional logo currently in use, the change should not preceded until a Simplified Chinese logo has been provided, or the community decided to drop Simplified Chinese logo support.
Aug 20 2020
Schedule to deploy around 2020-08-24 11:00–12:00 UTC.
@Jdlrobson, @Urbanecm: zh-classic (Classical Chinese) is not the same as zh (Chinese), and adding the wordmark as zh only, rather than project-specific, such as zhwiki is crazy. How can this even pass the code review?
Aug 19 2020
Chromium-based Edge still does support Windows 7 and Windows 8 right now, and anyone who still using IE 11 should start the switch now (either voluntarily, or forced as Microsoft has pulled the plug)
Aug 18 2020
What about
a. Upgrade to Vega 5.0 and Support Vega-lite 4.0
b. Use Vega’s own Server-Side Deployment using Node.js to generate PNG, SVG or Canvas for server-side rendering.
c. If server side did not finishing rendering, we then start client rendering and use Vega 5.15’s Expression Interpreter to ensure CSP.
Aug 17 2020
I am curious about the current status of this task. Currently, the overall IE traffic is around 1.3%, and desktop IE traffic is around 3.7% (based on analytics). Maybe it is a good time to consider starting to drop IE 11, so we can move on to ES6 considering how low the traffic right now.
Aug 15 2020
I do not know if it is possible to pass the mediawiki system version info to the puppet file, so we can simply to an if statement for to Parsoid configuration.
Aug 13 2020
@alexhollender, thank you for your detailed explanation. However, I still quite not understand the thought for going from step 3 to step 4. I believe for ordinary users, such design choice failed to communicate that " the space to the right and left of the header is essential 'out of bounds'". A simple question a user might ask is "why there also a blank white space between the outer grey one and the content itself". I personally prefer your design in picture 3 if that is possible.
Aug 12 2020
It seems working now, with correct page previewing. Closing as invalid since no code is changed for this ticket.
Aug 10 2020
It is now deployed and the Template Editor Protection is available at Special:已保护页面
Now deployed and working.
Is your iOS system language also in zh-Hans-CN?
Scheduled for deployment on 2020-08-10 11:00–12:00 UTC
Aug 9 2020
@Bugreporter, there is nothing wrong with the translation in translatewiki. The current problem is Mediawiki uses
Category:Something rather than Something to replace $1 in the system message.
The patch is scheduled to be deployed around 2020-08-10 11:00–12:00 UTC
The patch will be deployed around 2020-08-10 11:00–12:00 UTC
The patch works flawlessly, but it is best for us to consider how we should be dealt with the puppets that are still requiring Parsoid/JS (see T259988)
Adding Release-Engineering-Team based on Maintainers list.
Aug 8 2020
@Legoktm I am on Linux using addshore's mediawiki-docker-dev. I used a clean installation with CLI.
OS | Ubuntu 18.04.4 LTS |
MediaWiki | 1.35.0-rc.0 (c1ac169) |
PHP | 7.2.24-0ubuntu0.18.04.3 (fpm-fcgi) |
MariaDB | 10.5.4-MariaDB-1:10.5.4+maria~focal-log |
Aug 7 2020
@Legoktm @cscott I have retried with both the latest master branch as well as REL_1.35 branch of MediaWiki core and VisualEditor. I set up MediaWiki by using addshore's mediawiki-docker-dev. I have only put wfLoadExtension( 'VisualEditor' );, and it unfortunately still does not work.
Aug 5 2020
Aug 4 2020
I think it still follows W3C accessibility guideline on hovering, and better as there is no longer the need for users to exactly position of the video play button.
Aug 2 2020
Due to the current un-deployment of Graphoid (See T242855), declining the task as won't be fixed.
@cscott, I will move this to the future idea for consideration, as we will need to move away from an on-page handwritten rule-based system to an automatic system with customized dictionary per page generated by Wikidata (Tools like OpenCC support customized dictionary on top of standard dictionary for conversion).
For the discussion, It should be considered a consensus has been reached. However, the task is still stalled due to T44473.