維基百科

維基百科:互助客棧/消息/存檔/2021年6月

< Wikipedia:互助客栈 | 消息 | 存档
由Mohammed Sadat (WMDE)在話題Wikidata weekly summary #474上作出的最新留言：3 年前

Wikidata weekly summary #471

最新留言：3 年前1則留言1個人參與討論
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • You can now add a title to a query visualisation by adding #title:YourTitle to your SPARQL code (phab:T225883, example query with a title)
    • Added a new constraints type to indicate that a certain Property should only be used on Lexemes of a certain language (phab:T200689)
    • Working on not checking the format constraints via SPARQL to take that load off the SPARQL endpoint and make it technically better (phab:T176312)
    • Working on making the API-Sandbox not suggest edits to real Items (phab:T219215)


You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

《中文維基百科站務案例集·存廢覆核案例集·2021年卷》1-5月快報

最新留言：3 年前9則留言3個人參與討論

下述選編自《中文維基百科站務案例集·存廢覆核案例集·2021年卷》的案例，可能對最頻繁出現的站務處理具有參考或指導作用：

號 案號 案名 案情要點 裁定結果 裁判管理員
1 2021年1月存廢覆核第11號 重定向頁面《腳異味》、《足部異味》、《臭的腳》存廢覆核案 批量建立的口語重定向是否適用快速刪除方針準則G3 維持原決：刪除 KirkLU
4 2021年1月存廢覆核第23號 模板頁面《2017年香港播出之動畫》存廢覆核案 出於站務維護清理需要的模板刪除提請是否滿足刪除方針理由第9項的要求 推翻原決：刪除 Wong128hk
6 2021年2月存廢覆核第8號 圖片《吉林省標準地圖 1：450萬政區版.jpg》、模板頁面《PRC-StandardMap》存廢覆核案 中華人民共和國政府測繪地理信息行政主管部門向社會公布的公益性地圖是否滿足「創用CC 署名-相同方式共享 3.0」協議 維持原決：刪除 AT
8 2021年2月存廢覆核第32號 條目頁面《颱風夏浪 (2019年)》存廢覆核案 利用特定手段觀測或特定年份的風力最大值是否是關注度(氣旋)指引準則第2項所指的「相關氣象紀錄」 維持原決：保留 KirkLU
9 2021年2月存廢覆核第33號 重定向頁面《新萊茵報。民主派機關報》存廢覆核案 有可靠來源使用但顯著錯誤的別名重定向是否適用快速刪除方針準則R3 推翻原決：恢復 Techyan
11 2021年3月存廢覆核第14號 條目頁面《上海民族黨》存廢覆核案 行文引文高度類似但有新來源的原關注度不足條目是否適用快速刪除方針準則G5 發還：存廢討論 Antigng
12 2021年3月存廢覆核第175號 圖片《Microsoft Visual Studio Code 1.53.2 zh CN.png》存廢覆核案 基於開原始碼的專有軟體的界面截圖是否是自由版權的 推翻原決：恢復 蟲蟲飛
13 2021年5月存廢覆核第26號 條目頁面《馬玉靈》存廢覆核案 關注度(人物)指引收錄條件第6項的「主要演員」如何認定 推翻原決：刪除 KirkLU
15 2021年5月存廢覆核第40號 條目頁面《陳俊龍 Dr.Leon Chen》存廢覆核案 快速刪除方針準則G11中所規定的「宣傳內容」應如何認定 維持原決：刪除 Wcam

