跳至內容

Wikipedia:Duâi chéu â/Archive 2

對Wikipedia
Archive
Cī bĭk hiĕk-méng sê gô-dā̤ tō̤-lâung gì còng-dáung. Kī-dâe̤ng nṳ̄ ng-tĕ̤ng piĕng-cék cī siŏh hiĕk. Ṳ̀-guō nṳ̄ hĭ-uông huák kī sĭng gì tō̤-lâung hĕ̤k-chiā tṳ̀ng-kī hiêng-iū gì tō̤-lâung, kī-dâe̤ng diŏh dŏng siĕng tō̤-lâung hiĕk lā̤ có̤.
茲萆頁面是舊底討論其存檔。起動汝伓嗵編輯茲蜀頁。如果汝希望發起新其討論或者重啟現有其討論，起動著當先討論頁𡅏做。

外國國家名字其福州話名字翻譯問题

罕見其外國國家名字其福州話名字著叫什乇？（稠見其名字無必要討論了）譬如講 Antigua and Barbuda ，聯合國官方中文名是簡體中文「安提瓜和巴布达」，轉成繁體中文是「安提瓜和巴布達」，香港就是總款寫，但是臺灣也価媒體叫做「安地卡及巴布達」。再加福州話一般無講「和」，是講「共」，故此講是伓是著寫「安提瓜共巴布達」？但是若按福州話處理也有問題，就是音譯使伓使改成福州話音譯「安提瓜共巴不大」，但是總款不利統一名稱，也有儂看𣍐會意。故此到底著蔣做？

  • 甲、使國家其聯合國官方中文名直接轉繁體——安提瓜和巴布達
  • 乙、使臺灣媒體平常使其名稱——安地卡及巴布達
  • 丙、根據國家其聯合國官方中文名，音譯部分直接轉繁體，意譯部分翻譯成福州話——安提瓜共巴布達
  • 丁、完全使福州話重新翻譯——安提瓜共巴不大、馬剌加

起動大家儂來討論蜀下。謝謝！ --Yejianfei (對話) 2017 nièng 9 nguŏk 24 hô̤ (LB) 10:57 (UTC)[回覆]

我其意見是，音譯著按福州話其讀音，意譯著按福州話其意義。比如講馬剌加就共普通話勿會蜀樣。固有蜀點，我聽儂講海外其福州儂有對當地地名其習慣叫法，比如長島號𡅏long-a-lang，是英語其音譯，總款其福州話翻譯也可以考慮儷。若卜挃漢字，就按long-a-lang討讀音對應其漢字去寫就會使了。當然著說明嚽是維基自家定其漢字寫法，伓是通行其。以後翻譯其事如果罔做罔儕，學新華社做音譯用字規範也會使。--Davidzdh (討論/Tō̤-lâung) 2017 nièng 9 nguŏk 24 hô̤ (LB) 14:48 (UTC)[回覆]

罔講罔聽，「和」總款其詞，文言維基是意譯其，作東亞共通其「及」。--Davidzdh (討論/Tō̤-lâung) 2017 nièng 9 nguŏk 24 hô̤ (LB) 14:51 (UTC)[回覆]
固有蜀萆事實，讓蜀隻福州儂講自家去外國底呢客佻，若定著講平話，不使普通話講國名地名，儂應該會使福州話其音讀普通話其地名用字。故此講是伓是福州話「強讀」普通話地名其讀音，也應該敆維基記錄儷？我罔講。--Davidzdh (討論/Tō̤-lâung) 2017 nièng 9 nguŏk 24 hô̤ (LB) 14:58 (UTC)[回覆]
A rule of thumb is, if a name can be found in the Foochow Bible or any of the formally published dictionaries, then use the translated form. For example, Greece is translated as Hĭ-lé-nà̤ (希利尼) in the old days and Hĭ-lăk (希臘) nowadays, so both terms are okay. But for other less-known names like "Antigua and Barbuda", using the original Western language should be okay. In light of this rule, England should be changed to Ĭng-gáik-làng, etc.
However, an exception to this is the Japanese, Korean, and Vietnamese names that also use Chinese characters. Translated names according to Min Dong should be preferred. Therefore Akihito (明仁) should be Mìng-ìng, etc. --GnuDoyng (對話) 2017 nièng 9 nguŏk 24 hô̤ (LB) 15:36 (UTC)[回覆]
Of course we are talking about less-known names. As for frequently used names, just copy what my neighbours usually call it. --Yejianfei (對話) 2017 nièng 9 nguŏk 24 hô̤ (LB) 17:32 (UTC)[回覆]


--Yejianfei (對話) 2017 nièng 9 nguŏk 24 hô̤ (LB) 18:04 (UTC)[回覆]

No, I totally disagree with using the original foreign spelling / pronunciation of names from the Sinosphere. It's so alien, so weird, so unnatural. To be honest I don't think any of the Foochow speakers, yourself included, will actually use "Abe Shinzō" instead of "Ăng-buôi Céng-săng" to refer to the current Japanese PM in their everyday speech. But since it's not a major black-or-white issue, I'll just turn a blind eye. --GnuDoyng (對話) 2017 nièng 9 nguŏk 25 hô̤ (B1) 05:03 (UTC)[回覆]
Oh I may have misunderstood your meaning. I was talking about Foochow Romanized, not the Chinese characters. --GnuDoyng (對話) 2017 nièng 9 nguŏk 25 hô̤ (B1) 05:06 (UTC)[回覆]
OK, let me modify the description a little bit to make it clearer that it is talking about "Chinese characters". --Yejianfei (對話) 2017 nièng 9 nguŏk 25 hô̤ (B1) 06:19 (UTC)[回覆]

All right. Please go ahead and disregard my comments. I'm not at all interested in writing Foochow characters. --GnuDoyng (對話) 2017 nièng 9 nguŏk 25 hô̤ (B1) 06:26 (UTC)[回覆]

備案：按普通話倛漢字翻譯寫倛條目：波斯尼亞共黑塞哥維那。發現總款倛條目可以放茲邊，如果卜改以後好改。--Davidzdh (討論/Tō̤-lâung) 2017 nièng 10 nguŏk 9 hô̤ (B1) 13:05 (UTC)[回覆]

ESEAP Conference 2018

Hello Min Dong Wikipedians, we would like to inform you that we propose the conference grants for our region, East, Southeast Asia and Pacific. It's including your region too. If you would like to involve more please join in our conference grants talk page and fill our survey too.--Beeyan (對話) 2017 nièng 10 nguŏk 17 hô̤ (B2) 08:26 (UTC)[回覆]

这个维基亚太会议有没有人想参加的？2018年5月25至27日，位于印尼国巴厘岛。--Yejianfei (對話) 2017 nièng 10 nguŏk 19 hô̤ (B4) 02:20 (UTC)[回覆]

平話維基其界面文字分漢字共羅馬字會使𣍐？ / Bâng-uâ Wiki gì gái-méng ùng-cê buŏng Háng-cê gâe̤ng Lò̤-mā-cê â̤-sāi mâ̤?

