Wikipedia:城市論壇 (技術)

政策

技術

提議

諗法實驗室

雜項

睇晒

• 目錄
• 第一串討論
• 呢版最尾

城市論壇嘅技術部係用嚟討論技術問題。如果遇到臭蟲或者請求新嘅功能，請到Phabricator提出，因為開發人員唔能夠保證會睇呢一頁。 常見問題： 伺服器嘅間歇延遲可能會令到篇新文需要幾分鐘時間至會出現，以致監察清單、貢獻同埋頁面歷史／舊檢視有時唔會顯示到非常之近嘅更改。呢個問題我哋而家響度跟進緊。 個搜尋索引有時會脫班，有機會去到幾個星期前有多。由於咁嘅原因，響搜尋度搵到嘅變動未必會即時反映出嚟。 如果全部嘅連結突然間加咗底綫（又或者冇咗條底綫），噉就可能你嘅瀏覽器載入其中一個css時失敗咗。請強制去重載或者繞過你嘅快取。 如果你對整你別出心裁嘅簽名係有問題嘅話，可以睇下Wikipedia:點樣修正你嘅簽名。 如果你換咗塊皮，但係又唔可以換返嚟，用呢個連結。 喺城市論壇技術部嘅新手人兄，喺呢度貼文之前請先閱讀呢啲指引。

請喺你嘅留言道加上你嘅簽名用埋時間（打入~~~~或者撳一下編輯工具欄上面嘅簽名掣）。請響最尾道加上新嘅題目。

Internal link helper升級

我發現中文維基嘅Internal link helper（綠色link）原來已經升級，指埋去就可以睇埋預覽，有無熟悉技術嘅朋友可以睇下點樣引進到呢邊？ Telematina (傾偈) 2025年2月15號 (六) 11:58 (UTC)

過中文維基搵下相關資料，睇落應該係同呢個有關：zh:Wikipedia:互助客栈/技术#新版跨语言链接小工具，係個Gadget（呢邊叫「架生仔」），預設向所有人（包括未登入嘅人）啟用。嗰邊仲係試行緊，就算呢邊想「借用」，建議等嗰邊試到穩定先至再諗。--Mikedou (傾偈) 2025年2月22號 (六) 06:23 (UTC)

搞咗個用喺粵維嘅fork，UI文字粵語化重未整（兩個messages.json），呢度嘅介面管理員可進行測試。 Dabao qian (傾偈) 2025年8月21號 (四) 18:40 (UTC)

我想問係咪等UI文字搞埋就可以用得？ Telematina (傾偈) 2025年10月11號 (六) 11:49 (UTC)

出錯: Lang-xx: text has italic markup

例子：我家有囍事。由 Category:Lang同lang-xx模錯誤 可見，應該有千幾篇文有同一錯誤。請睇下點樣修正。 Yaukasin (傾偈) 2025年3月10號 (一) 14:56 (UTC)

已經改進嘅內容翻譯工具儀表板

各位維基媒體成員大家好！

語言同產品本地化團隊改進咗內容翻譯儀表板 為所有使用行動裝置同桌面裝置嘅貢獻者創造一致嘅體驗。以下係有關改進嘅重要資訊嘅細目分類。

我哋有咩改進？

改進後嘅翻譯儀表板允許該工具嘅所有登入使用者享受一致嘅體驗 —— 無論佢哋使用咩設備。透過協調嘅體驗，已經登入嘅桌面使用者而家可以存取下圖所示嘅功能。

請注意，喺呢個螢幕截圖入面，新嘅儀表板允許：使用者使用「為您」同「⋯更多」按鈕調整建議，以選擇一般主題或社群創建嘅集合（例如氣候主題嘅範例）。 此外，使用者可以用翻譯嚟建立新文章（同以前一樣）並逐節擴展現有文章。你可以睇到新嘅儀表板入面點樣分為兩組（「建立新頁面」同「使用新章節進行擴充」）提供建議 —— 每項活動各佔一組。

喺目前嘅儀表板入面，你會注意到無法調整建議以選擇主題或社群建立嘅集合。另外，你唔可以透過翻譯新章節嚟擴展現有文章。

呢個改進係咪會改變呢個工具喺呢個維基百科入面嘅當前可訪問性？
語言同產品本地化團隊了解你對公開內容翻譯工具嘅擔憂。因此，請放心，呢個改進將會保持測試階段，確保只有從測試版功能啟動工具嘅登入使用者先可以繼續存取內容翻譯工具。此外，如果該工具只供特定用戶群組使用，噉就會保持現狀。

我哋計劃幾時實施呢項改進？
我哋會喺2025年3月24日前喺你嘅維基百科同其他網站上面實施呢項改進。

我哋實施改進之後，以前嘅儀表板會發生咩情況？
你仍然可以喺一段時間內透過工具頁面存取以前嘅儀表板。我哋會喺2025年5月之前將佢喺所有維基百科入面刪除，因為維護以前嘅儀表板唔會再有成效。

喺呢個維基入面實施呢個改進之前，我可以喺邊度測試呢個改進同埋報告任何問題？
你可以用呢個連結喺測試嘅維基媒體專案入面嘗試改進嘅功能：https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=contributionsmenu&to=zh&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en#/%E3%80%82%E5%A6%82%E6%9E%9C%E4%BD%A0%E7%95%99%E6%84%8F%E5%88%B0%E5%90%8C%E6%B8%AC%E8%A9%A6%E7%B6%AD%E5%9F%BA%E5%AA%92%E9%AB%94%E5%B0%88%E6%A1%88%E4%B8%AD%E6%94%B9%E9%80%B2%E5%98%85%E5%84%80%E8%A1%A8%E6%9D%BF%E7%9B%B8%E9%97%9C%E5%98%85%E5%95%8F%E9%A1%8C%EF%BC%8C%E8%AB%8B%E5%96%BA%E5%91%A2%E5%80%8B%E7%B7%9A%E7%A8%8B%E5%85%A5%E9%9D%A2%E8%A9%B1%E6%88%91%E5%93%8B%E7%9F%A5%EF%BC%8C%E6%88%96%E8%80%85%E5%96%BA 。如果你留意到同測試維基媒體專案中改進嘅儀表板相關嘅問題，請喺呢個線程入面話我哋知，或者喺 Phabricator 入面報告，並添加以下標籤：BUG REPORT同ContentTranslation。如果對此項改進有任何疑問，請向我哋提問。