要旨：

  • 存復集 卷2021 1號：大量口語重定向可適用WP:G3處理。（原存檔於[2021]DRV-01/06-11{RDRT}）
  • 存復集 卷2021 4號：出於善意整理目的提刪模板時，可視情況從寬適用刪除方針理由第9項。（原存檔於[2021]DRV-01/10-23{TPLT}）
  • 存復集 卷2021 6號：中華人民共和國政府有關部門公布的公益性地圖不滿足「創用CC 署名-相同方式共享 3.0」協議（原存檔於[2021]DRV-02/03-8{FILE}）
  • 存復集 卷2021 8號：基於特定觀測手段、特定年份界定的紀錄不認為是關注度(氣旋)指引準則第1項所指的「相關氣象紀錄」。（原存檔於[2021]DRV-02/14-32{ATCL}）
  • 存復集 卷2021 9號：有可靠來源使用但顯著錯誤的別名重定向不適用WP:R3（原存檔於[2021]DRV-02/15-33{RDRT}）
  • 存復集 卷2021 11號：由於內容的細微變化（如，補充可能足以證明關注度的來源），原有的刪除理據已經明顯消除或已經不充分的，不適用G5。（原存檔於[2021]DRV-03/04-14{ATCL}）
  • 存復集 卷2021 12號：基於開原始碼的專有軟體的界面截圖並不自然具有自由版權，需綜合考慮該專有軟體的版權協議決定；但截圖所含元素不超過原創性門檻（threshold of originality）時，截圖仍然為自由版權（原存檔於[2021]DRV-03/29-175{FILE}）
  • 存復集 卷2021 13號：關注度(人物)指引收錄條件第6項的「主要演員」應根據方針優先參照「各影視頒獎禮最佳男/女主角的提名的分量」處理。（原存檔於[2021]DRV-05/09-26{ATCL}）
  • 存復集 卷2021 15號：是否「頁面只作宣傳之用」應從頁面的內容客觀上實現了宣傳的效果和頁面的主要編輯主觀上具有進行宣傳的意圖或動機兩方面考慮。（原存檔於[2021]DRV-05/14-40{ATCL}）

以上。--Kirk # 2021年6月8日 (二) 13:38 (UTC)

@KirkLU：「有可靠來源使用但顯著錯誤的別名重定向是否適用快速刪除方針準則G3」？#9不是「顯著錯誤的別名重定向」。可能是我理解錯了。題外話：我個人對這裡所列出的涉及版權的諸多判例的結果並不滿意，並應當在某些方面慎引以往判例。--Techyan（留言） 2021年6月8日 (二) 13:52 (UTC)
是關於R3，已更正。Wikipedia:存廢覆核請求/存檔/2021年2月#新萊茵報。民主派機關報這個我是這麼理解的：
  • 方針規定R3的第四種情形是「標題中使用非常見的錯別字」；
  • 實務中我操作採用的是（見此第五章）「標題中含有錯誤使用的標點符號的，參考適用情形四」；
  • 「新萊茵報。民主派機關報」這個句號和規範漢語的句號用法衝突，正常翻譯的話應該用冒號或者破折號一類的。
  • 不過有可靠來源翻譯如此，才得出保留的結論。--Kirk # 2021年6月8日 (二) 14:00 (UTC)
@Techyan：忘ping。--Kirk # 2021年6月8日 (二) 14:01 (UTC)
不過無論如何，這些也不是方針，所以可以靈活使用，如果有什麼很極端的情況，應該可以逐個處理。--Kirk # 2021年6月8日 (二) 14:05 (UTC)
看報紙的配圖，那個位置的確本來就是個句號。翻譯時，將其直接翻譯成中文句號似乎並沒有太多不妥。即使是在西文，這個地方按常理也應該使用冒號。並且也如我在DRV裡面所說，英語維基用的是冒號，但德語維基是句號。因此我不認為這算「明顯錯誤」，而是正常用法。--Techyan（留言） 2021年6月8日 (二) 15:08 (UTC)
@Techyan：這方面我是這樣考慮的：
  1. 西文（德文）句號和中文句號功用並非對應，只有在表示句子結束等中外文句號功用一致的情況下，「.」才對應翻譯成「。」，否則有違格式手冊所參考的各種標點規範的要旨；（如果舉例沒錯的話）這跟日文的頓號不會直接原封不動納入譯文，而是視情況轉為中文逗號也是相似的；
  2. 西文（德文）句號起類似分隔注釋功能時，就不應當與中文句號（「。」）掛鉤，因為中文句號並不起到這類作用；且中文語境也不是截然不存在西文點號，這一點在類似《文後參考文獻著錄規則》（GB/T 7714-2015）一類的標準中可以得到證實；
  3. 最後，也許不構成理由，但這個句號看著就感覺像是錯的；如果不是有可靠來源這樣翻譯的話，直覺上也不會有這種選擇。
