User talk:Shizhao

Here's your quick overview of what has been happening around Wikidata over the last week.

• Discussions
  • Open request for adminship: NewDataB
  • New request for comments: semi-protection to prevent vandalism on most used Items, Allow for Wikidata items to be created that only link to a single Wikimedia Commons category (Wikidata notability discussion)

• Events
  • February 19th: Wikidata meetup in London - Facebook event
  • February 21st to 24th: International Mother Language Day edit-a-thon
  • February 23rd: editathon about Parliament of Ghana in Accra - Registration
  • March 28th: GLAM & Wikidata day in Switzerland (registration running until March 18th)

• Press, articles, blog posts
  • Let’s Tango: Computational Musicology Using Wikidata, MusicBrainz and the Wolfram Language, by Toni Schindler

• Other Noteworthy Stuff
  • Got some time? Add QIDs to the tools on Edit items, Query data, Enhance user interface, Visualize data, Lexicographical data, For programmers and List of properties. If some tools don't have their own Items, feel free to create them.
  • Hardware issues at Toolforge and CloudVPS affect lots of tools and coincide with changes in the statement stats dynamics
  • WikibaseCirrusSearch will become a Mediawiki extension
  • You can still help Shani Evenstein with her research: Wikidata as a Learning Platform

• Did you know?
  • Newest properties:
    • General datatypes: drag coefficient, illiterate population, literate population, non-free artwork image URL, taxon author citation, total goals in career, stall speed
    • External identifiers: Enciclopedia delle donne ID, Joan Miró Online Image Bank ID, BIDICAM authority ID, Board Game Atlas ID, BVPH authority ID, CCBAE publication ID, ISTC No., KSI player ID, Biblioteca Virtual Andalucía authority ID, Georgian National Filmography ID for Persons, JWF Wrestlers Database person ID, Indian census area code (1991), Lithuanian Sport Encyclopedia (LSE) article ID, Eliseu Visconti Project ID, UN/CEFACT common code
  • New property proposals to review:
    • General datatypes: ScaleNet ID, Lokalhistoriewiki article, Identifiant itch.io, approach angle, departure angle, ride height, type of front suspensions, type of rear suspensions, Football Money League rank, is model of, constraint clarification, has phenotype, observed in, replacement property, evidenční číslo domu, Stack Exchange site
    • External identifiers: WhoSampled artist, äriregister, ISO 639-3 Change Request ID, Queerly Represent Me identifier, V.League player ID, Martindale-Hubbell profile, Google Play Movies & TV id, Fondation Maeght ID, identifiant d'un jeu de données sur data.gouv.fr, BHL part ID, ETS Designated Institution code, Gateway to Research Project ID, Yandex.Music label ID, Yandex.Music genre ID
  • Query examples:
    • Bubble chart of Indian universities with the most people ever employed by them (source)
    • Graph of shared borders between certain West Bengal community development blocks (source)
    • Tree map of ambassadors to India (source)
    • Fictional swords (source)
    • Taxa named after women scientists (source)
    • Timeline of red pandas (source)

• Development
  • Improve the tools dropdown on query.wikidata.org, which now links Tools categories and the Toolforge (phabricator:T214577)
  • Implement the diff view for Schemas (phabricator:T214396, phabricator:T215514)
  • Implement undo for Schemas (phabricator:T214914)
  • Prevent redirecting an entity to itself (phabricator:T214775)
  • Make pressing enter when editing a lemma save the lemma (phabricator:T206140)
  • Strip whitespace around sense glosses (phabricator:T212019)
  • Create LilyPond datatype (phabricator:T215284)
  • More work to get the new version of the termbox readable on mobile

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

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Suggested and open tasks!
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Lea Lacroix (WMDE) 2019年2月18日 (一) 15:36 (UTC)