多謝！

僅代表語言同產品本地化團隊 UOzurumba (WMF) (傾偈) 2025年3月18號 (二) 19:56 (UTC)

請求改下MediaWiki:Sitenotice嘅句子

原先嗰個講到唔似廣東話咁，新版搞掂咗哩個問題，請求管理員搞下。

第1行：	第1行：
<span style="font-size:larger;">無法顯示部份嘅字體？可以睇下[[Wikipedia:Unicode擴充唐字|有乜字型]]，然後安裝落部電腦度。<br>想搵嘢寫，可以睇下[[Wikipedia:文章請求]]同埋[[Wikipedia:翻譯請求]]。<br>繁簡字轉換標籤喺版面右上角，技術詳情請睇[[wikipedia:傳統字同簡化字對換|JavaScript 繁簡字轉換工具]]。</span>	<span style="font-size:larger;">有啲字睇唔到？可以睇下[[Wikipedia:Unicode擴充唐字|有乜字型]]，然後安裝落部電腦度。<br>想搵嘢寫，可以睇下[[Wikipedia:文章請求]]同埋[[Wikipedia:翻譯請求]]。<br>繁簡字轉換標籤喺版面右上角，技術詳情請睇[[wikipedia:傳統字同簡化字對換|JavaScript 繁簡字轉換工具]]。</span>

User:1F616EMO (最好去中文維基揾我) 2025年4月4號 (五) 09:58 (UTC)

@1F616EMO：Y 搞掂，多謝你嘅提議。 ——Z423X5C6（傾偈） 2025年4月8號 (二) 17:14 (UTC)

twinkle工具歡迎用戶

有冇人知道點解我用twinkle呢個工具歡迎用戶嘅時候，會自動重複簽名，例子1、2、3。 Jackyming 2025年4月13號 (日) 12:43 (UTC)

近排香港公共圖書館上維基百科經常出現Timed out錯誤

我間唔中用香港公共圖書館電腦上維基百科，但發現近排（未有刻意紀錄幾時開始，應該大約3月開始）上維基百科（包括粵文、中文、英文），經常載入好耐後出現Timed out錯誤，頭一兩次遇到以為咁啱網絡繁忙，但接連幾次於唔同時段於唔同圖書館上都有問題，試過用Chrome同Firefox亦都一樣，都係時得時唔得。究竟係維基伺服器阻攔香港公共圖書館嘅IP，定係香港公共圖書館阻攔連去維基伺服器嘅連線？（送出呢個留言又出現「The server did not respond within the expected time.」，要重新載入先至可以送出） ~2025-46706 (talk) 2025年4月19號 (六) 07:02 (UTC)

Sub-referencing: User testing

Apologies for writing in English, please help us by providing a translation below

Hi I’m Johannes from Wikimedia Deutschland's Technical Wishes team. We are making great strides with the new sub-referencing feature and we’d love to invite you to take part in two activities to help us move this work further:

1. Try it out and share your feedback

   Please try the updated wikitext feature on the beta wiki and let us know what you think, either on our talk page or by booking a call with our UX researcher.

2. Get a sneak peak and help shape the Visual Editor user designs

   Help us test the new design prototypes by participating in user sessions – sign up here to receive an invite. We're especially hoping to speak with people from underrepresented and diverse groups. If that's you, please consider signing up! No prior or extensive editing experience is required. User sessions will start May 14th.

We plan to bring this feature to Wikimedia wikis later this year. We’ll reach out to wikis for piloting in time for deployments. Creators and maintainers of reference-related tools and templates will be contacted beforehand as well.

Thank you very much for your support and encouragement so far in helping bring this feature to life!

Johannes Richter (WMDE) (talk) 2025年4月28號 (一) 15:04 (UTC)

(翻譯)子參考：用戶測試

以下訊息由Jeffrey Kim翻譯，Al12si修正

你好，我係德國維基媒體嘅技術願望團隊嘅約翰尼斯；我哋喺新嘅子參考功能取得咗巨大進展，所以好想邀請你參加兩個活動，幫我哋將呢項工作推得更遠：

1. 試吓用，然後分享你嘅意見

   麻煩喺測試版維基嗰度試吓更新咗嘅維基文字功能，然後話畀我哋知你覺得點；你可以喺我哋嘅討論頁留言，或者約個時間同我哋嘅用家體驗研究員傾傾。

2. 睇吓，幫我哋設計「視覺編輯器」嘅用家介面

   如果想幫我哋測試新嘅設計原型，你可以參與用家測試，參與測試可以喺呢度申請；我哋特別希望可以同代表性不足同非主流嘅社羣嘅人傾偈。如果你認為你屬於呢兩類社羣，請考慮申請！測試將會喺5月14號開始，參加者唔需要任何編輯維基嘅經驗。

我哋計劃喺今年尾將呢個功能帶到維基媒體嘅各個維基；我哋會預先聯絡各個維基進行試驗，以便可以及時部署，我哋亦會事先聯絡有份整同維護參考相關工具同模嘅人。

非常感謝你哋一直以來嘅支持同鼓勵，係你哋嘅支持同鼓勵令呢個功能可以成真！ Johannes Richter (WMDE) (talk) 2025年4月28號 (一) 15:04 (UTC)

We will be enabling the new Charts extension on your wiki soon!

(Apologies for posting in English)

Hi all! We have good news to share regarding the ongoing problem with graphs and charts affecting all wikis that use them.

As you probably know, the old Graph extension was disabled in 2023 due to security reasons. We’ve worked in these two years to find a solution that could replace the old extension, and provide a safer and better solution to users who wanted to showcase graphs and charts in their articles. We therefore developed the Charts extension, which will be replacing the old Graph extension and potentially also the EasyTimeline extension.

After successfully deploying the extension on Italian, Swedish, and Hebrew Wikipedia, as well as on MediaWiki.org, as part of a pilot phase, we are now happy to announce that we are moving forward with the next phase of deployment, which will also include your wiki.