一言以蔽之，即——正確的標點轉化，是功用對應而不是形式（點號的名稱）對應，所以考慮是明顯用錯。--Kirk # 2021年6月10日 (四) 12:22 (UTC)
  • @KirkLU：我看了一眼Commons的存廢討論，「File:Microsoft Visual Studio Code 1.53.2 zh CN.png」最終的保留理由實際上是因為美國的原創性門檻很低，這樣的圖文排版不足以達到原創性。解讀為「基於開原始碼的專有軟體的界面截圖考慮為自由版權」恐怕欠妥。--DreamerBlue（留言） 2021年6月10日 (四) 03:39 (UTC)
    @DreamerBlue：謝謝指正，這是個大錯誤，看完commons發現其實我剛好說反了。已變更為「基於開原始碼的專有軟體的界面截圖並不自然具有自由版權，需綜合考慮該專有軟體的版權協議決定；但截圖所含元素不超過原創性門檻（threshold of originality）時，截圖仍然為自由版權」。--Kirk # 2021年6月10日 (四) 12:28 (UTC)

This Month in GLAM: May 2021

最新留言：3 年前1則留言1個人參與討論
 


Headlines
Read this edition in full • Single-page

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

Universal Code of Conduct News – Issue 1

最新留言：3 年前1則留言1個人參與討論

Universal Code of Conduct News
Issue 1, June 2021Read the full newsletter

Welcome to the first issue of Universal Code of Conduct News! This newsletter will help Wikimedians stay involved with the development of the new code, and will distribute relevant news, research, and upcoming events related to the UCoC.

Please note, this is the first issue of UCoC Newsletter which is delivered to all subscribers and projects as an announcement of the initiative. If you want the future issues delivered to your talk page, village pumps, or any specific pages you find appropriate, you need to subscribe here.

You can help us by translating the newsletter issues in your languages to spread the news and create awareness of the new conduct to keep our beloved community safe for all of us. Please add your name here if you want to be informed of the draft issue to translate beforehand. Your participation is valued and appreciated.

  • Affiliate consultations – Wikimedia affiliates of all sizes and types were invited to participate in the UCoC affiliate consultation throughout March and April 2021. (continue reading)
  • 2021 key consultations – The Wikimedia Foundation held enforcement key questions consultations in April and May 2021 to request input about UCoC enforcement from the broader Wikimedia community. (continue reading)
  • Roundtable discussions – The UCoC facilitation team hosted two 90-minute-long public roundtable discussions in May 2021 to discuss UCoC key enforcement questions. More conversations are scheduled. (continue reading)
  • Phase 2 drafting committee – The drafting committee for the phase 2 of the UCoC started their work on 12 May 2021. Read more about their work. (continue reading)
  • Diff blogs – The UCoC facilitators wrote several blog posts based on interesting findings and insights from each community during local project consultation that took place in the 1st quarter of 2021. (continue reading)

--MediaWiki message delivery（留言） 2021年6月11日 (五) 23:05 (UTC)

Wikidata weekly summary #472

最新留言：3 年前1則留言1個人參與討論
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Wikidata Community/Diversity 2021 Survey has been published. The results are meant to serve as a baseline to see how the community might (not) change in the future.
    • WikidataCon 2021: A sustainable future for Wikidata. Information about "the conference theme, its three-day program structure and a special project on diversity taking place before the conference itself".
    • The call for candidates for 2021 Wikimedia Foundation Board elections has begun on June 9. The last date to apply is June 29, 2021.
  • Development
    • Working on no longer using the Query Service to evaluate Constraints Checks regular expressions (this should make our checks faster and allow for further improvements) (phab:T176312)
    • Changing the rate limits for assigning Item IDs further, which should result in even fewer Q-IDs being skipped in the future (phab:T284538)
    • Finalizing the concepts for a tool to help work on mismatches between Wikidata's data and other databases/websites/...

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