The winner this Translation of the week is en:Tierra del Fuego gold rush Please be bold and help to translation this article! Between 1883 and 1906 Tierra del Fuego experienced a gold rush attracting a large number of Chileans, Argentines and Europeans to the archipelago, including a large number of Dalmatians. The gold rush led to the formation of the first towns in the archipelago and fueled economic growth in Punta Arenas. After the gold rush was over, most gold diggers left the archipelago, while the remaining settlers engaged in sheep farming and fishing. Indigenous Selk'nam populations declined sharply during the rush. (Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.) About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery 2019年2月18日 (一) 01:09 (UTC)

Welcome to the fifth newsletter for the new Growth team!  

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

New projects for discussion

We began the "Personalized first day" project with the welcome survey so that we could gather information about what newcomers are trying to accomplish. The next step is to use that information to create experiences that help the newcomers accomplish their goal – actually personalizing their first day. We asked for community thoughts in the previous newsletter, and after discussing with community members and amongst our team, we are now planning two projects as next steps: "engagement emails" and "newcomer homepage".

• Engagement emails: this project was first discussed positively by community members here back in September 2018, and the team how has bandwidth to pursue it. The idea is that newcomers who leave the wiki don't get encouraged to return to the wiki and edit. We can engage them through emails that send them the specific information they need to be successful – such as contact from a mentor, the impact of their edits, or task recommendations. Please read over the project page, and comment on its discussion page with any ideas, questions, or concerns. Do you think this is a good idea? Where could we go wrong?
• Newcomer homepage: we developed the idea for this project after analyzing the data from the welcome survey and EditorJourney datasets. We saw that many newcomers seem to be looking for a place to get started – a place that collects their past work, options for future work, and ways to learn more. We can build this place, and it can connect to the engagement emails. The content of both could be guided by what newcomers say they need during their welcome survey, and contain things like contact from a mentor, impact of their edits, or task recommendations. Please read over the project page, and comment on its discussion page with any ideas, questions, or concerns. Do you think this is a good idea? Where could we go wrong?

Initial reports on newcomer activity

We have published initial reports on each of the team's first two projects. These reports give the basic numbers from each project, and there are many more questions we will continue to answer in future reports. We're excited about these initial findings. They have already helped us define and design parts of our future projects.

• Welcome survey: the initial report on welcome survey responses is available here. Some of the main findings:
  • Most users respond to the survey, giving it high response rates of 67% and 62% in Czech and Korean Wikipedias, respectively.
  • The survey does not cause newcomers to be less likely to edit.
  • The most common reason for creating an account in Korean Wikipedia is to read articles—not for editing—with 29% of Korean users giving that responses.
  • Large numbers of respondents said they are interested in being contacted to get help with editing: 36% in Czech and 53% in Korean.
• Understanding first day: the initial report on what newcomers do on their first day is available here. Some of the main findings:
  • Large numbers of users view help or policy pages on their first day: 42% in Czech and 28% in Korean.
  • Large numbers of users view their own User or User Talk page on their first day: 34% in Czech and 39% in Korean.
  • A majority of new users open an editor on their first day – but about a quarter of them do not go on to save an edit during that time.

Help panel deployment

The help panel was deployed in Czech and Korean Wikipedias on January 10. Over the past four weeks:

• About 400 newcomers in each wiki have seen the help panel button.
• About 20% of them open up the help panel.
• About 50% of those who open it up click on one of the links.
• About 5% of Czech users ask questions, and about 1% of Korean users ask questions.

We think that the 20% open rate and 50% click rate are strong numbers, showing that a lot of people are looking for help, and many want to help themselves by looking at help pages. The somewhat lower numbers of asking questions (especially in Korean Wikipedia) has caused us to consider new features to allow people to help themselves. We're going to be adding a search bar to the help panel next, which will allow users to type a search that only looks for pages in the Help and Wikipedia namespaces.

How to create a good feedback page?

What is the way to built a good help page? What blocks you when writing an help page? Your replies will help to create better help contents to newcomers, that would be used on Help panel.