福州話維基百科倛界面文字無分漢字共羅馬字，都混蜀堆去寫了。但是寫福州話倛儂啊，有倛愛寫羅馬字，有倛愛漢字。界面文字混蜀堆去，寫漢字倛就𣍐會意羅馬字講了什乇，復𣍐歡喜屏幕都是羅馬字；愛羅馬字倛看見界面乞漢字佔去也𣍐歡喜。復加同蜀萆網頁裏勢，復有羅馬字復有漢字，也𣍐好看。無分漢字共羅馬字，大家都𣍐爽快。𣍐爽快倛事計，快勢去做嚕？Yejianfei講，界面翻譯可以分漢字共羅馬字，翻譯放𣍐蜀樣倛所在𡅏，總款愛漢字倛使漢字版本，愛羅馬字倛看羅馬字版本。界面文字雖然分了版本，但網站無分，固是齊去乞平話維基做貢獻。大家儂見覺總款何如？有什乇意見，歡迎敆租塊講。

注意：租塊討論界面文字，共條目寫什乇漢字羅馬字無關係。

Hók-ciŭ-uâ Wikipedia gì gái-méng ùng-cê mò̤ buŏng Háng-cê gâe̤ng Lò̤-mā-cê, dŭ hông siŏh dŏi kó̤ siā lāu. Dáng-sê siā Hók-ciŭ-uâ gì nè̤ng ā, ô gì óṳ ó̤i siā Lò̤-mā-cê, ô gì ó̤i Háng-cê. Gái-méng ùng-cê hông siŏh dŏi kó̤, siā Háng-cê gì cêu mâ̤ huòi-é Lò̤-mā-cê gōng lāu sié-nó̤h, bô mâ̤ huăng-hī bìng-mŏk dŭ-sê Lò̤-mā-cê; ó̤i Lò̤-mā-cê gì káng-giéng gái-méng ké̤ṳk Háng-cê ciéng kó̤ iâ mâ̤ huăng-hī. Bô-gă dùng siŏh bĭh uōng-hiĕk diē-sié, bô ô Lò̤-mā-cê bô ô Háng-cê, iâ mâ̤ hō̤ káng. Mò̤ buŏng Háng-cê gâe̤ng Lò̤-mā-cê, dài-gă dŭ mâ̤ sōng-kuái. Mâ̤ sōng-kuái gì dâi-gé, ká̤-sié kó̤ có̤ lū? Yejianfei gōng, gái-méng huăng-ĭk kō̤-ī buŏng Háng-cê gâe̤ng Lò̤-mā-cê, huăng-ĭk bóng mâ̤ siŏh-iông gì sū-câi lā̤, ciŏng-uâng ó̤i Háng-cê gì sāi Háng-cê bāng-buōng, ó̤i Lò̤-mā-cê gì káng Lò̤-mā-cê bāng-buōng. Gái-méng ùng-cê chŭi-iòng buŏng lāu bāng-buōng, dáng uōng-câng mò̤ buŏng, gó sê cà̤ kó̤ ké̤ṳk Bâng-uâ Wiki có̤ góng-hióng. Dài-gă-nè̤ng giéng-gáe̤k ciŏng-uâng hò̤-ṳ̀? Ô sié-nó̤h é-giéng, huăng-ngìng găk cŭ-uái gōng.

Cé̤ṳ-é: Cŭ-uái tō̤-lâung gái-méng ùng-cê, gâe̤ng dèu-mŭk siā sié-nó̤h Háng-cê Lò̤-mā-cê mò̤ guăng-hiê.

  1. (＋)支持--Davidzdh (討論/Tō̤-lâung) 2017 nièng 11 nguŏk 2 hô̤ (B4) 10:37 (UTC)[回覆]
  2. (＋)支持--Ztl8702 (對話) 2017 nièng 11 nguŏk 2 hô̤ (B4) 13:40 (UTC)[回覆]
  3. (＋)支持--Cyclohexane233 2017 nièng 11 nguŏk 2 hô̤ (B4) 14:20 (UTC)[回覆]
  4. (＋)支持--GnuDoyng (對話) 2017 nièng 11 nguŏk 2 hô̤ (B4) 20:54 (UTC)[回覆]
  5. (＋)支持--Yejianfei (對話) 2017 nièng 11 nguŏk 3 hô̤ (B5) 01:14 (UTC)[回覆]
  6. (＋)支持 這個話題也放了很久了，是時候做個表態了吧。--Clzls (tō̤-lâung) 2019 nièng 1 nguŏk 1 hô̤ (B2) 06:46 (UTC)[回覆]

第一次點進來，不太會用，有一個建議，無知冒犯的話非常对不住： 我見左邊選擇【語言】那欄，伊恁吳語客家話名字都有羅馬音和漢字，平話無漢字，平時都無好注意到，寫作Mìng-dĕ̤ng-ngṳ̄/平話/閩東語言會使？ 還有就是羅馬字不好學，有門檻，要是主要用和粵語一樣日常書寫，會不更好宣傳推廣用平話，我仈曉，大家見覺呢？因為我朋友（平時不太講平話）昨瞑點近來，看漢字就立馬會曉，羅馬音她講念不來，如果要分開，會不漢字為default好？因為容易入門，好讀好推廣。 個人意見：我見覺漢字/羅馬字 一個頁面裡前後這樣寫會好，會羅馬字的寫羅馬字會漢字的寫漢字，弄清楚格式就欸賽，因為野可以讓只會漢字的對照羅馬字，野方便看的人學。--UdNgoi (tō̤-lâung) 2020 nièng 9 nguŏk 6 hô̤ (LB) 04:44 (UTC)[回覆]

“愛”其羅馬字寫做ó̤i。--GnuDoyng (對話) 2017 nièng 11 nguŏk 2 hô̤ (B4) 20:54 (UTC)[回覆]
Nguāi dâng kó̤, siâ-siâ nṳ̄. 我綻去，謝謝汝。--Davidzdh (討論/Tō̤-lâung) 2017 nièng 11 nguŏk 3 hô̤ (B5) 04:14 (UTC)[回覆]

閩東語維基新聞成立了，大家儂快來寫

點擊 閩東語維基新聞 ，大家儂開始寫維基新聞啊！--Yejianfei (對話) 2017 nièng 12 nguŏk 20 hô̤ (B3) 08:39 (UTC)[回覆]

現在固是孵化器項目，歡迎大家寫新聞，總款有希望變成正式網站。--Davidzdh (攀講/Păng-gōng) 2017 nièng 12 nguŏk 20 hô̤ (B3) 15:02 (UTC)[回覆]

關於知乎上的討論

有儂著知乎上提出蜀萆問蔣蔣評價閩東語維基百科？ 大家儂有興趣會使去看蜀看。

@Cyclohexane233:已經發表蜀萆回答，我看伊回答也算真好。

--Yejianfei (對話) 2018 nièng 1 nguŏk 3 hô̤ (B3) 18:56 (UTC)[回覆]

ESEAP Conference 2018

各位好，
2018年度ESEAP会议补助申请现已开放！
2018年度ESEAP会议是面向东亚、东南亚和太平洋区域维基媒体社群的地区性会议。本次会议将于2018年5月5日-6日在印度尼西亚巴厘岛举行，这是该区域维基媒体社群的首次区域会议。
全额补助受名额限制，每个国家地区最多两人，您所在国家地区符合申请条件，请参见此页面。
多种形式的资料提交也已开放，包括：
  • 研讨会及教程：这些展示重在实用，或是传授某一特定技能，或是完成某项特定任务。时长55分钟，会在适于使用电脑和工作的教室空间进行。
  • 海报：A2大小，分享新闻、社群活动/项目、发表某一想法、提出某一概念或解释某一问题。海报必须上传至维基共享资源并提供适当的授权。
  • 简短展示/经验交流：10到15分钟针对特定议题的展示。