《維基百科政策簡報》2021年5月號

最新留言：3 年前1則留言1個人參與討論
維 基 百 科 政 策 簡 報
— 每月一期，掌握政策脈動 —

過去一個月（2021年5月1日至2021年5月31日）內，中文維基百科之重要人事及政策變動大致如下，個別項目基本依變動或施行時間先後排序：

  人事動態

  方針與指引重要變動：重大的方針與指引修訂。過去一個月內，互助客棧方針區共有方針與指引相關新提案25項，另有7項方針與指引相關提案獲得通過：

  1. 《命名常規（化學）》：規範化學物質條目名稱，避免未經社群討論的移動。（討論紀錄）
  2. 《命名常規》暨《非條目頁面命名方針》：建立頁面命名一致性的通用（普遍性）規定。（討論紀錄）
  3. 《快速刪除方針》：將維基專題命名空間納入G14準則條文中（討論紀錄），後調整R2準則條文，禁止建立跨計畫與維基專題命名空間的捷徑重定向（討論紀錄）；相關模組一併修訂。
  4. 《格式手冊（兩岸四地用語）》：調整〈國籍〉一節中標示人物（前）國籍的規定。（討論紀錄）
  5. 《標誌指引》：在〈上傳非自由標誌〉一節中新增關於可縮放向量圖形（SVG）非自由標誌的規定，禁止使用自行製作或來自第三方網站的向量圖形。（討論紀錄）
  6. 《COVID-19條目共識》：規範條目標題、內文中對嚴重急性呼吸道症候群冠狀病毒2型（SARS-CoV-2）變種的稱呼，並規範重定向頁面標題中含對SARS-CoV-2變種稱呼者的處理。（討論紀錄）

  其他方針與指引雜項修訂，包括未於互助客棧方針區討論而進行之小修改、方針與指引之相應修訂或事實性修訂等。請核查此等修訂，若有需要，可提案至互助客棧方針區復議。

  其他重要社群動態：此處列出的動態雖不一定與正式方針或指引有關，惟對維基百科之社群或站務運作有一定影響。

Wikidata weekly summary #473

最新留言：3 年前1則留言1個人參與討論
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Interlanguage links now work for multilingual Wikisource. phab:T275958
    • User:Nikki/LexemeEntitySuggester.js now supports searching for senses for the translation property.
    • The call for candidates for 2021 Wikimedia Foundation Board elections has begun on June 9. The last date to apply is June 29, 2021.
    • Since the beginning of the month, phabricator tickets about language codes (and names of languages) were reviewed and triaged to better reflect their content and current status. Some work was done to better identify the steps for such changes, highlight and address bottlenecks and system issues. Patches for a few codes were contributed and are being released. Phabricator "Language codes" workboard provides an overview, phab:T284856 attempts to identify maintenance steps and phab:T284276 determine turn-around times. phab:T284808 should finally close a gap in termbox language handeling. A way to better address some or all aspects of changes of language codes applicable to Wikipedia editions still needs to be found. Don't hesitate to request the addition or update of language names (e.g. the name of Dutch in Danish) or missing language codes, notably for monolingual strings (see Help:Monolingual text languages).

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

This Month in Education: June 2021

最新留言：3 年前1則留言1個人參與討論
This Month in Education

Volume 10 • Issue 6 • June 2021

Contents • Headlines • Subscribe

In This Issue

The visual editor

最新留言：3 年前10則留言6個人參與討論

本主題或以下段落文字，移動自Wikipedia:互助客棧/其他。執行人：LightyearsTalk·Sign#維貓報 2021年6月15日 (二) 15:31 (UTC)。

Hello, all. 請幫助翻譯至您的語言.

My teammate @Trizek (WMF) works with the mw:Growth team, and he tells me that the Chinese Wikipedia can have Growth's tools for new editors (see mw:Growth/Feature summary). At most Wikipedias, new editors use the visual editor for their first few edits. The visual editor is still in Special:參數設置#mw-prefsection-betafeatures (the mw:Beta Features system) here.