Growth team's newsletter prepared by the Growth team and posted by bot, 2019年2月13日 (三) 14:15 (UTC) • Give feedback • Subscribe or unsubscribe.

抱歉迟了，新年快乐，祝福。感谢处理站务以及TOW。祝身体健康，愉快!

我看到您最近正在大量移动法语城市名称，并附上google链接。事实上，google对法国市镇的中文翻译大部分都直接按照英文标准，没有尊重法语地名的原有读音。比如蓬斯（Pons），事实上该市镇"s"在法语中不发音。此外，一些明显可以意译的名称却直接音译，虽符合标准，但却使得其名称冗长，不易让中文读者记忆。

参考WP:命名常规，维基百科取常用名，而不是正确发音的名字。你的一些音译完全没有任何中文来源，而一些意译更没有任何参考来源。请参考WP:原创研究，这样是不行的

本人阅读维基百科:命名常规及维基百科:命名常规/中文译名具争议条目命名后并未发现有"维基百科取常用名，而不是正确发音的名字"这一项。谷歌地图对法国境内的大多数市镇中文翻译未按照法语标准，事实上也并非官方名称，不具有权威性。在没有别的文献资料情况下，本人完全按照规则翻译，个人认为不属于所谓的"原创研究"。

我最近在修正法国地名翻译，发现您对许多地方都进行过更改。事实上，您并没有按照规则进行更改。首先，在改之前请您看看《世界地名翻译大辞典》，网上有现成的pdf可供您下载甚至在线参看，很多地名上面都有，若上面有并且无误则不需要更改。其次，当下以音译为主，意译的当下原则是只把两个地名的位置关系意译，例如Neuilly-sur-Seine亦作塞纳河畔讷伊，不能见到什么有含义的就都把他意译了，比如把布瓦科隆布Bois-Colombes意为鸽林，不可取，要不然当今世界上大多数地名都得重译，比如把里弗赛德Riverside译成河边，把诺伊施塔特Neustadt译成新城，这不出大乱子了，学过点外语，这点基本的单词谁不知道？这个城市名的意思谁看不出来？英国人把北京译成North Capital了？法国人把山东译成L’est de Montagne了？事实上正确的做法应该是把含义可以在括号内补充，比如 布瓦科隆布（法语：Bois-Colombes，意为“鸽林”）。还有，您真的是知道规则翻译了？给您个好东西：Wikipedia:外語譯音表/法語，虽说不能用于地名翻译，但结合《世界地名翻译大辞典》看，实际上跟《世界地名翻译大辞典》上翻译出来的效果出入不大，您完全可以拿来当地名翻译参考。还有一些规则，把《世界地名翻译大辞典》可以翻烂了总结出来，比如l在最末译成勒，在词中辅音前译成尔；元音+se+辅音，se译成斯而不是瑟；aux译作欧而不是奥……而您呢，把wi译成威就不说了，甚至还把原本好端端的Dannemarie达讷马里给改成了当讷马里，您不会连最基本的发音规则——ann读成[an]而不是[ɑ̃]都不知道吧？更有甚者还把re译成赫，您是想步台巴子的后尘把Macron马克龙译成马克宏？在当代应该做的是把真正错误的有错误的音译更正，比如把Éblange（原为埃布朗格）改正为埃布朗日，而不是做徐志摩把威尼斯译成翡冷翠。鄙人在更正译名之前都先翻一遍《世界地名翻译大辞典》，若实在是有疑义则再去该词条法语页面以及https://fr.wiktionary.org/wiki/Wiktionnaire:Page_d%E2%80%99accueil上查音标，若是在是太小的地方连个音标记录都没有，我会上Forvo搜本地人对这个地方的发音，甚至是去Youtube上搜该地名看有没有视频里有人念出该地名，查完了才会按照规则去修正，而阁下对各词条东改一下西改一下会让整个维基的地名翻译严重碎片化。当然，我上述之言多少可能会带点情绪，但本着共同维护建设维基的目的，还是能希望与阁下携起手来完善法国及法语区的地名翻译。