The deployment will happen in batches, and will start from May 6. Please, consult our page on MediaWiki.org to discover when the new Charts extension will be deployed on your wiki. You can also consult the documentation about the extension on MediaWiki.org.

If you have questions, need clarifications, or just want to express your opinion about it, please refer to the project’s talk page on Mediawiki.org, or ping me directly under this thread. If you encounter issues using Charts once it gets enabled on your wiki, please report it on the talk page or at Phabricator.

Thank you in advance! -- User:Sannita (WMF) (talk) 2025年5月6號 (二) 15:07 (UTC)

(翻譯)我哋好快就會喺你嘅 wiki 上面啟用新嘅圖表擴充功能！

以下訊息由Jeffrey Kim翻譯，Al12si修正

咁多位好！有關圖表功能嘅持續問題對各個用呢種功能嘅維基所造成嘅影響，我哋有個好消息話你知！

咁多位可能都知道，由於安全原因，舊嘅圖表擴充功能喺2023年停用咗。我哋喺兩年嚟一直努力咁搵一個可以取代舊有擴充程式嘅解決方案，等大家喺文章入面展示圖表可以有個更安全、更好嘅解決方案，所以我哋開發咗個圖表擴充功能；佢會取代舊嘅圖表擴展，甚至可能會取代埋EasyTimeline擴充程式。

我哋已經完成試點階段，當中包括成功喺意大利文維基百科、瑞典文維基百科、希伯來文維基百科同 MediaWiki.org 成功部署擴充程式；而家好高興宣布我哋會進入下一階段嘅部署，包括喺你哋呢個維基部署呢個功能。

部署將會由5月6號開始分批進行；新嘅圖表擴充功能幾時會喺你嘅維基部署嘅詳情，請睇睇喺 MediaWiki.org 嘅頁面，你亦可以睇埋擴充程式喺 MediaWiki.org 嘅文件。

如果你有任何疑問、需要澄清，或者只係想表達你對呢件事嘅意見，請參考項目喺 Mediawiki.org 嘅討論頁, 或者直接喺呢個主題下面 ping 我。如果你喺你嘅維基啟用咗圖表之後遇到使用圖表嘅問題，請喺相關功能嘅討論頁或者 Phabricator 報告。

多謝晒先！-- User:Sannita (WMF) (talk) 2025年5月6號 (二) 15:07 (UTC)

@H78c67c、Jeffrey Kim、Al12si、Jackyming：我暫時整做咁樣，大家睇睇得唔得？ ——Z423X5C6（傾偈） 2025年5月7號 (三) 13:24 (UTC)

好，個人認為以後嘅英文 MassMessage 都用呢個 format 原文譯文並列都唔錯。 h78c67c (傾偈) 2025年5月7號 (三) 13:29 (UTC)

咁好（除非喺元維基一早譯咗）；上一篇嘅作者嘅意思就係想咁。

我只係留意到個訊息想睇，發覺睇唔明，所以執咗一執。

補充：執嗰陣有啲執突咗（即係超出咗 comparative editing 嘅範疇，已經係 stylistic editing），唔好意思。 Alıƨsi (傾偈) 2025年5月7號 (三) 18:33 (UTC)

好，我已經補埋雜項嗰邊嘅原文。 ——Z423X5C6（傾偈） 2025年5月8號 (四) 13:24 (UTC)

對某啲用戶點樣攞到睇臨時戶口IP地址呢個權嘅一啲改動

你好！我哋係信任與安全產品團隊。我哋想分享下，我哋決定咗修改存取臨時戶口IP地址嘅最低要求。呢項改動對貴社羣嘅影響會係甚低嘅。我哋計劃喺5月26號嗰個禮拜實施呢項改動（T393358 + T393360 + T390942）。關於啲細節我會keep住update你哋。

我哋改呢項規則淨係針對冇進階權限（例如管理員、事務員、用戶稽查員—— 想搵更多例子，請睇份政策）但個戶口至少開咗6個月同喺呢個維基度修改咗至少300次嘅用戶。佢哋會冇得再睇啲IP地址（T393360），而想睇得返嘅話，佢哋會須要申請個權限。管理員或者執行員會決定畀唔畀好（T390942）。換言之人手工作係會多咗，但係呢個方法會安全過繼續自動授呢種權。我哋想強調，喺貴維基度，只有幾個冇進階權限嘅用戶曾經揭露一個臨時戶口嘅IP地址。

我哋作出呢個決定，係基於我哋由你哋呢啲試點維基——尤其係羅馬尼亞文維基百科——度聽返嚟嘅嘢。我哋亦都諮詢咗啲執行員嘅意見，並喺維基元同約20個比較大嘅維基百科度進行討論。當我哋部署臨時戶口去多啲維基度嗰陣，我哋會評估個影響，並有可能再次調整我哋嘅approach。

除此之外， 我哋想話你哋知道，存取IP資訊功能嘅最低要求會同存取臨時戶口IP地址嘅一樣（一位用戶一就睇到曬所有資訊，一就乜都睇唔到）。

呢個改動嘅理由

我哋喺任何維基上部署臨時戶口之前，揀咗現時嘅數值門檻同埋授權程序自動化。但係而家我哋清楚明白到呢啲要求頗低，對心懷不軌嘅人嚟講，睇到臨時戶口IP地址仲係太容易。我哋想臨時戶口有意義噉改善編者私隱，所以我哋要加緊拘束。我哋嘅目標係一致噉限制IP地址淨係畀有需要嘅人睇。

噉會點運作

• 當一位冇進階權限嘅用戶須要睇臨時戶口IP地址嘅時候，佢哋須要申請加入「Temporary account IP viewers」權限組。佢哋會向管理員（在地社羣可以決定個過程會係點）或者執行員（for冇在地管理員嘅維基）申請。
• 軟件會要求個用戶至少有300次修改，並且開咗個戶口至少6個月。管理員同執行員唔會將呢個權畀到唔符合呢啲條件嘅戶口。呢個係最低限，我哋建議你哋設更高嘅門檻。
• 審視個請求嘅用戶會檢查申請緊嘅用戶符合最低要求並且提供咗有效理由。個權本身會經Special:UserRights頒授。
• 畀呢個權嘅用戶亦會處理撤銷個權嘅程序。

