維基辭典:城市論壇
粵語：喺伊到唔一定要用粵語，不過最好都係用番粵語啦，因為會快啲有人覆。
English：You may use any language here, but it is better if you use Cantonese here since you would get a reply sooner.
（新版）歸檔：Special:PrefixIndex/維基辭典:城市論壇/歸檔/
睇以往討論：Special:PrefixIndex/Project:城市論壇/
預製件[編輯]
請問有冇得設置一d預製格式，喺開新版嘅版面度？即係開新版嘅時候，個輸入框呢處係自動有咗格式，而唔係空白一片。我見第啲wiktionary，譬如德文版英文版，喺工具欄附帶一d一click即有嘅架生。如果有得整定d預製件個話，可以慳返各位編輯少少時間掛。--Roy17 (talk) 10:52, 18 August 2018 (UTC)
wishlist[編輯]
- 求引進HotCat. --Leiem (傾偈) 2018年11月21號 (三) 15:16 (UTC)
- Cat-a-lot
- d:Q14048022 Template:Sp-contributions-footer
- CharInsert
- Gadget-UTCLiveClock --Roy17 (傾偈) 2018年11月21號 (三) 18:46 (UTC)
- MediaWiki:Recentchangestext--Hello903hello (傾偈) 2018年11月22號 (四) 03:51 (UTC)
- 各項政策--Hello903hello (傾偈) 2018年11月25號 (日) 14:27 (UTC)
- 1、3搞掂--Hello903hello (傾偈) 2019年1月10號 (四) 09:36 (UTC)
版名[編輯]
呢度會唔會跟返其它維基嘅做法？英維係叫做 "Beer parlour" ，建議呢版講政策嘅可以改名做『啤酒廳』。 Shinjiman (傾偈) 2018年11月19號 (一) 11:01 (UTC)
- 冇意見。不如整d特色嘢，叫「茶樓」？:D--Roy17 (傾偈) 2018年11月19號 (一) 16:19 (UTC)
- 嗰邊其實分咗做Information desk（求助）、Tea room（辭條）、Etymology scriptorium（語源）、Beer parlour（政策）、同Grease pit（技術），但呢度照計唔使分散到噉--Hello903hello (傾偈) 2018年11月20號 (二) 06:59 (UTC)
- 我覺得「茶樓」呢個建議幾好。Jonashtand (傾偈) 2019年11月9號 (六) 15:03 (UTC)
政策：關於辭條參考嘅格式[編輯]
而家辭條參考一啲擺喺語言小節道，第啲另開新小節。後者會搞到唔知便條參考係for邊個語文（噉係因為維基辭典唔用<ref/>標籤）。最好就係訂立統一做法，唔係嘅話會亂七八糟。--Hello903hello (傾偈) 2018年12月7號 (五) 13:58 (UTC)
- 英文維基辭典我唔清楚，但法文維基辭典就係每個語言小節後面分別加參考嘅。例1 例2 實際操作可以用
<ref group="乜乜乜">同埋<references group="乜乜乜"/>。補充澄清：我贊成嘅做法係每個語言小節後面分別加參考。【粵語文學大使殘陽孤侠】粵維辭典起錨！ 2018年12月21號 (五) 19:44 (UTC)
提議將en:Module:yue-pron搬過來[編輯]
粵文有好多種拼音，有國際音標表記更有利於學習。提議將en:Module:yue-pron搬過來，模仿en:Template:zh-pron寫一個Template:yue-pron。也建議將en:Module:wuu-pron、en:Module:nan-pron等都搬過來，分別建立模板。--唐吉訶德的侍從 (傾偈) 2019年8月12號 (一) 15:53 (UTC)
模組編輯有移位[編輯]
唔知有冇人亦都遇到咁嘅問題，就係響編輯緊模組陣時，明明光標係停喺一個地方，打出嚟嘅時候又會行到其他地方，或者揀中一笪地方要刪除，結果又刪咗其他地方。唔知咁樣要點解決。--Sayonzei (傾偈) 2019年12月23號 (一) 11:24 (UTC)
機械人政策/Bot Policy[編輯]
我寫起咗Wiktionary:機械人，建議通過做政策，容許機械人喺道運作。Ping最近有編輯嘅
@Marcus Mac 2002, Z423x5c6, Sun8908, and Westmother:。H78c67c (傾偈) 2021年2月1號 (一) 20:04 (UTC)
- 對呢個wiki有幫助嘅政策應該點都好嘅。對於個政策，我覺得起碼要寫埋運作者需要有嘅操守。即係好似英文嗰邊噉，而家「唔接受嘅用途」感覺唔係好帶出到機械人一定要係有用同埋唔會破壞wiki嘅重點。--Sun8908 (傾偈) 2021年2月2號 (二) 09:19 (UTC)
超過兩個禮拜無異議，升格做政策。H78c67c (傾偈) 2021年3月14號 (日) 20:19 (UTC)
Wiki Loves Folklore 2021 is back![編輯]
請幫手去譯做你嘅語言
You are humbly invited to participate in the Wiki Loves Folklore 2021 an international photography contest organized on Wikimedia Commons to document folklore and intangible cultural heritage from different regions, including, folk creative activities and many more. It is held every year from the 1st till the 28th of February.
You can help in enriching the folklore documentation on Commons from your region by taking photos, audios, videos, and submitting them in this commons contest.
Please support us in translating the project page and a banner message to help us spread the word in your native language.
Kind regards,
Wiki loves Folklore International Team
MediaWiki message delivery (傾偈) 2021年2月6號 (六) 13:25 (UTC)
機械人請求：H78c67c-bot[編輯]
- 操作者 / Operator：User:H78c67c
- 自動或手動協助？ / Automatic or manually assisted?：手動協助（AWB）
- 程式語言 / Programming language：N/A（AWB）
- 任務 / Task：大規模清理，包括用langue模取代lang-xx模、big模取代<big><big>同埋移除多餘嘅wikilink顯示文字（即[[foo|foo]] -> [[foo]]）。
- 編輯時段 / Edit period：唔定時、分批一次性
- 編輯頻率 / Edit rate：最多每分鐘10次
- 機械人戶口 / Bot account：Special:CentralAuth/H78c67c-bot
- 源碼 / Source code：N/A
--H78c67c (傾偈) 2021年3月14號 (日) 20:32 (UTC)
開唔到文[編輯]
字：genial
內容（請入去編輯模式睇）：
== {{langue|es}} == === 發音 === * {{es-IPA}} === 意思 === # {{PoS|lang=es|PoS=adj}}好。 # {{PoS|lang=es|PoS=adj}}聰明、醒目。
以前都係噉開架喎，點解而家開唔到？
--Z423x5c6 (傾偈) 2021年4月11號 (日) 19:21 (UTC)
@H78c67c:過濾器4有問題，=={{langue過到，== {{langue多個空格就過唔到，麻煩搞搞佢，唔該嗮。--Z423x5c6 (傾偈) 2021年4月11號 (日) 19:28 (UTC)
新法蘭西拼音方案唔妥，系統式撈亂咗穗港發音。[編輯]
陰平聲（第一聲）個聲調，家陣香港音調值一律係「55」，廣州音多數係「51」。然而，喺呢度，個新法蘭西系統會寫話係「廣州音」，而實際標「香港音」。建議參考官話維基辭典，模仿普通話同國語嗰種分列格式嚟處理。正如大家都知道，香港嘅電視台同廣州嗰啲兩者之間，後生嘅新聞報道員，發音分別好明顯；勁老嘅就聽落差唔多。隨着歲月流逝，穗港粵語都變咗，不過廣州嘅改得少啲。不如寫啲指令入個程式道，一刀切釐清呢個聲嘅簡單分野。若果仔細睇，重可以發現啲極之複雜嘅半隨機變調，唔理為妙。（https://www.cuhk.edu.hk/ics/journal/articles/v02p081.pdf）110.174.132.162 2021年6月2號 (三) 10:03 (UTC)
- 新法蘭西拼音方案經過討論已經決定咗會棄用。H78c67c (傾偈) 2021年6月7號 (一) 02:11 (UTC)
- 多謝提醒。本人日後亦會避用。110.174.132.162 2021年6月14號 (一) 10:00 (UTC)
- 另外，請依然用緊上述系統嘅人，加入新資料時，唔好再標錯城市。--110.174.132.162 2021年12月4號 (六) 08:24 (UTC)
- 啱啱將模組嘅城市名由廣州改成香港，暫時阻止佢誤人子弟。期望有識得編碼嘅朋友徹底改善。--110.174.132.162 2022年3月31號 (四) 06:40 (UTC)
- 另外，請依然用緊上述系統嘅人，加入新資料時，唔好再標錯城市。--110.174.132.162 2021年12月4號 (六) 08:24 (UTC)
- 多謝提醒。本人日後亦會避用。110.174.132.162 2021年6月14號 (一) 10:00 (UTC)
Wikidata Lexemes[編輯]
維基數據技術部討論緊點樣喺維基辭典度用維基數據，好似維基百科啲自動明細模噉，麻煩大家過去望望。 --Deryck Chan (傾偈) 2021年10月25號 (一) 10:10 (UTC)
起嘢同防拆設施比例反常……[編輯]
請管理員同事務員營運時用下常識。呢度長期都拍烏蠅，重猛咁起啲防禦設備嚟做乜呢？倒不如花啲時間，由隔籬搬多幾件建築工具過嚟啦。啱啱發覺，跳轉模亦已經被禁用，起碼係對於無名氏而言。--110.174.132.162 2021年12月4號 (六) 08:13 (UTC)
- 正正因為呢度唔多人維修同清理內容，我之前設立咗幾個過濾器，隔走唔符合Project:PCFL嘅內容，減輕清理負擔。 H78c67c (傾偈) 2021年12月7號 (二) 04:58 (UTC)
又係過濾器問題[編輯]
{{lang-yue}}
{{zh-see|劍}}
...然後過濾器唔俾我save。點搞？Deryck Chan (傾偈) 2021年12月31號 (五) 11:53 (UTC)
- @Deryck Chan: 要用
== {{langue|代碼}} ==先得。 H78c67c (傾偈) 2021年12月31號 (五) 23:40 (UTC)- 好。我諗諗下，都係改做「通用資料」。 Deryck Chan (傾偈) 2022年1月1號 (六) 17:33 (UTC)
Wiki Loves Folklore is back![編輯]
請幫手去譯做你嘅語言
You are humbly invited to participate in the Wiki Loves Folklore 2022 an international photography contest organized on Wikimedia Commons to document folklore and intangible cultural heritage from different regions, including, folk creative activities and many more. It is held every year from the 1st till the 28th of February.
You can help in enriching the folklore documentation on Commons from your region by taking photos, audios, videos, and submitting them in this commons contest.
You can also organize a local contest in your country and support us in translating the project pages to help us spread the word in your native language.
Feel free to contact us on our project Talk page if you need any assistance.
Kind regards,
Wiki loves Folklore International Team
--MediaWiki message delivery (傾偈) 2022年1月9號 (日) 13:15 (UTC)
[編輯]
Dear community members,
Greetings from the EWOC Newsletter team and the education team at Wikimedia Foundation. We are very excited to share that we on tenth years of Education Newsletter (This Month in Education) invite you to join us by subscribing to the newsletter on your talk page or by sharing your activities in the upcoming newsletters. The Wikimedia Education newsletter is a monthly newsletter that collects articles written by community members using Wikimedia projects in education around the world, and it is published by the EWOC Newsletter team in collaboration with the Education team. These stories can bring you new ideas to try, valuable insights about the success and challenges of our community members in running education programs in their context.
If your affiliate/language project is developing its own education initiatives, please remember to take advantage of this newsletter to publish your stories with the wider movement that shares your passion for education. You can submit newsletter articles in your own language or submit bilingual articles for the education newsletter. For the month of January the deadline to submit articles is on the 20th January. We look forward to reading your stories.
Older versions of this newsletter can be found in the complete archive.
More information about the newsletter can be found at Education/Newsletter/About.
For more information, please contact spatnaik模:@wikimedia.org.
提議：將{{Yue-rom}}個模分清楚係邊個片嘅粵語區音[編輯]
最近發現粵語區唔止得一個城市有當地嘅特色發音。點解{{Yue-rom}}呢個模淨得個“廣州音”而冇定義到其它地區（例如廣東嘅粵西一帶或廣西白話、平話片）嘅城市定義發音？建議城市名有得修改成其它片。--PQ77wd (傾偈) 2022年2月19號 (六) 09:36 (UTC)
- 要修改「模組:Yue-rom」；本用户唔識得編碼，只夠本事改兩個字。--110.174.132.162 2022年3月31號 (四) 06:46 (UTC)
- 想問應該改成點先啱？--Sun8908 (傾偈) 2022年5月12號 (四) 08:55 (UTC)
- 我家下將模組:Yue-rom呢個模組第29行改咗兼喺第10行聲明咗新嘅變量，睇下得唔得喇。--PQ77wd (傾偈) 2022年5月25號 (三) 14:44 (UTC)
- @PQ77wd、@Sun8908：我提議直接棄用 Yue-rom 。zh-pron 有齊各種通用拼音方案，亦都可以容易加各地讀音。H78c67c (傾偈) 2022年6月4號 (六) 05:43 (UTC)
Community Wishlist Survey 2023 opens in January[編輯]
請幫手去譯做你嘅語言
(There is a translatable version of this message on MetaWiki)
你好
The Community Wishlist Survey (CWS) 2023, which lets contributors propose and vote for tools and improvements, starts next month on Monday, 23 January 2023, at 18:00 UTC and will continue annually.
We are inviting you to share your ideas for technical improvements to our tools and platforms. Long experience in editing or technical skills is not required. If you have ever used our software and thought of an idea to improve it, this is the place to come share those ideas!
The dates for the phases of the Survey will be as follows:
- Phase 1: Submit, discuss, and revise proposals – Monday, Jan 23, 2023 to Sunday, Feb 6, 2023
- Phase 2: WMF/Community Tech reviews and organizes proposals – Monday, Jan 30, 2023 to Friday, Feb 10, 2023
- Phase 3: Vote on proposals – Friday, Feb 10, 2023 to Friday, Feb 24, 2023
- Phase 4: Results posted – Tuesday, Feb 28, 2023
If you want to start writing out your ideas ahead of the Survey, you can start thinking about your proposals and draft them in the CWS sandbox.
We are grateful to all who participated last year. See you in January 2023!
多謝！ Community Tech, STei (WMF) 2022年12月15號 (四) 16:44 (UTC)
Global ban for PlanespotterA320/RespectCE[編輯]
Per the Global bans policy, I'm informing the project of this request for comment: m:Requests for comment/Global ban for PlanespotterA320 (2) about banning a member from your community. Thank you.--Lemonaka (talk) 21:40, 6 February 2023 (UTC)
Your wiki will be in read only soon[編輯]
維基百科基金會將會測試第一同埋第二個數據中心嘅轉換。 咁樣就會確保維基百科同其他維基媒體維基項目，即使喺發生意外之後，仍然可以保持在線。 為咗確保一切正常運作，維基媒體技術部門計劃進行測試，保證系統能夠可靠噉喺兩個數據中心之間切換。測試需要好多個團隊做好準備，隨時可以修復任何突發嘅問題。
1 三月 所有流量會切換到新數據中心， 測試會喺 14:00 UTC開始。
因為MediaWiki有某啲限制，切換期間都一定要停止所有嘅編輯。 我哋諒解今次測試帶來嘅不便，我哋喺度響未來度努力減少同樣嘅情況。
喺一段好短嘅時間，你可以閱讀，但係響短時間之內唔可以編輯所有啲維基。
- 10月27號當日嘅其中一個鐘之內唔可以編輯所有啲維基。
- 嗰陣時如果你嘗試編輯文章或者保存更改，你就會睇到一個錯誤信息。 我哋希望過程中唔會有編輯丟失，但係我哋保證唔到呢點。 如果你見到錯誤訊息，噉就請等到一切恢復正常， 然後你就應該可以保存你嘅編輯。 之但係，我哋建議你複製你嘅改動，以防萬一。
其它影響：
- 後台背景作業會變慢，有啲可能會被丟棄。 紅色連結可能更新得無平時咁快。 如果您開咗一版已經喺第度有連結嘅文章，個連結變色要耐過平時。 有啲長時間運行嘅腳本將不得不停止。
- We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
- GitLab will be unavailable for about 90 minutes.
Trizek (WMF) (討論) 2023年2月27號 (一) 21:21 (UTC)
Wikimania 2023 Welcoming Program Submissions[編輯]
Seeking volunteers for the next step in the Universal Code of Conduct process[編輯]
Hello,
As follow-up to the message about the Universal Code of Conduct Enforcement Guidelines by Wikimedia Foundation Board of Trustees Vice Chair, Shani Evenstein Sigalov, I am reaching out about the next steps. I want to bring your attention to the next stage of the Universal Code of Conduct process, which is forming a building committee for the Universal Code of Conduct Coordinating Committee (U4C). I invite community members with experience and deep interest in community health and governance to nominate themselves to be part of the U4C building committee, which needs people who are:
- Community members in good standing
- Knowledgeable about movement community processes, such as, but not limited to, policy drafting, participatory decision making, and application of existing rules and policies on Wikimedia projects
- Aware and appreciative of the diversity of the movement, such as, but not limited to, languages spoken, identity, geography, and project type
- Committed to participate for the entire U4C Building Committee period from mid-May - December 2023
- Comfortable with engaging in difficult, but productive conversations
- Confidently able to communicate in English
The Building Committee shall consist of volunteer community members, affiliate board or staff, and Wikimedia Foundation staff.
The Universal Code of Conduct has been a process strengthened by the skills and knowledge of the community and I look forward to what the U4C Building Committee creates. If you are interested in joining the Building Committee, please either sign up on the Meta-Wiki page, or contact ucocproject
wikimedia.org by May 12, 2023. Read more on Meta-Wiki.
Best regards,
Xeno (WMF) 2023年4月26號 (三) 19:01 (UTC)
Selection of the U4C Building Committee[編輯]
The next stage in the Universal Code of Conduct process is establishing a Building Committee to create the charter for the Universal Code of Conduct Coordinating Committee (U4C). The Building Committee has been selected. Read about the members and the work ahead on Meta-wiki.
-- UCoC Project Team, 2023年5月27號 (六) 04:21 (UTC)
Announcing the new Elections Committee members[編輯]
Hello there,
We are glad to announce the new members and advisors of the Elections Committee. The Elections Committee assists with the design and implementation of the process to select Community- and Affiliate-Selected trustees for the Wikimedia Foundation Board of Trustees. After an open nomination process, the strongest candidates spoke with the Board and four candidates were asked to join the Elections Committee. Four other candidates were asked to participate as advisors.
Thank you to all the community members who submitted their names for consideration. We look forward to working with the Elections Committee in the near future.
On behalf of the Wikimedia Foundation Board of Trustees,
RamzyM (WMF) 2023年6月28號 (三) 18:00 (UTC)
Review the Charter for the Universal Code of Conduct Coordinating Committee[編輯]
Hello all,
I am pleased to share the next step in the Universal Code of Conduct work. The Universal Code of Conduct Coordinating Committee (U4C) draft charter is now ready for your review.
The Enforcement Guidelines require a Building Committee form to draft a charter that outlines procedures and details for a global committee to be called the Universal Code of Conduct Coordinating Committee (U4C). Over the past few months, the U4C Building Committee worked together as a group to discuss and draft the U4C charter. The U4C Building Committee welcomes feedback about the draft charter now through 22 September 2023. After that date, the U4C Building Committee will revise the charter as needed and a community vote will open shortly afterward.
Join the conversation during the conversation hours or on Meta-wiki.
Best,
RamzyM (WMF), on behalf of the U4C Building Committee, 2023年8月28號 (一) 15:36 (UTC)
== Opportunities open for the Affiliations Committee, Ombuds commission, and the Case Review Committee ==[編輯]
Hi everyone! The Affiliations Committee (AffCom), Ombuds commission (OC), and the Case Review Committee (CRC) are looking for new members. These volunteer groups provide important structural and oversight support for the community and movement. People are encouraged to nominate themselves or encourage others they feel would contribute to these groups to apply. There is more information about the roles of the groups, the skills needed, and the opportunity to apply on the Meta-wiki page.
On behalf of the Committee Support team,
維基媒體基金會2024年度理事遴選規則章程公佈暨咨詢啟事[編輯]
敬啟者：
維基媒體基金會理事會成員嘅遴選規則章程已經出咗，麻煩睇睇，然後畀啲意見，畀意見嘅限期係2023年10月29號。呢份遴選規則章程係根據選舉委員會往年用開嘅舊版本，新版本會用喺2024年度嘅理事會遴選。及早畀意見，可以幫選舉委員會提供更暢順，更妥善嘅遴選過程，章程可以喺元維基搵到。祝
安好。
選舉委員會主席
陳君婷（Katie Chan）謹上
2023年10月17號 (二) 01:13 (UTC)
刪走新法蘭西粵拼[編輯]
宜家有五百幾條辭條（[1]）用到模:新法蘭西標示新法蘭西粵語拼音方案，但係新法蘭西基本上無人用，喺維基之外幾乎無關注度。2019年喺維基百科有相關嘅討論（[2]），嗰時嘅結論係只保留百科篇文，盡量避免用呢個方案做主要標音。我認為2019年嘅論據都適用於維基辭典，因此提議刪走模:新法蘭西同辭條上嘅新法蘭西標示。 香蕉紳士 (傾偈) 2023年10月20號 (五) 10:20 (UTC)
其實係成個粵維嘅問題，有必要齊心合力剷走晒過去積落嚟嘅「粵維毒瘤」[編輯]
啱先尋日同今日，大家好多人喺TG群度，都異口同聲認為本來好地地嘅「史杜列治」（「丹尼爾·史杜列治」）畀人改咗做「屎塔」——「史塔列治」好離譜，管理員亦啱啱幫手搬咗版。不過呢個唔係個別問題，唔係單一事件。睇番改名嗰位人兄「WKDx417」，佢喺丹尼爾·史杜列治嘅編輯歷史度留言話「Sturridge嘅u字發/ʌ/音，唔係發/u/音」，呢一點經過大家查證，已經完全證實佢嘅講法係錯嘅。同時，佢又喺史杜列治嘅編輯歷史度留言話「其實正音係史塔列治，廣州當地媒體係噉嗌，而且同原音唔係相差好遠」，呢一點正正就係反映一啲舊粵維廣州編輯嘅唔正常心態而引致嘅一股歪風——就係睇香港傳媒唔順超，覺得香港人不學無術，亂咬啲香港譯名係「病毒音」、「歪音」，將啲正正常常又普及嘅粵語譯名改到不倫不類，突顯自己先識嘢噉款。相反，有啲跟咗普通話嘅名，明明有其他啱粵語名嘅選擇，但係反而嗰啲就唔理。
呢種唔正常心態，已曾經長期盤據粵維同粵維詞典、當粵維同粵維詞典係佢自己私竇嘅「殘陽孤侠」最最嚴重，甚至可以話係喺粵維上以「病毒音」、「歪音」呢啲冤罪嚟屈香港譯名嘅第一號人物。例如「舒拉寶娃」明明完全啱粵音、粵譯原理，但係「殘陽孤侠」就老屈佢話「病毒音譯名嘅概率高達百分之85」，話要用同普通話譯名一樣嘅「莎拉波娃」先至唔係咩「病毒音」喎——雖然「莎拉波娃」未致於好違反粵音，但係粵語傳媒同埋粵語人講嘢，用「舒拉寶娃」絕對係大多數。而「殘陽孤侠」係都唔理其他人點反對，夾硬將篇文搬版去「莎拉波娃」，後來到2021年喺其他編輯努力下先回復正常。又例如喺Talk:頭版度，有編輯見到時人時事用同大陸譯法一致嘅「沙特阿拉伯」，而唔係以前多數粵語傳媒本來叫開嘅「沙地阿拉伯」，慨嘆連粵維都唔用粵名，「殘陽孤侠」就已經咬人話：「大佬，唔好下下都以為得香港譯名先至係粵名」，已經反映出佢仇視港譯嘅不良態度。
而泡製出「屎塔」譯名嘅「WKDx417」唔單止發言支持「殘陽孤侠」呢老屈，仲係2015年將「舒拉寶娃」搬版去「莎拉波娃」嘅實際執行者。「WKDx417」嘅發言仲要語氣好惡咁話『我呢次提出搬係解決上面嘅尊港抑粵問題。要將Sharapova改譯做莎拉波娃係因為「舒拉寶娃」個「舒」同「寶」字同原音唔似，加上「莎拉波娃」四個字嘅讀音同廣州音唔係差好遠。假設WIKICANTONA話舒拉寶娃太出名嘅話，噉我哋廣州電視台叫嘅「莎拉波娃」唔出名啊（大佬，電視台講嘅都係粵語，都係講「莎拉波娃」個名）？吓？真係離嗮祖宗120代譜，廣州都係講粵語㗎。好唔好？』充份見證佢哋嘅無理取鬧，同時又充份引證我指出嘅關鍵：粵維上唔少譯名問題，在於有個別嘅人自己心態唔正常，睇香港傳媒唔順超，覺得香港人不學無術，亂咬啲香港譯名係「病毒音」、「歪音」，將啲正正常常又普及嘅粵語譯名改到不倫不類，突顯自己先識嘢噉款，絕對係歪風。
好希望粵維可以眾志成城，認真審視番以前一啲受到歪風影響而出現嘅問題。除咗譯名上故意歪批港譯，睇香港傳媒唔順超，亂咬啲香港譯名係「病毒音」、「歪音」，將啲正正常常又普及嘅粵語譯名改到不倫不類，但係跟咗普通話譯法嗰啲嚴重問題反而就唔理之外，「殘陽孤侠」等曾經長期盤據粵維（包括粵維百科同粵維詞典）嘅一班人仲帶出以下非常嚴重嘅重大問題：
1.老屈人哋寫嘅粵文唔係粵文，話係「國維行話」——有啲畀佢哋聲稱係「國維行話」（淨係呢四個字都睇死人，總之係咬人寫咗「國語」而唔係粵文啦），其實粵語都會好自然咁講，例如話「個註腳、張列表、條條目」等等。你可以話：「同一個粵維上呢文嘅格式希望一致啲，所以我哋com好咗一個統一共識，請大家跟呢個。」噉講OK。但係佢哋搞出嚟嘅「傑作」係：逢親有人一寫親後者，就彈系統通知老屈佢唔係寫粵文，甚至唔畀佢submit，呢樣超超超超超級乞人憎。
2.有正常粵文唔寫，信晒「曾焯文」之流嘅神棍呃，寫埋晒啲穿鑿附會嘅所謂「古字」、「本字」，但其實係錯別字火星文。例如將「嘅」改做咩「其、丌、忌」嗰啲，唔係叫「Choice of Chinese characters」，而係叫「亂寫錯別字、火星文之餘，仲要大大聲去話啲錯別字火星文先係『啱』，係你啲凡夫俗子唔識嘢」，完全係反智無極限。
3.第三，啲自創小眾拼音文字，其實唔適合做百科。到咗今時今日，粵維詞典都仲有大大大大大堆「新法躝西」喺度，冇人剷走。
每次見到呢三坺嘢，就算本來大好心情都即刻超低落。畀呢啲情況擴散，只會干擾正常粵文嘅語庫數據，誤導人哋以爲正常粵文應該噉寫，遺禍無窮。堪稱係過去積落嚟嘅「粵維毒瘤」。
如果話曾經衰過，但係而家粵維嘅人都萬眾同心，整理番好佢，改走番啲漏網之魚，大家互相支持嘅，噉本來都好。但實際上唔係，過去積落嚟嘅大大大大大堆毒瘤冇邊個編輯會去割番走。而且，繼續搞呢三類破壞嘅人仲持續出沒，特別係第二種。佢哋出沒，絕大部份編輯都唔理，然後佢哋得寸進尺，有好少數人睇唔過眼想整理番好嘅，佢哋就郁啲整理番好佢嘅人，然後其他編輯都唔會幫番道理、幫番想整理番好佢嘅人，繼續縱容啲破壞者。噉嘅粵維，keep住落去，只會成爲粵文嘅反面敎材，仲要吹捧佢、等啲人學粵文嗰陣走去學咗粵維啲毒瘤嘅話，就眞係誤人子弟、搞軭粵文、遺害萬年。
抱歉講咗啲掃興嘢，但係眞心非常非常非常非常非常希望粵維可以改晒呢三點，等佢成爲粵文嘅助力，而唔係阻力。如果有心做實事，眼前啲毒瘤多到咁嘅樣，係咪應該發起大型運動，等大家一齊眾志成城改正番晒、剷走晒佢？首先全體管理員身體力行，每人每日鏟五個或十個毒瘤（包括刪走啲「新法躝西」，將啲僞本字火星文改番做正常嘅粵文等等），並呼籲每個粵維人（甚至非粵維人）一齊參與。如果幾年前決定已經開始噉樣做，相信到而家已經有一定成果。好喇，之前冇做到，其實可唔可以由而家呢一刻就發起，係噉幾年後，都應該有一定嘅成果。111.255.209.226 2023年10月23號 (一) 10:42 (UTC)
(同時發表到Wikipedia:管理員留言板#「史塔列治」搬去「史杜列治」)
The Vector 2022 skin as the default in three weeks?[編輯]
Read this in your language • 請幫手去譯做你嘅語言 • Please tell other users about these changes
Hello. I'm writing on behalf of the Wikimedia Foundation Web team. In two weeks, we would like to make the Vector 2022 skin the default on this wiki.
If you prefer keeping the current skin select "Vector legacy (2010)" on the appearance tab of the global preferences and save the change. We encourage you to give the new skin a try, though.
Since I last came to you with this question, many things have changed. The skin is now the default on most Wikipedias, and all logos are done! We have also made some tweaks in the skin itself. Below is the text I've sent to you once, but I'm sending it again, just slightly edited, for those who haven't seen it.
If you know what this is about, jump straight to the section "Our plan":
It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy as a local (but not global) preference. Logged-in users can at any time switch to any other skin. No changes are expected for these skins.
- Top of an article
-
Vector legacy (current default)
-
Vector 2022
- A section of an article
-
Vector legacy (current default)
-
Vector 2022
About the skin[編輯]
[Why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were 14 years ago. Since then, new users have begun using the Internet and Wikimedia projects in different ways. The old Vector does not meet their needs.
[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. The PHP code in the other available skins has been reduced by 75%. The project has also focused on making it easier to support gadgets and use APIs.
[Changes in a nutshell] The skin introduces changes that improve readability and usability. The new skin does not remove any functionality currently available on the Vector skin.
- The limited width and pin-able menus allow to adjust the interface to the screen size, and focus on editing or reading. Logged-in and logged-out users may use a toggle button to keep the full width, though.
- The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
- The new table of contents makes it easier to navigate to different sections. Readers and editors jump to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
- The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the tested wikis.
- The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.
[Customize this skin] It's possible to configure and personalize our changes. We support volunteers who create new gadgets and user scripts. Check out the repository for a list of currently available customizations and changes, or add your own.
Our plan[編輯]
If no large concerns are raised, we plan on deploying on 14 November. If you'd like to ask our team anything, if you have questions, concerns, or additional thoughts, please comment in any language. If this is the first comment to my message, make sure to ping me. We will gladly answer! Also, check out our FAQ. Thank you! SGrabarczuk (WMF) (傾偈) 2023年10月26號 (四) 01:09 (UTC)
- @SGrabarczuk (WMF): This is a general concern (i.e., not yue-specific) but devs should test this skin on portrait monitors (eg 1080p, but rotated, i.e. 1080x1920 as opposed to 1920x1080), which are relatively common in editorial circles (i.e., people who actually do editing), to see how bad this skin has become. The skin was not too bad when it was first released, but it was modified afterwards to have side bars on both the left and right sides, making the skin unusable on portrait monitors.
- How bad is it? A while ago, on yuewiki I actually switched to Timeless because Vector was already bad; Vector 2022 was worse. If you want to see how bad the home page (on yuewiki) looks I can upload a screenshot.
- I find the lack of proper usability testing a serious concern. Wikimedia devs seem to have a very fixed idea of what’s normal in the wild and aren’t open to the idea that certain seemingly out-of-date use cases might actually be important. This is “design fixation” and isn’t good for accessibility. Al12si (傾偈) 2023年10月26號 (四) 01:41 (UTC)