此致

敬意

1. 您提到的《世界地名翻译大辞典》，其仅有的参考资料《外语地名汉字译写导则-法语》我一年前就邮购过了，短短十几页而已，虽有参考价值，但很多细微之处却各种自相矛盾，漏洞百出：比如按照该表，"Essonne"和"Yvelines"分别应翻译成埃索讷和伊夫利讷，结果新成立的Essonne省和Yvelines却是"埃松省"和"伊夫林省"，倒是下属的"Corbeil-Essonne"却被译为"科贝伊-埃索讷"，毫无逻辑可言；另外在文中距离提到"Notre-Dame-de-l'Isle"应译为"利斯圣母村"，结果Isle的法语读音是[lil]，没有S这个音节，何况法国行政区划当中并没有"村"这一级，加上这个单位完全是无中生有。综上，本人认为该表仅应做参考使用，不具有强制性。

2. aux的翻译由奥改成欧本来也是我的主张，比如；ge或ges在词尾应翻译成日亦同理：。此外翡冷翠是佛罗伦萨的翻译，和威尼斯一点关系都没有。

3. 本人涉足翻译也就两年历史，一些早期的误译在后期都在不断更正中，比如"Les"由"雷"改成"莱"。但本人精力有限，不可能一下子全部改掉。鸽林的翻译最早并非来源于本人：，就算阁下不去移动，我也会在之后改正。

4. 对于那些在2015-292法律颁布后成立的法国市镇，其大部分名称来源本来也是某个或某些具体事物，比如Val、Côte、Village之类；一些原有的地名内也含有具体的地理事物，比如Chapelle、Ferté、Eglise一类。对于这种地名，本人主张意译。前文提到的《外语地名汉字译写导则-法语》内也有类似的主张，比如Villeneuve翻译成"新城"。

5. 相同的拼写，也有可能在不同情况下发不同的音。比如"Brest"、"Crest"后面的"st"发音，而"Chârost"不发。要命的是，这种东西字面上很难判断，音标也不一定写在法语维基百科上，若不是本人生活中有朋友来自于Chârost，我可能也会把这个地方翻译成"沙罗斯特"。

6. 通过Youtube或者dailymotion之类的视频网站来检查也是我翻译地名的一个渠道之一，尤其是非正统法语区的地名。而正统法语区法语中几乎没有W开通的单词或城市，Wi本人翻译成"威"是为了和本土的"Vi"进行区分，阁下若觉不妥欢迎更正。

感谢

事实上鄙人最近做上下莱茵省和摩泽尔省各市镇的译名更正，因为此三省有大量德语词汇的地名，它们的发音方式并不遵循法语的正字法，而这些地名词条是当年大量按照法语正字法机翻的，所以发音方式错的离谱。打开谷歌，随便搜几个这些错译的译名，就会发现这些错译已经遗毒甚广了，所以最近我在更正这些译名，目前上莱茵省已经进展到一半了。另说一下我的音译原则，就是德法都有的音，用法语的音译法；只有德语有的音，就用德语的音译法。比如/ʃ/音德法都有，于是就用法译的“什”而不用德译的“施”；法译法里没有对应t͡s这个音的，于是就用德译的“茨”。

另说一下，《大辞典》中的译名基本上都是正确的，若地名真正的发音与《大辞典》给出的译法相匹，则应切实遵循《大辞典》。但书中偶有谬误，譬如Corbeil-Essonnes，《大辞典》中给出的译名为“科尔贝莱索讷”，事实上真正的发音是[kɔʁbɛj esɔn]，根本没有/l/，所以译成“莱”定是错的，而Essonnes的通俗译名是埃松，所以就算译成埃索讷也不可取。而更大的问题出在上下莱茵及摩泽尔省的各市镇译名，比如Drulingen，《大辞典》给出的翻译是德吕兰让，但事实上该词真正的发音是[dʁylɪŋən]，应译为德吕林根。若是错到如此明显了，则应该不再依照《大辞典》。