提交资料和补助申请的截止日期为2018年3月15日。如有任何疑问，请联系本人或电邮至eseap@wikimedia.or.id。
祝好，
--Beeyan (對話) 2018 nièng 3 nguŏk 8 hô̤ (B4) 06:30 (UTC) 06:15 (UTC)(粗略翻译：User:Kuailong)[回覆]

Galicia 15 - 15 Challenge

Wikipedia:Galicia 15 - 15 Challenge is a public writing competition which will improve improve and translate this list of 15 really important articles into as many languages as possible. Everybody can help in any language to collaborate on writing and/or translating articles related to Galicia. To participate you just need to sign up here. Thank you very much.--Breogan2008 (對話) 2018 nièng 3 nguŏk 12 hô̤ (Buái ék) 13:47 (UTC)

Time to bring embedded maps (‘mapframe’) to most Wikipedias

Time to bring embedded maps (‘mapframe’) to most Wikipedias

請協助翻譯成您使用的語言

Mapframe is a feature that enables users to easily display interactive maps right on wiki pages. Currently, most Wikipedias don’t have mapframe. But fifteen Wikipedias, along with all the other Wikimedia projects, are using mapframe today to display maps on thousands of pages.

A little background: over the last few months, the Foundation’s Collaboration team has been working to improve the stability and user experience of the maps service. In addition, a question about long-term support for the maps service was recently settled, and a small team has been assigned for routine maintenance. Given these developments, bringing the benefits of mapframe to Wikipedias that lack the feature seems both safe and supportable. Nine Wikipedias that use a stricter version of Flagged Revisions will not get mapframe in this release.

Maps are a valuable form of visual data that can improve readers’ understanding across a wide range of topics. If you know of any reasons why mapframe shouldn’t be implemented on your Wikipedia, let us know on the project talk page. Unless we hear from you, we plan to release mapframe to most Wikipedias in May, 2018. So, if you foresee an issue, please let us hear from you. Otherwise, happy mapping!

CKoerner (WMF) (talk) 2018 nièng 4 nguŏk 24 hô̤ (B2) 21:38 (UTC)[回覆]

Update on page issues on mobile web

Update on page issues on mobile web

請協助翻譯成您使用的語言 Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.

So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:

  • The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
  • Page issues make sense to readers and they understand how they work
  • Readers care about page issues and consider them important
  • Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues

Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.

CKoerner (WMF) (talk) 2018 nièng 6 nguŏk 12 hô̤ (B2) 20:58 (UTC)[回覆]

人名、地名、正字法

所有人名皆應本地化，即全部需要翻譯，不可保留原文，唯首次出現原文時以括號形式加上原文。 爲長遠計，從現實出發，除傳統譯名加以推廣學習之外（如大辟 David），餘者應多考慮在普通話譯名的基礎上發音，最爲經濟可行。 普通話中常見的縮寫詞，如 NBA，一應保留引入，不必再多翻譯。

所有章泉亂、io/uo 皆應嚴格區分，分了對於不分者無影響，不分對分者有影響。我們做的同時也是在提供標準。 以君主爲例，gŭng-cuō 於不分者仍讀作 gŭng-ciō,分者仍讀作 gŭng-cuō，兩無妨礙。 實際上，幫助不分者區分，有助於設立一種標準，爲後續統一的語文做準備。 強調平話字作用者的話是可以通行十邑，區分是必要的。

--DINGGOR (對話) 2018 nièng 6 nguŏk 14 hô̤ (B4) 06:28 (UTC)[回覆]

@DINGGOR:關於縮寫詞一條，個人的意見是，即便在官話白話文的場合，拉丁文字縮寫也並非最正式用法，只是便宜之計耳。如果是普通地行文，那麼寫上NBA倒也無妨。只是條目的標題宜從最正式的「國家籃球協會」。--Davidzdh (攀講/Păng-gōng) 2018 nièng 6 nguŏk 14 hô̤ (B4) 14:45 (UTC)[回覆]
同意关于泉漳乱的严格区分。对于术语的翻译，建议采用投票的方式表决。--GnuDoyng (對話) 2018 nièng 6 nguŏk 14 hô̤ (B4) 21:30 (UTC)[回覆]
關於人名地名的在地化持保留意見，聖經中提到的人名地名不用原名，用平話字聖經中的譯名；大部份外來名我更傾向於學越南語和閩南語版本那樣直接使用原名（也可以考慮像英文版那樣附注一個發音重拼，例如詞條en:Aruba、en:ASCII等）。專業術語的名詞翻譯，可以考慮跟隨中文版。
能夠符合可供查證這一要求的權威文獻全部來自19世紀末至20世紀初，僅能體現當時的福州話實際發音，而與現代發音存在一定區別。雖然現代有人提出改進建議，但事實上均不符合維基百科方針與指引中可靠來源，便存在有原創研究之嫌疑。io、iong、ioh等的現代讀音雖與差別古代差別迥異，但都存在明顯的對應規律，既然Help:Ciŏng-iông tĕ̤k中提到了，在新的權威的正字法還沒出來之前，我看還是將就著用吧。（閩南語維基也是沿用19世紀的拼寫法，例如Pek-kho-choân-su、Bêng-tiâu、Hùi-thêng等拼寫都跟今日大部份閩南語方言實際讀音有差異。可做參照。）
另外事實上實現「平話字通行十邑」是有點困難的，本身平話字創造時候就只是用來表記福州在地的方言，查閱福建省地方志编纂委员会可知即便是同屬於閩東語侯官片，各地用詞有時候也存在較大差異（比如與古田話對比）。--el caballero de los Leones (tō̤ nguāi păng-gōng) 2018 nièng 6 nguŏk 17 hô̤ (LB) 17:16 (UTC)[回覆]
羅馬字在語音上對十邑鄉親應該是平等的。比如食字的羅馬字表記爲siah，市區已不如此讀，然而包括福清在內許多地方依舊如此讀。十邑所有福州話使用者都可以在當年傳教士定下的羅馬字系統中找到自家鄉音的成體系的映射，這應該就是Ding君指出的溝通十邑的目的吧。至於各地用辭差異，反倒如同兩岸國語的詞彙差異一般，無傷大雅。不過從這一點上看，io、uo的問題似乎也可以透過讀者自己樹立映射的觀念來解決？
關於外來語問題，在下還是建議從福州話角度出發的翻譯優先，比如唐先生指出的聖經譯，又比如林紓翻譯的“仲馬”，又比如被海外福州鄉親們福州話化的大中華地區以外的地名，這種翻譯就算當作條目標題，我想大家也不會有意見吧？
在下整理了用戶:Davidzdh/海外福州話地名，當然，暫時只是草稿，僅供參考。--Davidzdh (攀講/Păng-gōng) 2018 nièng 6 nguŏk 18 hô̤ (Buái ék) 07:00 (UTC)

漢字文化圈事物羅馬字條目標題表記