我哋亦都想澄清一啲細節。為咗方便大家，我哋亦都會喺個專案嘅FAQ度記錄低一部分。

IP地址嘅存取

• Separation of the new right (checkuser-temporary-account) out to a new group (Temporary account IP viewers), as opposed to technically attaching it to any existing group (like patroller). 我哋基於幾個原因決定噉做：
  • 睇到IP地址帶嚟風險：呢個權同用戶稽查員相似。IP地址算係識別個人資訊（一種個人數據）。想存取IP地址嘅外部人士而家起將會需要同有呢個權嘅用戶互動。有呢個權嘅用戶應該要知道呢點，並且對可疑存取請求嘅可能性保持警惕。
  • 為保護私隱嘅良好做法：將存取權畀受信任但冇需要睇嘅用戶唔符合處理個人資料嘅良好做法。
  • 剝奪個權：睇親IP都會喺日誌記錄低（例子）。如果偵測到一個用戶有任何濫用呢個權嘅情況，呢個權可以就噉拎走，唔影響任何其他權。攞走啲同睇IP地址無關嘅權限會有困難，有時甚至係唔合理。
  • 你哋可以將呢個權逐一畀曬所有屬於一個現有權限組嘅用戶。但呢啲用戶一定要符合Temporary account IP viewers嘅資格。
  • 為求清晰——呢度所有嘢唔影響管理員、事務員、用戶稽查員、執行員，以及全域政策所提及嘅其他權限組。
• 活躍度要求：對於需要人手授權嘅用戶，政策現時話佢哋「一定要喺365日內喺個在地專案度作出至少一次修改或日誌記錄嘅動作」。呢個要求冇改動。

授權程序

• 授權手續：冇需要好似申請做管理員噉討論或者投票。一位管理員自己判斷作出決定就夠。
• 對申請呢個權嘅用戶嘅額外要求：
  • 授權過程你哋可以自己話事。你哋可以將個門檻設喺300次修改以上，或者唔畀「非 管理員或以上」嘅用戶攞呢個權。個過程有幾簡單或複雜先係合適，可以由你哋決定。
  • 管理員決定畀唔畀個權嘅時候須要考慮咩條件——點知一位用戶須唔需要睇IP地址呢？300次修改同6個月嘅戶口以外並冇其他必要嘅最低要求。你哋可以就個用戶嘅可信性（例如冇俾人封鎖過或者侵犯過版權）或就巡查活動嘅經驗設立額外嘅條件。
• 對管理員嘅額外負擔：我哋明白要授予同剝奪多一個權所需嘅勞力。呢個的確係個缺點。我哋就諗要授呢個權畀一大班人只會係個一次性嘅工夫啫。我哋好奇你哋有冇計限制呢個負擔。

我哋建議你哋採取嘅下一步

• 我哋鼓勵你哋就授予同剝奪個權採納一項政策，如果你哋對個全域政策有嘢想加嘅話。
• 我哋建議你哋開始授呢個權。但考慮到我哋嘅數據（得幾個非管理人員曾經喺呢到揭露過臨時戶口嘅IP地址）我哋相信你哋喺呢個改動實行之前唔須要趕住或者花好多時間準備。
• 我哋想show畀你哋睇，喺我哋心目中咩程度嘅維基官僚似乎足夠。喺個沙盒度，我哋準備咗份草稿，顯示一版請求呢個權嘅版面可以係咩樣。當然嗰版嘅最終內容取決於貴社羣。我哋唔想暗示我哋係指點緊你哋呢方面應該點做。

如果有咩問題嘅話，請話畀我哋知。Thank you! NKohli (WMF) 同 SGrabarczuk (WMF) (傾偈) 2025年5月16號 (五) 02:11 (UTC)

討論

While this isn’t an objection, the way this change is being phrased is odd and I find this very disconcerting if this is typical of how things are decided at WMF.

I am one of those users who have ever used the reveal IP function, and if my own experience is representative, the reason why very few users have ever used the function is probably because it is not obvious how to reveal IP addresses; in fact, for a very long time I thought the right had no function at all, and I’d believe most people probably thought the same. (ETA: To clarify, who will go into their preferences to check for new options? hardly anyone ever.) Alıƨsi (傾偈) 2025年5月16號 (五) 03:56 (UTC)

PS: Sometimes I really wonder if there are designers working for WMF. Even a properly trained graphic designer would help, but a properly trained industrial designer would reveal a lot of process-related issues; this specific decision is totally related to not seeing pain points in the user journey. (Disclaimer: I am neither.) Alıƨsi (傾偈) 2025年5月16號 (五) 04:09 (UTC)

@NKohli (WMF)、SGrabarczuk (WMF)： Alıƨsi (傾偈) 2025年5月16號 (五) 13:26 (UTC)

Hello @Al12si, sure, some people haven't used IP reveal because they don't know how to enable it. To address this, we are working on an onboarding dialog. It will be displayed when users visit Recent Changes, Watchlist, or History pages, and it will explain some things, including how to enable the feature. Check the Phabricator ticket for more details. (Note that our designer is working on the dialog - so you were very correct about what should be done and by whom ^^) SGrabarczuk (WMF) (傾偈) 2025年5月16號 (五) 17:11 (UTC)

@SGrabarczuk (WMF) – The general problem here is that the whole decision is based on a false premise. It’s useless to make the decision first, then try to address the false premise; the false premise has already been used to justify the decision, and from the wording of the announcement, the decision is already final. Zero consultation. Zero research.

This is part of a series of general process-related issues that I have been seeing (this specific one is relatively minor, I have been bullied before); I seriously suggest WMF take the time to look at these policies from an industrial designer’s POV, with user journeys as a start. Alıƨsi (傾偈) 2025年5月18號 (日) 19:38 (UTC)

譯咗一半，順手擅自改咗少少文句令個翻譯通順啲（但係有儘量保留原文意思）。 h78c67c (傾偈) 2025年5月16號 (五) 10:28 (UTC)

譯多咗啲，多得濟，聽朝未有人譯埋嘅話我可以整埋佢。h78c67c (傾偈) 2025年5月16號 (五) 10:54 (UTC)

Join the 6th Wikipedia Pages Wanting Photos Campaign – 2025 Edition