还有，许多市镇的区arrondissement和县canton在15年区改组后都发生了变化，望阁下能在编辑时把他们对照法语页面进行改正，这也是我现在在做的另一件事。

Merci

关于最后一条，根据2015年的法国新行政法案，Canton不再隶属于arrondissement，一个canton可能由不同的区当中的commune组成，这样的话XX区XX县的表达就会明显有误；此外，新法案当中canton仅保留省级选举功能，在日常生活中几乎用不上，因此显示canton信息的价值量大大降低。综上，本人在更改词条时偏向于不再介绍其所在的canton。

最近发现阁下把大量的-ville改成了维勒，这个不用改。虽说是以/-l/结尾，但-ville翻译成维尔是属于历史原因约定俗成的，外语地名汉字译写导则 法语(GB/T 17693.2-1999)明确说明了“…但ville发[vil]，汉字习惯译为“维尔”；其派生形式也按此译法”，望阁下留意

不太同意这一条。"历史原因"是因为近代法语存在大舌音，使得法语的"r"在汉语中只能通过"l"来翻译，真正的"l"却由倒过来，比如阿尔比，加之同一时期北美殖民地出现了大量的以ville结尾的城市，因此"维尔"一名大肆流传。但因为现代法语已不存在大舌音，个人认为为了和英语国家的ville进行区分，法国本土地名中的ville翻译成维勒可能更好（省会城市和有过重大历史项目的城市除外，比如沙勒维尔-梅济耶尔和阿尔贝维尔）。何况"维尔"也会和vire之类的法国常见地名混淆。

Belle之类的同理

如果真要按照"约定俗成"的话，可以意译为"XX城"，比如"美丽城"或"犹太城"。

我说的历史原因约定俗成指的是在法语地名翻译中已经习惯了把ville翻译成维尔，译写导则上亦作了规定，所以应该遵循而不要违背，哪怕发音是[vil]。还有，l在词中译作尔词尾译作勒是因为二者在听感上事实是不一样的，词尾的l在听感上接近于/lə/，词中的l则不是，说白了就是词中的l是舌头抵着上颚，“勒”没“勒”出来，而词尾的l是“勒”出来了，我想阁下应该很清楚这一点，故词中的l应译作尔而不是勒。

维尔的话，我不想管了，以后都在条目正文里以"XX维尔，现代法语又译XX维勒（法语：），是法国XX省的一个市镇..."这样开头吧（火车站类条目同理）。

关于词中的l，我想阁下应该不会把Albi读成Abi吧。。。

词中的位于辅音前l的发音我很清楚，也会标准地发出，而不是发不出来读成Abi，因为我是德语使用者，舌头抵着上颚，“勒”没“勒”出来这个音，德法都有也都一样。不同的是德语词尾的l仍然是这个音，而不是像法语一样发得类似/lə/，故德语词尾的l仍译作尔。

德语我不了解。法语里面l在词尾必须发音；词中可能发音，也可能省略（比如Montmarault）。“勒”没“勒”出来这个音在法语里确实存在，比如Castelnaudary，l读的很轻，但不会变成"r"的发音。

私以为Montmarault的l不发音应该属于词尾辅音不发音的范畴，准确地说是词尾lt不发音，如果没有t的存在，那么l必定发音；而我所说的位于辅音前的l那种“勒”没“勒”出来的发音也不是指的"r"音，此l的发音既不像"r"也不是"r"

既然"发音既不像"r"也不是"r""，那l就不应该翻译成"尔"。个人认为约定俗成不应成为现代法语地名翻译的唯一理由，就像不会因为"巴黎"而把所有的"ris"或者"ri"都翻译成"黎"一样。