平話維基都是有儂愛改日本儂其條目，共漢字讀音搬遘日本話其羅馬字。我見覺嚽有仂囝「反直覺」。講平話其儂若是看見日本儂其名字，一定會直接按伊漢字讀音讀出來，怎講會蜀邊看漢字，蜀邊反應出來伊名字其日本話讀法嚕？著會仈伓是所有講平話其儂都會講日本話。

前首其討論，GnuDoyng也指出：

However, an exception to this is the Japanese, Korean, and Vietnamese names that also use Chinese characters. Translated names according to Min Dong should be preferred. Therefore Akihito (明仁) should be Mìng-ìng, etc.

閩南、客家維基乜乇辰候開始愛直接使外語羅馬字，我無研究過。但是講儂家閩東語維基，僅驚伓是起頭就是總款。請看書看茲蜀篇野価年前就建立起去其《哈利波特》條目，伊就伓是蜀開始就照搬外語其羅馬字。閩東語維基僅驚其實是敆一五年左右，乍有儂剃了共標題改成（伓啻日本話其）外語羅馬字。嚽胼後有無社群意見背書哩？也勿會仈。茲蜀月日得遘Joe young yu先生其建議，故此來租塊繼續討論，希望可以有蜀隻明確其共識。--Davidzdh (攀講/Păng-gōng) 2018 nièng 9 nguŏk 21 hô̤ (B5) 13:01 (UTC)[回覆]

使閩東語讀音

使外語羅馬字

這個問題恐怕並非那麼簡單。東亞文化圈雖然說廣泛使用（或曾經廣泛使用漢字），但並非所有漢字都擁有福州語讀音。這些漢字的讀音查證比較困難，有的不存在中文讀音。例如：和製漢字，有匁、躾、榊、辻、峠等；韓國國字，乭、哛、畓、㸴、怾等；喃字就不用說了，如Mạc Ngọc Liễn (莫玉 王+輦)、Lê Duy Mật (黎維 礻+密)、Lê Duy Khiêm (黎維 礻+兼)、Lê Quýnh (黎 亻+冏)、Lê Văn Khôi (黎文 亻+褢)等人名中的字，如何在網頁顯示都是個頭疼的問題，更不用說查證其中文讀音。

還有一個值得注意的是，東亞文化圈的日韓越三國或多或少都存在去漢字化的現象。許多人名地名事實上不存在漢字寫法。日本：うるま市、サロベツ原野、小野リサ、松たか子、夏川りみ、沢尻エリカ、蒼井そら、水咲ローラ、小澤マリア。韓國：장나라 (張--)、강하늘 (姜--)。越南，直接徹底廢除漢字，漢字譯名非常混亂，由於漢字史料匱乏，查證其真正漢字寫法比較困難（越南官方媒體居然還有把U Minh翻譯成幽冥縣的，不信可以google一下）

另外，韓國人名使用漢字但被廣泛錯譯：송혜교 (宋慧敎/宋慧喬)、임윤아 (林潤妸/林允兒)、전도연(全道嬿/全度妍)...諸如此類，應該使用本人的漢字寫法，還是廣泛流傳的中文譯名？

我覺得若是漢字名字確定的，讀音也可以查證出來，標題當然可以用閩東語來寫。若是一定要統一？我覺得還是用外語羅馬字，一是省事，二是避免各種混亂。--el caballero de los Leones (tō̤ nguāi păng-gōng) 2018 nièng 9 nguŏk 24 hô̤ (Buái ék) 06:24 (UTC)

  • 感谢表态。有的日本、韩国国字已经经过普通话审音，或是华文世界里有了习惯读法，比如石乙念石，我想按照规律推出福州话读音不是什么问题。如果电视台或者广播要读它名字的话，肯定也是如此操作。简单来说一句话，福州台的福州话节目里（像是攀讲节目），节目主持肯定不会蹦出一个普通话来，就是这个意思
  • 关于韩国人名因为汉字失落导致的错译，取错译还是取户籍原名，确实需要讨论。
  • 对于“若是一定要統一？我覺得還是用外語羅馬字，一是省事，二是避免各種混亂。“的回复：至少就目前来看，闽东维基收录的日本人条目名字还没到不可直读的程度。为应对以后可能出现的情况，我们可以开出闽东语难读人名表，供编辑自由参考。中文维基在汉和韩越用字问题或者外语译音也是类似的做法吧――列出一张张表供参考。--Davidzdh (攀講/Păng-gōng) 2018 nièng 9 nguŏk 24 hô̤ (Buái ék) 08:24 (UTC)
  • 補充一下西洋名字音譯的問題。閩東語與標準漢語讀音差異頗大，為何非要用標準漢語的漢字譯名按照閩東語的讀音來讀？這樣讀讀音不僅與原文差異大，而且很難聽，真的非常難聽。我不僅聽閩東語還是閩南語的使用者遇上這種譯名，很多人都是直接用標準漢語讀出來的。--el caballero de los Leones (tō̤ nguāi păng-gōng) 2018 nièng 9 nguŏk 24 hô̤ (Buái ék) 06:30 (UTC)
    • @唐吉訶德的侍從:虽然这里没有在讨论西洋译名不过既然提到了还是蛮讲一下，大仲马这个词是福州人林纾按福州话音译的，这个福州话译名在闽东语维基居然上不了台面，做不成标题，是否有点过了。我也不是排斥外语罗马字，但是一刀切统一为外语，恐怕也过于粗暴，不是太妥。有的译名进入中国时间早，在福州话还完全统治福州的时代，就被福州人用福州话读出。这种词在阁下前面引用的那本传教士词典里也可见。闽东语维基是不是好歹尊重一下它们的闽东语读音会比较好一点。有的词进入时间晚，像最近建立的各种群岛名字，那种名字不翻成闽东语我也没什么意见。汝见觉哩？侬家是伓是可以定下范围，如果什乇外来语，平话字文献里势会看见，就直接写平话字？--Davidzdh (攀講/Păng-gōng) 2018 nièng 9 nguŏk 24 hô̤ (Buái ék) 08:24 (UTC)

其他意見

(！)意見：在我與User:Davidzdh攀談中也有提到，關於漢字文化圈遊戲、漫畫、動畫等的平話字化問題，例如：

日語 普通話 羅馬字（或英語） 平話字 類型
パックマン 吃豆人 Pacman Ngék-dâu-ìng 遊戲系列
キテレツ大百科 奇天烈大百科 Kiteretsu Daihyakka Gì-tiĕng-lè Duâi-báik-kuŏ 漫畫
ルイージ 路易基 Luigi Lô-ì-gĭ 遊戲角色
はたらく細胞 工作細胞 Hataraku Saibō Gĕ̤ng-cáuk Sá̤-bàu 動畫
KADOKAWA 角川 KADOKAWA Gáe̤k-chiŏng 公司

以上只是粗略列舉，但希望大家投票時能夠多加註意。——Joe young yu (tō̤-lâung) 2018 nièng 9 nguŏk 22 hô̤ (B6) 14:10 (UTC)[回覆]

感谢列举！小小提醒，吃豆人真要用福州话读多半会变成食豆侬（siăh-dâu-nè̤ng），奇天烈的烈是（liĕk）。--Davidzdh (攀講/Păng-gōng) 2018 nièng 9 nguŏk 22 hô̤ (B6) 14:30 (UTC)[回覆]