Dear Wikipedia community,

We invite your community to participate in the 6th edition of the Wikipedia Pages Wanting Photos Campaign, a global campaign taking place from July 1 to August 31, 2025.

Participants will choose among Wikipedia pages without photos, then add a suitable photo from among the many thousands of photos in the Wikimedia Commons, especially those uploaded from thematic contests (Wiki Loves Africa, Wiki Loves Earth, Wiki Loves Folklore, Wiki Loves Monuments, etc.) over the years.

More than 80 Wikimedia affiliates have participated since the campaign was launched in 2020 and have added images to more than 400,000 Wikipedia articles in over 245 Wikipedia languages. Thanks to the volunteer contributors!

We now invite your community to organize and lead the campaign within your community. As a local organizer, you may:

• Encourage individual members to take part by adding images to Wikipedia articles.
• Host edit-a-thons focused on improving visual content.
• Organize training workshops to teach contributors how to correctly integrate images into Wikipedia.

These activities will help build local capacity and increase visual content across Wikipedia.

Please note that for participants to be eligible to participate in the campaign, they need to have registered an account for at least a year before the official start date of the contest. That is, for the 2025 edition, they must have registered an account on or before July 1, 2025. The account can be from any Wikimedia project wikis.

The organizing team is looking for a contact person to coordinate WPWP participation at the Wikimedia user group or chapter level (geographically or thematically) or for a language Wikipedia.

We would be glad for you to sign up directly at WPWP Participating Communities.

With kind regards,

User:Reading Beans On behalf of the Wikipedia Pages Wanting Photos campaign 2025. MediaWiki message delivery (傾偈) 2025年5月18號 (日) 21:53 (UTC)

(翻譯) 請參加2025年第 6 屆 ｢維基百科文章要相｣ 活動！

親愛嘅維基百科社群：

我哋邀請你哋嘅社群參與第六屆 ｢維基百科文章要相｣（WPWP）活動，呢個跨維基活動將會喺2025年7月1日至8月31日舉行。

咁多年嚟， 參加者會喺冇相嘅維基百科文章入面揀，然後喺維基共享嘅幾千張相入面加入一張適合嘅相，特別係嗰啲喺專題比賽上載嘅相（例如Wiki 維基愛非洲、維基愛地球、維基鍾意民間傳說、維基鍾意紀念碑等等）。

我哋而家邀請你嘅社群喺你嘅社群入面組織同埋帶領呢個活動。作為本地主辦單位，你可以：

• 鼓勵個別維基人參與，方法係將相加入去維基百科文章。

• 主持以改善視覺內容作為目標嘅編輯大賽。

• 組織培訓工作坊，教有心貢獻嘅維基人點樣將圖片正確整合到維基百科入面。

呢啲活動不但可以幫助建立你哋社羣嘅本地能力，同時更加可以增加維基百科嘅整體視覺內容。

注意活動有參加資格，參加者喺比賽正式開始前至少一年要註冊咗個帳戶，即係話如果要參加2025年度嘅比賽，參加者必須喺2025年7月1號或之前（校對按：應該係 ｢2024年7月1號或之前｣ 筆誤）註冊咗個帳戶，開戶維基不限，帳戶可以嚟自任何維基媒體項目嘅維基。

組織團隊喺度搵緊一個聯絡人，嚟協調各個（按地域或者主題設立嘅）維基媒體用戶群組或者分會或者唔同語言維基百科參與 ｢維基百科文章要相｣ 活動。

如果你可以喺 ｢維基百科文章要相｣ 參與社羣頁面直接申請，我啲會好高興。祝

安好。

｢2025年維基百科文章要相｣ 活動
User:Reading Beans 上

Jeffrey Kim (傾偈) 2025年5月23號 (五) 14:14 (UTC)

報錯：加唔到外連

加親外連都出現錯誤畫面，標題係「內部錯誤」，錯誤訊息係「 [7a84f1b2-8618-427e-bd0c-3bef59f48f1e] 2025-06-02 11:55:23: 嚴重例外類型「UnderflowException」 」。 ~2025-63175 (talk) 2025年6月2號 (一) 11:57 (UTC)

粵維取消專門版條link？

以前粵維任何頁面一直都有顯示專門版條link，而家左右兩邊欄都唔見，要人手輸入 https://zh-yue.wikipedia.org/wiki/Special:SpecialPages先至得。我見專門版有改版，唔知係咪因為呢個原因而唔見條link。 Alfakwan (傾偈) 2025年6月7號 (六) 08:05 (UTC)

@Shinjiman：想問吓介面管理員係咪有得搞？——Z423X5C6（傾偈） 2025年6月13號 (五) 14:16 (UTC)

啱啱加返入去，可能係同phab:T385346同埋phab:T388927有關；@Z423x5c6：係，呢個要介面管理員先至搞得到。 Shinjiman ⇔ ♨ 2025年6月16號 (一) 02:38 (UTC)

喺廣東話維基百科啟用「貢獻」入口嘅建議

粵語嘅維基媒體成員大家好，

維基媒體基金會嘅語言同產品本地化團隊建議喺你嘅維基百科啟用一個叫做「貢獻」選單嘅入口點。「貢獻」選單係一個中心地方，編輯可以喺呢度發掘同存取粵語維基百科入面所有可用嘅貢獻工具。

呢個入口點係受到維基媒體基金會嘅產品團隊合作嘅啟發，呢個工作係基於編輯發現嘅工作，驗證咗一個專用入口點嘅想法，揭示咗佢係一個一致嘅路徑畀貢獻者搵到方法去貢獻內容。

啟用呢個入口點會幫助新嘅貢獻者快速發現可用嘅工具，令佢哋可以即刻開始使用呢個工具。呢個建議嘅啟用會包括支援一小部分貢獻工具，但係個選單係設計嚟可擴充嘅，而且隨住時間嘅推移，會加入更多工具。以下係有關「貢獻」選單嘅重要資料。

邊個可以存取到呢個工具？

啟用咗之後，新手就會透過登入佢哋嘅帳戶自動存取呢個入口點。佢哋可以喺「用戶」下拉式選單入面搵到「貢獻」標籤，呢個標籤會帶佢哋去另一個選單，入面有個自導標籤，概述佢哋可以點樣貢獻內容，如下圖所示。

 