小舌音ʁ也不像普语的尔啊，事实上诸外语与普语能对的上的音节就没几个，而翻译成尔则是遵循规则，我前面给你讲的l的发音不同只是给你讲为何词中词尾尔勒两译，而不是说它像不像ʁ。至于巴黎则是至少百年之前的老翻译，那个时候可没有外语地名汉字译写导则，现在留用巴黎是使用约定俗成的译名，而现在其他的的ri就都依照导则译作里了。

德语发音有规则可循，就算是发音和汉语不像，统一翻译成“尔”可以倒推出原词。但法语却很难做到，因此遵循城市名的原发音应是法语汉译的原则。按照《外语地名汉字译写导则-法语》，由Ville和Paris两个"约定俗成"单词而衍生出来的"Villeparisis"恐怕就得翻译成"维尔巴黎西"了。

是维勒帕里西。因为-ville译成维尔只规定用于词尾后缀，前面的Ville不受影，比如Villepinte在导则的中的译名就是维勒潘特。还有parisis是一个区域名，或者说是一种历史称呼，现在都叫Pays de France，翻译不用拘泥于巴黎，就像英格兰中的“英格”与盎格鲁（不过拼写和发音都有差别），罗曼与罗马。

我也赞成维勒帕里西的译法，但严格来说Parisis是巴黎一名的来源，按照"约定俗成"就应该保留"巴黎"词根。Pays de France（全名为"Communauté d'agglomération Roissy Pays de France"）是2016年才成立的城市公共社区，该名称不影响历史上的Parisis部落称呼，Villeparisis也没有因此而改名。罗曼和罗马分别对应Romain和Roma（法语为Rome），不是一个单词。

回到正题上，在词根母语发音没有变化的情况下，其在词中位置不应影响汉语翻译。按照导则的标准（前置与后置翻译不同）将产生大量逻辑上的混乱：比如Francheville和Villefranche当中的Ville法语发音完全相同，若按照导则的标准来音译却分别是"弗朗什维尔"和"维勒弗朗什"（不过此词根一般意译为"自由城"）；再比如若Ville在词中翻译为"维勒"，那Ville-la-Grand、Joinville-le-Pont这种多个词汇组成的地名按照音译又该怎样翻译？Charleville翻译成"沙勒维尔"，合并了Mézières之后组成的新城市也要更名成"沙勒维勒-梅济耶尔"吗？

不用保留巴黎，除非他叫Villeparis，还是那句话，不用拘泥于Paris来自Parisis，实在想告诉读者二者联系的话可以在条目中作补充说明。我所说的罗曼是指的罗曼语族的罗曼。弗朗什维尔和维勒弗朗什两译我觉得没什么问题。xxxville与其他成分组合的话，xxxville单独拿出来译作xxx维尔，不会因为后面加了什么东西而变化，如Joinville-le-Pont = Joinville + le-Pont ，故译作茹安维尔勒蓬； Charleville-Mézières = Charleville + Mézières，故同理译作沙勒维尔-梅济耶尔；Ville-la-Grand则译作维勒拉格朗或拉格朗城。

见WP:COMMONNAME，使用事物的常用名称。这和官方名称无关。有其他的中文文献资料使用了这个译名，自当使用这个译名。这和发音是否正确/是否按照法语标准一点关系没有。

我承认很多法国城市名称仅有谷歌为唯一的中文文献。但若将谷歌作为文献命名标准，至少三分之一以上的法国城市的中文译名和其本身的读音或含义完全不一致。

因此，为了方便读者理解，我认为您在移动条目的时候也应当在对应条目中注明"该市镇的中文名称来源于谷歌翻译，不符合法语实际发音，实际中文音译更接近于XXX"之类的提示语，而并非简单的移动了事。