Joe君在这个问题上做了很重要的提示，现将和Joe君在我的用户页的讨论记录中，和这个问题有关的对话，引用在下方，并致对Joe君的谢忱。--Davidzdh (攀講/Păng-gōng) 2018 nièng 9 nguŏk 24 hô̤ (Buái ék) 08:29 (UTC) 

另，关于日本游戏、动画、漫画是否也使用此原则（如Pacman、Doraemon等等）？——Joe young yu (tō̤-lâung) 2018 nièng 9 nguŏk 22 hô̤ (B6) 05:47 (UTC)[回覆]
感謝關注。這類條目可能還是需要具體問題具體分析，但是我想應該要有一個原則。首先閩東語的慣用說法肯定應該優先，比如Gameboy被叫做Gĕng-bŏ̤（漢字音同更褒）。其次宜從中譯，如果一個外國事物福州人沒有自己翻譯的話，福州話媒體一般會照讀或照譯通行的中譯。如《Re:從零開始的異世界生活》，在下就傾向稱為《Re:由環開始其異世界生活》而不是“Re: Zero kara Hajimaru Isekai Seikatsu”，至少要讓人讀得懂吧。如果有的東西實在是小眾，哪怕在中文維基都是照搬假名的，民間也實在沒有翻譯，那實在沒辦法了，照用羅馬字也不失為權宜的辦法。在下也不是排斥外語羅馬字，只是不希望所有的東西都被外語羅馬字所替代——而明明自己的語言可以讀出或翻譯。閩南、客家維基的外語羅馬字習氣暫時無暇置喙，但是至少在閩東維基，這個問題能得到明確，在下就滿足了。--Davidzdh (攀講/Păng-gōng) 2018 nièng 9 nguŏk 22 hô̤ (B6) 06:04 (UTC)[回覆]
Doraemon，那時候電視臺都是放“小叮噹”來著？福州話多半會照讀吧。剛在網上發現了這段福州話配音，也是用“小叮噹”。--Davidzdh (攀講/Păng-gōng) 2018 nièng 9 nguŏk 22 hô̤ (B6) 06:22 (UTC)[回覆]
(：)回應 《從零開始的異世界生活》，我會讀成「趁零開始其異世界生活」（téng lìng kăi-sṳ̄ gì ê-sié-gái sĕng-uăk）。--Yejianfei (tō̤-lâung) 2018 nièng 10 nguŏk 15 hô̤ (Buái ék) 11:25 (UTC)
嚽是作品名，講零固好，汝講其有道理。--Davidzdh (攀講/Păng-gōng) 2018 nièng 10 nguŏk 15 hô̤ (Buái ék) 13:05 (UTC)
(：)回應 @唐吉訶德的侍從: 林紓福州話譯名：「大仲馬」共「福爾摩斯」，建議閩東語維基百科采用，漢字頁面共羅馬字頁面都采用，其它西洋名字酌情處理，不強制要求。東亞漢字文化圈中日韓越名字，建议直接寫漢字，羅馬字頁面也使漢字音，但是碰遘日本「和製漢字」共越南「喃字」時候，也可以酌情處理，不強制要求。 --Yejianfei (tō̤-lâung) 2018 nièng 12 nguŏk 22 hô̤ (B6) 10:36 (UTC)[回覆]
(＋)支持。遘現刻爲止，只條建議看起第一好。--Davidzdh (攀講/Păng-gōng) 2019 nièng 5 nguŏk 23 hô̤ (B4) 14:43 (UTC)[回覆]

Enabling a helpful feature for Template editors

Hello.

The team working on TemplateStyles at the Wikimedia Foundation would like to enable TemplateStyles on this wiki.

TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions.

TemplateStyles is useful for a few reasons.

  • It makes it possible for templates to work better on mobile.
  • It cuts out confusion on where to apply CSS rules.
  • Editing CSS is currently limited to administrators, which is a major barrier to participation.
  • All stylesheets must be loaded on all pages (whether they actually use the page or not), which wastes bandwidth and makes debugging style rules more difficult.

You can learn more about TemplateStyles on MediaWiki.org. Technical documentation is also available.

This is an optional feature and no one must use it, but template contributors are encouraged to do so! Please discuss and let us know if there are any concerns. If there are no concerns we will proceed to deploy the feature on the 9th of August.

Thank you.

CKoerner (WMF) (talk) 2018 nièng 8 nguŏk 6 hô̤ (Buái ék) 21:28 (UTC)

Multilingual Shared Templates and Modules

Hello cdo-wiki community! (請協助翻譯成您使用的語言)

I recently organized a project to share templates and modules between wikis. It allows modules and templates to be “language-neutral”, and store all text translations on Commons. This means that it is enough to copy/paste a template without any changes, and update the translations separately. If someone fixes a bug or adds a new feature in the original module, you can copy/paste it again without any translation work. My bot DiBabelYurikBot can help with copying. This way users can spend more time on content, and less time on updating and copying templates. Please see project page for details and ask questions on talk page.

P.S. I am currently running for the Wikimedia board, focusing on content and support of multi-language communities. If you liked my projects like maps, graphs, or this one, I will be happy to receive your support. (any registered user group can vote). Thank you! --Yurik (talk) 2019 nièng 5 nguŏk 11 hô̤ (B6) 05:57 (UTC)[回覆]

Wikidata Bridge: edit Wikidata’s data from Wikipedia infoboxes

Sorry for writing this message in English - feel free to help us translating it :)

Hello all,

Many language versions of Wikipedia use the content of Wikidata, the centralized knowledge base, to fill out the content of infoboxes. The data is stored in Wikidata and displayed, partially or completely, in the Wikipedia’s language, on the articles. This feature is used by many template editors, but brought several issues that were raised by communities in various places: not being able to edit the data directly from Wikipedia was one of them.

This is the reason why the Wikidata Bridge project started, with the goal of offering a way to Wikipedia editors to edit Wikidata’s data more easily. This will be achieved by an interface, connected to the infobox, that users can access directly from their local wiki.

The project is now at an early stage of development. A lot of user research has been done, and will continue to be done through the different phases of the project. The next steps of development will be achieved by the development team working at Wikimedia Deutschland, starting now until the end of 2019.

In order to make sure that we’re building a tool that is answering editors’ needs, we’re using agile methods in our development process. We don’t start with a fixed idea of the tool we want to deliver: we will build it together with the editors, based on feedback loops that we will regularly organize. The first version will not necessarily have all of the features you want, but it will keep evolving.

Here’s the planned timeline:

  • From June to August, we will build the setup and technical groundwork.
  • From September to November 2019, we will develop the first version of the feature and publish a test system so you can try it and give feedback.
  • Later on, we will test the feature on a few projects, in collaboration with the communities.
    • We will first focus on early adopters communities who already implemented a shortcut from their infoboxes to edit Wikidata (for example Russian, Catalan, Basque Wikipedias)
    • but we also welcome also communities who volunteer to be part of the first test round.
    • Then we will reach some of the big Wikipedias (French, German, English) in order to see if the project scales and to address their potentially different needs.
    • Even later, we can consider enabling the feature on all the other projects.

In any case, no deployment or big change will be enforced on the projects without talking to the communities first, and helping the template builders to prepare for the changes they will have to do on the infoboxes’ code.

If you want to get involved, there are several ways to help:

More ideas will be added on this page along the way