Years ago, the visual editor was not very good with the language/script variants. It has improved – but unfortunately, I don't read or type in Chinese. Do you all think that the visual editor is a good option for new editors here? Does it work reliably? Please let me know what you think.

--Whatamidoing (WMF)（留言） 2021年6月14日 (一) 22:25 (UTC)

大家好。 我的同事@Trizek (WMF)在mw:Growth小組工作，他告訴我中文維基百科的新手編輯可以使用Growth的工具（參見mw:Growth/Feature summary）。在很多語言版本的維基百科中，新編輯都是使用可視化編輯器進行他們一開始的幾次編輯。可視化編輯器的開關依舊在Special:參數設置#mw-prefsection-betafeatures (mw:Beta Features system) 中。

幾年前，可視化編輯器在語言和腳本的變種中工作的並不是很好。但該問題現已得到改善——但很不幸，我不能用中文讀或寫。請問你們大家都覺得對中文維基的新手編輯來說可視化編輯器是個好的選擇嗎？可視化編輯器的工作是否可靠？請讓我知道你們的想法。

翻譯：LightyearsTalk·Sign#維貓報 2021年6月15日 (二) 02:14 (UTC)

Server switch

最新留言：3 年前3則留言3個人參與討論

Read this message in another language • 請幫助翻譯至您的語言

The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

  • You will not be able to edit for up to an hour on Tuesday, 29 June 2021. The test will start at 14:00 UTC (07:00 PDT, 10:00 EDT, 15:00 WEST/BST, 16:00 CEST, 19:30 IST, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday 30 June).
  • If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

  • Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
  • There will be code freezes for the week of June 28. Non-essential code deployments will not happen.
This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. A banner will be displayed on all wikis 30 minutes before this operation happens. Please share this information with your community.

SGrabarczuk (WMF) 2021年6月27日 (日) 01:19 (UTC)

簡而言之，從本月二十九號下午兩點（UTC時間）開始，一個小時內將不能進行編輯。--安憶Talk 2021年6月27日 (日) 03:10 (UTC)
在某些必要的情況下他們會推遲上述時間。具體以時間表和提前半小時在網頁頂部顯示的中央通知為準。--安憶Talk 2021年6月27日 (日) 03:26 (UTC)

The Signpost: 27 June 2021

 
News, reports and features from the English Wikipedia's weekly journal about Wikipedia and Wikimedia
Read this Signpost in full · Single-page · Unsubscribe · Global message delivery 2021年6月27日 (日) 20:17 (UTC)

Wikidata weekly summary #474

最新留言：3 年前1則留言1個人參與討論
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Mismatch Finder: We started building the foundation of the place that will store the mismatches between Wikidata and other databases/catalogs/...
    • Continued work on migrating the checks of regular expressions for constraints from SPARQL to a better solution to take that load off of the SPARQL endpoint (phab:T176312)
    • Made it possible to show language links from multilingual Wikisource to the other language versions of Wikisource (phab:T275958)
    • Added a new constraint type to indicate that a certain Property should only be used on Lexemes with a specific language (phab:T200689)
    • Fixed a weird issue with suggesters popping back up when they shouldn't (phab:T284219)
    • Invalid data will not be handled better in RDF outputs (phab:T285131)
    • Working on lowering the rate limit at which a misbehaving bot can waste new Item IDs to further reduce the percentage of skipped Item IDs (phab:T284538)
    • Working on not suggesting real Item IDs in the API sandbox to avoid accidental edits by people who think it is not making real edits (phab:T219215)
    • Working on reducing the time it takes between entering a value in a new statement and being able to save the statement (phab:T281669)
    • Improved documentation of the usage tracking aspects in API help pages. Usage tracking is an internal mechanism to track which article on Wikipedia etc uses which data from an Item on Wikidata. (phab:T283040)
    • Language codes for monolingual strings "gsw-fr", "ykg", "wya", "osa-latn" were made available: Alsatian, Tundra Yukaghir, Wendat, Osage (phab:T262922, phab:T252198, phab:T283364, phab:T265297)
    • The English name for language code "crh" and the Swedish name for "fa" were corrected (phab:T240350, phab:T281702)
    • Lexeme language codes ha-arab, sux-latn, sux-xsux, gsg, tlh-piqd, tlh-latn, bfi, pwn, enm were added. That is Hausa in Arabic script, Sumerian in cuneiform and Latin-script, German Sign Language, Klingon in pIqaD and Latin script, British Sign Language, Paiwan and Middle English. (phab:T282512, phab:T279557)
    • It was determined that language codes can be activated for Wikidata while being blocked for use on Incubator (phab:T273705), this to avoid projects such as a "British English Wikipedia"
    • Language code "es-419" for Latin American Spanish has been available for labels and descriptions for quite some time (phab:T230786)
    • A possibly confusing Russian mis-translation of the name of the language code for "multiple languages" (mul) is being reviewed (phab:T245927)
    • "en-simple:" can be used instead of "simple:" to link to Simple Wikipedia. Query Services outputs "en-simple", not "simple" for sitelinks to Simple Wikipedia (phab:T283149).
    • There was some discussion about the creation of a language code "en-in" for monolingual strings, but "en-in" as interface language seems to be preferred (phab:T212313)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #474