我并没有单单参考google地图（更没有用google翻译），我只是尽量去找已有的中文译名（给出一个google地图链接只是一种方便）。用什么译名不应该由维基百科决定，而是应该由维基百科之外来决定。换句话说，不应该让维基百科去影响世界，而是让世界来影响维基百科。维基百科只是记录这些知识。中文语境下某个地名就是这么翻译，发音再不准，也是实际情况如此，用一个发音准的译名，在中文语境下反而不知道是什么了。如果想要中文语境下使用准确发音的译名，正确做法是通过维基百科之外的出版、发表等等各种手段来使大家接受这个准确的发音译名，在此之后，维基百科才应该使用这个准确的译名。

我承认这一点。但即便是这样，您也不应该直接回退了事。我之前在更正每个法国市镇名称的时候，大部分都或多或少地增加或修改了一些条目内容（比如所处的地理位置、从属的上一级行政单位等）。您的直接回退使得这些内容完全消失，我认为直接回退不妥。

我只是移动了。只有个别几个修改了一下版本

Wikipedia:外語譯音表/法語，此音译表下方有详尽的地名翻译规则，愿各位维护者共同按照此规则将目前wiki上有误的译名更正。我大体看了一下，不说法国，很多国家的地名页面都是当年机翻批量生产的（也好，一是如果不机翻那么现在中文地名页面估计没有几个，二是如果各个翻译者各按各的想法翻译那么译名的碎片化会很严重，比如同一个-ville可能有的人翻译成维尔有的翻译成维勒有的翻译成威尔……），不过能看出来，机器是按照各个国家语言对应的音译规则表去翻译的，而且基本上都翻译的很准确，但是由于法语地名的发音以及法语正字法实在是太野鸡，所以翻译错误率比很多其他地方要高（相比之下德语各地名基本上都翻译的没错），上下莱茵省的地名由于大都来源于德语，所以地名翻译基本上全线阵亡……

Here's your quick overview of what has been happening around Wikidata over the last week.

• Events
  • Past: Linking OpenStreetMap and Wikidata at FOSDEM

• Press, articles, blog posts
  • Paper: Discovering Implicational Knowledge in Wikidata

• Other Noteworthy Stuff
  • There is now an experimental SPARQL service to query Wikidata history

• Did you know?
  • Newest properties:
    • General datatypes: day of regular release, Euler characteristic, has lyrics, maintenance method, CBFC rating, does not have quality
    • External identifiers: Code of Natura 2000/FFH habitat, Douban Author ID, Douban Book ID, Douban Drama ID, Douban Game ID, Douban Music ID, Douban Musician ID, Douban Read Author ID, Douban Read eBook ID, Douban Site Name, Douban Username, Zhihu username, Bilibili bangumi ID, Bilibili tag ID, Bilibili username, Bilibili video ID, Eventa Servo ID, Mtime movie ID, QQ number, Swedish Organization Number, Rock's Backpages artist ID, Rock's Backpages author ID, Rock's Backpages publication ID, Mtime people ID, Democracy Club ID, Hulu movie ID, Hulu series ID, ISA ID, Fuzhou Architecture Heritage ID, DALFAN ID, Den Digitale Byport ID, GameFAQs franchise ID, NMSRCP reference number, Swiss Films ID, CABB player ID, castingvideos ID, Mecklenburg-Vorpommern protected area ID, IEEEXplore author ID, IEEEXplore document ID, Strepsiptera database species ID, Image Archive, Herder-Institut, WBCHSE code, Antarctica NZ Digital Asset Manager, Brentidae of the world species ID, Pacific Coast Architecture Database building ID, Illustrated catalog of Tessaratomidae species ID
  • New property proposals to review:
    • General datatypes: creator name string, Literate population, Illiterate population, designated survivor, stall speed, maintain, Insects (Insecta) of the World ID, solar eclipse type, student organization of
    • External identifiers: BibliotecaVirtualAndalucia authority ID, BIDICAM authority ID, BVPH authority ID, CCBAE ID, identifiant sur l'annuaire du service public, Joan Miró Online Image Bank ID, ISTC No., KSI player ID, Board Game Atlas ID, LSE article ID, JWF Wrestlers Database, Georgian National Filmography ID for Persons, Eliseu Visconti Project ID, Indian census area code (1991), AICTE Permanent ID, German School ID, DOGC ID, DoBIH Number
  • Query examples:
    • Counts of Indian films directed and written by the same person, sorted by film language (source)
    • Sovereign states that have more than one capital city (source)
    • Decreases in sex ratio for mandals of West Godavari district between 2001 and 2011 (source)
    • Counts of articles published in different Indian medical journals, sorted by year/journal (source)
    • Forms to Lexeme ratio per language (source)
    • Airports and railway stations named after fictional people or works of fiction (source)
    • Species of hummingbirds, their genus, and image (source)