If you have any questions for the development team, feel free to ask them on the main talk page. You can also ask under this message, but if you expect an answer from me, please make sure to ping me.

Thanks for your attention, Lea Lacroix (WMDE) 2019 nièng 6 nguŏk 24 hô̤ (Buái ék) 13:03 (UTC)

發現外國譯名gì問題

發現一隻有關外國譯名gì問題，就是病毒音gì問題。病毒音就是kĕk一種語言ngâing diŏh套用另一種語言gì讀音。目前福州語gì使用現狀是除去少數幾個常用國名地名外，大部份外國地名、人名根本都無福州語gì譯名，即便是ngâing diŏh kĕk國語漢字gì譯名使福州語來讀，大部份人根本就mâ̤曉講gì是sié-nó̤h。並且，cuòi也是mâ̤尊重外文原文gì讀音，不管講福州語gì人、講國語gì人、gó是講ciā外語gì人，都完全mâ̤曉到底講gì是sié-nó̤h。故此，ciōng-uâng ngâing lā̤使國語gì譯名是mâ̤好gì。

大部份福州語詞典都無收錄外國國名、地名gì福州語，也無看見diê ciáh學者寫過相關gì研究報告，故此sié-nó̤h是已ké̤ṳk福州語吸收gì譯名，查證cĭng困難，mò̤-niĕ-ài界定。惟一găk Dictionary of the Foochow Dialect 3rd version.  cī部辭典â̤查gáu最sâ̤國名gâe̤ng地名，比如英國(ĭng-guók)、美國(mī-guók)、澳大利亞(ó̤-dâi-lé-ā)、倫敦(lùng-dŭng)、巴黎(bă-là̤)等等，但是其實也nâ有少數國名gâe̤ng地名。故此建議，găk平話字版本，如果nâ â̤ diŏh cī部詞典查出gì詞認定為福州語gì譯名，查mâ̤出gì暫時無承認，用英文名。

對於外國譯名問題gì處理方法目前cĭng混亂，普遍gì處理方式都是直接kĕk國語讀出。cuòi gâe̤ng香港粵語gì中英夾雜gì現象比較像。以福州語節目攀講為例：

http://m.fztvapp.zohi.tv/pj-db/p/108138.html 26:37 "英国伦敦汉威尔动物园" (Ĭng guók Lún dūn Hàn Wēi ěr dông ŭk huòng), 26:51 "该雕塑的设计师唐尼·迪亚兹表示" (găi dĕu sé̤ṳk gì sié gié sṳ̆ Táng Ní Dí Yǎ Zī biēu sê)

http://m.fztvapp.zohi.tv/pj-db/p/102636.html 17:20 "英国白金汉郡" (Ĭng guók Bái Jīn Hàn Jùn)

http://m.fztvapp.zohi.tv/pj-db/p/99687.html 27:58 "美国加利福尼亚州南部" (Mī guók Jiā Lì Fú Ní Yǎ Zhōu nàng buô)

三位不同主持人都使過福州語國語混用gì方法，可見cī種現象găk福州是cĭng普遍gì。但是"倫敦"已經是cĭng sâ̤人都â̤ báik gì地名，ká̤-diê cī ciáh主持人gó是kĕk國語來讀？可見diŏh平常生活dâi-dŏng對cī類譯名gì處理方法是cĭng混亂gì，根本都無統一認定gì標準。

漢字版本，理論上也應該kĕk讀音接近福州語gì漢字譯名，但是cuòi違反wikipedia非原創研究gì原則。無辦法，暫時先使國語gì譯名，畢竟用福州語讀書gì時候，看見cī種譯名一般也是直接kĕk國語來讀gì。雖然講nguāi cĭng反對ciōng-uâng使，但是也是無辦法。畢竟現在福州語táu-dā̤無使cê-gă語言gì報紙lāu（gô-dā̤教會cĭng像做過，dāng都無lāu），故此也無標準化gì譯名。cuòi是福州語gì悲哀。--el caballero de los Leones (tō̤ nguāi păng-gōng) 2019 nièng 8 nguŏk 26 hô̤ (Buái ék) 10:38 (UTC)

  • 復想gáu一點，其實東南亞有gì國家像馬來西亞、印尼ciŏng-uâng，都有一定數量gì福州人後代，伊各人也是講福州語gì，故此馬來西亞gâe̤ng印尼gì州、省或者主要城市可能都有福州語自家gì譯名，最少來講găk福州人比較sâ̤ gì城市應該有福州語自家gì譯名。但是問題是，gó無研究gì書或者論文講gáu cī類譯名。nâ是ô-niĕ-ài查gáu gì話，應該使福州語gì名字。
    東南亞地名gì漢字譯名來源cĭng複雜，有cĭng sâ̤一部份可能是téng潮州語或者閩南語hiā借來gì。nâ是kĕk泉漳閩南語讀（無辦法肯定東南亞閩南人是ng是ciŏng-uâng讀），像馬六甲（Má-la̍k-kah，nâ是"馬"字kĕk讀冊音、"六"字kĕk講話音來讀gì話cĭng像，但是潮州語"六"字nâ有"lag8" ciā音）=Melaka、霹靂（phek-le̍k（廈漳臺）/phiak-lia̍k（泉州））=Perak、雪蘭莪 （seh-lân-gô）=Selangor、砂拉越 （Sa-la-oa̍t）=Sarawak、森美蘭 （serm-bí-lân（泉州）/sim-bí-lân（廈臺）/som-bí-lân（漳州））=Sembilan、納閩 （la̍p-bân）=Labuan、林夢（lîm-bāng）=Limbang、勿加泗（bē-ka-sì）=Bekasi都可能是téng潮州語或者閩南語借來gì（găk語言學上潮州語gâe̤ng閩南ho-lo話是方言之間gì關係）。
    但是需要指出gì是，福州語有可能是使自家gì譯名，ng是使國語漢字譯名。像"Melaka" gì福州語是/ma˨˩ laʔ˥ ka˥/（Mā-lăk-gă?），漢字寫法肯定ng是"馬六甲"，gâe̤ng福州語讀音差過遠。nē̤ng-gă大部份人都對東南亞gì福州語文化gâe̤ng方言mâ̤熟，故此nguāi認為ng使直接使國語gì譯名，nguāi估計cī類地名都有福州語自家gì譯名，需要有學者專門去研究考證。
    另外，diŏh美國紐約有cĭng sâ̤福清人gâe̤ng長樂人。對於美國gì主要地名，伊各人有無自家起gì福州語譯名？cuòi也需要有人去考證。--el caballero de los Leones (tō̤ nguāi păng-gōng) 2019 nièng 8 nguŏk 27 hô̤ (B2) 04:41 (UTC)[回覆]

我有收集過馬來西亞共美國其幾個地名。我也問過詩巫衛理報Wong主編，伊講野価地名，大馬其福州儂也都是按漢字翻譯讀出來。

我對「福州話讀出來聽賣會意，故此賣使使福州話翻譯」有保留意見。如果總款講，野価學術概念（ing啻地名）都賣使使福州話講，因為「生活臺中都無」，以後只些條目都寫漢語拼音咯？總款dĕ̤-nè̤ng都會意。

故有汝講「對原語言賣尊重」，那驚會賣尊重ing是儂家需要考慮其問題。翻譯以後其讀音共原底其讀音賣蜀樣，只種情況著野価語言都価得很。