最新留言：3 年前1則留言1個人參與討論
 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Mismatch Finder: We started building the foundation of the place that will store the mismatches between Wikidata and other databases/catalogs/...
    • Continued work on migrating the checks of regular expressions for constraints from SPARQL to a better solution to take that load off of the SPARQL endpoint (phab:T176312)
    • Made it possible to show language links from multilingual Wikisource to the other language versions of Wikisource (phab:T275958)
    • Added a new constraint type to indicate that a certain Property should only be used on Lexemes with a specific language (phab:T200689)
    • Fixed a weird issue with suggesters popping back up when they shouldn't (phab:T284219)
    • Invalid data will not be handled better in RDF outputs (phab:T285131)
    • Working on lowering the rate limit at which a misbehaving bot can waste new Item IDs to further reduce the percentage of skipped Item IDs (phab:T284538)
    • Working on not suggesting real Item IDs in the API sandbox to avoid accidental edits by people who think it is not making real edits (phab:T219215)
    • Working on reducing the time it takes between entering a value in a new statement and being able to save the statement (phab:T281669)
    • Improved documentation of the usage tracking aspects in API help pages. Usage tracking is an internal mechanism to track which article on Wikipedia etc uses which data from an Item on Wikidata. (phab:T283040)
    • Language codes for monolingual strings "gsw-fr", "ykg", "wya", "osa-latn" were made available: Alsatian, Tundra Yukaghir, Wendat, Osage (phab:T262922, phab:T252198, phab:T283364, phab:T265297)
    • The English name for language code "crh" and the Swedish name for "fa" were corrected (phab:T240350, phab:T281702)
    • Lexeme language codes ha-arab, sux-latn, sux-xsux, gsg, tlh-piqd, tlh-latn, bfi, pwn, enm were added. That is Hausa in Arabic script, Sumerian in cuneiform and Latin-script, German Sign Language, Klingon in pIqaD and Latin script, British Sign Language, Paiwan and Middle English. (phab:T282512, phab:T279557)
    • It was determined that language codes can be activated for Wikidata while being blocked for use on Incubator (phab:T273705), this to avoid projects such as a "British English Wikipedia"
    • Language code "es-419" for Latin American Spanish has been available for labels and descriptions for quite some time (phab:T230786)
    • A possibly confusing Russian mis-translation of the name of the language code for "multiple languages" (mul) is being reviewed (phab:T245927)
    • "en-simple:" can be used instead of "simple:" to link to Simple Wikipedia. Query Services outputs "en-simple", not "simple" for sitelinks to Simple Wikipedia (phab:T283149).
    • There was some discussion about the creation of a language code "en-in" for monolingual strings, but "en-in" as interface language seems to be preferred (phab:T212313)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


取自「https://zh.wikipedia.org/w/index.php?title=Wikipedia:互助客栈/消息/存档/2021年6月&oldid=66492751」