• Development
  • Working on the "in more languages" and "all entered languages" parts of the termbox on mobile
  • Working on making undo, revert, edit summaries and more work for Shape Expressions
  • Fixed an error when detecting the same label and description in another Item (phabricator:T194770, thanks Matěj)
  • Making Lemma input on Lexeme pages save your input when you press enter (phabricator:T206140)
  • Making QuickStatements work more easily for other Docker-powered Wikibase instances (phabricator:T205606)
  • Worked more on making Federation work for making Statements on Wikimedia Commons (phabricator:T214557)
  • Working on stripping whitespaces at the beginning and end of Glosses when saving them (phabricator:T212019)
  • Looking into adding more signals to ORES' vandalism detection model so we can detect bad edits more accurately (phabricator:T194737)
  • Preventing a redirect of an Entity onto itself (phabricator:T214775)
  • Fixed an issue with adding sitelinks from Wikimedia Commons (phabricator:T213975)
  • Unified the separators between language and lexical category in different places (phabricator:T201808)

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Suggested and open tasks!
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Lydia Pintscher (WMDE) 2019年2月11日 (一) 20:32 (UTC)

The winner this Translation of the week is en:Fairbank train robbery Please be bold and help to translation this article! The Fairbank train robbery occurred on the night of February 15, 1900, when some bandits attempted to hold up a Wells Fargo express car at the town of Fairbank, Arizona. Although it was thwarted by Jeff Milton, who managed to kill "Three Fingered Jack" Dunlop in an exchange of gunfire, the train robbery was unique for being one of the few to have occurred in a public place and was also one of the last during the Old West period. (Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.) About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery 2019年2月11日 (一) 02:26 (UTC)

This Month in GLAM – Volume IX, Issue I, January 2019 Headlines Armenia report: Photographs by Vahan Kochar (continuation) Belgium report: Public domain day edit-a-thon; Hack The Gender Gap edit-a-thon Brazil report: GLAM Wiki at the Digital Collections Conference and new partnership with Casa de Rui Barbosa Colombia report: First report from GLAM in Wikimedia Colombia Czech Republic report: Prachatice Museum France report: #1lib1ref; Museum of Brittany Indonesia report: Indonesian Wikisource meetup; more documents from Museum Tamansiswa Italy report: Celebrating Wikipedia and remembering the Holocaust Norway report: Diversity in Glam projects Serbia report: GLAM Winter in Serbia Sweden report: Hackathon with the National Library of Sweden UK report: Wales and Oxford USA report: Snowdays/Shutdowns but Lots of Open Access Wikidata report: New year, new newsletter format WMF GLAM report: Structured Data on Wikimedia Commons Calendar: February's GLAM events Read this edition in full • Single-page To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

About This Month in GLAM · Subscribe/Unsubscribe · Global message delivery · Romaine 2019年2月9日 (六) 13:59 (UTC)

我想問閣下https://zh.wikipedia.org/w/index.php?title=34%E8%A1%97-%E5%93%88%E5%BE%B7%E9%81%9C%E8%AA%BF%E8%BB%8A%E5%A0%B4%E8%BB%8A%E7%AB%99&diff=46039057&oldid=45981873 這個移動是因為沒有其他消歧義重名嗎？若然，我會去移動其他類似的車站了。

	新年快樂！
	祝書生新年快樂，身體健康！