你哋仲可以喺「貢獻」選單入面睇到啲咩？

除咗新手可以撳入去探索貢獻工具嘅自助分頁之外，選單仲會包括一個「睇吓你嘅貢獻」嘅選項，畀新人睇到佢哋到目前為止嘅貢獻清單。

呢個工具會唔會取代有經驗嘅貢獻者嘅「貢獻」標籤？

唔會，用戶下拉式選單上面嘅「貢獻」標籤唔會取代你現有嘅「貢獻」標籤，除非佢哋選擇透過「特殊：貢獻」（Special:Contribute）手動存取，否則有經驗嘅貢獻者唔會喺佢哋嘅用戶下拉式選單入面睇到「貢獻」標籤。

呢個選單仲有喺邊度啟用？

呢個入口點而家可以喺超過245個維基百科頁面上面搵到，我哋收到部分維基百科嘅貢獻者嘅寶貴意見，呢個方法幫我哋提升咗佢哋嘅可發現性。其中一個重要嘅改進係令到有經驗嘅貢獻者可以選擇呢個入口點，而呢啲貢獻者仍然偏好預設嘅「貢獻」標籤。

桌面同流動裝置上面嘅新貢獻者會唔會可以存取「貢獻」選單？

喺呢個初步階段，「貢獻」選單只會畀透過瀏覽器存取維基百科嘅流動用戶使用。我哋暫時只會將佢限制畀流動瀏覽器用戶使用。

噉會唔會改變我哋維基百科入面嘅工具配置？

透過「貢獻」選單存取嘅工具設定會保持不變。例如，如果內容翻譯工具只限你維基百科入面嘅特定使用者，就算新手喺「貢獻」選單度撳一下，佢哋仍然會存取唔到呢個工具。

點解我睇唔到而家啟用咗呢個功能嘅維基百科嘅「貢獻」選單入面所有可用嘅工具？

隨住時間嘅推移，「貢獻」入面會有其他工具，無論係新嘅定係舊嘅工具。

我哋嘅維基幾時會啟用呢個功能？

如果喺2025年7月18號之前你嘅維基百科冇任何異議，我哋就會計劃部署「貢獻」入口點。

我哋歡迎大家對喺粵語維基百科提供「貢獻」選單嘅意見同問題，我哋期待你嘅回應。多謝！ UOzurumba (WMF) (傾偈) 2025年6月26號 (四) 00:50 (UTC)

Hi @UOzurumba (WMF), I don’t know if this is completely off-topic or if it counts as some sort of feedback, but I’m not sure if it’s a good idea to actively encourage translations. In my personal experience, translations (especially if it’s of a single section) often cause more problems than they solve (not just here, but also on the French Wikipedia where I also do some edits). There are a few reasons this is the case, but one major cause is a mismatch in overall article structure between the source and target Wikipedias.

(I have seen this happen even on the English Wikipedia, though merely at a copy editing level and not at a structural editing level, where an article was clearly translated from frwiki, but where the translator clearly was completely unfamiliar with frwiki conventions.)

If machine translation is involved, some people also don’t check their work afterwards (here specifically, if this isn’t a thing on other wikis); this can cause a whole load of problems, which can sometimes be very difficult to correct (in some cases, the easiest fix would be to scrap the entire translated section(s) and rewrite, which is something usually not done, partly out of respect for the translator and partly because the section(s) had been translated because it was (they were) difficult to write in the first place). Alıƨsi (傾偈) 2025年6月26號 (四) 06:37 (UTC)

Thank you @Al12si for this feedback. Your cross-wiki experience on both English and French Wikipedia provides a valuable perspective on translation challenges. However, it deviates from the communication in question, which is the proposal to enable the Contribute menu. I will clarify that the Contribute menu serves as a central access point for various contribution tools, and the translation tool is one of the many tools that will have its entry point in the Contribute menu.

You raise a relevant concern about the mismatch of article structure when translating content in sections and quality issues that can arise from translations, whether machine-assisted or manual. We're aware of the mismatch as reported here andthe team is working to resolve it.

For communities experiencing problems with machine translation (MT) quality and abuse of the support in the Content translation tool, I recommend discussing adjusting the machine translation limit, which is a mechanism that restricts the publishing of the initial automatic translation without reviewing and editing it with your community and agree on a suitable limit.

In deciding how strict the automatic translation should be, your community should consider different samples of the automatic translation as case studies and agree on a suitable threshold based on its accuracy and the extent to which translators edit the machine translation.

Once a consensus is reached on the percentage of adjustment (e.g., 99% automatic translation and 1% adjustment), you can create a Phabricator ticket like this one so that the WMF Language team can adjust the machine translation limit.

I hope my response was helpful. Please don't hesitate to ask any additional questions, and if there are no objections, we will proceed with the deployment as planned.

UOzurumba (WMF) (傾偈) 2025年7月9號 (三) 17:00 (UTC)

想請問吓「貢獻」同埋「翻譯」會唔會有粵文界面設定？ Jeffrey Kim (傾偈) 2025年6月26號 (四) 07:40 (UTC)

Hello @Jeffrey Kim,

There is a Cantonese traditional and simplified interface for it. You can translate the message strings through the following links:

• For Cantonese traditional: https://translatewiki.net/w/i.php?title=Special%3ATranslate&group=core&language=yue-hant&filter=&action=translate
• For Cantonese simplified: https://translatewiki.net/w/i.php?title=Special%3ATranslate&group=core&language=yue-hans&filter=&action=translate

Thank you! UOzurumba (WMF) (傾偈) 2025年7月15號 (二) 19:44 (UTC)

Template:N/A rowspan失效

留意到以前寫落嘅Template:N/A rowspan（跨行）失效（例子）。我睇返Template:N/A，見到最近Al12si改過，好可能有關係。呢個改動原意應該係想加多個方法處理跨行，但而家卻意外令以前寫落嘅跨行失效。如果可以改到新舊方式並存當然最好，但如果新舊方式只能存在一個，為方便兼容其他語言版本習慣（主要係英文同中文），建議恢復舊方式。 Stanley678 (傾偈) 2025年7月12號 (六) 07:35 (UTC)