汝講著有紀錄外國地名其書，佪故有子善之前講過其『福州語テキスト』只本書。裏勢其日本地名，全部都是按漢字其福州話讀音讀出來其。--Davidzdh (攀講/Păng-gōng) 2019 nièng 8 nguŏk 27 hô̤ (B2) 06:10 (UTC)[回覆]

大中华地区以外福州话地名表盡好，可以參考 --Yejianfei (tō̤-lâung) 2019 nièng 12 nguŏk 30 hô̤ (Buái ék) 07:10 (UTC)

邀請大家於9月15日前對九工作組的建議草案提供回饋

各位社群夥伴們好：

抱歉因為不熟悉平話字，這邊容許我使用現代漢語。我是今年維基策略討論的聯絡員上官良治。想跟各位分享目前願景2030的進度。在今年瑞典的Wikimania（維基媒體國際會議）中，九個工作組已經針對維基媒體2030發展，撰寫了對於未來的建議草案，每一組成員各自用不同的形式來描述維基媒體九個層面的不同風貌。在此邀請中文維基媒體的社群成員閱讀、提供回饋（尤其這份翻譯文件出自翻譯社，並不是熟悉維基社群的譯者所翻譯，所以若有誤譯或錯譯，也請不吝指出）。以下針對九個工作組各自介紹一個較為大膽或有趣的建議——

  • 倡議工作工作組概述：在未來遇到與開放知識相關的公共政策倡議時（例如網路中立性、著作權的開放等），加強與國際社群的對話，甚至要建立一個全球社群「宣言」或「意向書」，來定義哪些公共政策的倡導工作是維基運動所支持、哪些不是。藉以加強社群對於公共政策倡導的參與與成功度。
  • 能力建設工作組概述：在未來希望能夠建議「能力建設」的新單位，讓志工的各種與維基相關的能力（像是組織、募款、維基功能的教學、合作關係的拓展⋯⋯等種種能力）可以跨過語言以及地域現有的鴻溝。
  • 社群健康工作組概述：在未來將建立全球統一的維基平台行為準則，闡述維基所有計畫所不能容忍的行為（如霸凌、歧視、人肉搜查、未經同意公開隱私）等，提升社群健康多元。
  • 多樣性工作組概述：在未來要所有的相關組織（例如各地分會、主題式組織、甚至用戶組）的領導層級都能夠按照多元族群或性別的背景比例來組成理監事或聯絡人，以最低需要40%男性、40%女性、20%多元族群背景者為組成，若無法達成會有相對應的賞罰機制（例如，若領導比例錯，將無法獲得維基的補助）
  • 合作關係工作組概述：在未來，此工作組認為要打造培訓合作關係能力的教學模組、讓像是紀錄建檔、標示正確的捐贈來源方⋯⋯並且建立一個中央基礎設施，來讓合作關係能夠更好的交流。
  • 產品與技術工作組概述：在未來，讓產品和技術相關的工作能夠更加從基金會去中心化的分散出去，這包括了邀請更多社群的技術人員參與、打造「維基技術宣教團」用深入淺出的方式來介紹維基媒體計畫上相關的技術內涵；對於使用維基的第三方應用，也要花心力來開發（例如，現在已經有很多像是Google Alexa、蘋果Siri等聲控助理使用維基數據Wikidata這個計畫，來訓練自己公司的聲控助理產品）未來運動要花更多心力在了解第三方開放之上。
  • 資源分配工作組概述：工作組所说的“资源”指财务資源，但也包括员工时间、能力和数据。在未來，需要建立平權的资源分配系统。此工作組理解的平權包含三點——（一）机会（例如利用系统和获得资源）、（二）权力（例如就资源做出决策的能力、改变文化現況的能力）和（三）產出。
  • 收入流工作組概述：在未來，增加維基媒體運動財務收入的方式，可以透過「用API要收費」、「品牌授權（把產品標上維基商標販售後獲得權利金）」等方式獲取支持維基媒體運動永續運作的經費。
  • 角色與責任工作組概述：在未來，要將集中在北營（發達國家）的決策權力分散給更多非英語使用者、讓決策機制更貼近社群，並建立一個全球認同的「憲章/章程」來作為未來的維基媒體組織治理基礎。

這些議題在其他社群也引起了許多的討論，期待漢語社群也有機會多方表達自己的想像。本次建議草案的收集期限為期兩週，我將於9月15日截止回饋給策略核心團隊，歡迎在此之前大家有任何問題、意見，都不吝向我直接提出，或是在此文後續發表，讓九個工作組能夠及時獲得社群的回饋，讓我們朝更更開放的人類知識總和前進！謝謝。

--LShangkuan (WMF) (tō̤-lâung) 2019 nièng 9 nguŏk 2 hô̤ (Buái ék) 06:30 (UTC)

@LShangkuan (WMF):已經對手汝敆電報羣裡勢講了。/已經幫你在電報羣裡講了。--Davidzdh (攀講/Păng-gōng) 2019 nièng 9 nguŏk 12 hô̤ (B4) 17:21 (UTC)[回覆]

Wikipedia Asian Month 2019

請協助翻譯成您使用的語言

Wikipedia Asian Month is back! We wish you all the best of luck for the contest. The basic guidelines of the contest can be found on your local page of Wikipedia Asian Month. For more information, refer to our Meta page for organizers.

Looking forward to meet the next ambassadors for Wikipedia Asian Month 2019!

For additional support for organizing offline event, contact our international team on wiki or on email. We would appreciate the translation of this message in the local language by volunteer translators. Thank you!

Wikipedia Asian Month International Team.

MediaWiki message delivery (tō̤-lâung) 2019 nièng 10 nguŏk 31 hô̤ (B4) 16:57 (UTC)[回覆]

Extension of Wikipedia Asian Month contest

In consideration of a week-long internet block in Iran, Wikipedia Asian Month 2019 contest has been extended for a week past November. The articles submitted till 7th December 2019, 23:59 UTC will be accepted by the fountain tools of the participating wikis.

Please help us translate and spread this message in your local language.

Wikipedia Asian Month International Team

--MediaWiki message delivery (tō̤-lâung) 2019 nièng 11 nguŏk 27 hô̤ (B3) 14:16 (UTC)[回覆]

Wiki Loves Folklore

Hello Folks,

Wiki Loves Love is back again in 2020 iteration as Wiki Loves Folklore from 1 February, 2020 - 29 February, 2020. Join us to celebrate the local cultural heritage of your region with the theme of folklore in the international photography contest at Wikimedia Commons. Images, videos and audios representing different forms of folk cultures and new forms of heritage that haven’t otherwise been documented so far are welcome submissions in Wiki Loves Folklore. Learn more about the contest at Meta-Wiki and Commons.

Kind regards,
Wiki Loves Folklore International Team
— Tulsi Bhagat (contribs | talk)
sent using MediaWiki message delivery (tō̤-lâung) 2020 nièng 1 nguŏk 18 hô̤ (B6) 06:14 (UTC)[回覆]

模板:TwinLAT、模板:TwinHAN與模板:Twincdo應該考慮合併

抱歉用普通話，@GnuDoyng, Yejianfei, and 唐吉訶德的侍從:我個人認為這3個模板功能高度重複，都是在白話字與漢字版本條目間連結之用，希望能夠合併成統一一個模板。--Liuxinyu970226 (tō̤-lâung) 2020 nièng 10 nguŏk 31 hô̤ (B6) 00:59 (UTC)[回覆]