多謝回報問題，已經修正咗。因為我唔知有咁嘅用法，所以冇測試到；而今知，已經寫咗落模解。 Alıƨsi (傾偈) 2025年7月12號 (六) 08:59 (UTC)

Wikidata Item and Property labels soon displayed in Wiki Watchlist/Recent Changes

(Apologies for posting in English, you can help by translating into your language)

Hello everyone, the Wikidata For Wikimedia Projects team is excited to announce an upcoming change in how Wikidata edit changelogs are displayed in your Watchlists and Recent Changes lists. If an edit is made on Wikidata that affects a page in another Wikimedia Project, the changelog will contain some information about the nature of the edit. This can include a QID (or Q-number), a PID (or P-number) and a value (which can be text, numbers, dates, or also QID or PID’s). Confused by these terms? See the Wikidata:Glossary for further explanations.

The upcoming change is scheduled for 17.07.2025, between 1300 - 1500 UTC. The change will display the label (item name) alongside any QID or PIDs, as seen in the image below:

These changes will only be visible if you have Wikidata edits enabled in your User Preferences for Watchlists and Recent Changes, or have the active filter ‘Wikidata edits’ checkbox toggled on, directly on the Watchlist and Recent Changes pages.

Your bot and gadget may be affected! There are thousands of bots, gadgets and user-scripts and whilst we have researched potential effects to many of them, we cannot guarantee there won’t be some that are broken or affected by this change.

Further information and context about this change, including how your bot may be affected can be found on this project task page. We welcome your questions and feedback, please write to us on this dedicated Talk page.

Thank you, - Danny Benjafield (WMDE) on behalf of the Wikidata For Wikimedia Projects Team. MediaWiki message delivery (傾偈) 2025年7月14號 (一) 12:46 (UTC)

｢監視清單｣ 變咗最近一個鐘

由幾日前開始（冇記低係邊日），｢監視清單｣ 雖然如常可以㨂 ｢顯示最後｣ 任何㨂得嘅時間長度，但係喺出嚟嘅畫面，｢顯示最後｣ 一定會自動變成一個鐘頭（即係再撳掣就變咗淨係出得一兩行），以前未見過咁嘅事，想問下有冇人知係呢度改咗設定，定係大台改咗嘢，同如果係大台改，係咪一個 bug（唔小心改錯嘢唔知）定有乜特別原因？麻煩哂！ Alıƨsi (傾偈) 2025年7月16號 (三) 03:04 (UTC)

搜尋功能問題

搜尋intitle:打底理論上會出到所有標題含「打底」嘅文，但現時只有一個打底 (衣物)嘅結果，點解會咁？例如intitle:香港又正常出到二千幾個結果。

根據數據庫，標題含「打底」嘅文：

• 唔打底（跳轉）
• 打底（跳轉）
• 打底 (衣物)
• 打底褲
• 無打底（跳轉）

Sohryu Asuka Langley Not Shikinami (傾偈) 2025年8月14號 (四) 01:28 (UTC)

文字大中細無效

雖則外觀畀人揀文字大中細，呢度實情無效。而其他百科有效。 HenryLi (傾偈) 2025年9月29號 (一) 12:22 (UTC)

界面譯文問題

當將篇文連Wikidata時，如果目標已經有連去粵維另一版，會有提示訊息，印象中以前係正常（唔記得係有譯好定係直接出英文版），而家係顯示：「你想連結嘅頁面已經附加咗去中央資料庫上面嘅[$1項目]，而呢個項目會連結去呢個網站嘅[[$2]]。每個網站嘅項目只可以附加一頁。請揀另一個頁面去條拎。」，明顯$1、$2參數都未有正常顯示。 Yaukasin (傾偈) 2025年10月29號 (三) 12:29 (UTC)

我喺translatewiki改咗（），不過唔肯定咁樣係咪解決到個問題。我試嘅時候佢仲係出返無空格嘅版本。 ——Z423X5C6（傾偈） 2025年10月29號 (三) 13:43 (UTC)

譯自日文

報告一下自動翻譯

翻譯版自動翻譯，譯自日文漢字名，好多都出錯，會變成另一樣嘢。大概經英文轉啲字化成拼音，再轉返做啲字，效果張三變李四咁。日文同音字超多，唔一定估得啱。同埋駁去啲詞會錯位。駁得啱位，又唔曉用返本百科題字。日文同粵文，引用數字，都放喺標點符號前便，自動翻譯會擺喺後面。

另外無論乜嘢文，有時引用位置都幾奇怪，唔會跟原文，而散落喺片語當中。 HenryLi (傾偈) 2025年10月30號 (四) 03:41 (UTC)

據我所知，自動翻譯背後應該係用Google嘅大型語言模型，而且好似係會透過英文翻譯（日英，然後英粵），導致你所講嘅問題出現。 h78c67c (傾偈) 2025年10月30號 (四) 20:33 (UTC)

同意，應該係咁。對比言語結構好有意思，涉及三種語言。

不過就翻譯，意思相差千里有時都幾麻煩，可謂唔使轉而轉，做咗多餘嘢。

例如，構成→composition?→作曲

又例如，日文寫，管子の構成は成立の事情と散逸した箇所があるため非常に複雑である。以下やや詳しく構成について述べる。化成粵文，由於創立嘅情況同埋部分部分已經失去，關子嘅結構極其複雜。以下，我哋會詳細討論佢嘅結構。

姑且唔理其他問題，關鍵字管子變咗關子。專名誤譯，若有人不察，都好難搞。 HenryLi (傾偈) 2025年10月31號 (五) 03:53 (UTC)

而家2025年，傳統網上翻譯器已經係過時產物，用AI翻譯效果好好多，相對識得兼顧上文下理，雖然依然都需要人手執（例如部份字詞唔夠粵語化），但成品已經大致可以收貨。免費而香港又用得到嘅網上AI翻譯，之前主要係Copilot（背後係GPT），最近Google有個AI Mode（背後係Gemini），雖然原意係搜尋用，但落指令叫佢幫手翻譯佢都肯做。 Jason6698 (傾偈) 2025年11月1號 (六) 02:15 (UTC)

不過百科翻譯經已用咗Google翻譯，英文百科引PC Mag話用咗 PaLM 2 Generative AI model。來源副題話With an assist from the PaLM 2 AI model, Google Translate now supports 243 languages. HenryLi (傾偈) 2025年11月3號 (一) 07:49 (UTC)

登入技術問題

我唔肯定係自己電腦定係系統問題，先報告一下。我唔係長期登入而係每次登入，但瀏覽器本身有自動記住密碼，9月登入時，用自動記住嘅密碼登入，系統話密碼錯誤，要人手入多次相同密碼另加驗證碼先至登入到。當時我覺得奇怪但無深究。今日登入前我檢查肯定密碼正確先至登入，但系統依然話密碼錯誤，依然要人手入多次相同密碼另加驗證碼先至登入到。唔知其他人有無同一問題，如果有就應該係系統問題。 Cwingsum (傾偈) 2025年12月22號 (一) 01:20 (UTC)

Feminism and Folklore 2026 starts soon

請幫手去譯做你嘅語言

Invitation to Organize Feminism and Folklore 2026

Dear Wiki Community,

We are pleased to invite Wikimedia communities, affiliates, and independent contributors to organize the Feminism and Folklore 2026 writing competition on your local Wikipedia.

The international campaign will run from 1 February to 31 March 2026 and aims to improve coverage of feminism, women’s histories, gender-related topics, and folk culture across Wikipedia projects.

About the Campaign

Feminism and Folklore is a global writing initiative that complements the Wiki Loves Folklore photography competition. While Wiki Loves Folklore focuses on visual documentation, this writing campaign addresses the gender gap on Wikipedia by improving encyclopedic content related to folk culture and marginalized voices.

What Can Participants Write About?

Communities can contribute by creating, expanding, or translating articles related to:

• Folk festivals, rituals, and celebrations
• Folk dances, music, and traditional performances
• Women and queer figures in folklore
• Women in mythology and oral traditions
• Women warriors, witches, and witch-hunting narratives
• Fairy tales, folk stories, and legends
• Folk games, sports, and cultural practices

Participants may work from curated article lists or generate new article suggestions using campaign tools.

How to Sign Up as an Organizer

Organizers are requested to complete the following steps to register their community:

1. Create a local project page on your wiki (see sample)
2. Set up the campaign using the CampWiz tool
3. Prepare a local article list and clearly mention:
   • Campaign timeline
   • Local and international prizes
4. Request a site notice from local administrators (see sample)
5. Add your local project page and CampWiz link to the Meta project page

Campaign Tools

The Wiki Loves Folklore Tech Team has introduced tools to support organizers and participants:

• Article List Generator by Topic – Helps identify articles available on English Wikipedia but missing in your local language Wikipedia. The tool allows customized filters and provides downloadable article lists in CSV and wikitable formats.
• CampWiz – Enables communities to manage writing campaigns effectively, including jury-based evaluation. This will be the third year CampWiz is officially used for Feminism and Folklore.

Both tools are now available for use in the campaign. Click here to access the tools

Learn More & Get Support

For detailed information about rules, timelines, and prizes, please visit the Feminism and Folklore 2026 project page.

If you have any questions or need assistance, feel free to reach out via:

• Meta talk page
• Email us using details on the contact page.

Join Us

We look forward to your collaboration and coordination in making Feminism and Folklore 2026 a meaningful and impactful campaign for closing gender gaps and enriching folk culture content on Wikipedia.

Thank you and best wishes,

Feminism and Folklore 2026 International Team

---

Stay connected:  

Invitation to Host Wiki Loves Folklore 2026 in Your Country

請幫手去譯做你嘅語言

Hello everyone,

We are delighted to invite Wikimedia affiliates, user groups, and community organizations worldwide to participate in Wiki Loves Folklore 2026, an international initiative dedicated to documenting and celebrating folk culture across the globe.

About Wiki Loves Folklore

Wiki Loves Folklore is an annual international photography competition hosted on Wikimedia Commons. The campaign runs from 1 February to 31 March 2026 and encourages photographers, cultural enthusiasts, and community members to contribute photographs that highlight:

• Folk traditions and rituals
• Cultural festivals and celebrations
• Traditional attire and crafts
• Performing arts, music, and dance
• Everyday practices rooted in folk heritage

Through this campaign, we aim to preserve and promote diverse folk cultures and make them freely accessible to the world.

Project page on Wikimedia Commons

Host a Local Edition

As we celebrate the eight edition of Wiki Loves Folklore, we warmly invite communities to organize a local edition in their country or region. Hosting a local campaign is a great opportunity to:

• Increase visibility of your region’s folk culture
• Engage new contributors in your community
• Enrich Wikimedia Commons with high-quality cultural content

Sign up to organize:

If your team prefers to organize the competition in either February or March only, please feel free to let us know.

If you are unable to organize, we encourage you to share this opportunity with other interested groups or organizations in your region.

Get in Touch

If you have any questions, need support, or would like to explore collaboration opportunities, please feel free to contact us via:

• The project Talk pages
• Email: support@wikilovesfolklore.org

We are also happy to connect via an online meeting if your team would like to discuss planning or coordination in more detail.

Warm regards,

The Wiki Loves Folklore International Team

MediaWiki message delivery (傾偈) 2026年1月18號 (日) 13:21 (UTC)

Migration to Parsoid

Read this in another language

Hello everyone! I am glad to inform you that as the next step in the Parser Unification project, Parsoid will soon be turned on as the default article renderer on your wiki. We are gradually increasing the number of wikis using Parsoid, with the intention of making it the default wikitext parser for MediaWiki's next long-term support release. This will make our wikis more reliable and consistent for editors, readers, and tools to use, as well as making the development of future wikitext features easier.

If this disrupts your workflow, don’t worry! You can still opt out through a user preference or turn Parsoid off on the current page using the Tools submenu, as described in the Extension:ParserMigration documentation.

There is more information about our roll-out strategy available, including the testing done before we turn on Parsoid for a new wiki.

To report bugs and issues, please look at our known issues documentation and if you found a new bug please create a phab ticket and tag the Content Transform Team in Phabricator.

Content Transform Team 2026年2月18號 (三) 00:42 (UTC)