你說得有道理，你覺得怎麼合併比較好呢？其實我最希望能做成像中文維基百科一樣的左上角切換方式（大陸簡體、港澳繁體、臺灣正體），搞成跟那樣類似的切換，分別是「平話字」和「漢字」。這樣子能做到嗎？--Yejianfei (tō̤-lâung) 2020 nièng 11 nguŏk 19 hô̤ (B4) 13:52 (UTC)[回覆]

Global bot policy proposal: invitation to a Meta discussion

您好!

I apologize for sending a message in English. 請協助翻譯成您使用的語言. According to the list, your wiki project currently is opted in to the global bot policy. Under this policy, bots that fix double redirects or maintain interwiki links are allowed to operate under a global bot flag that is assigned directly by the stewards.

As the Wikimedia projects developed, the need for the current global bot policy decreased, and in the past years, no bots were appointed via that policy. That is mainly given Wikidata were estabilished in 2013, and it is no longer necessary to have dozens of bots that maintain interwiki links.

A proposal was made at Meta-Wiki, which proposes that the stewards will be authorized to determine whether an uncontroversial task may be assigned a global bot flag. The stewards already assign permissions that are more impactful on many wikis, namely, global sysops and global renamers, and I do not think that trust should be an issue. The stewards will assign the permission only to time-proven bots that are already approved at a number of projects, like ListeriaBot.

By this message, I would like to invite you to comment in the global RFC, to voice your opinion about this matter.

Thank you for your time.

Best regards,
Martin Urbanec (Tō̤-lâung) 2020 nièng 11 nguŏk 24 hô̤ (B2) 11:49 (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 (tō̤-lâung) 2021 nièng 2 nguŏk 6 hô̤ (B6) 13:25 (UTC)[回覆]

Proposal: Set two-letter project shortcuts as alias to project namespace globally

請協助翻譯成您使用的語言

Hello everyone,

I apologize for posting in English. I would like to inform everyone that I created a new global request for comment (GRFC) at Meta Wiki, which may affect your project: m:Requests for comment/Set short project namespace aliases by default globally.

In this GRFC, I propose that two-project shortcuts for project names will become a default alias for the project namespace. For instance, on all Wikipedias, WP will be an alias to the Wikipedia: namespace (and similar for other projects). Full list is available in the GRFC.

This is already the case for Wikivoyages, and many individual projects asked for this alias to be implemented. I believe this makes it easier to access the materials in the project namespace, as well as creating shortcuts like WP:NPOV, as well as helps new projects to use this feature, without having to figure out how to request site configuration changes first.

As far as I can see, Wikipedia currently does not have such an alias set. This means that such an alias will be set for you, if the GRFC is accepted by the global community.

I would like to ask all community members to participate in the request for comment at Meta-Wiki, see m:Requests for comment/Set short project namespace aliases by default globally.

Please feel free to ask me if you have any questions about this proposal.

Best regards,
--Martin Urbanec (talk) 2021 nièng 2 nguŏk 18 hô̤ (B4) 14:12 (UTC)[回覆]

Global bot policy changes

您好!

I apologize for sending a message in English. 請協助翻譯成您使用的語言. According to the list, your wiki project is currently opted in to the global bot policy. As such, I want to let you know about some changes that were made after the global RfC was closed.

  • Global bots are now subject to a 2 week discussion, and it'll be publicized via a MassMessage list, available at Bot policy/New global bot discussion on Meta. Please subscribe yourself or your wiki if you are interested in new global bots proposals.
  • For a bot to be considered for approval, it must demonstrate it is welcomed in multiple projects, and a good way to do that is to have the bot flag on at least 5 wikis for a single task.
  • The bot operator should make sure to adhere to the wiki's preference as related to the use of the bot flag (i.e., if a wiki doesn't want a bot to use the flag as it edits, that should be followed).

Thank you for your time.

Best regards,
—Thanks for the fish! talk•contribs 2021 nièng 4 nguŏk 6 hô̤ (B2) 18:48 (UTC)[回覆]

Global ban proposal for Musée Annam

Apologies for writing in English. 請協助翻譯成您使用的語言 There is an on-going discussion about a proposal that Musée Annam be globally banned from editing all Wikimedia projects. You are invited to participate at Requests for comment/Global ban for Musée Annam on Meta-Wiki. 感謝您！ NguoiDungKhongDinhDanh (Tō̤-lâung) 2021 nièng 12 nguŏk 27 hô̤ (B1) 14:22 (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 (tō̤-lâung) 2022 nièng 1 nguŏk 9 hô̤ (LB) 13:14 (UTC)[回覆]

Subscribe to the This Month in Education newsletter - learn from others and share your stories

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.

About This Month in Education · Subscribe/Unsubscribe · Global message delivery · For the team: ZI Jony (Talk), Buái-sé 20:20, 24 Sĕk nguŏk 2024 (UTC)

We are really sorry for posting in English

Voting in the Wikimedia sound logo contest has started. From December 6 to 19, 2022, please play a part and help chose the sound that will identify Wikimedia content on audio devices. Learn more on Diff.

The sound logo team is grateful to everyone who participated in this global contest. We received 3,235 submissions from 2,094 participants in 135 countries. We are incredibly grateful to the team of volunteer screeners and the selection committee who, among others, helped bring us to where we are today. It is now up to Wikimedia to choose the Sound Of All Human Knowledge.

Best wishes, Arupako-WMF (tō̤-lâung) 2022 nièng 12 nguŏk 15 hô̤ (B4) 08:32 (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)

IMPORTANT: Admin activity review

Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, interface administrator, etc.) was adopted by global community consensus in 2013. According to this policy, the stewards are reviewing administrators' activity on all Wikimedia Foundation wikis with no inactivity policy. To the best of our knowledge, your wiki does not have a formal process for removing "advanced rights" from inactive accounts. This means that the stewards will take care of this according to the admin activity review.

We have determined that the following users meet the inactivity criteria (no edits and no logged actions for more than 2 years):

  1. GnuDoyng (bureaucrat, administrator)

These users will receive a notification soon, asking them to start a community discussion if they want to retain some or all of their rights. If the users do not respond, then their advanced rights will be removed by the stewards.

However, if you as a community would like to create your own activity review process superseding the global one, want to make another decision about these inactive rights holders, or already have a policy that we missed, then please notify the stewards on Meta-Wiki so that we know not to proceed with the rights review on your wiki. Thanks, ~~~~ Uncitoyen (tō̤-lâung) 2023 nièng 2 nguŏk 19 hô̤ (LB) 21:13 (UTC)[回覆]

語言欄標籤已經改成雙文字

嘢高興告訴大家，語言欄標籤已經改成雙文字！現在，汝敆其他語言其維基百科上，就會使看見儂家語言顯示「閩東語 / Mìng-dĕ̤ng-ngṳ̄」。感謝相關人員其貢獻。 Yejianfei (tō̤-lâung) 2023 nièng 3 nguŏk 31 hô̤ (B5) 08:00 (UTC)[回覆]

取自「https://cdo.wikipedia.org/w/index.php?title=Wikipedia:Duâi_chéu_â/Archive_2&oldid=98702」