User talk:Suzukaze-c/archive

Active discussions



Just wondering, why you have tagged 宏碁 with RFV? --Anatoli T. (обсудить/вклад) 22:47, 22 December 2014 (UTC)

I supposed that it fell under Wiktionary:Criteria_for_inclusion#Company_names —umbreon126 00:23, 23 December 2014 (UTC)


Thanks for the usage example. Note that Cantonese Jyutping, like Mandarin Pinyin is semi-automated. You only need to provide it with {Jyutping} when you want to override the automatic transliteration. I've also added red-linked words: 成日, 喺度, 食煙. --Anatoli T. (обсудить/вклад) 02:31, 21 January 2015 (UTC)

I overrided the automatic transliteration because it output "hai2 dok6" for "喺度" (And thank you for cleaning up my red links!) —umbreon126 02:34, 21 January 2015 (UTC)
Oops. It's better this way, note 度{dou6}:
  1. 阿伯成日喺度食煙到死 [Cantonese, trad.]
    阿伯成日喺度食烟到死 [Cantonese, simp.]
    Jau5 go3 aa3 baak3 sing4 jat6 co5 hai2 dou6 sik6 jin1, cau3 dou3 sei2. [Jyutping]
    There's always an old man who sits here and smokes, and it reeks.
--Anatoli T. (обсудить/вклад) 02:55, 21 January 2015 (UTC)
I was unaware that it also worked for Cantonese, I'm sorry (^^;;) (Template:zh-usex/documentation says "For MSC,"; perhaps this should be updated/changed?) —umbreon126 02:58, 21 January 2015 (UTC)
No worries, updated the doc. --Anatoli T. (обсудить/вклад) 03:04, 21 January 2015 (UTC)


Discussion moved to Talk:塑.



{{vi-hantu}} is used for longer words as well, proper nouns are an exception. You need |pos=n, etc. The doc needs updating to reflect this. --Anatoli T. (обсудить/вклад) 05:27, 11 March 2015 (UTC)

I see (´∀`;) Updated documentation would be good. —umbreon126 05:41, 11 March 2015 (UTC)
Your edit was right because it's a proper noun (exception) :) --Anatoli T. (обсудить/вклад) 05:55, 11 March 2015 (UTC)
ah. oops —umbreon126 05:57, 11 March 2015 (UTC)
I find this a bit inconsistent. You can use {{vi-new/ht}} to generate Hán tự entries but it only generates "Noun" header, doesn't add PoS - only works for common nouns. We can ask Wyang when he gets back to address this. I can't do it. --Anatoli T. (обсудить/вклад) 06:03, 11 March 2015 (UTC)

Explanation for edit version at Edit

I'm curious as to why you reverted my edit at . Any reasonable explanation will do. Bumm13 (talk) 04:56, 28 March 2015 (UTC)

See the edit history (summary?) —umbreon126 05:00, 28 March 2015 (UTC)
Okay, I apologize for being so brusque with my previous comment; I found that variant glyph at Glyphwiki and it is correct. Thanks for your correction! Bumm13 (talk) 05:03, 28 March 2015 (UTC)
It's fine :) —umbreon126 05:05, 28 March 2015 (UTC)


4 :]

No problem :) —umbreon126 06:35, 24 April 2015 (UTC)

therusd2b.abutn@ ea.rndampp'shownewr.pag,wasv.andyw/myhandz.. 07:00, 25 April 2015 (UTC)

My apologies, but I'm having a hard time deciphering this message (;´д`) Could you please make it a bit clearer? (the most I got was "there used to be a button at" (?); the rest is less legible...)--—umbreon126 07:29, 25 April 2015 (UTC)
-@[sou'dHOPfromrnd2rndp.i/1lect w/outgoinbakea.time:)
"there used to be a button at each random page <so you'd hop>? from random page to random page ... without going back each time :)"
A "Random entry" link is on the left of each page under but unfortunately it's not restricted to one language (I don't really like this either; conjugated forms of Italian verbs just don't catch my interest...)
I'm not aware of any other buttons :(
Perhaps you could add one of the Wiktionary:Random_page links to an easily accessible browser bookmark? —umbreon126 06:31, 26 April 2015 (UTC)

kanucheko/dadROLBAKpl?Edit wasboutmakinC.HEELofit~c-neus,sai[nitypmy.andzpainfl4such,man-evnmorsoi/ensuinconfusin,juscosoftrig-fingrmoronz:(( 03:27, 26 April 2015 (UTC)

I'm not sure I understand what the issue is (I'm afraid that I can't really understand this sentence either) :( (by the way, it's a good idea not to insult other users, no matter what the situation) —umbreon126 08:18, 26 April 2015 (UTC)


Hello. Why is there a trend for unified Chinese? Is there a discussion board for it? DerekWinters (talk) 07:14, 3 May 2015 (UTC)

Wiktionary:Votes/pl-2014-04/Unified_Chinese —umbreon126 07:15, 3 May 2015 (UTC)


nididntstartit ou are currently unable to edit pages on Wiktionary.

You can still read pages, but you cannot edit, move, or create them.

Editing from has been disabled by Ungoliant MMDCCLXIV for the following reason(s): Repeat offender: the disabld8rs lunatic.

This block has been set to expire: 01:24, 23 September 2015.

Even if blocked, you will usually still be able to edit your use

"lawsuit" "disgusting scum"← It's generally a good idea to not leave nasty messages like this :/ —umbreon126 10:32, 4 May 2015 (UTC)lunatik=k,ic

下單 and 落單Edit

Just letting you know that you added the Cantonese reading in hanzi but didn't add the pronunciation at either entry. ---> Tooironic (talk) 11:37, 31 May 2015 (UTC)

ta!Edit entrycreator dunworkwel4zh>contctYAIRAND? 08:54, 14 June 2015 (UTC)

I'm not sure it's worth pestering Yair rand about it; Template:zh-new does a good job of things. —suzukaze (tc) 08:57, 14 June 2015 (UTC)

pl.vluk atEdit

mypostsATchuk entz'p

I'm not sure I have the authority to comment on SemperBlotto's edits (although some of them do seem a bit zealous) :/ —suzukaze (tc) 03:37, 15 June 2015 (UTC)

wel1.u=entitled2OWNOPINION;),noSBprivvatbakyard3.ta4rply!:) 06:17, 15 June 2015 (UTC)


pl.bearw/me.. 02:47, 17 June 2015 (UTC)

Don't worry about it. —suzukaze (tc) 17:33, 18 June 2015 (UTC)


Hello, User:Suzukaze-c.

You have recently mail me about the romanisation I use, and saying that Wiktionary uses its own romanisation. I want to say you that Wu is non-official language, and due to this, threatened. Because of such situation, I think it's important to use an unified romanisation, easy and representative of Wu Phonology and particularities, so I've created a romanisation called 吳語拉丁字. All details are explained inside (if you understand french...). You can look also here


Lingstudisto (talk) 18:26, 19 June 2015 (UTC)

"WT Romanization" is the standard created by Shanghainese-speaking Wiktionary editors and the standard that they have decided to use despite at least three other methods already existing. Perhaps you could talk to User:Wyang, he is more knowledgeable about Wu than I am. —suzukaze (tc) 04:30, 20 June 2015 (UTC)



Is RC Recent Changes? I don't think there are language-specific versions. —suzukaze (tc) 15:16, 20 June 2015 (UTC)
I liedsuzukaze (tc) 00:09, 25 June 2015 (UTC)

Use of 𧾷 (U+27FB7) character in articlesEdit

Hi Suzukaze-c, Instead of using "𧾷" (U+27FB7), go ahead and just use the non-unified (U+2ECA) as it already redirects to the unified character article. U+27FB7 is an Extension B character and those are almost always non-standard/variant characters. Cheers! Bumm13 (talk) 22:56, 2 July 2015 (UTC)

Makes sense. Good thing I didn't get around to replacing them all. —suzukaze (tc) 19:05, 3 July 2015 (UTC)

Chinese chemical element articles and Edit

I noticed that you've been changing the Category:zh:Chemical elements template links in Chinese chemical element articles to Template:zh-cat|Chemical elements. Is there any way to add the Mandarin pinyin reading to Template:zh-cat|Chemical elements as were being done previously in the Category:zh:Chemical elements templates? Adding those readings puts the Chinese characters in Category:zh:Chemical elements under Latin letters instead of various Chinese character header categories. I'm not even sure if this behavior is desired or not, so I thought I'd ask for your input. Thanks! Bumm13 (talk) 08:26, 4 July 2015 (UTC)

Special:ExpandTemplates gives an idea of what {{zh-cat}} does (sort by radical like a dictionary, which is probably most appropriate for a "Chinese" (!= Mandarin) dictionary):
  • Title: 字
  • Input text:
    {{zh-cat|Chemical elements}}
  • Result:
    [[Category:zh:Chemical elements|子03字]]
Although I see it doesn't work right with 䥑 yet (which is probably a bad thing):
  • Result:
    [[Category:zh:Chemical elements|䥑䥑]]
    suzukaze (tc) 08:32, 4 July 2015 (UTC)

"Compounds" section - conversion to traditional character words errorEdit

Be careful when converting simplified character compound words to their traditional forms. I found an error you made in converting 钠灯; it should be 鈉燈 instead of "鈉灯". Thanks Bumm13 (talk) 09:30, 4 July 2015 (UTC)

Indeed it is. Japanese is messing with my perception of "Traditional" >_< —suzukaze (tc) 09:31, 4 July 2015 (UTC)


I'm not that familiar with Cantonese, but especially not with Hakka and Min Nan. Do you mind taking a look? I wasn't sure how to split it into three, since I don't know the Cantonese, Hakka, and Min Nan pronunciations. I assumed the Hakka and Min Nan were the same. Also, should the Middle and Old Chinese sections be expandable for all three? Thanks. —  WikiWinters ☯ 韦安智   20:43, 11 July 2015 (UTC)

I wasn't aware that 數 could be used as a noun... ._. Try someone else, I'm sorry... (I'm also not sure about the Middle and Old Chinese) —suzukaze (tc) 00:17, 13 July 2015 (UTC)



Re this revision - you should refrain from adding any sections, including "References" to soft-redirect entries. The vote on the structure of simplified entries was specific about that. References, etc. belong to the main entries, in this case the traditional forms. Pls consider moving them to entries, to which they redirect. --Anatoli T. (обсудить/вклад) 01:25, 12 July 2015 (UTC)

Got it. —suzukaze (tc) 00:15, 13 July 2015 (UTC)
(I feel that it would be beneficial for 異體字 pages like 𢇅 though...) —suzukaze (tc) 00:40, 13 July 2015 (UTC)
Nope, usage notes, references, etc. should be on the main page, not a (soft) redirect page. It doesn't matter if it isn't reformatted to have "Chinese" L2 header yet, "Mandarin" can do for now. --Anatoli T. (обсудить/вклад) 01:01, 14 July 2015 (UTC)
@Atitarev What about , 𫔭, and ? —suzukaze (tc) 05:39, 29 July 2015 (UTC)‎Edit

I suppose it doesn't hurt to try, but this idiot has a history going back five years of generally bad edits and ignoring dozens of attempts to get him to shape up or stop.

He has an obsession with deities and all things supernatural, with occasional side excursions into things like flowering shrubs. He also has abysmally poor judgment about sources: he's admitted to using Bing Translate and anime fansites, though I suspect most is extracted from a certain nether orifice. He's easy to spot: no one else edits Japanese entries from UK Sky/Easynet IPs, and his interests and editing style are dead giveaways as well.

He's not as bad as he used to be: since we started blocking him on sight, his volume has gone way down, and I think he's slowly improving on his own. At one time it was so bad we were burning out good editors just from the constant flood of crap that had to be fixed. Chuck Entz (talk) 06:50, 13 July 2015 (UTC)

D: —suzukaze (tc) 20:54, 13 July 2015 (UTC)

The citation of ふいんきEdit

 Hello. Thank you for your contribution, but I think we had better avoid using copyrighted materials published in Japan even as a quotation because it is often disputed whether we can apply the fair use doctrine to such materials or not (see article 'Fair use' in jawp).

 I know you have no intent to deliberately infringe copyright and just tried to show a lively example of a term. Personally I would like to let it be. Just imagine, however, if authors accuse us of violating their own right and even sue the whole Wikiproject as a nest of illegality. Then, responsibility will be a serious matter. I'm anxious about such kinds of elements unless the author gives permission. What do you think about it? Regards, Eryk Kij (talk) 22:42, 2 August 2015 (UTC)

I thought that it would be okay because it is a transcription of a very short spoken line (not even picture or audio like a Niconico Douga MAD could feature) —suzukaze (tc) 23:12, 2 August 2015 (UTC)
Thank you for your answer. I understand your standpoint. I still consider raising it at Information desk to ask for other's opinions. May I do that? --Eryk Kij (talk) 08:44, 3 August 2015 (UTC)
Go ahead. —suzukaze (tc) 08:48, 3 August 2015 (UTC)
Thank you for your cooperation and I apologize to you for this trouble. --エリック・キィ (talk) 04:03, 11 August 2015 (UTC)



POS at Edit

You have an empty "Adposition" section here. Do you mean this is something that acts like a preposition, but is equally likely to be used as postposition? Or do you mean that you're have no idea whether it's a preposition or a postposition, so you're saying it could be either?

The reason I ask is that we currently don't recognize "adposition" as a valid part of speech. That's not to say we couldn't adopt it, but it would take more justification than its occurence in a single section that's completely devoid of any useable content. Unless you have something specific in mind that you can support with a usage example or a note or something, it would be better to just remove that section and add it back some other time when there's more to work with. Chuck Entz (talk) 01:48, 17 August 2015 (UTC)

The reference I used tranlated to adposition and I don't have the skills to translate the definition. That's all I know. —suzukaze (tc) 04:31, 17 August 2015 (UTC)


do not have permission to edit this page, for the following reason: You are currently unable to edit pages on Wiktionary.

You can still read pages, but you cannot edit, move, or create them.

Editing from has been disabled by SemperBlotto for the following reason(s): Vandalism: repeat offense (multiple)

This block has been set to expire: 13:22, 19 October 2015. wel,OVIESLY,resindDADAMAGroughtbyusualsuspkt.


ta4urprogres!:))+ineded2getridofmyeg[wp'bot'censorship,puke[nher2,sai "While I would dearly love to have my way with her in a wild and uninhibited fashion, Jolin needs to realise SHE IS CHINESE AND THUS NOT FUCKING AFRICAN-AMERICAN. God DAMN that woman is confused. And watching her with Luo Zhixiang in that new video trying to dance like some hip-hop slut is just embarrassing. Stupid cunt that girl is. Bet she fucks like a tiger though."<=diskindofSEXIST/RACISTçmntOKhere???????wmf=~dapits:(((( 09:36, 25 August 2015 (UTC) butwait,woduzdaAVRIDGWPNUTHED[holdfest]Please refrain from making nonconstructive edits to Wikipedia, as you did at Talk:Jolin Tsai with this edit. Your edits appear to constitute vandalism and have been reverted or removed. If you would like to experiment, please use the sandbox. Repeated vandalism can result in the loss of editing privileges. Thank you. ~Oshwah~ (talk) (contribs) 10:55, 24 August 2015 (UTC) [wasment4userTHUMPERWARD,abrviatedvrsn

I'm not sure what you want me to do here :/ —suzukaze (tc) 09:44, 25 August 2015 (UTC)

Overlapping kanji readings and kana?Edit

Although I don't speak Japanese, I spend a good bit of my time working with Special:WantedCategories, so I've created a substantial number of the kanji-readings categories. I've noticed lately that a number of the categories resulting from your use of {{ja-kanjitab}} don't match the readings for the kanji themselves in a very specific way: a kanji with a reading that ends in a particular syllable is missing that syllable in the ja-kanji-tab for an entry with the kanji followed by the hiragana for that syllable. Let me give you an example:

For 片想い, you provided {{ja-kanjitab|かた|おも}}. Looking at the entry for , the kun readings are おもう and おもい.

Now, either there's a missing kun reading for of おも, or the correct reading for the in 片想い is おもい, and there's overlap between the kanji and kana. As I understand it, sometimes the kana are there to show that a particular ending is present, even if it's phonetically merged with the morpheme represented by kanji, or to show that the kanji has one of the readings that end with the sound represented by the kana.

As I said, I don't speak Japanese, so you should check a more reliable source to verify that I'm correct, and even if I am, it will only apply in some cases. It's just that I've run into this pattern more than a couple of times, and because I don't know the language, I'm not going to create categories in cases where things don't add up completely- so it's adding to the backlog of redlinked categories. Chuck Entz (talk) 22:43, 30 August 2015 (UTC)

口走る has くち|はし|yomi=kunCategory:Japanese terms spelled with 走 read as はし , although only lists "hashiru" as a kun reading. It should be okay. —suzukaze (tc) 00:48, 31 August 2015 (UTC)
  • Butting in...
@Chuck Entz: Japanese has something called okurigana (which you allude to), which amounts to the kana added onto the end to indicate inflection. needs reworking, as the actual phonetic part of the kun'yomi that correlates just to the kanji character is only omo. However, omo on its own is not a word meaning thought or thinking (it matches “main” or “face” or “weight, heaviness” instead), so Japanese needs to add the -i on the end to clarify which kun'yomi word indicates.
In idiomatic older writing especially, the okurigana are more commonly subsumed into the kanji and left to the reader to reconstruct (perhaps vaguely similar to how vowels are often omitted in writing for Semitic languages). In modern Japanese, there is more of an educational effort to ensure consistent and unambiguous spellings, and more explicit use of okurigana.
The upshot of all this is that, in most cases, the oddities you're discovering are because many (most?) of our single-kanji entries are old content from before various of our JA entry conventions were established. More basic dictionaries will often give the kun'yomi for a kanji as the entire word, without indicating which parts are okurigana. We're slowly going through and trying to clarify this, such as at 青#Japanese or 雪#Japanese.
HTH! ‑‑ Eiríkr Útlendi │Tala við mig 21:58, 30 September 2015 (UTC)


The entry doesn't make it clear what the exact pinyin is. In the example sentence, a variant is used. In the pronunciation box, "yīgè" is used. This should be clarified.  WikiWinters ☯ 韦安智  22:48, 29 September 2015 (UTC)

I overrode the pinyin in {{zh-usex}} because the pronunciation box and the previous revision of the page said ge4. —suzukaze (tc) 23:07, 29 September 2015 (UTC)


The discussion has been moved to Talk:得了. -- SzMithrandir (talk) 22:32, 25 October 2015 (UTC)

需#Chinese and the Old Chinese glossEdit

Hi Suzukaze,

The link you gave only shows java.lang.NullPointerException for me, in both Chrome and Firefox. From your comment, I assume that this might be the modern Taiwanese definition. That's fine. What I'm concerned about is that at least some of the Old Chinese sources I've looked at give a sense of need and require for this character, which isn't currently given in the table there in the 需#Chinese entry.

I'm a little annoyed that the content provided by {{zh-pron}} is so hard to edit or even access, but that's probably a separate matter. :)

‑‑ Eiríkr Útlendi │Tala við mig 21:45, 30 September 2015 (UTC)

The right link is [1] (the website relies too heavily on JavaScript; I forgot that copy-and-pasting the link straight from the address bar doesn't work). It's not a Taiwanese dictionary but one run by the Taiwanese Ministry of Education that specializes in characters. The definition from the above website quotes sources like the Shuowen Jiezi saying "需,也。"
It looks like the {{zh-pron}} data for Old/Middle Chinese is quoted from elsewhere so it might not even be a good idea to correct it (?) —suzukaze (tc) 00:35, 1 October 2015 (UTC)
  • Thanks for the working link. I note that the definitions listed there also include 有所欲求。如:「需求」、「需要」。清. But as you note, it's a bit of a puzzle where to make any changes. ‑‑ Eiríkr Útlendi │Tala við mig 04:45, 1 October 2015 (UTC)

Some things I want to talk aboutEdit

Dear Suzukaze-c,

as you can maybe guess by the headline of this entry, there is some things that I would want to talk with you about. First off, I love what you did to the "Han etyl" template. It looks and works better than ever. Second off, I really like the new "Han simplified forms" template. I have some questions about it though. Would it be possible and/or useful if it had four sections instead of three, and by that I mean that it would have a kyujitai section in addition to the three other sections. In some cases this could actually be useful. Take for example the character 絲. In traditional, it is written as 糹+糸, while it is 糸+糸 in kyujitai. Is this something that you think you could and should add? And also, do you think that it is possible to make it so that pages which uses the template only gets added to the category "Han characters simplified differently in China and Japan" if the characters actually are simplified differently? I "might" have used your temple on this page: . This character is simplified the same way in Japan and China, but because I used the template, it got placed in the category.

There is one last thing that I wish to discuss with you; character variants. I want you to look at this page: A time ago, I added a list of variants to several pages, including that page. It seems as such that you have moved some of variants from the translingual section to the Chinese section. May I ask you why you have done so? Can I, before you answer, leave you with one final thought? If you look up any of those variants, whether or not they are in the Chinese or translingual section, of you look up any of those (or at least most of them) on the Japanese version of Wiktionary, they will have an entry. And in every one of these entries, it says that it is a variant of c. And it does not say that is a Chinese variant, but there is simply a text in the 漢字 section saying that it is a variant. If you still think that certain variants should be in the Chinese section, you might as well also move 𡆻, 𡇎, 𡇏, 𡇕, 𡈑, 𢦾, 𢧌, 𤦒, 𤦂, and 𡆸 there.

Sorry of this post seemed impolite or rude, I am not very skilled in the art of communicating with others. VulpesVulpes42 (talk) 19:14, 2 October 2015 (UTC)

  • {{Han etyl}} bothered me so much, it looked so awkward ( ´∀`);
  • I would consider 絲 an example of a very minor glyph variation (the 糸 radical always looks different in contemporary PRC/Taiwan fonts versus the more conservative Japan/Korea forms, where one has three dots and the other has 小. in addition, the Unicode charts record 5 or 6 shapes for , which should differ in China, Hong Kong/Taiwan, Japan, Korea, and Vietnam fonts)
  • {{ja-forms}} was used primarily for illustrating the difference between shinjitai and jiantizi, so it seems a bit redundant to add it ({{Han simplified forms}}) to pages where the shinjitai and jiantizi forms are the same. (TBH what I find puzzling is, if it was meant for this purpose, why was it named ja-forms if PRC simplified forms are included, and why does the obsolete but original kyujitai forms come last????)
  • As for the variants, I think that it would be better if they added to only the languages they are a variant in; for example is exclusive to Korea, so calling it a "Translingual" "Alternative form" would be a bit odd (even with context labels). If the Japanese have used 𤦂 (GlyphWiki data suggests that they haven't), then it can go under Japanese Alternative forms.
  • And I think that your communication skills are much better than mine. —suzukaze (tc) 01:26, 3 October 2015 (UTC)



"you've been an admin before?"
Elsewhere, but not here. —suzukaze (tc) 17:22, 20 October 2015 (UTC)

Hello again!Edit

Hello Suzukaze-c, do you remember when I added as a synonym to 黃昏? When you undid my edit I said:

Obscure it may be, but still a synonym. If you really can't stand it being there, then you may re-revert my edit.

I have to be honest with you, in reality it was me who couldn't stand it not being there XD

You see, one of my favorite websites (which I oftenly use) define 曫 as 黃昏, making it a synonym by the first definition of the word.

But that was not what I wanted to talk about. I came here to ask you a question: How in the world do you upload a file to wikimedia commons that has a character from the Supplementary Ideographic Plane in it? Whenever I try to upload a file that has such a character in its name I get the following message:

The title you are about to create contains undesirable characters. Undesirable characters include unusual space characters, BiDi overrides, control characters, byte order marks, soft-hyphens, surrogates, Private Use Area and Specials, including the replacement character U+FFFD and characters outside the Basic Multilingual Plane. In case you do not know which character triggered this message, have a look at Commons:User scripts/Invisible charaters.

But the thing is, there are files which have characters outside the Basic Multilingual Plane in their names, take for example the seven last files on this page. Can you help me? Thanks in advance. Sorry for messy message, I would have made it better-looking if I had the patience. VulpesVulpes42 (talk) 13:39, 23 October 2015 (UTC)

Suggestion one: Ignore the notice
Suggestion two: Don't put the problematic character in the file name. —suzukaze (tc) 19:38, 23 October 2015 (UTC)

Hello again (again)!Edit

Thank you for replying to me. But the methods you mentioned won't work. You can't ignore the notice, and I must have those problematic characters in the file name. You know how the SVG files depicting seal script characters always have the same name? X-seal.svg with X being the character this file is showing in seal script form. That X could be a character from CJK Unified ideographs extended A, or from CJK Unified ideographs, in which case there wouldn't be a problem as those blocks are in the Basic Multilingual Plane, or that X could be a character from CJK Unified ideographs extended B, CJK Unified ideographs extended C, CJK Unified ideographs extended D, or CJK Unified ideographs extended E, in which case I'd be unable to upload the file as those blocks are in the Supplemental Ideographic Plane. I even tried to upload a new version of a file that had a problemtic character in its name, and I couldn't do that! When I tried to do that, I got this message:

The title you are about to create contains undesirable characters. Undesirable characters include unusual space characters, BiDi overrides, control characters, byte order marks, soft-hyphens, surrogates, Private Use Area and Specials, including the replacement character U+FFFD and characters outside the Basic Multilingual Plane.

In case you do not know which character triggered this message, have a look at Commons:User scripts/Invisible charaters.

Even though this isn't about a file that I want to upload, this is about an already existing file that I want to update. VulpesVulpes42 (talk) 07:06, 24 October 2015 (UTC)

I'm not familiar with the inner workings of Commons. Maybe you could contact the users who have successfully uploaded files with non-BMP characters in the file names and ask them for help. —suzukaze (tc) 07:08, 24 October 2015 (UTC)


Hi Suzukaze. Can you tell me why リア充爆発しろ failed RFD? — I.S.M.E.T.A. 22:43, 30 October 2015 (UTC)

Other editors considered it SoP (which TBH I find puzzling; the phrase tells people to explode [as in "kaboom"]). —suzukaze (tc) 23:40, 30 October 2015 (UTC)
I see. So it is deemed to be the sum of its parts; but what are its parts? — I.S.M.E.T.A. 23:55, 30 October 2015 (UTC)
リア充 (someone with a fulfilling life in the real world) + 爆発する (to explode) + しろ (imperative form of する) —suzukaze (tc) 01:43, 31 October 2015 (UTC)
Thanks. I've moved/copied your citations of the phrase to Citations:リア充 and Citations:爆発. There was no point deleting a couple of perfectly good citations. — I.S.M.E.T.A. 15:28, 31 October 2015 (UTC)
The full phrase リア充爆発しろ also appears to be the name of a popular phone app (see some of the top hits at google:"リア充爆発しろ"), which might account for its recent increase in use online. That said, 爆発しろ is also used in other contexts. C.f. google:"爆発しろ" -"リア充爆発しろ". ‑‑ Eiríkr Útlendi │Tala við mig 07:47, 2 November 2015 (UTC)
Google Trends graph for 爆発しろ, リア充爆発しろ, "爆発しろ" -"リア充爆発しろ", and リア充爆発しろ アプリ. The lines(?) for 爆発しろ and リア充爆発しろ closely match each other. It seems that the spike in April 2015 was because this app got deleted. 爆発しろ アプリ is also the weakest graph line(←?) —suzukaze (tc) 08:21, 2 November 2015 (UTC)
@Eirikr, suzukaze-c: Just FYI, I only really asked about this because the original citations page had been tagged for speedy deletion. — I.S.M.E.T.A. 14:13, 2 November 2015 (UTC)
  • @I.S.M.E.T.A.: Aha, I hadn't seen that. Good of you to step in -- as you note above, it would be a shame to have those citations vanish into the ether, as they are equally applicable to the constituent terms.
@ suzukaze-c: Very interesting. I have no experience with Google Trends; I'll have to give that a try. Thank you. ‑‑ Eiríkr Útlendi │Tala við mig 19:21, 3 November 2015 (UTC)

Hakka DictionaryEdit

I saw that you've used 客英大辭典 as a source for PFS, such as in 懶人多屎尿. I just wanted to tell you that this dictionary does not use the variety of Hakka that we currently support with {{zh-pron}}, that is, Siyen Hakka. The romanization used in 客英大辭典 is slightly different from the PFS used for Siyen. BTW, this might be a reason why there is a POJ option for Hakka. — Justinrleung (t...)c=› 02:17, 18 November 2015 (UTC)

I see. Thanks for fixing it >.< —suzukaze (tc) 08:03, 18 November 2015 (UTC)

Atitarev's removal of Chinese section from Edit

Atitarev removed the "Chinese" section from the page on 11 July, but the character is in the Shuowen Jiezi, so I consider this removal as questionable. Eyesnore (talk) 04:08, 27 November 2015 (UTC)

A common courtesy...Edit

I would really appreciate it if you would wait a few minutes before starting to edit CJKV articles that I've made very recent edits to. I'm often in the process of unifying the separate Chinese sections when you decide to make the very same edit to a particular article. This causes an otherwise undetectable edit conflict to occur and makes editing very difficult for me. Thanks for your consideration. Bumm13 (talk) 06:35, 31 December 2015 (UTC)

My apologies, I wasn't aware. (Have you considered using Special:ExpandTemplates to generate the code? It's really efficient, and often the pronunciations are already there, although additional Mandarin pronunciations need to be added manually.) —suzukaze (tc) 06:37, 31 December 2015 (UTC)

Korean word article edit reversionsEdit

Umm, would you care to explain why you just reverted my recent edits to those select Korean word articles? Your edit summaries gave no indication why you made the reverts in question. Bumm13 (talk) 14:38, 31 December 2015 (UTC)

I explained it in the first two reversions; the edits were incorrect. The PUA mapping that you used is MingLiU_HKSCS, which uses PUA to map HKSCS Cantonese characters to PUA instead of CJK Ext B. The PUA mapping that should be referred to is the one noted on wikipedia:List of hangul jamo, this "Hanyang Private Use" thing. After a quick Google search I found the proper fonts, which show characters that match the Yale romanization. —suzukaze (tc) 14:42, 31 December 2015 (UTC)
Supposedly there is a way to display Old Hangul using standard Unicode, but it doesn't seem to be a question a quick Google search solves. —suzukaze (tc) 14:46, 31 December 2015 (UTC)
Better examplesuzukaze (tc) 14:51, 31 December 2015 (UTC)
Okay, I obviously was totally confused about the situation with those word spellings. Bumm13 (talk) 06:02, 1 January 2016 (UTC)

Vietnamese Nouns in Han ScriptEdit

I wish either {{vi-hantu}} or {{vi-noun}} could link to a category like Category:Korean nouns in Han script, which is Category:Vietnamese nouns in Han script. --Lo Ximiendo (talk) 04:40, 10 January 2016 (UTC)

Seems like a good idea. I imagine that it wouldn't be too difficult for {{vi-hantu}}. However, the way {{vi-noun}} seems really weird to me, and {{vi-hantu}} is locked. —suzukaze (tc) 04:45, 10 January 2016 (UTC)
Then you could examine {{ko-noun}} for ideas. --Lo Ximiendo (talk) 04:53, 10 January 2016 (UTC)
I know how to do it, but {{vi-hantu}} is locked from editing. I'll try editing {{vi-noun}} to see what I can do. —suzukaze (tc) 04:58, 10 January 2016 (UTC)
@Lo Ximiendo

Module:ja-kanjitab table layoutEdit

Heya Suzukaze --

I recently noticed that {{ja-kanjitab}} was no longer floating to the left of the floating <div> containing WP links and images, as at 神道, and was instead pushed down below these elements. I just tried undoing one change you made to the table layout, and {{ja-kanjitab}} is back to floating to the left of the <div>.

I think it might be the floatright you added previously, but I'm out of time today for editing on Wiktionary. If you have the bandwidth, could you have a look and change Module:ja-kanjitab as appropriate?

TIA, ‑‑ Eiríkr Útlendi │Tala við mig 18:10, 18 January 2016 (UTC)

I think it was my replacement of align="right" with class="floatright". Is it okay if I change the code back, save for the class="floatright" part that I'll change back to align="right"? The old appearance is slightly lacking in design sense IMO. —suzukaze (tc) 20:15, 18 January 2016 (UTC)
  • Please give it a whirl! I liked the font / color / line changes, it was just the layout change that worried me: too many items lined up vertically on the right margin can cause the entry's extras to push down into the following language's area, which just looks messy. ‑‑ Eiríkr Útlendi │Tala við mig 22:39, 18 January 2016 (UTC)
It should be good now (ゝω・)b —suzukaze (tc) 22:45, 18 January 2016 (UTC)


The strong conjugations are pretty odd too. Hillcrest98 (talk) 01:53, 19 January 2016 (UTC)

Thanks for your editing!Edit

That's exactly what I intended to do but failed. I simply use Ctrl+H and it didn't work out. 06:39, 24 January 2016 (UTC)

(ゝω・)b —suzukaze (tc) 06:53, 24 January 2016 (UTC)

ow2mov pp?Edit 21:11, 28 January 2016 (UTC)

"how to move pages?"
If you mouse over the "More ▼" thing at the top of the pages a "Move" option will appear. —suzukaze (tc) 22:53, 28 January 2016 (UTC)

ys-hm,no c>no4IPs?ta4elp:) 11:27, 30 January 2016 (UTC)


ur | prev) 21:36, 3 February 2016‎ Leasnam (talk | contribs)‎ . . (413 bytes) (-31)‎ . . (→‎Noun: a plant can also act as host) (undo) (cur | prev) 21:36, 3 February 2016‎ (talk)‎ . . (444 bytes) (+58)‎ . . (undo) (cur | prev) 21:35, 3 February 2016‎ Leasnam (talk | contribs)‎ . . (386 bytes) (-3)‎ . . (→‎Noun) (undo)

fe<he nozALDAFLUKES??wa awhizthen
i1.thought~deletindad(=that)pasag,buthenLEScanbLES2.. 21:48, 3 February 2016 (UTC)
Hmm, I don't know anything about this word so I don't have any meaningful comments :/ —suzukaze (tc) 23:06, 3 February 2016 (UTC)

wel,aHOSTfedz,mekanical atahmnt=difrnt(budunwuri,,difrntcyclz>ard2generaliz3.igotridof myeg,ta! 10:04, 7 February 2016 (UTC)

Possible bug in Template:zh-pronEdit

Hi suzukaze-c,

I just edited the article to added "mc=y" and "oc=y" parameters to Template:zh-pron in that article. It returned this error: "Lua error in Module:ltc-pron at line 485: attempt to concatenate field '?' (a nil value)". I'm letting you know since you were the last person who edited the template. Nothing about my edit was unusual in any way. Cheers! Bumm13 (talk) 23:50, 5 February 2016 (UTC)

The error appears with the December 2014 version of the module too, so it doesn't seem to be caused by my edits.—suzukaze (tc) 00:55, 6 February 2016 (UTC)

frame/()<wotmeanin pl?Edit

User group rights

The following is a list of user groups defined on this wiki, with their associated access rights.


   Granted right
   Revoked right

Group Rights (all)

   Create discussion pages (createtalk)<FE81.11.219.30 10:01, 7 February 2016 (UTC)
I'm not sure what you mean by "frame" :( —suzukaze (tc) 10:02, 7 February 2016 (UTC)

daCONTINUUSLINE4ROUNDITãpic'sframe81.11.218.210 12:47, 10 February 2016 (UTC)

So, I'm assuming that you want an explanation of the above text [that I'm guessing was inside a frame]? (It's not immediately clear how "frame" was relevant, since no frame was copy-and-pasted)
I see a legend (Granted right/Revoked right), and I see an attribute (Create discussion pages) that presumably would have one of the legend's symbols attached to it, but I don't see any symbols. Too much formatting was lost, so it is impossible to explain. —suzukaze (tc) 13:11, 10 February 2016 (UTC)

praps gotlost i/myBLAKBAKGROUND(scren,ta4tryintho!:) 22:32, 10 February 2016 (UTC)


What did not work and on which page? --kc_kennylau (talk) 10:05, 7 February 2016 (UTC)

[2]suzukaze (tc) 10:08, 7 February 2016 (UTC)
Wow. Wonderful tool, never known before. So what went wrong is that the "||" makes an empty string parsed as the first parameter. --kc_kennylau (talk) 10:11, 7 February 2016 (UTC)
Yep; PAGENAME isn't being passed on for some reason. (Although, IMO {{Sinoxenic-word/code}} seems a bit unnecessary since all {{Sinoxenic-word}} does is pass on all of its parameters...) —suzukaze (tc) 10:13, 7 February 2016 (UTC)

canu'v aluk?Edit 12:45, 10 February 2016 (UTC)

SemperBlotto's been contributing for ages, unlike me; I don't think I have enough experience to say whether trequartista it should have an English section or not. However, I do think that the border between code-switching and borrowing can be rather thin (although, I'm not a linguist; don't listen to me). —suzukaze (tc) 13:15, 10 February 2016 (UTC)

agre(thin,ta:)(1'dsayEN_PLURAL=inkompetns,ordad it=TREATINit~ENGL,yep[niFOUNDAWORD(smeanin,mymainconcern;) 22:23, 10 February 2016 (UTC)


Could you check this edit? I thought 竜 is the standard Japanese character. I don't know enough Japanese to know if this is right. — justin(r)leung (t...) | c=› } 01:51, 22 February 2016 (UTC)

From my observations, it seems like some reason people like to use 龍 (and 櫻) for stylistic reasons. Like in w:ja:青龍_(将棋).—suzukaze (tc) 02:07, 22 February 2016 (UTC)
I see. Should we use 烏龍茶 or 烏竜茶 in the descendants section in the Chinese section? — justin(r)leung (t...) | c=› } 02:51, 22 February 2016 (UTC)
IMO it should be 烏龍茶, because 1. it's the name the Japanese Wikipedia uses: w:ja:烏龍茶, and 2. 烏竜茶 seems to be much less common than 烏龍茶. —suzukaze (tc) 03:25, 22 February 2016 (UTC)


Can you check the Cantonese readings here? The verb and noun in Mandarin are different, but have no idea about Canto. Thanks. ---> Tooironic (talk) 07:26, 26 February 2016 (UTC)

It looks good to me. —suzukaze (tc) 08:03, 26 February 2016 (UTC)

(zhāi) and , (tīng) and , (lóng) and Edit

I have added the {{Han simplified forms}} template to these pages. By the way, the "Cantonese" and "Mandarin" sections for these pages (apart from ) are yet to be unified. Eyesnore (talk) 23:12, 27 February 2016 (UTC)

Wiktionary:Requests for deletionEdit

Why did you blank the page? --Robbie SWE (talk) 10:34, 2 March 2016 (UTC)

I think Opera Mini was fucking up; I was trying to fix a typo in the top header >< —suzukaze (tc) 10:36, 2 March 2016 (UTC)
Ah, ok. What a relief :-) --Robbie SWE (talk) 10:39, 2 March 2016 (UTC)

歌 vs 唄Edit --kc_kennylau (talk) 14:52, 7 March 2016 (UTC)

Just thinking out loud :) I didn't even try to look up the actual difference yet :p —suzukaze (tc) 17:49, 7 March 2016 (UTC)

Extended shinjitai and Asahi charactersEdit

Extended shinjitai characters are no longer categorized in Category:CJKV characters simplified differently in Japan and China. They are not official forms. Eyesnore (talk) 23:52, 19 March 2016 (UTC)


Hello, it's written boy here: À la 雞 (talk) 01:13, 21 March 2016 (UTC)

The site is displaying errors for me. —suzukaze (tc) 02:48, 21 March 2016 (UTC)
It was also showing errors for me yesterday, but it's working now. It does say boy. — justin(r)leung (t...) | c=› } 02:08, 22 March 2016 (UTC)
I'm just following the file talk page and file description. —suzukaze (tc) 04:39, 22 March 2016 (UTC)


Do you think the Bopomofo pages should use the Chinese section instead of Mandarin? Mandarin is not the only Chinese language that uses Bopomofo. Most notably are the Taiwanese Phonetic Symbols used for Hokkien and Hakka. Also, each symbol has a name, so /p/ for ㄅ might not be correct. ㄅ is pronounced as bē or bō. — justin(r)leung (t...) | c=› } 06:19, 27 March 2016 (UTC)

I think that there should be separate Mandarin and Min Nan sections, similar to how POJ entries have Min Nan headers and Pinyin entries have Mandarin headers. According to Wikipedia, ㄏ and ㄜ differ in phonetic value, and there are extra letters that would mess up the "1st letter of" scheme. Unless we use {{label}} and dump the numbering, in which case I'd be fine with a "Chinese" header. —suzukaze (tc) 06:22, 27 March 2016 (UTC)
About pronunciation, z#English has separate Letter name and Phoneme sections; should something like that be done? Also do the the vowels have names? —suzukaze (tc) 06:25, 27 March 2016 (UTC)
The vowels are pronounced as they are. About the numbering, I don't know if the Min Nan has a specific order. — justin(r)leung (t...) | c=› } 06:28, 27 March 2016 (UTC)
(Also, some letters are Mandarin-only, and some are Min Nan-only; it seems wrong to use {{lb|zh|Mandarin}} for .) —suzukaze (tc) 06:34, 27 March 2016 (UTC)
OK, we should have separate sections then. About the pronunciation sections, I think we should have letter name and phoneme sections. — justin(r)leung (t...) | c=› } 06:46, 27 March 2016 (UTC)


I have long put variant forms on separate lines to distinguish them from main forms. For the sake of consistency, would you mind if I undid your edit? ---> Tooironic (talk) 09:22, 27 March 2016 (UTC)

Hmm, but it's all the same word though; putting them on separate lines makes it seem like there's 曬太陽, whose simplified form is 晒太阳, and another new term 晒太陽... I don't really care though. —suzukaze (tc) 09:24, 27 March 2016 (UTC)
Also, about 葡萄 - I do not support collapsible tables for derived terms on Chinese pages, and have undone many of them in the past, since they do not allow for alphabetical sorting. Can I also undo your edit here? ---> Tooironic (talk) 09:29, 27 March 2016 (UTC)
The list is super long though; is diff okay? It's still in alphabetical pinyin order. —suzukaze (tc) 09:30, 27 March 2016 (UTC)
Genius! I will edit this way in the future for long lists. Many thanks. ---> Tooironic (talk) 09:33, 27 March 2016 (UTC)

Triad of / Edit

{{Han simplified forms}} template not present yet on these pages. Possibly an extended shinjitai? Eyesnore (talk) 18:13, 29 March 2016 (UTC)


Why did revert my edit Johnny Shiz (talk) 23:13, 16 April 2016 (UTC) Johnny Shiz (talk) 23:13, 16 April 2016 (UTC)

My sources do not indicate such thing. —suzukaze (tc) 23:19, 16 April 2016 (UTC)


Hi. I see you reverted . Please check too. It said 托 is simp of 託. Should be add as another etymology? --Octahedron80 (talk) 07:49, 25 April 2016 (UTC)

I think so. —suzukaze (tc) 07:50, 25 April 2016 (UTC)

ZH 石綿Edit

I'm curious about your recent revert. The ZH WP article itself lists 石綿 as an alternate rather than misspelling (「石棉,又稱石綿,...」), and MDBG has an entry for this spelling. Perhaps this is a regional or dialectal spelling? ‑‑ Eiríkr Útlendi │Tala við mig 19:00, 25 April 2016 (UTC)

I assumed Wyang knew what he was doing. Perhaps I should've checked first :/ —suzukaze (tc) 21:51, 25 April 2016 (UTC)
  • No worries. :)   I assumed I was missing out on a regionalism, and it looks like that might have been the case -- I see that the 石綿 spelling now has {{lb|zh|chiefly Taiwan}}. ‑‑ Eiríkr Útlendi │Tala við mig 23:08, 25 April 2016 (UTC)

Character compoundsEdit

Hi! Thanks for your work on characters! Just a heads-up: Chinese Wiktionary has compound lists for individual characters, e.g. zh:附录:漢語詞彙索引/女. You can remove "更多..." and "逆序" and replace all new lines with a "|" to generate lists for en.wikt. May be useful. Wyang (talk) 11:48, 26 April 2016 (UTC)

Pseudo-Japanese BSEdit

I see you've been busy with our resident Sky/Easynet-UK IP mental case. After 5 years of adding this kind of crap and consistently getting reverted, you'd think they would get something halfway resembling a clue, but they're completely impervious. I remember them asking Eirikr once how their bogus entry could be wrong if Bing Translate said it was right...

I block them for a couple of weeks every time I see them. They change their IP frequently, so it doesn't last, but it slows them down so we can keep up. They used to practically live here and churn out huge volumes of bad edits, but they only stop by occasionally these days, so I must be doing something right.

Thanks for all your tireless work on patrolling the recent edits and cleaning up the CJKV entries- you're definitely worth your weight in gold, as far as I'm concerned. Chuck Entz (talk) 03:04, 12 May 2016 (UTC)

display of measure wordsEdit

Is there a way we can get simplified forms and pinyin to display for this new measure word component you guys are using? (e.g. at 明月) ---> Tooironic (talk) 13:13, 15 May 2016 (UTC)

Yes, but User:Wyang probably has reasons for writing code that explicity doesn't display it... (likely partly because the template describes varying measure word usage across lects, so pinyin would be inappropriate) —suzukaze (tc) 18:25, 15 May 2016 (UTC)


is running out of memory, and it looks like it may have something to do with your edit to this module (you would know better than I would). Thanks! Chuck Entz (talk) 04:07, 18 May 2016 (UTC)


Hello! Please check the 留級 article in Wiktionnaire. Fête Phung (talk) 12:40, 23 May 2016 (UTC)

I'm sad, someone had deleted the 留級 article in Wiktionnaire! Fête Phung (talk) 13:04, 23 May 2016 (UTC)

對唔住,我唔識法文。 —suzukaze (tc) 21:51, 23 May 2016 (UTC)
@Fête Phung: I've helped you asked the deleter. --kc_kennylau (talk) 02:10, 12 June 2016 (UTC)
He got into an edit war with Wyang and Wyang blocked him as a sock of a globally-blocked user- which he indeed is. If his current IP (see below) keeps making revertable edits, it may very well meet a similar fate.
As for the deleted entry at Wiktionnaire: they aren't as tolerant as we are of banned users coming back to continue making edits, so that was the reason given in the deletion comments of the first 2 deletions. His English-language edits displayed an appalling lack of understanding about what it means to repeat a grade, so I wouldn't be surprised if there were content-related reasons this was deleted, as well, though you would know better than I would. Chuck Entz (talk) 02:50, 12 June 2016 (UTC)

new sense at 溫馨Edit

A "happy" memory? Is that what you were getting at with those example sentences? ---> Tooironic (talk) 01:46, 4 June 2016 (UTC)

If I knew/was sure I wouldn't use {{rfdef}}... There are multiple "of a..." and none of them seem to match the citations. —suzukaze (tc) 02:25, 4 June 2016 (UTC)

Something you might want to seeEdit

I've gone through all the talk pages in Category:Chinese terms needing attention, and added sort keys (starting with the last character in the category) to the ones where the tag was added by a certain inquisitive person whose IP geolocates to Kent (earlier Lorain), Ohio. The results are here. I don't know how long it will last, because it shouldn't be that hard to figure out what I did, but I thought I might as well do something while I was checking the pages. Chuck Entz (talk) 05:28, 4 June 2016 (UTC)

Hm :o Are you doing it manually? Seems like a lot of work D: —suzukaze (tc) 21:30, 4 June 2016 (UTC)


唔該你睇吓明知故犯206.180.250.57 00:54, 12 June 2016 (UTC)


I don't recommend we add glosses for see also terms. It's going to mean a heck of lot of work for us to remain consistent across all entries. Please reconsider. ---> Tooironic (talk) 19:06, 15 June 2016 (UTC)

It is true that remaining consistent is important. However, from a usability standpoint, glosses are helpful. For example, compare こうしょう#Japanese and 女#Compounds_2 to tú#Mandarin. —suzukaze (tc) 19:44, 15 June 2016 (UTC)
As you know, the amount of work required to maintain a high level of accuracy, usability and consistency across all Chinese entries on Wiktionary is huge. I'm only thinking about how we can avoid overwork, wherever possible. In the future, we may be able to find a way to have glosses appear automatically, without the need to input them manually. ---> Tooironic (talk) 05:27, 16 June 2016 (UTC)
Alas Wiktionary is not a database... —suzukaze (tc) 05:49, 16 June 2016 (UTC)
こうしょう#Japanese is a disambiguation page but it's an overkill still, if you ask me. Homophones for multisyllabic words in Japanese is even a bigger problem than in Chinese. The entry's definitions are too short, not always accurate and get out of date, as soon as lemmas are changed. No need to do glosses on each synonym, related term, etc., IMO. --Anatoli T. (обсудить/вклад) 06:39, 16 June 2016 (UTC)
  • How could a user possibly disambiguate the items in the list without glosses? I agree that data consistency can be an issue -- but in most cases, the glosses are short renderings of a term's central meaning(s), and as such, they are unlikely to vary that much from the information in the targeted entry. For my part, I view the こうしょう#Japanese as close to ideal for this kind of disambig page, given the constraints of the MediaWiki software. ‑‑ Eiríkr Útlendi │Tala við mig 16:05, 17 June 2016 (UTC)
    • Presumably, by clicking on them. ---> Tooironic (talk) 16:47, 17 June 2016 (UTC)
      • Every single one? —suzukaze (tc) 23:35, 17 June 2016 (UTC)

Module error at Edit

When you converted everything in the "Compounds" section to use {{ja-r}}, the module choked on one of them:

  • {{ja-r|実は|じつわ}}

I have it commented out for now, but you'll probably want t go back and fix it. Thanks! Chuck Entz (talk) 07:36, 17 June 2016 (UTC)

Thanks for pointing it out; fixed. —suzukaze (tc) 07:37, 17 June 2016 (UTC)

On my reverted editEdit

 Hello, Suzukaze-c. I am writing in reference to my edit to the page which you reverted about a month ago. After doing extensive research, I found that 「花占い」(はなうらない, hanauranai) does mean "flower fortune-telling" or "flower divination." That has led me to the logical conclusion that the example sentence given,「こんな時は花占いだ!」would in fact mean that events such as these were the fortune derived from flower divination. I see now that the example sentence has been removed (I'm assuming by another user), but I was simply wondering why you found my translation insufficient. (No malice whatsoever; merely looking for clarification here.) Here's the history comparison page for reference.

 Thank you very much,
 BlueCaper (talk) 21:28, 17 June 2016 (UTC)時&diff=next&oldid=38585994suzukaze (tc) 21:30, 17 June 2016 (UTC)

Music Memory?Edit

Discussion moved to User talk:Lo Ximiendo.

Sort args in etymologiesEdit

I just noticed your removal of sort args from calls to {{etyl}}. This causes the entry to be indexed under the kanji spelling in the category page at Category:Japanese_terms_derived_from_Chinese. The WT:AJA page also notes that category sorting should be by hiragana, as described at Wiktionary:About_Japanese#Sorting.

I thought I'd ask before reverting, since I'm unclear on why you removed the sort args. Was there something specific you had in mind? ‑‑ Eiríkr Útlendi │Tala við mig 23:27, 20 June 2016 (UTC)

Ahh, previously it said "Lua error in Module:parameters at line 110: The parameter "sort" is not used by this template." because the template was {{m}}, so I fixed the template and removed sort. I'll fix it. —suzukaze (tc) 23:29, 20 June 2016 (UTC)

Kanji entries that lack Chinese entriesEdit

Is there any way to make a list of the kanji entries on Wiktionary that are lacking Chinese entries? This would be useful to have. ---> Tooironic (talk) 16:02, 30 June 2016 (UTC)

A handful of CJK A characters are missing, as well as a large part of Appendix:Unicode#Supplementary_Ideographic_Plane. Most of them are fairly obscure or obsolete. —suzukaze (tc) 20:57, 30 June 2016 (UTC)
Or do you mean Japanese kanji entries without Chinese? There's this. —suzukaze (tc) 23:41, 30 June 2016 (UTC)
The latter, yes, thanks! ---> Tooironic (talk) 04:12, 1 July 2016 (UTC)

hiragana to kanji pagesEdit

Hi. If I were to create hiragana entries to point to the kanji form, do I need to replicate every POS the kanji entry has? For example, "流暢" is a "Noun" and an "Adjectival noun". Does this mean I have to also do two parts of speech in りゅうちょう?

By the way, a similar entry きゅうでん, when it comes to linking to 休電, looks like this:

  きゅうでん ‎(romaji kyūden)
  1. 宮殿: palace
  2. 給電: electricity supplying
  3. 休電: electricity cut-off
  4. 球電: ball lightning

  きゅうでんする ‎(romaji kyūden suru)
  1. 休電: for electricity to be temporarily cut off

Should the entry at the bottom be "休電する" or something?

Thanks. -- Dine2016 (talk) 08:41, 1 July 2016 (UTC)

Regarding ryuuchou: yes.
Regarding kyuuden: no, as the verb is found on 休電 and not 休電する. —suzukaze (tc) 08:46, 1 July 2016 (UTC)


Do you have an example of the Cantonese sense you added? I can't think of it being used as that sense. — justin(r)leung (t...) | c=› } 13:39, 2 July 2016 (UTC)

I was thinking of [3] ("繼續"; "to keep on; (in the same old way, as ever) to persist (adv? persistently; accordingly; in accordance with)"). —suzukaze (tc) 23:43, 2 July 2016 (UTC)


cat=n,m=,'uncreated,(bloCHIN=wot? 11:50, 4 July 2016 (UTC)

If i understand correctly, you are asking about the purpose of cat= and m=? An explanation can be found at T:zh-pron.—suzukaze (tc) 01:10, 5 July 2016 (UTC)


Would you mind checking the Japanese entry here? Is 叛逆 really an alternative form? It can't be in Chinese. ---> Tooironic (talk) 12:50, 16 July 2016 (UTC)

It's probably a situation like 作飯 and 做飯 that have close meanings and sound identical in Mandarin (but non in Cantonese: zokfaan vs. zoufaan). —suzukaze (tc) 15:55, 16 July 2016 (UTC)

Thank you for your thanks!Edit

I must confess that I got a little giddy over the notification. I think it's the first time that I got thanked here. Just before I read the notification, I coincidentally had been admiring your user name after seeing it in the history of a page. Thanks again for a happy moment! Geekdiva (talk) 08:36, 21 July 2016 (UTC)

Japanese renyoukeiEdit

Hi. I wonder whether 出来 needs a Japanese part, saying that it's the stem of 出来る? Thanks. Dine2016 (talk) 12:14, 21 July 2016 (UTC)

Forms of Japanese verbs are rather neglected here unlike other languages. IMO yes, but as the format is essentially undecided, maybe not yet. (@Eirikr, any insight?)—suzukaze (tc) 14:45, 21 July 2016 (UTC)
It probably needs a Japanese section with the readings of でき, しゅつらい and しゅったい. Links to 出来る and 出来す can be put into {{also}} +/- etymology. Wyang (talk) 22:58, 21 July 2016 (UTC)
  • Ditto Wyang's and Suzukaze's comments. Japanese in general doesn't have the best coverage here; we're working to fix that, but it takes time. Verb forms are less of a priority than simply getting the core lemmata in place, but we are gradually (very gradually) filling in. 出来 is one such page that is in need of a Japanese entry. As Suzukaze notes, some of our formatting and infrastructure is still TBD when it comes to verb forms, and Old and Classical Japanese for that matter -- 出来 is also a valid spelling for the Classical (maybe even OJP?) verb deku, ancestor to modern dekiru.
Anyway, TL:DR version: we're slowly getting around to entries like this. :)   ‑‑ Eiríkr Útlendi │Tala við mig 07:59, 7 September 2016 (UTC)
PS: @Suzukaze, sorry for the lag -- I never saw the ping.

JA misspellingsEdit

Thanks for the heads-up at ウィクショナリ. Could we get a proper header template for that? Using the generic {{head}} just looks so wrong... ‑‑ Eiríkr Útlendi │Tala við mig 00:37, 29 July 2016 (UTC)

I suppose it could be added to Module:ja-headword somehow... —suzukaze (tc) 20:26, 30 July 2016 (UTC)


英語ではseabassは、siːbæsと発音します。日本語の発音だと/ʃiːbæs/となります。日本でシーバスを意味する言葉は、スズキ、セイゴ、ヨーロッパスズキです。主に釣り用語や市場などで使われます。wiktionary は、辞書なので、意味を書かないと意味がないです。-- 08:44, 1 August 2016 (UTC)

ɕiːba̠sɯᵝ この発音記号は微妙です。言えなくもないですが、少し変です。日本語の発音だと/ʃiːbæs/となります。あとシーバスのEnglishの項目を消そうとするのは、なんで?-- 08:53, 1 August 2016 (UTC)

/ɕiːba̠sɯᵝ/は国際音声記号での日本語の発音の表現です。奇妙に見えますが正しいはずです。シーバス英語話者が使用しない英語から日本語への借用語。(=seabassは英語の言葉でシーバスは日本語の言葉)—suzukaze (tc) 09:03, 1 August 2016 (UTC)

u=v.fas2+ta4elp!:)Edit 02:48, 8 August 2016 (UTC)

:) —suzukaze (tc) 04:32, 8 August 2016 (UTC)


Editing 面摊 (section)

information 	Warning: Your contribution does not contain a valid language and part-of-speech header. Please see Wiktionary:Entry layout explained for details regarding formatting entries. Guidelines regarding formatting entries of specific languages may be found in Category:Wiktionary language considerations. Click the "Show preview" button to see if there are any anomalies.

Unconstructive edits will be quickly reverted, and egregious or repeated unconstructive editing will result in your account or IP address being blocked. If you believe this action to be constructive, you may submit it again to confirm it. If this message is erroneous, please report it at WT:Grease pit.

    This action has been automatically identified as harmful, and therefore disallowed.

If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: strips L3

You are not logged in. If you save your edits to this page, your IP address will be recorded in the page's history. For that and other reasons, you should create an account.

Please do not save test edits. If you want to experiment, please use the sandbox. Inserting nonsense, knowingly adding false information and gratuitously removing content are considered vandalism, and editors who engage in such behavior may be blocked without a warning.
Embedded file
Special characters
Bulleted list
Numbered list
No wiki formatting
New line
Picture gallery
Search and replace

Edit summary:

By clicking the “Save Page” button, you are agreeing to the Terms of Use and the Privacy Policy, and you irrevocably agree to release your contribution under the CC-BY-SA 3.0 License and the GFDL. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel 15:43, 11 August 2016 (UTC)

The edit filter doesn't see Chinese simplified entries as a valid entry since it does't have an L3 (===Noun===, ===Verb===, etc) so it won't let you save. It's been brought up a few times but the problem hasn't been resolved yet since the filter doesn't apply to autopatrolled users. IMO the easiest way to deal with this is to let other established users create the simplified form. —suzukaze (tc) 20:03, 11 August 2016 (UTC)


Thanks for fixing a lot of my old entries. Sorry they're such a mess! ---> Tooironic (talk) 04:57, 14 August 2016 (UTC)

They were probably up-to-standard at the time so it's not your fault :) —suzukaze (tc) 04:59, 14 August 2016 (UTC)


ta4elp/gudtransl!:) 04:30, 18 August 2016 (UTC)


jingqiu<thoutickekd(butiprimarilyneDIC4dad,circlclozd,uh-ta4urefets!(pr=rillibitmuchtypin4me..(bitiredritenowfysicaly,inTWidWAYmortime4editin(nchines),itryd2tem..(urcoligz81.11.218.228 18:38, 21 August 2016 (UTC)


I doubt something. At ja.wiktionary, don't users like to make hiragana entries? I found many redirect like this [4] --Octahedron80 (talk) 05:22, 27 August 2016 (UTC)

I don't know about their policies regarding hiragana. It doesn't seem to be included in their editing guidelines. Please ask at ja:Wiktionary:Sabo (;'∀')suzukaze (tc) 05:26, 27 August 2016 (UTC)


Incomplete sentence?Edit

This is not a complete sentence: It is one of four myeloproliferative disorders, characterised by increased production of a particular line of blood cellS butAPARTFR the lymphocytic lineage. but the lymphocytic lineage what? Jim1138 (talk) 08:11, 31 August 2016 (UTC)



   (obsolete outside Scotland) Outside of.
       Away but the hoose and tell me whae's there.
   Without, apart from, except.
       Everyone but Father left early.
       I like everything but that.<en.wt

furthr:Acute myeloid leukemia (AML), also known as acute myelogenous leukemia or acute nonlymphocytic leukemia (ANLL), is a cancer of the myeloid line of blood cells,<itspretySTANDEDuno..(i'preciatecomunicatn,butIgetoldÃBILITYasaDISABLDusrSMH213.49.48.38 08:27, 31 August 2016 (UTC)


red blood cell formation,<dundefinewords(dys-)w.componnts(a.@eqinox-bad'abitsdyard:(btw,semzi=diagnozdw.cmleukemia:|ta4urefets! ur | prev) 13:24, 31 August 2016‎ SemperBlotto (talk | contribs)‎ . . (445 bytes) (-4)‎ . . (→‎Noun) (undo)<bringthis@POLICYBOARD>helbreaxluz,gudintentns-hel:/ 17:54, 2 September 2016 (UTC)

I'm not sure I understand your message this time, other than it has to do with dyserythropoiesis and using erythropoiesis in the definition :( —suzukaze (tc) 02:58, 3 September 2016 (UTC)

dunwury-1thingitryd2saywasigotD/W.CANCER(PMF81.11.206.159 19:30, 14 October 2016 (UTC)

2actualy:( 13:30, 22 October 2016 (UTC)

breakfast cerealEdit

Could you check the Cantonese translation here? 麥片 only refers to oatmeal or rolled oats, at least that's the case in Mandarin. ---> Tooironic (talk) 09:55, 4 September 2016 (UTC)

To be honest I don't think I've even heard of cereal being referred to in Cantonese (I'm just a 竹升)... Pinging @Justinrleung as a much more competent Cantonese speaker. —suzukaze (tc)

Question on templatesEdit

Hi, thank you for fixing the forced addition of a space in one of my templates. I'm new to this and I have a question : everytime I change my templates, I do not see the changes in the pages that transclude them, unless I edit / resave these pages to force a reparse. This would be completely unmanageable to do when the number of pages grow... Do you know how to his work? Does wiktionary update in batch every night and not real-time? Thx! Julien Daux (talk) 17:29, 12 September 2016 (UTC)

Julien Daux (talk) 17:29, 12 September 2016 (UTC)
@Julien Daux The pages do not update right away but they usually update in a decently short amount of time (speaking from experience tinkering with Chinese templates that are used on thousands of pages). But if you are feeling impatient for some reason you can add buttons to the top of pages to quickly "purge" a page (make the software reparse the page). —suzukaze (tc) 17:34, 12 September 2016 (UTC)
Thank you, I have this button now.. But it doesn't work recursively, so I think I'm better off waiting for the automated batch ... Julien Daux (talk) 17:57, 12 September 2016 (UTC)

Yeah, no.Edit

   (cur | prev) 05:55, 19 September 2016‎ Suzukaze-c (talk | contribs)‎ . . (621 bytes) (-16)‎ . . updated since my last visit (undo | thank) (Tags: no-documentation, removal-of-deletion-or-rfv-template)
(cur | prev) 05:48, 19 September 2016‎ Suzukaze-c (talk | contribs)‎ . . (637 bytes) (+16)‎ . . (undo | thank) (Tag: no-documentation)
(cur | prev) 05:43, 19 September 2016‎ UtherPendrogn (talk | contribs)‎ . . (621 bytes) (+621)‎ . . (Created page with "{| class="wikitable" style="width: 800px" ! colspan="6" | Chess pieces in Undetermined {{#ifeq:{{{chess pieces}}}|-|| · {{{ch...") (Tag: no-documentation)

It's quite clear it WASN'T updated since your last visit, since there was only one edit before you RFD'd it. Why are you lying? UtherPendrogn (talk) 05:57, 19 September 2016 (UTC)

@UtherPendrogn updated since my last visit is used to denote edits that have taken place since the last time you looked at a page. In this case, you looked at the page history before looking at the newest version at 05:55. —suzukaze (tc) 05:58, 19 September 2016 (UTC)

Reason for reversion at ?Edit

Why exactly did you revert my edit at ? "Formatting is lacking" is not a valid reason. Bumm13 (talk) 15:56, 22 September 2016 (UTC)

@Bumm13 Because you seem to not give a shit about the messages on your talk page, so I used a different method to get your attention. —suzukaze (tc) 18:15, 22 September 2016 (UTC)

Japanese combining formsEdit

Feel free to correct me or suggest doing something else, I know only a little bit of Japanese. Small characters like are defined as "combining forms" because apparently they can't be used by themselves to form syllables/morae, as opposed to normal characters like which are defined as "syllables". The small characters are using {{ja-combining form}}, which for some reason was categorizing entries in Category:Japanese syllables and leaving Category:Japanese combining forms and its children empty. I see you marked the combining form category (and its children) for imminent deletion, because it was empty. If it's okay for you, I removed your deletion request and fixed the template, so the right categories will get populated once the system catches up. --Daniel Carrero (talk) 13:03, 23 September 2016 (UTC)

Got it. —suzukaze (tc) 17:19, 23 September 2016 (UTC)


noentryz?? 20:54, 2 October 2016 (UTC)

Hmm, I don't think English entries are really my specialty, especially with something as technical as "mental anguish"... —suzukaze (tc) 05:54, 3 October 2016 (UTC)

Curious about Korean reading "evolutions"Edit

Hi suzukaze,

I noticed your two reversions regarding Korean "reading evolutions" and ">" sign usage. I was genuinely curious as to why we are using the ">" signs in the first place. Are the readings on the left some sort of earlier readings? I'm just not quite sure what is being conveyed within the context of (older) Korean hanja readings and some clarification would be helpful. Cheers! Bumm13 (talk) 06:30, 11 October 2016 (UTC)

@Bumm13 User talk:Atitarev#Question regarding '>' on hanja entries. —suzukaze (tc) 06:32, 11 October 2016 (UTC)
Okay, yes, I just now finished reading your post on Atitarev's talk page... this makes all those edits I made a pointless waste of time, it seems. I wish this had been clearer but for now, the status quo usage is the only option. Bumm13 (talk) 06:44, 11 October 2016 (UTC)

Zen BuddhismEdit

Is the Japanese translation correct? In Chinese this is known as 禪宗. ---> Tooironic (talk) 06:39, 14 October 2016 (UTC)

Nope. —suzukaze (tc) 06:58, 14 October 2016 (UTC)

Mandarin readingEdit

I noticed that when you unified the formatting at , the Mandarin reading changed from wèi to wēi. I just wanted to check to see if this is what you intended since the sources I've checked show it as "wèi". Cheers! Bumm13 (talk) 11:22, 18 October 2016 (UTC)

Possible bug in Module:nan-pronEdit

Hi suzukaze, When I try to say the following set of readings (chian/chó̍/chu) in the "mn=" (Min Nan) entry of Template:zh-pron, it returns the following module error:

Lua error in Module:nan-pron at line 667: attempt to concatenate field '?' (a nil value)

Hopefully it's not a major issue. Thanks! Bumm13 (talk) 22:21, 22 October 2016 (UTC)

@Bumm13 The 8th tone character is present after "chó", which already has the 2nd tone on ó. I think the module can't cope with the weird input. —suzukaze (tc) 22:58, 22 October 2016 (UTC)

Band (K-ON!輕音少女 quotations)Edit

Which season are they from? Also, could you check the pronunciation of leader in the second quote? — justin(r)leung (t...) | c=› } 13:22, 28 October 2016 (UTC)

✔—suzukaze (tc) 02:38, 29 October 2016 (UTC)


Hi, in Mandarin Chinese, the terms 咱們 and 我們 both mean 'we', but 咱們 includes myself. Can 我們 also include myself? – AWESOME meeos * (「欺负」我) 01:13, 8 November 2016 (UTC)

"We" always includes myself, in any language. 咱們咱们 (zánmen) includes the speaking partner (the person you're talking to) and 我們我们 (wǒmen) doesn't. --Anatoli T. (обсудить/вклад) 01:25, 8 November 2016 (UTC)
Can 咱們 be replaced with 我們? 我們 seems more common. – AWESOME meeos * (「欺负」我) 01:36, 8 November 2016 (UTC)

(@Awesomemeeos: Don't ask me these questions man, I'm just an ABC who thinks language is cool. My Mandarin is downright terrible. —suzukaze (tc) 01:59, 8 November 2016 (UTC))

Data for Middle ChineseEdit

Hi, where do you get the data for the Middle Chinese pronunciations; for example, how do you know that was pronunced like /*mˠie̞u/, /*mˠau/, with initial 4, final 92 and level tone? And what about the other reconstructions? Are they based on other dialects of Middle Chinese? Sorry for the abruptness – AWESOME meeos * (「欺负」我) 23:52, 8 November 2016 (UTC)

@Awesomemeeos: I'm not sure. Wyang is the one who set up the system. —suzukaze (tc) 00:30, 9 November 2016 (UTC)
The data seems to be from here. The Middle Chinese reconstructions are based on an ancient rime dictionary called Guangyun. All the reconstructions are slightly different depending on how each linguist reconstructed it. Reading the Wikipedia article on Middle Chinese should give you more insight. — justin(r)leung (t...) | c=› } 00:32, 9 November 2016 (UTC)

Module errors due to Module:ja etc.Edit

I hope you can fix it ASAP. --kc_kennylau (talk) 14:18, 10 November 2016 (UTC)

Category:Zhuang Sawndip formsEdit

Please deal with this category which I believe you have populated. Thank you. --kc_kennylau (talk) 16:14, 11 November 2016 (UTC)

I'm not sure what template should be used to create it (if there even is one) (;´∀`) —suzukaze (tc) 21:45, 11 November 2016 (UTC)

Incomplete Dubeolsik supportEdit

In Wiktionary:Grease pit/2016/September#Template:Hangul Syllables character info, you suggested using {{character info/new}} for all existing Hangul Syllables entries, because the old template had a very unsightly bug that you described in the GP discussion. This task is   done, I added {{character info/new}} in all these entries.

But, the Dubeolsik support seems incomplete. (currently, affected entries have a "?" in the Dubeolsik; before, adding the template in these entries would cause a module error) Do you know what is the Dubeolsik for all the "composite" final jamos, like the ㄳ in the end of ? I'd like to fill in all these question marks in the code:

['ㄳ'] = '?'; ['ㄶ'] = 's-g'; ['ㄽ'] = 'f-t'; ['ㄵ'] = 's-w';
['ㄺ'] = '?'; ['ㄻ'] = '?'; ['ㄻ'] = '?'; ['ㄼ'] = '?';
['ㄾ'] = '?'; ['ㄿ'] = '?'; ['ㅀ'] = '?'; ['ㅄ'] = '?';
['ㅆ'] = '?';

(Should I just use this table: It does not seem to be compatible with this online Korean keyboard: )

--Daniel Carrero (talk) 21:49, 20 November 2016 (UTC)

TBH I'm not really familiar with Korean input methods :/ But it should be straightforward ㄳ→ㄱㅅ→rt... (@Wyang, TAKASUGI Shinji?)
Also, ㄻ is listed twice in the code above. —suzukaze (tc) 22:23, 20 November 2016 (UTC)

The nonidentical complex codas are entered as a sequence of two consonants, and the tense consonant codas are entered as uppercase equivalents of the plain consonants. So:

['ㄳ'] = 'r-t'; ['ㄶ'] = 's-g'; ['ㄽ'] = 'f-t'; ['ㄵ'] = 's-w';
['ㄺ'] = 'f-r'; ['ㄻ'] = 'f-a'; ['ㄼ'] = 'f-q';
['ㄾ'] = 'f-x'; ['ㄿ'] = 'f-v'; ['ㅀ'] = 'f-g'; ['ㅄ'] = 'q-t';
['ㅆ'] = 'T';

Wyang (talk) 22:34, 20 November 2016 (UTC)

Thank you.   Done. All Korean syllable entries, like , should have a character box with automatic composition and Dubeolsik now. --Daniel Carrero (talk) 22:42, 20 November 2016 (UTC)

Silly translationEdit

Hi suzukaze, I know this might be a funny translation to translate into Cantonese, but how do you translate "three cats in one week", considering the context of a cat giving three cats as children. I know. – AWESOME meeos * (「欺负」我) 07:23, 28 November 2016 (UTC)

禮拜 [Cantonese, trad.]
礼拜 [Cantonese, simp.]
jat1 go3 lai5 baai3 saam1 zek3 maau1 [Jyutping]
but my grammar is terrible, please check with others —suzukaze (tc) 13:04, 28 November 2016 (UTC)

Min Nan readingsEdit

Hi Suzukaze, I was just curious about the Min Nan readings at (iaⁿ/iang), which you added to the article. The Taiwanese Ministry of Education dictionary gives just an iong reading while another Min Nan dictionary gives "iong" and "iòng". I just thought I'd bring it up since I'm not an authority on which Min Nan readings are actually correct. Bumm13 (talk) 23:45, 30 November 2016 (UTC)

It came from the data here that Wyang imported into Wiktionary for use by Template:zh-new. TBH I don't know how accurate it is. User:Justinrleung probably knows more about it. —suzukaze (tc) 07:28, 1 December 2016 (UTC)
@Bumm13: TBH, it's not a very common character. Here's what I found so far:
  • nothing in 閩南方言大詞典 or 普通話閩南方言常用詞典
  • 甘字典 (probably the other dictionary you're talking about): iong ("(of clouds) agitated; (of water) deep and wide; tall and big") and iòng ("(of clouds) agitated; (of water) deep; tall and big")
  • 台語線頂字典: iong, iàng, iang and iaⁿ
  • 當代泉州音字彙: iong (e.g. 泱灢 "(of water) murky"). — justin(r)leung (t...) | c=› } 21:32, 12 December 2016 (UTC)
  • 台日大辭典: iaⁿ ("ripple"), oaiⁿ (e.g. 清泱泱 "(of water) very clear"; 飾泱泱 "very beautiful")
I'd say it is xm,qz,tw:iong/zz,twv:iang almost for sure. xm,twv:iòng/zz,twv:iàng could possibly follow. I am unsure about the other readings, but they seem to be valid, albeit for different meanings. — justin(r)leung (t...) | c=› } 21:32, 12 December 2016 (UTC)


Hi suzukaze, the title should tell you something. Why did you add this? – AWESOME meeos * (「欺负」我) 08:39, 12 December 2016 (UTC)

User talk:Prisencolin#Edit at 鼠suzukaze (tc) 08:54, 12 December 2016 (UTC)

Template:za-sawndip form ofEdit

It took a lot of trial and (mostly) error, but I think I got this to work. With my meager knowledge of lua, I haven't figured out the details, but it looks like at least one of the modules involved insists on getting its positional parameters from the entry rather than the template, so it interprets the {"t"/"s"/""} values as the term to link to. I probably should have let you figure it out, since you know more about this, but I'm pretty stubborn at times. I edited all the entries to work with this version, but it wouldn't surprise me if I missed one or two of the ones with "t" or "s" as the first parameter. If you can figure out how to get it to not link to the first parameter, feel free to rework or replace my version. Chuck Entz (talk) 04:45, 24 December 2016 (UTC)

Thank you for noticing a problem and fixing it >_< —suzukaze (tc) 05:01, 24 December 2016 (UTC)


When you're free could you check the non-Mandarin readings for this entry? Thanks. ---> Tooironic (talk) 02:27, 28 December 2016 (UTC)

I think @Justinrleung and @Wyang could do a much better and more knowledgeable job at that. —suzukaze (tc) 04:47, 28 December 2016 (UTC)
OK, I'll ask them, thanks anyway. ---> Tooironic (talk) 04:57, 28 December 2016 (UTC)


The おたく entry currently has the most information, but I see that you've recently changed the link at リア充 to point to オタク instead.

I don't care much which spelling is used as the lemma, but whatever the case, that lemma entry should have the full details.

If you prefer オタク, would you be so kind as to move the relevant content from おたく, and then edit the relevant etym section at おたく to point the reader to オタク? Alternatively, would you change the links back to point to おたく instead, and edit the オタク entry to point the reader to おたく? Either is fine by me. ‑‑ Eiríkr Útlendi │Tala við mig 17:56, 9 January 2017 (UTC)

I was actually considering doing it but I guess it slipped my mind... —suzukaze (tc) 22:27, 9 January 2017 (UTC)

Translingual BrailleEdit

Feel free to discuss this, but actually I think a Braille entry like should have separate Japanese, Korean, Thai, Greek sections... This would be consistent with Latin script entries like a. --Daniel Carrero (talk) 07:06, 13 January 2017 (UTC)

I'm doing it because the Braille entries currently have literally everything under Translingual except for Japanese and it stands out weirdly. If you want to revert my edits go ahead. —suzukaze (tc) 07:07, 13 January 2017 (UTC)
Ok, thanks. Yes, then I'm going to revert your edits, if you don't mind. I agree with your reasoning: Japanese really is currently standing out weirdly. I've been meaning to create separate sections for the other languages in Braille entries but it's going to take some work... I've been procrastinating that project and doing other things instead. FWIW, if I remember correctly, around 2009 I created separate sections for all Latin script letters I found that were using "Translingual" to list a bunch of specific languages, like in this diff. Another thing: the Japanese section was properly categorized, but these "Thai Braille", "Greek Braille", etc. in the Translingual section don't have any categories at the moment. --Daniel Carrero (talk) 07:24, 13 January 2017 (UTC)



At to iu ma ni watashi no kakushinteki na kōdo wa usui kūki ni kieta.
AWESOME meeos * (chōmtī hao /t͡ɕoːm˩˧.tiː˩˧ haw˦˥/) 09:45, 22 January 2017 (UTC)
  1. A succeeding edit made it do weird things. In theory, it's back and even stronger than before now.
  2. I think that 無駄(むだ)なった (ga muda ni natta) (google:が無駄になる) is a more natural way of saying "disappeared into thin air". "Thin air" is an English idiom, and usage of 'は' in this case feels inexplicably weird. —suzukaze (tc) 10:03, 22 January 2017 (UTC)
suzukaze (tc) 10:03, 22 January 2017 (UTC)
@Suzukaze-c Thanks for the edits in the module. But what does muda ni natta literally mean and can Japanese people still understand kūki ni kieta as muda ni natta? – AWESOME meeos * (chōmtī hao /t͡ɕoːm˩˧.tiː˩˧ haw˦˥/) 10:07, 22 January 2017 (UTC)
  1. ??? ga muda ni natta — "??? became a waste [of effort]".
  2. Not sure.
  3. (You don't need to ping me when writing on my own talk page. People already get notifications that they have a talk page message.)
suzukaze (tc) 10:13, 22 January 2017 (UTC)

Irregular Korean pronunciationEdit

Hi Suzukaze-c, I was talking about random things to my Korean friend, and we eventually hit a Korean word called 해돋이 (haedodi, sunrise). The thing was, I thought that this word was pronunced like haedodi [hɛ̝do̞di], but he told me it was actually [hɛ̝do̞d͡ʑi]. I thought Hangul was a completely phonetic orthography for Korean! What do you think of this? – AWESOME meeos * (chōmtī hao /t͡ɕoːm˩˧.tiː˩˧ haw˦˥/) 05:28, 23 January 2017 (UTC)

PS I have also asked Wyang about this as well – AWESOME meeos * (chōmtī hao /t͡ɕoːm˩˧.tiː˩˧ haw˦˥/) 05:28, 23 January 2017 (UTC)
Language change happens. ¯\_(ツ)_/¯ —suzukaze (tc) 05:35, 23 January 2017 (UTC)


Module error here due to insufficient memory — can you fix it? —Μετάknowledgediscuss/deeds 02:09, 11 February 2017 (UTC)

Fixed. Wyang (talk) 02:19, 11 February 2017 (UTC)
Can't we add {{character info/new}} in the entry? It was removed a month ago. I tried to readd it now, but didn't do it because it would cause module errors again. --Daniel Carrero (talk) 02:23, 11 February 2017 (UTC)
No idea. My best opinion is that if adding it produces errors, don't add it. My weaker opinion is that it is not entirely necessary in the first place: the Translingual#References section already tells us the hexadecimal codepoint and has a link to the Unihan database. The extra information provided by the infobox is trivial ("CJK UNIFIED IDEOGRAPH-4EBA", wow!) —suzukaze (tc) 06:24, 14 February 2017 (UTC)
I agree with this: "if adding it produces errors, don't add it". That said, I hope it can be readded without errors eventually, for consistency with all other character pages that use it if nothing else. Today I suggested opening up to Wikidata and moving our character information there (in this discussion: Wiktionary:Beer parlour/2017/February#Proposal: Implementing Wikidata access). I wonder if using Wikidata would make entries like lighter, because I believe we would only access the data items and properties needed in each case, as opposed to loading many modules with information about everything (and the kitchen sink).
If we add the charbox to someday, then this will happen automatically: a link to Appendix:Unicode/CJK Unified Ideographs is going to appear, the entry will be categorized in Category:CJK Unified Ideographs block, it will show previous/next characters and it will display an additional image. I kinda like to know the codepoint name too ("CJK UNIFIED IDEOGRAPH-4EBA"), although it's easily derived from the "CJK UNIFIED IDEOGRAPH-(hexadecimal)" formula, so this one is less informative than usual anyway. --Daniel Carrero (talk) 06:47, 14 February 2017 (UTC)

Japanese names in Chinese questionEdit

Hi Suzukazec, I've wondered how would Chinese speakers know how to pronounce the original Japanese names? For example, the surname Suzuki is Língmù in Mandarin. Totally different! — AWESOME meeos * (chōmtī hao /t͡ɕoːm˩˧.tiː˩˧ haw˦˥/) 05:50, 21 February 2017 (UTC)

They don't pronounce it the Japanese way, they pronounce it the Chinese way.
If a name has kana in it, they assign a theoretical kanji spelling to it and then still read it the Chinese way.
Sometimes you have the funny case where surnames include kokuji (Japanese-made kanji), in which case youbian dubian is invoked (which again allows it to be read the Chinese way). —suzukaze (tc) 05:54, 21 February 2017 (UTC)
Example: Ānbèi Jìnsān (Abe Shinzō)suzukaze (tc) 05:59, 21 February 2017 (UTC)
But they may not know the original pronunciation, in Japanese. With English, it's taken directly from Japanese with a few pronunciation modifications. But with Chinese—it's changed completely! Just saying... — AWESOME meeos * (chōmtī hao /t͡ɕoːm˩˧.tiː˩˧ haw˦˥/) 06:00, 21 February 2017 (UTC)
They don't need to know the original pronunciation. —suzukaze (tc) 06:04, 21 February 2017 (UTC)

Q re: gyozaEdit

I took the "Shandong" mention from the EN term's etym, [[gyoza#Etymology]]. Does that entry need editing too? Would Wyang be of any help in ferreting out the likely source dialect? ‑‑ Eiríkr Útlendi │Tala við mig 07:57, 23 February 2017 (UTC)

I only think it's too specific since there are other historical cases of k ~ j, such as in Peking (Beijing) and Chekiang (Zhejiang). Other than that my opinions on the topic are are not that strong. —suzukaze (tc) 08:00, 23 February 2017 (UTC)


Since you asked, here's the answer. Our main page for telling people how to format a Japanese entry is terribly outdated and is directly inspiring this kind of problem. —Μετάknowledgediscuss/deeds 05:41, 5 March 2017 (UTC)

While we're at it, a lot of these pages are pretty badly out of date. WT:AZH could use some attention too. —Μετάknowledgediscuss/deeds 05:46, 5 March 2017 (UTC)
How do people get there? —suzukaze (tc) 06:28, 5 March 2017 (UTC)
Probably from CAT:Japanese language, I'd guess. —Μετάknowledgediscuss/deeds 06:48, 5 March 2017 (UTC)

Rom in WP linksEdit

As a usability consideration, I've added rom in cases where the WP link term doesn't match the headword. In such cases, users do not have any information on the entry page regarding the reading of the WP link term, unless we provide it right there in the WP link.

Since ja:w:紅鶴 now exists (as a redirect), we may as well just use {{wikipedia|lang=ja}} with no params -- possibly less confusing. ‑‑ Eiríkr Útlendi │Tala við mig 23:49, 15 March 2017 (UTC)


Thanks for the kind message. :D I do have a bit of knowledge of Japanese, but my onyomi and kun'yomi knowledge is mostly rudimentary at best, but I am slowly learning the ropes of all this. Thank you again, and I look forward to contributing to more in the future. Johnnysama (talk) 05:51, 22 March 2017 (UTC)


Just so you know, nationalities are adjectives like "French" or "Swedish". Nouns for people are demonyms. —CodeCat 01:37, 17 April 2017 (UTC)

@CodeCat Ah, thank you. It seemed off to me but when I looked at Category:en:Nationalities there were entries like Siraya and Acholi and I thought my own understanding of something was wrong. —suzukaze (tc) 01:40, 17 April 2017 (UTC)
Not really, the English category has a bunch of miscategorised entries. —CodeCat 01:41, 17 April 2017 (UTC)


Hi! Do you mind taking a look? I deleted it, but restored it again because of the Japanese section at orz. --Robbie SWE (talk) 18:21, 18 April 2017 (UTC)

  Done(?)—suzukaze (tc) 04:07, 19 April 2017 (UTC)


You might want to take a look at this entry. ---> Tooironic (talk) 04:53, 29 April 2017 (UTC)

I'm not sure how to word the definition since the other ones are so specific. —suzukaze (tc) 04:57, 29 April 2017 (UTC)

Appendix:Japanese verbsEdit

Hi Suzukaze! I'm a bit unsure if this change is legit. Mind taking a look? --Robbie SWE (talk) 17:21, 8 May 2017 (UTC)

Looks good to me.—suzukaze (tc) 17:45, 8 May 2017 (UTC)

Category: Hong Kong EnglishEdit

Hi Suzukaze! I see that you have deleted a lot of entries from this category. I'm not sure that these changes are very helpful. Very few words are absolutely only exclusive to one variety of English, especially in this day and age of information technology where boundaries are more porous that they may have been in the past. However, that does not mean that certain terms (e.g. chow fun or char siu) are not part of Hong Kong English. In fact, I would argue that most of the terms you have deleted from the list are more common/frequent there than in other varieties of English (with the exception, perhaps, of Chinese English). Char siu, for example, is a famous item of cuisine in HK, the local HKers identify this word as part of HK English, and other sources/dictionaries that treat HK English include "char siu" as part of HK English (e.g. Bolton 2003, Cummings and Wolf 2011). In addition, the evidence I have suggests that a lot of these terms originated in HK English. The general understanding/practice in the lexicography of regional varieties of English (see for example the dictionaries of Ramson 1988, Orsman 1997, Winer 2009, Silva 1996) is to include terms that originated in that variety, or that are more common there than in other varieties. Now, when someone goes to the category of HK English they do not get a link to "char siu" ... not very helpful. Can we revert your deletions? - Sonofcawdrey (talk) 04:32, 14 May 2017 (UTC)

I believe your understanding of the category is fundamentally wrong. It's for "Hong Kong-isms", "English words specific to the Hong Kong region", not "words more common in the Hong Kong region". A lot of the words you added (dragon boat, hong, bubble tea, Wing Chun, har gow, hoisin sauce, Mongkok) are definitely words that will not be found exclusively in Hong Kong. Dragon boats, hongs, bubble tea, and Wing Chun don't even originate in Hong Kong, and the last two may be found across the US with decent frequency. har gow and hoisin sauce are a part of Cantonese cuisine and may be found in the cookbooks of people who are probably not from Hong Kong and are probably not for Hong Kongers. Mongkok is literally the only name the place has. Perhaps you are looking for Category:en:Hong Kong? (although, I believe most of the words I mentioned don't belong there, either, not being intrinsically linked to Hong Kong) —suzukaze (tc) 04:49, 14 May 2017 (UTC)
Hi Suzukaze, I understand why you took them out. But, if we don't include such terms, then I think that the real problem is that the category is fundamentally misnamed. If it is a category of Hongkongisms, then it should be Category: Hongkongisms, not Hong Kong English - these aren't the same thing. - Sonofcawdrey (talk) 07:44, 16 May 2017 (UTC)
IMO there is no problem—Category:British English = Britishisms (The following are British English terms; terms only used or having specific meanings in the United Kingdom), Category:Taiwanese Chinese = Chinese terms exclusive to Taiwan, etc. "Hongkongisms" is merely an informal wording. —suzukaze (tc) 07:51, 16 May 2017 (UTC)
I added "The following are terms, or specific meanings of terms, only used in Hong Kong" to the "Hong Kong English" page to clarify matters. - Sonofcawdrey (talk) 14:02, 16 May 2017 (UTC)

Mandarin readingsEdit

I was just curious about supposedly having the Mandarin readings "āo, āo, niū, " when other sources say they are "ǎo, ào, niù (not 100% sure about )". Bumm13 (talk) 08:29, 31 May 2017 (UTC)

Shoot, it must have been one of those cases where the code I used to generate the entry accidentally ignored tone marks... I must figure out a way to track them down. —suzukaze (tc) 19:57, 31 May 2017 (UTC)

ja-readings templateEdit

I just wanted to say thanks for what you did to the {{ja-readings}} template. Awesome job! thanks!! 馬太阿房 (talk) 07:42, 9 June 2017 (UTC)

You're welcome! User:Krun was the impetus though. —suzukaze (tc) 21:18, 9 June 2017 (UTC)
I'm curious to know where you got the list of jōyō kanji which designates certain jōyō readings as uncommon (the one the {{ja-readings}} template draws data from). Knowing that a reading is uncommon is useful information, so I'm glad that information is included, but I was wondering how trustworthy that information is. For example, I could be wrong, but I thought 久遠 read as くおん is more common than 久遠 read as きゅうえん but the く reading has the "Jōyō, uncommon" label. 馬太阿房 (talk) 17:12, 13 June 2017 (UTC)
@馬太阿房 It was extracted from the Japanese Wikipedia page. If you know of any better sources I could look at it.—suzukaze (tc) 17:25, 13 June 2017 (UTC)
Okay, I think I figured out what it means, and it is useful information. I don't think it means that it is less common, but rather that is used in just a few or maybe just one or two words (words which may themselves be considered common and also more commonly read with that reading).馬太阿房 (talk) 17:32, 13 June 2017 (UTC)


Please check what I did to the Japanese section under . Feel free to revert or change my editing as you see fit, but I thought it looked very confusing the way it was and decided to do something about it. I'm thinking maybe User:Krun had already asked you to do something about this too because I noticed that he was the one who had made the changes utilizing the {{ja-kanji}} template which doesn't work properly in cases like this. Can you maybe do something with this template and template documentation to make it more usable for cases like this? 馬太阿房 (talk) 22:28, 16 June 2017 (UTC)

Hmm, I don't think anyone has discussed {{ja-kanji}} nor this particular problem (shinjitai co-opting of older characters) before. I'll think about it. —suzukaze (tc) 00:55, 17 June 2017 (UTC)


Hiya. You can see what I'm doing; converting {{ja-accent-common}} to {{ja-pron}}. But can you do a big favour for me? Please list all of the pages that use the former template. Thank you! 07:15, 18 June 2017 (UTC)

Special:WhatLinksHere/Template:ja-pronSpecial:WhatLinksHere/Template:ja-accent-commonsuzukaze (tc) 07:40, 18 June 2017 (UTC)
ありがとうございます。 08:14, 18 June 2017 (UTC)

/ 𪡏Edit

The character is not being simplified correctly in the compounds section on its page. I presume that its simplified form, having been fairly recently added to Unicode, is missing from a simplification table in some module we have. Do you know how to fix this? There will also be several more new simplified characters missing from there, so it would probably be best to scour the most recent version of the Unihan database to get all the connections we’re missing. Edit: I noticed e.g. that the simplified form was added to the page late (2013), manually, by User:Bumm13, so I guess we’ve never had a good coverage of these later-encoded simplified forms. – Krun (talk) 00:57, 24 June 2017 (UTC)

@Krun: The data is at Module:zh/data/st (trad→simp) and Module:zh/data/ts (trad→simp). I've considered regenerating the data from other sources online (that are better than the Unihan database), but haven't gotten around to it... —suzukaze (tc) 01:04, 25 June 2017 (UTC)


Why isn't the reading なま showing the Jōyō kanji lable in the readings section? I can't figure out what the problem is. Can you fix this? 馬太阿房 (talk) 20:12, 27 July 2017 (UTC)

Well, I see that the issue is resolved now. I don't know if you did anything, I did anything, or if it resolved itself.馬太阿房 (talk) 20:37, 27 July 2017 (UTC)

Transclusion limitsEdit

In this diff you used a rather ingenious kludge to get the desired display. Unfortunately, that caused the entry to hit the template include size, and a number of templates toward the bottom of the page displayed as links to the templates themselves without any of the parameters. An IP (sort of) fixed this by selectively undoing the edit on those templates that weren't displaying, but the display is now inconsistent and less-than-optimum. I'm not sure the best way to fix this, but you may think of something I haven't (the easiest way would be to split the page, I guess). Thanks! Chuck Entz (talk) 01:40, 29 July 2017 (UTC)

@Chuck Entz: Damn, I hadn't noticed. I can only think of splitting the page. —suzukaze (tc) 05:50, 29 July 2017 (UTC)

Hanzi sortkeysEdit

I was looking at the sortkey data modules when you were experimenting with a sortkey function in Module:sandbox. Your data module is pretty huge. I wonder, had you considered splitting it by Unicode codepoint or something? Then a function could get the codepoint for a character and look up its sortkey in the correct module. And then, at least on most pages (i.e., those that have characters from fewer submodules), the function would use less memory.

Isomorphyc divided up modules used for reference templates in a similar way, though I really don't understand how it works (see Category:Reference module sharded data tables). — Eru·tuon 06:23, 29 July 2017 (UTC)

I have considered it. I know Module:zh does it at .check_pron() but I don't understand the code. —suzukaze (tc) 06:32, 29 July 2017 (UTC)
Hi @Erutuon, Suzukaze-c: Sorry I'm still away much longer than I thought. I am trying to make regular time for Wiktionary again. If you would like to pursue the sharding idea for data modules I can put my sharding code in GitHub or share it with some notes on my user page. It is in Python and it is simple conceptually; and I can help with explanations or cleaning up my Python style if necessary. Isomorphyc (talk) 18:30, 29 July 2017 (UTC)
I would add that I do not really recommend sharding if you can avoid it. It is not very friendly to other editors, and is too low-tech to maintain itself cleanly, while the robot client nexus with Lua is overpowered for data storage, brittle, and not very open. I wasn't able to find your data-intensive sort key module, but my binary hash index key is probably not appropriate; if you must shard, a user transparent key, such as stroke count, radical or initial Pinyin letter would probably be better. Isomorphyc (talk) 19:12, 29 July 2017 (UTC)
The module of sortkeys is at Module:User:Suzukaze-c/zh/data/skeys. It has single characters indexed to a radical (?) and a number. I was thinking of just putting it in a bunch of separate modules organized by Unicode codepoint. I'm new to programming and I'm not totally sure how it would work, but I might be able to figure it out. — Eru·tuon 19:21, 29 July 2017 (UTC)
I created a function to print out the content for the separate modules: Special:Permalink/47139321. — Eru·tuon 19:23, 29 July 2017 (UTC)
If you like I could share the code I used to process into Module:User:Suzukaze-c/zh/data/skeys. —suzukaze (tc) 23:24, 29 July 2017 (UTC)
Naw (if you're talking to me). I can just compile the submodules from your master module. See the current version of Module:sandbox/documentation. (I've exceeded the template include size, so it won't display in Module:sandbox. XD)
Only question is how big the submodules should be.
Right now, the module puts each range of 5000 codepoints (for instance, codepoints 13312 to 18311) in a single module, and it yields 36 submodules. (That indicates there are gaps, because there are 87870 codepoints total, and 87870/36 ≈ 2440. So the number of characters in each module probably varies.)
This system might be maintainable: we could keep the submodule-compiling function and your master sortkey module, and recompile the submodules if there are any changes. And because it's based on codepoints, the organization should be stable. However, I wonder if the submodules should be smaller. More work, but less likely to cause memory problems. I don't know how to figure out the actual amount of memory used by the module, though. — Eru·tuon 00:44, 30 July 2017 (UTC)
Bleh. There aren't actually that many modules. There's a big skip in the actual module numbers, corresponding to a skip in codepoints. There are still only 18 modules, approximately 87870 / 5000. — Eru·tuon 01:03, 30 July 2017 (UTC)
(I imagine that theoretically we could exclude a good number of the characters as being unused, but the modules might be used for unanticipated purposes in the future... —suzukaze (tc) 02:10, 30 July 2017 (UTC))
My experience was that 5k-50k is a good module size. One can be on the small side of the range if a single page might have a large number of different module transclusions; otherwise on the larger side. It is necessary to optimise for the worst case scenarios, usually involving short, high traffic, multi-language pages, depending on use case. I regularly made the mistake of not checking `Category:Pages_with_module_errors' often enough after changes for memory errors. Good luck. I did look over your data and I agree this is a very good candidate for sharding, and code point value is a good key. Isomorphyc (talk) 05:23, 30 July 2017 (UTC)
I'm starting to create the modules. I think they're on the lower end of the range that you give. That should be safer. — Eru·tuon 06:19, 30 July 2017 (UTC)

Okay, I've got less than half of Module:User:Suzukaze-c/zh/data/skeys added to subpages of Module:zh-sortkey/data. You can see the results on Module:zh-sortkey. (I should probably zero-pad the pagenames....) — Eru·tuon 07:26, 30 July 2017 (UTC)

I moved the pages to zero-padded versions. So there are like 80 modules left to go. If you'd be willing to help, I'd greatly appreciate it. Just go to Module:User:Erutuon/zh/documentation and copy the module code into the appropriately numbered subpages of Module:zh-sortkey/data/. — Eru·tuon 18:07, 30 July 2017 (UTC)

@DTLHS: Thank you for doing this; you beat me to it. Isomorphyc (talk) 21:48, 30 July 2017 (UTC)
Heh, I was planning to do it by hand and ask others to help, but then I thought, This is stupid, a bot should do it, so I asked DTLHS. But I hadn't considered that you might do it with OrphicBot. — Eru·tuon 22:00, 30 July 2017 (UTC)


Hi. I saw your work on the new format of {{ja-readings}} and it looked much nicer. Just asking if it was possible to add the correspondence between the reading section and the kanji definitions for 多音字 like ? --Dine2016 (talk) 01:21, 19 August 2017 (UTC)

Like 樂#Korean? (which is an experiment) —suzukaze (tc) 04:12, 19 August 2017 (UTC)
The Korean hanja section looks great. I'd like to wait until we have enough Japanese 漢和 coverage, though. --Dine2016 (talk) 06:03, 19 August 2017 (UTC)

By the way, what would be the criterion for inclusion of kun-readings? I've just got a copy of the three-volume 広漢和辞典, but it seemed to list too many kun-readings, some of which are only used for reading kanbun. --Dine2016 (talk) 03:01, 8 September 2017 (UTC)

I'm not sure... —suzukaze (tc) 03:12, 8 September 2017 (UTC)


Please check your last edit there. It looks like there are at least a couple of bogus/empty items in the list (at least those seem to be hyphens, not kana- but what do I know). The reason I noticed is that it led to the automatic creation of Category:Japanese kanji with kun reading -, which {{auto cat}} doesn't know what to do with. Chuck Entz (talk) 02:58, 23 August 2017 (UTC)

Darn. Thanks for noticing.—suzukaze (tc) 03:01, 23 August 2017 (UTC)

Cáo CāoEdit

Objecting your proposed quick deletion, I changed it to discussion. Personal names should generally be excluded, but limited exception should be considered with specific reasons. I was just trying to delink 曹操.Jusjih (talk) 00:05, 2 September 2017 (UTC)

So far, the pinyin forms of deleted entries have also been deleted. Why should we keep a non-lemma form of a deleted entry? —suzukaze (tc) 00:06, 2 September 2017 (UTC)
I have a new thought at Wiktionary:Requests for deletion#Cáo Cāo.--Jusjih (talk) 03:03, 3 September 2017 (UTC)


Probably, but luckily Metaknowledge just protected it. - Amgine/ t·e 23:31, 18 September 2017 (UTC)

, and on'yomi of the pattern CVchiEdit

I was curious about this change.

Generally speaking, I remember reading somewhere that at least some of the on'yomi ending in ち are essentially reconstructed and only found in kanji dictionaries, based on Middle Chinese readings that ended in /t/. Meanwhile, つ ending for such readings would basically be allophone, as the alternative Japanese nativization of a final /t/.

More specific to the entry, this would point to the がつ reading as the expected goon pair for がち. What is the basis for removing がつ from goon?

Also, is there any attestable evidence for the ごち reading in the historic record? I've had a poke in my resources and can't find anything.

Curious, ‑‑ Eiríkr Útlendi │Tala við mig 17:49, 20 September 2017 (UTC)

I don't know about the other readings but gatsu is already listed as kan'youon. —suzukaze (tc) 22:36, 20 September 2017 (UTC)
  • If there's a case to be made for がつ being goon, it would seem to make more sense to remove the kan'yōon...? ‑‑ Eiríkr Útlendi │Tala við mig 01:26, 24 September 2017 (UTC)
  • I suppose so. [5] has ガツ(グヮツ)(慣) though. It's either one or the other... —suzukaze (tc) 01:28, 24 September 2017 (UTC)


I'm surprised you are not a rollbacker yet, considering you are patrolling and reverting many (if not most) of the recent changes to CJKV entries. Would you like to become one? It is a one-click revert function, and will make patrolling much easier. Wyang (talk) 12:40, 23 September 2017 (UTC)

Also, would you like to become an admin, Suzukaze? I think the community would greatly benefit from your patrol and reverting of vandalism, entry maintenance and technical skills. Wyang (talk) 12:59, 23 September 2017 (UTC)
rollbacker: Maybe. I must think about it more. I'm not sure I'm responsible enough.
admin: Never, for various personal reasons. —suzukaze (tc) 13:51, 23 September 2017 (UTC)
No worries! Just let me know when you make up your mind with the rollbacking tool. I'm not sure what the correct procedure is with this, but I will find out. I think you will be the perfect candidate for it, with your invaluable patrolling edits. Wyang (talk) 14:11, 23 September 2017 (UTC)
I've seen it done on the Whitelst page, just like autopatroller. @Suzukaze-c: As for responsibility: if you're responsible enough to regularly undo edits, you're responsible enough to do the same thing using the rollback tool. There are only two drawbacks: the rollback tool has a generic edit comment that you can't change, and it marks the edit as patrolled, so it disappears from Recent Changes for those who have patrolled edits filtered. The first gets you the occasional "why didn't you say what was wrong?" gripes, but you seem to good enough at dealing with that kind of thing. The second means that you need to let admins know when someone should be blocked or inappropriate content (mostly personally-identifiable details and spam/promotional content, but also some copyvios) hidden.
As for adminship: it's a responsibility, it changes how people deal with you, and it takes a certain temperament. It's not for everyone. We're all volunteers here, so I'm just grateful for anything anyone is willing to contribute- and you contribute a lot!!!. Chuck Entz (talk) 16:09, 23 September 2017 (UTC)
Also, I'm trying to cut down on obsessively looking at Recent Changes all the time. It can't be good for me. —suzukaze (tc) 02:33, 7 October 2017 (UTC)
Haha, you are not the only one obsessively doing that. Wyang (talk) 05:53, 7 October 2017 (UTC)

Q re: {{ja-readings}}Edit

I was editing recently to add readings, and found myself wondering what to do about いまいましい, canonically spelled 忌ま忌ましい. I added it to the readings list, but it's showing up as 忌まいましい, which is incorrect. Adding the reading as い-ま-い-ましい didn't work (I didn't really expect it to, but I gave it a try), and I couldn't figure out how to override the template.

Which leads to my questions:

  • Is there an override for readings like this?
  • Or should readings like this be omitted from the {{ja-readings}} list, as the kanji appears more than once?

TIA, ‑‑ Eiríkr Útlendi │Tala við mig 17:39, 16 October 2017 (UTC)

I wasn't aware of such words existing. Imaimashii doesn't seem to be listed in my (admittedly feeble) sources for readings; are you certain it should be included in the first place? —suzukaze (tc) 04:49, 18 October 2017 (UTC)
I guess that's the question. If a given kanji has a kun'yomi that includes that kanji plus kana, but the kanji appears more than once in the spelling, do we list that as a kun'yomi? I suppose it could be analyzed as a derivative instead. Your thoughts? ‑‑ Eiríkr Útlendi │Tala við mig 18:24, 18 October 2017 (UTC)
No idea, but I lean towards exclude for now until there is further information. —suzukaze (tc) 03:36, 20 October 2017 (UTC)
Thanks, I'll remove the いまいましい reading from the kanji section at for now. :) ‑‑ Eiríkr Útlendi │Tala við mig 15:50, 23 October 2017 (UTC)


Hi there! I wonder if you could lend a little help here. I'm trying to find out what this File:Culto do chá p25.png writing says. I'm almost positive it's an author signature, saying either Yoshiki or Goto Seikodo. Thanks! NMaia (talk) 15:09, 17 October 2017 (UTC)

I'm not sure what it says either. Try asking someone else, I'm sorry. —suzukaze (tc) 04:47, 18 October 2017 (UTC)
@NMaia It reads 芳明 (drawn by 芳明 Yoshiaki), whoever that is. Maybe Utagawa Yoshiaki. Wyang (talk) 22:10, 23 October 2017 (UTC)
@Wyang, Eirikr Many thanks for your help! :) NMaia (talk) 23:30, 23 October 2017 (UTC)
@Wyang, Eirikr, Suzukaze-c Pure curiosity here, but this work cites a Gotô Seikôdô as illustrator. Does that name ring any bells? NMaia (talk) 02:49, 30 October 2017 (UTC)
@NMaia -- Googling for that name (google:"goto seikodo") throws up a handful of results suggesting that Gotō Seikōdō did the engraving. That said, while "Gōtō" is a common surname (後藤), "Seikōdō" sounds like a company rather than a personal name. I can find online reference to google:"後藤清高堂" (read as Gotō Seikōdō) as a company based in Kyōto, close to Kōbe, but I'm not sure if this is the correct kanji spelling for the work you're looking at. ‑‑ Eiríkr Útlendi │Tala við mig 03:26, 30 October 2017 (UTC)


This looks pretty cool.

One concern -- the "nn" spelling. That is unusual, and unexpected as a romanization spelling. Would you object to moving this to Template:ja-kana-manyogana-etym with one n? ‑‑ Eiríkr Útlendi │Tala við mig 15:49, 23 October 2017 (UTC)

Not really. I think I was thinking in waapuro romaji at the time. —suzukaze (tc) 19:29, 23 October 2017 (UTC)
(why not man'yogana? —suzukaze (tc) 19:37, 23 October 2017 (UTC))
I'm open to including the apostrophe. I had come by the thought somewhere that apostrophes weren't allowed in template names? If that's not an issue, sure. ‑‑ Eiríkr Útlendi │Tala við mig 19:45, 23 October 2017 (UTC)
It seems like it's OK. en.wp has a template named '. —suzukaze (tc) 19:51, 23 October 2017 (UTC)
I think whatever works in entry names also works in template names. — Eru·tuon 21:42, 23 October 2017 (UTC)

Links in usage examplesEdit

"Unusual"? There's a problem with the linking within the usage example, so my preference is to link the romanized parameter so the terms within the ll template go directly to the respective language heading. For comparison: before your revision, your revision after that

Tried using on the usage itself, but there are "escaped" links or something. --POKéTalker (talk) 03:46, 1 November 2017 (UTC)

Ah, I see. I hadn't noticed that the #Japanese anchor was missing, my bad. I do think it is unusual to have links in the romanization instead of in the original text; I don't think I've seen it before in our entries. I believe this shouldn't be hard to fix, although I haven't had the time to fix things lately. Instead, I shall call on @Erutuon. —suzukaze (tc) 03:57, 1 November 2017 (UTC)
I ran the ruby through the language_link function in Module:links if it contains double brackets; that sends the links to the Japanese header. Till now, the ruby was just being language-tagged and nothing more. —This unsigned comment was added by Erutuon (talkcontribs).


Hi. Any ideas about including 文語 forms for Japanese terms? Seen a lot of them in Japanese dictionaries. Perhaps the headword template of Japanese verbs and adjectives can give the classical conjugation, and the shuushikei if it is different from the modern form in hhira, and the conjugation/declension tables could be extended to include the six bases of the classical form? @Eirikr --Dine2016 (talk) 05:49, 8 November 2017 (UTC)

I think that would be fantastic. Honestly I really think our current conjugation tables aren't helpful (I certainly don't use them) and need some sort of overhaul in general. I am hesitant about working on stuff like this though; I didn't learn Japanese conventionally, and I suspect many of my views regarding grammar are really weird. Japanese grammar from the Japanese point-of-view is also not something I'm that familiar with (I think that's why I don't like the current conjugation tables). —suzukaze (tc) 06:35, 8 November 2017 (UTC)
  • I think it would make more sense to figure out how to represent Classical Japanese, which is what 文語形 essentially is. The hhira parameter is intended to express the historical kana spelling of the headword; using that to show the kana spelling of something other than the headword would be very confusing. And to clarify, the historical kana is the pre-reform spelling of the same form of the same word. Modern 匂う (niou) is spelled におう (niou) in the modern spelling, and にほふ (nihofu) in the pre-reform spelling, although both were pronounced as niou in recent history. Meanwhile, modern 付ける (tsukeru, to stick one thing onto another thing; to turn something on, transitive) has the same kana spelling in both modern and pre-reform orthography, and a Classical Japanese form of 付く (tsuku), identical to the modern intransitive verb -- the transitive and intransitive were differentiated by conjugation patterns. Adding the Classical to the hhira of modern 付ける (tsukeru) would be highly confusing.
I'm completely supportive of building in Classical Japanese content. It's just not compatible with our modern Japanese infrastructure, and it's different enough that we should probably treat it separately. We have lang code ojp for Old Japanese, which I'd also like to see built out at some point, but so far as I know, Classical Japanese has no ISO language code. Can we create our own code for Classical Japanese and go from there? ‑‑ Eiríkr Útlendi │Tala við mig 06:42, 8 November 2017 (UTC)
PS: I'm in agreement that our conjugation tables could use reworking. ‑‑ Eiríkr Útlendi │Tala við mig 06:52, 8 November 2017 (UTC)
(Sorry for the misunderstanding in my post above. I was aware that modern form, modern form in historical spelling, and classical form are three things, and I meant to include the third, e.g. たずねる―たづねる―たづぬ, if it is different from the second, not put the third in the place of the second. I should have checked the grammar before posting it.) --Dine2016 (talk) 13:01, 8 November 2017 (UTC)

If you want a head start, 紅葉つ (momitsu) and 紅葉ず (momizu), classical verb forms of 紅葉 (momichi, momiji), have been created a long time ago. Do they have to be under the Old/Classical Japanese header? --POKéTalker (talk) 21:00, 9 November 2017 (UTC)

  • My 2p is on "yes" -- momitsu is listed as 四段活用, which is not modern, and momizu is described as 上二段, also not modern, as an innovation on momitsu that arose some time in the early Heian, maybe later (「平安初期以後上二段化し...」). Shogakukan's 国語大辞典 lists two spellings for momizu, and neither is listed on Weblio, suggesting that the verb is obsolete: 紅葉ず, and 黄葉ず. OJP is sometimes delineated as everything before the Heian, which would suggest that momizu would be Classical and not Old. Then again, w:Old Japanese says the transition was some time during the Heian, suggesting that momizu could be classed as Old Japanese.
That said, we only have limited infrastructure for OJP, and we don't have any infrastructure at all for Classical -- until such time as we have somewhere more specific to put momitsu and momizu, I have no strong objection if they stay under a ==Japanese== header for the time being.
My bigger concern, as relates to this whole idea of building out our Classical Japanese content, is how to delineate between Classical Japanese, and Old Japanese? If we can narrow down a term's etymological details to show that the term only arose in the Muromachi, for example, then that's clearly not OJP. But if a term is attested in OJP, and also in later stages of the language, do we include it in all three (Old, Classical, modern)? ‑‑ Eiríkr Útlendi │Tala við mig 22:18, 9 November 2017 (UTC)


Why was my edit to this word reversed? Johnnysama (talk) 15:57, 16 November 2017 (UTC)

@Johnnysama: My guess (since I'm not Suzukaze) is that he objected to your removal of the count/noncount distinction. 精液 in Japanese is not countable, so it has no counter. The count=- text that you removed specifies that this term is not countable and has no counter. This is useful and correct information, and your removal of this information made the entry less useful and less correct.
HTH, ‑‑ Eiríkr Útlendi │Tala við mig 20:34, 16 November 2017 (UTC)
Eiríkrさんのおっしゃる通りです。—suzukaze (tc) 04:34, 18 November 2017 (UTC)


Hi Suzukaze - I see you reverted my added pron. for 莫. To tell you the truth, it was my first time at making an edit to a Chinese page, so perhaps I did not do the right thing. However, I do believe this character is pronounced mài in Hokkien in Singapore (and is apparently an old-fashioned pronunciation in Taiwan as well). Is there some way that info can be added? - Sonofcawdrey (talk) 05:15, 20 November 2017 (UTC)

Read my edit summary. —suzukaze (tc) 05:29, 20 November 2017 (UTC)
Ah all is clear. Sorry to have caused you an unnecessary tidy-up.- Sonofcawdrey (talk) 07:35, 21 November 2017 (UTC)


I noticed your recent edit to restore withtext.

My understanding was that both notext and withtext were slated for removal. I think notext was already removed, and withtext is deprecated. C.f. [[Wiktionary:Beer_parlour#Template:bor:_Replace_notext=1_with_withtext=1]]. Is there a reason to use withtext that I've missed?

Curious, ‑‑ Eiríkr Útlendi │Tala við mig 21:18, 3 December 2017 (UTC)

Oh, huh. Man, this is confusing. —suzukaze (tc) 21:22, 3 December 2017 (UTC)

JA い-adjective く formsEdit

Would something like this be acceptable to you? く forms are really more adverbs than adjectives, much like EN -ly forms. What do you think? ‑‑ Eiríkr Útlendi │Tala við mig 22:24, 18 December 2017 (UTC)

Sure. (I was thinking about it too.) —suzukaze (tc) 22:31, 18 December 2017 (UTC)

@Eirikr: I think it needs to still be categorized as an adjective form somehow. It is an adverb, but it is ultimately derived from an adjective, similar to things like eating#Verbeating#Noun. —Suzukaze-c 04:28, 4 May 2018 (UTC)

Um, I can't agree.
English quickly is an adverb, and it is definitively not an adjective. Same with Japanese なく. Both are ultimately derived from adjectives, but they themselves are not treated as adjectives and should not be categorized as adjectives.
The eating example is a non-sequitur: eating is neither an adverb, nor derived from an adjective. This is a manifestation of a separate grammatical construct altogether, and eating is both the present participle (i.e. verb form) and gerund (i.e. noun). By contrast, なく (the one from ない) is just an adverb: it is not an adjective, verb form, noun, etc. but only an adverb.
I would be supportive of adding an ===Etymology=== section or additional verbiage to further clarify that this is derived from the adjective ない. Would that work for you? ‑‑ Eiríkr Útlendi │Tala við mig 16:53, 4 May 2018 (UTC)
There is definitely value in keeping the adverb category; I am not saying that "Japanese adverbs" should be removed. But ~く is used in the construction of other forms like ~くない and ~くて, so I see value in including an adjective section as well.
I suppose an etymology section could be added but I think that {{inflection of}} is sufficient. —Suzukaze-c 18:37, 4 May 2018 (UTC)
Re: construction of other forms, granted. However, these can be analysed either as integral forms (how they're often presented to Japanese-as-a-foreign-language learners), or as adverbial ~く + additional endings.
I'm still unclear on what an "adjective" heading would be for. Again, this く form does not function as an adjective. If we're viewing terms analytically and decomposing to smaller units, [ADJ STEM] + く is still adverbial, with ~ない and ~て attaching to that. If we're looking at bigger pieces more synthetically as integral forms, then [ADJ STEM] + くて or [ADJ STEM] + くない would be the entries with their own headers, and [ADJ STEM] + く would be yet another entry, with the latter clearly -- and only -- an adverb. It might well be translated as an adjective when going into other languages (such as when using the く form at the end of a clause as a kind of conjunction, but without the て), but that is a function of the grammar of the target language, and not a reflection of how the form functions in Japanese.
Also, all three of the links to Weblio describe the く form as the 連用形. This form (形) can only attach (連) to another inflecting word (用語), and the closest analog to this form of an adjective, for purposes of describing the grammar in English, is the "adverb".
I guess ultimately I'm confused how these would be adjectives, and I'm worried that other readers would be similarly confused. ‑‑ Eiríkr Útlendi │Tala við mig 19:18, 4 May 2018 (UTC)
I thought about く + ない and く + て but I'm not really aware of scholarly analysis of grammar, and I found it hard to interpret く + て as adverb + ??.
I'm not saying that it is an adjective either; just that it is an inflected form of an adjective, and should be categorized as such. It's funny how you oppose an "Adjective" header because it might confuse readers as to how it is used, while I was thinking about adding "Adjective" in case readers would wonder how 赤い#Adjective赤く#Adverb works. (yeah, I didn't mention this before...)
Maybe I'm worrying too hard about this, and maybe I'm out of my depth. You mentioned "ADJ STEM", and I realized that I would probably be more accepting of having only an adverb section (akaku#Adverb) if we had entries for aka#Adjective stem (and thus aka#Adjective).
At this point in time I don't really care that much about it, and you know more about it than me, so I shall leave it alone.
(mostly-unrelated question: are things like わからない and 赤くない regarded as adjectives or verbs?) —Suzukaze-c 02:23, 7 May 2018 (UTC)

「 」Edit

I see you removed "Encloses a character sequence that is supposed to represent a single character" from 「 」. Do you think that sense does not actually exist, or maybe that it is not citable? I realize it's usually hard to find quotes on Google Books for punctuation marks. --Daniel Carrero (talk) 06:21, 26 December 2017 (UTC)

Not sure it's citable. Probably just an offhand way of noting that character A and character B are supposed to be grouped together. —suzukaze (tc) 06:25, 26 December 2017 (UTC)
I remember seeing them used like this, but it's mostly online, so it's not that easy to cite. — justin(r)leung (t...) | c=› } 07:50, 26 December 2017 (UTC)

Category:Han characters needing common meaningsEdit

Can this category be cleared?--2001:DA8:201:3512:55FD:63A0:5A07:6206 07:21, 26 December 2017 (UTC)

Not sure. I think our hanzi entries are weird, and when I think about the topic it gets complicated. —suzukaze (tc) 07:28, 26 December 2017 (UTC)
Common meanings are going to be phased out. I think this template no longer have purposes as definition should be added to appropriate language sections.--Zcreator (talk) 12:01, 2 January 2018 (UTC)
Bumping it again. It is no longer preferred to add any definitions to translingual section and current contents in translingual section is being migrated. So I don't think this serves any use (rfdef template in Chinese section is enough). Also, it is three months since the proposal for deletion of this category.--Zcreator (talk) 17:39, 22 January 2018 (UTC)
It is certainly no longer preferred, but I worry about the quality and formatting of the pre-existing definitions, like . —suzukaze (tc) 18:02, 22 January 2018 (UTC)
If it is no longer preferred, we don't need to add or request it anymore; cleaning pre-existing definitions is another thing. What I request is remove {{defn|Han|sort=...}} from pages in the category, which displays the text "This term needs a translation to English." in the translingual section.--Zcreator (talk) 12:15, 23 January 2018 (UTC)
Ahh, sorry, I forgot what the original proposal was. Yes, I think we can probably get rid of most of them. But what do we do about characters that don't have any other language sections besides Translingual? —suzukaze (tc) 18:05, 23 January 2018 (UTC)
If the character have some meaning, they should almost always be added to appropriate language sections (which may be created if needed). Having defn in translingual instead encourage people to add definitions to translingual section.--Zcreator (talk) 18:18, 23 January 2018 (UTC)
That's true. But then we need to think of another way to keep track of those characters. —suzukaze (tc) 18:20, 23 January 2018 (UTC)
They are now tracked in Special:WhatLinksHere/Template:tracking/zh-han/translingual-only_character.--Zcreator (talk) 18:40, 23 January 2018 (UTC)
Nice. —suzukaze (tc) 18:52, 23 January 2018 (UTC)
Is it ready to be cleared?--Zcreator (talk) 20:41, 25 January 2018 (UTC)
I suppose so. —suzukaze (tc) 20:48, 25 January 2018 (UTC)


There'd been some discussion a while back about having entries for historical spellings. I think せう was created as part of an earlier effort towards that same end; looking at the history, I revamped it in May 2016, likely after our more-recent discussions.

If we are to have entries for historical spellings, then the entry should be cleaned up somewhat to more clearly redirect users to the modern spelling しょう.

If we are not to have entries for historical spellings, we should probably have a broader discussion on that to gain consensus, and then delink hhira and hkata spellings in headlines. ‑‑ Eiríkr Útlendi │Tala við mig 20:10, 27 December 2017 (UTC)

I marked it for deletion as part of the WT:RFDO discussion for {{ja-kanji reading}}, and because it had no actual definitions. (I think people should go to Wikipedia for such detailed information on the evolution from seu > shou). I think that if it is to be kept, it should be as an entry that concisely points to shou, with some header other than Usage notes. —suzukaze (tc) 01:27, 28 December 2017 (UTC)
Helpful resource → KSound link. Please refer to the link, the list of historical readings derived from Middle Chinese. From there, it is possible to list the kanji with that historical spelling/pronunciation. What do you think? How about an appendix extending the KSound? --POKéTalker (talk) 02:13, 3 January 2018 (UTC)


Hey! Please let me know what you think of the page I made about 𡿺! Thanks for your tireless work.--Geographyinitiative (talk) 13:38, 1 January 2018 (UTC)

It seems like Justin has already looked at it, so I don't really have any comment other than I like your work too. —suzukaze (tc) 03:45, 8 January 2018 (UTC)


Why the reversion? It is the Chinese Wikipedia, and not just any Wikipedia, and that dot before the word on the other template looks weird to me. PseudoSkull (talk) 21:22, 30 January 2018 (UTC)

The dot is a bullet.
{{zh-wp}} is different from the normal {{wikipedia}} template, but I think it is necessary. See 中國 for an example. —suzukaze (tc) 23:21, 30 January 2018 (UTC)
Ok, that makes sense. PseudoSkull (talk) 07:07, 31 January 2018 (UTC)


I was wondering where you got the Chinese pronunciation of 𭒹 from? Johnkn63 (talk) 04:52, 11 February 2018 (UTC)

@Johnkn63: It comes from the Zhonghua Zihai. —suzukaze (tc) 06:05, 11 February 2018 (UTC)
Thank you very much for a quick and clear answer. I asked because only pronunciation given.Johnkn63 (talk) 09:33, 11 February 2018 (UTC)

Grammar for 鬱#Japanese adjectiveEdit

My references all list this as a と・たる adjective, not a な adjective. C.f. the Daijirin entry at Weblio and the Daijisen entry at Kotobank. Examples of 鬱な気分 found via Google mostly seem to be cases of 憂鬱な気分. Can you confirm usage of 鬱な where it's not part of a larger compound? ‑‑ Eiríkr Útlendi │Tala við mig 05:39, 19 February 2018 (UTC)

I wonder if it's a colloquial thing. These Google News results seem to have 鬱な気分. —suzukaze (tc) 05:47, 19 February 2018 (UTC)
Thank you! I suspect this is a literary term that is now making (or has recently made?) the transition back into common vernacular use, with a grammatical change as part of that process.
I feel like we should note that this is also a と・たる adjective... but I don't think we have the templates for that, as classical stuff and rare grammar patterns keep getting back-burnered. :) ‑‑ Eiríkr Útlendi │Tala við mig 07:06, 19 February 2018 (UTC)


Hello. You said in an edit summary at moon rune, "reddit is not a source of quotes". I am curious about why. I actually don't know much about Reddit, but I had imagined that it is something like 'alt' spaces were in usenet – a basically open forum where people share messages. Is Reddit not durably archived? or does it have in-group language norms that make it problematic for examples? Just curious. Cnilep (talk) 00:37, 15 March 2018 (UTC)

I don't think Reddit is durably archived. (Honestly, I think the "durably archived" criteria is out of touch with the current state of the internet...) —suzukaze (tc) 00:51, 15 March 2018 (UTC)
Reddit comments can be (and are frequently) deleted by their creators, by moderators, or by site administration. Sometimes entire communities are banned or locked off from public view. In those cases, it becomes impossible to verify that someone said something on Reddit unless recorded on another website. Now, we can (and possibly should) broaden the "durably archived" criterion, but including Reddit directly is not the way to go about it. —Μετάknowledgediscuss/deeds 02:27, 15 March 2018 (UTC)

'full=' in ja-verb-suruEdit

Hello. The documentation at Template:ja-verb-suru/documentation says, “full= full form with the suru included ¶ This parameter is required.” It appears, though, that the template works well without that parameter. Should the documentation be changed? Cnilep (talk) 01:43, 5 April 2018 (UTC)

"full" doesn't exist in Module:ja-headword, the code that powers Template:ja-verb-suru. I think it is outdated documentation. —suzukaze (tc) 02:55, 5 April 2018 (UTC)



Do you have another source for Min Bei? --Anatoli T. (обсудить/вклад) 03:23, 17 April 2018 (UTC)

@Atitarev: I personally don't, but it seems to me like nêng belongs to 人#Etymology_2, not 人#Etymology_1. I don't think we are in any hurry to add Min Bei pronunciation to words that we don't have information for, even if it a word like 中國. I'm not really a fan of blindly concatenating readings. —Suzukaze-c 03:27, 17 April 2018 (UTC)
I got the transliteration from Min Bei incubator, apparently an enthusiast of Min Bei. The Min Bei (Jian'ou) pronunciation of (nêng) is /neiŋ³³/, I don't see any discrepancy here. --Anatoli T. (обсудить/вклад) 03:32, 17 April 2018 (UTC)
Nêng is a reading of 人, which is corroborated by 漢字古今音資料庫 and this excerpt of Matthew in the New Testament, but it strikes me as too similar to 人#Etymology_2.
Of course, it is possible that I am wrong too, and that nêng really is part of 人#Etymology_1. —Suzukaze-c 03:37, 17 April 2018 (UTC)
I can only see one Min Bei reading - "nêng" and /neiŋ³³/ is the only reading listed there under the "Dialectal data" in the expanded mode. I've added "nêng" to etymology 1. --Anatoli T. (обсудить/вклад) 03:42, 17 April 2018 (UTC)
Nêng is actually etymology 1. Compare other characters with the same rime (Min Bei / Min Nan): 親 (chéng / chhin), 認 (nēng / jīn). Min Bei is inland Min, not coastal Min, so it's lexically quite different from Min Nan, Min Dong, or Puxian Min. — justin(r)leung (t...) | c=› } 07:37, 17 April 2018 (UTC)
Alright, thanks for clearing that up. The initial threw me off a lot. I guess I was indeed wrong :o —Suzukaze-c 07:43, 17 April 2018 (UTC)
Min Bei initials are kinda weird, but this is just a mild case. There are weirder ones, like 狗 (ě), 食 (iè) or 老 (sē). My bigger concern for 中華人民共和國 and 中國 is the fact that dô̤ng is a vernacular reading, which I can only find in 中央 at this point. I've left a message at @唐吉訶德的侍從's page on Wikipedia, so hopefully we can get an answer on this. — justin(r)leung (t...) | c=› } 19:40, 17 April 2018 (UTC)
(I wonder if we can invite more editors from China by infiltrating their QQ/Wechat/whatever groups...?) —Suzukaze-c 21:10, 17 April 2018 (UTC)

Katakana in ja-usexEdit

Hello. Regarding this edit, notice that without the duplicate kana the '''bolded''' word doesn't appear in bold face. At least, it doesn't in my browser. Also, タイヤ should be in katakana. It seems like the bold face works if there is カナ|かな in the template, but not if there is only one kana entry. I'm not sure if this is a technical snafu. Cnilep (talk) 03:43, 18 April 2018 (UTC)

I didn't notice that たいや was in hiragana orz
The font thing should be fixed! —Suzukaze-c 03:53, 18 April 2018 (UTC)
Now the bold face looks fine. I wonder if it's a browser issue? Any road, thanks for your edits. Cnilep (talk) 04:02, 18 April 2018 (UTC)


Hello! I have created a page that has a problem I can't fix on it: 烟店. The page reads: "For pronunciation and definitions of 烟店 – see 煙店 (“[[w:Yandian, Hubei; etc.”)."

It shouldn't say "(“[[w:Yandian, Hubei; etc.”)", it should say "(“Yandian, Hubei; etc.”)" or something like that.

How can I fix this problem? Thanks for any assistance! --Geographyinitiative (talk) 01:18, 21 April 2018 (UTC)

It has to do with some of the code in Module:zh but I'm not sure how to fix it. —Suzukaze-c 22:16, 22 April 2018 (UTC)
(In Perl notation) \{\{place\|zh\|[^\}]*t=((?:[^\n\}\|\[]|\[\[.+?\]\])+)[^\}]*\}\} apparently works. The point is to match the part after t= in a way that accepts (one-or-more) not only single characters but also clusters beginning with [[ and ending with ]] so that inner pipes will be regarded as part of the cluster and skipped. --Dine2016 (talk) 06:15, 23 April 2018 (UTC)
Sadly, Lua implements a crippled subset of regex they call "patterns". :( Thanks for looking at it though. @Zcreator alt, any ideas? —Suzukaze-c 19:12, 23 April 2018 (UTC)

鴯鶓 spellingEdit

Heya, this is getting complex enough that a proper discussion thread is in order. :)

I thought I'd read somewhere about this spelling reaching JA via CMN rather than YUE. I can't find that now that I'm looking for it again, so perhaps it would actually be better to leave out any mention of which flavor of Chinese was the source.

The Mandarin connection was from the pronunciation. Modern Cantonese is quite close to one of the expected on'yomi readings, so if this were borrowed from Cantonese, we would probably expect the on'yomi. But there's no Cantonese or Japanese reason for pronouncing as e -- only Mandarin provides any such direction.

However, I sure can't find where I'd read that. Thank you for prompting me to dig into that again. For now, would you be open to going back to your earlier version? ‑‑ Eiríkr Útlendi │Tala við mig 20:18, 2 May 2018 (UTC)

I think it is fairly plausible that English /ˈiːmjuː/ became Cantonese /jiː²¹ miːu̯²¹/, c.f. (M. /ˀɤɻ³⁵/, C. /jiː²¹/) and (M. /mi̯ɑʊ̯³⁵/, C. /miːu̯²¹/).
And IMO it is irrelevant anyway, since JA took the hanzi from Chinese in general, and the pronunciation from English. —Suzukaze-c 23:00, 2 May 2018 (UTC)
Re: EN → ZH, no real argument there. My earlier concern was due to confusion on my part, that Jyutping ji indicated an English-y "j" more like /d͡ʒi/, rather than an English-y "y" like /ji/. /d͡ʒi/ would align with JA じ, as the expected on'yomi.
Anyway, as you point out, the ZH reading is largely irrelevant anyway, so I removed that and essentially restored your earlier version. Thank you for the sanity check. :) ‑‑ Eiríkr Útlendi │Tala við mig 19:25, 4 May 2018 (UTC)


I don't mind the revert, but maybe you could edit it into one, concise sentence? ---> Tooironic (talk) 04:41, 7 May 2018 (UTC)

When I made the entry I already tried to make it short (;´Д`) I'm not quite sure what to do with it. I'd prefer to point to Wikipedia or an English entry or something, but that doesn't seem to be an option. —Suzukaze-c 04:45, 7 May 2018 (UTC)
The definition given by the Taiwan MoE is also pretty long anyway. —Suzukaze-c 04:49, 7 May 2018 (UTC)


I'm not really up to speed on Lua, but it looks like you passed the wrong parameter to the new function. At any rate, the Japanese entries in CAT:E and the Japanese Type-1 verbs were rapidly approaching identity- so I temporarily reverted you until you have a chance to look at it. Feel free to undo my undo once fixed. Chuck Entz (talk) 05:11, 14 May 2018 (UTC)

Darn. I think I've fixed it. —Suzukaze-c 05:18, 14 May 2018 (UTC)
The module errors are going away, at least. I wouldn't know if the code is actually doing anything... I haven't been checking CAT:E much, lately, but I seem to have picked a good time: there were a couple hundred module errors from work Wyang was doing on the Korean modules, so the Japanese ones weren't on the first page where anyone would have seen them. All the Korean ones are gone now, and half of the Japanese ones (so far). Much better. Thanks! Chuck Entz (talk) 05:54, 14 May 2018 (UTC)
No, thank you for remembering to check CAT:E :) —Suzukaze-c 06:16, 14 May 2018 (UTC)


My personal theory is that they just can't wait to try out their favorite small shiny objects templates and labels, and throw them in everywhere they can think of. Chuck Entz (talk) 03:44, 22 May 2018 (UTC)

ポケット and ポケモンEdit

Of course there is no devoicing. What a silly mistake. The appropriate transcriptions should be [po̞ke̞t̚to̞] and [po̞ke̞mõ̞ɴ] respectively, and I readded the proper transcription for the latter page. I'm kind of new here so I'm still getting used to the {{ja-pron}} template parameters... Sorry about that. — Lucarubis (talk) 00:16, 25 May 2018 (UTC)

Make sure you understand what the parameters mean, because you also copied improper parameters to ポケモン. :p —Suzukaze-c 00:25, 25 May 2018 (UTC)
I understand, but it was an accident. Sincere apologies for my utter carelessness. —Lucarubis (talk) 00:27, 25 May 2018 (UTC)
I've been creating more pages lately out of sheer boredom. I just hope I don't screw things up again. In the meantime, I'll be on the lookout for vandalism. —Lucarubis (talk) 00:23, 28 May 2018 (UTC)


Sorry to bother you again, but I have one random question. Is any one here proficient in Dungan? —Lucarubis (talk) 00:23, 28 May 2018 (UTC)

@Lucarubis: There's no-one here proficient in Dungan. We use dictionaries and other sources we consider reliable. So, if your edit in diff can't be confirmed in dictionaries or other good sources, it must be removed. --Anatoli T. (обсудить/вклад) 00:28, 28 May 2018 (UTC)
I have a feeling the tones I provided in 韓國 are incorrect, but not the readings. I'll remove it anyway. --Lucarubis (talk) 00:30, 28 May 2018 (UTC)
@Lucarubis: The trouble is, Dungan may not even have a word for Korea, other than Чощян (Čoxi͡an) - 朝鮮朝鲜 (Cháoxiǎn). --Anatoli T. (обсудить/вклад) 01:04, 28 May 2018 (UTC)

Chinese Characters for Transcribing SlavonicEdit

Hello, I have had some questions regarding the Chinese characters for transcribing Slavonic. Do you feel it would be alright to include their pronunciation (eg. 鿦 shows pronunciation as vin, 鿚 shows pronunciation as gi, etc.)? —This unsigned comment was added by (talk).

鿚 represents gi, but I wonder if gi is actually the pronunciation? (were they read using original Slavic pronunciation, were they read using a Chinese approximation...?) (鿚 = gi is definitely important information.) —Suzukaze-c 21:54, 22 June 2018 (UTC)


  Hello, Suzukaze-c. You have new messages at MediaWiki talk:Common.css#Japanese uses MS PGothic but it should use Meiryo.
You can remove this notice at any time by removing the {{talkback}} template.

-- 20:51, 4 July 2018 (UTC)

Hakka pronunciations for Malaysian place namesEdit

I'm wondering where you're getting these. We have really limited support for Hakka dialects - just Sixian and Meixian. — justin(r)leung (t...) | c=› } 19:15, 17 July 2018 (UTC)

I stumbled across "Hakka Lessons for Malayan Students" on Google Books. I am not sure what dialect it describes though. It's not easy to figure things out from 6-line snippets... —Suzukaze-c 19:23, 17 July 2018 (UTC)
Whichever it's describing is definitely not Sixian, which is only spoken in Taiwan. I've removed the reading at 新埠 for now. — justin(r)leung (t...) | c=› } 19:33, 17 July 2018 (UTC)
This says that it's Huizhou Hakka, which seems to be common in Malaysia. — justin(r)leung (t...) | c=› } 19:35, 17 July 2018 (UTC)
Oh, cool. —Suzukaze-c 19:36, 17 July 2018 (UTC)
It looks like Mantaro Hashimoto says it is the Meixian dialect. —Suzukaze-c 05:21, 18 July 2018 (UTC)

Use of Template:bor for on'yomi termsEdit

I think it was you that (I noticed) first started using {{bor}} for the etyms of on'yomi terms. Fumiko has decided to be a dick again over at 女性, here, and here. (I've blocked her for three days for abusiveness and edit warring.) I have read the documentation, and it looks to me like {{bor}} could apply -- especially as we haven't differentiated the historical stages of the Japanese language.

What's your take?

‑‑ Eiríkr Útlendi │Tala við mig 01:29, 24 July 2018 (UTC)

Hmm, was it me? I tend to not add the etymology for kango (can't be too sure...). At this very moment in time, near the end of July 2018, I think would use {{der|ja|ltc}} for kango???? I'm not sure though. I can be inconsistent with the things I do when I don't have a terribly strong opinion either way. {{bor}} absolutely makes sense too, and I disagree very much with Fumiko's dickish behavior. —Suzukaze-c 04:03, 24 July 2018 (UTC)
@Eirikr: Fumiko is a she? Per utramque cavernam 20:39, 2 November 2018 (UTC)
@Per utramque cavernam: IRL, dunno. Trying out {{User gender}} returns -, which apparently means that the user hasn't set any gender preferences. That said, Fumiko is definitely a feminine name, and in a since-deleted post, Fumiko stated that the username was a near-translation into Japanese of their real-life name. Based on that, I use the feminine gender when referring to this user. If Fumiko ever states a different preference, I'm happy to follow suit. ‑‑ Eiríkr Útlendi │Tala við mig 20:52, 2 November 2018 (UTC)
Ok, I see. Per utramque cavernam 21:02, 2 November 2018 (UTC)

Technical issue with Template:zh-seeEdit

Hey suzukaze,

I'm seeing instances of the {{zh-see}} template showing "tr=-" text for unknown reasons, sometimes after valid linked words are shown. I figured you might know more about template issues than I do. Cheers! Bumm13 (talk) 14:46, 17 August 2018 (UTC)

@Bumm13: Do you have an example? —Suzukaze-c 20:35, 17 August 2018 (UTC)
Finally found it. Here at 𧈡. Bumm13 (talk) 21:34, 17 August 2018 (UTC)
It seems to be faulty processing of {{zh-alt-form|早|tr=-}}. I think I've fixed it. —Suzukaze-c 21:59, 17 August 2018 (UTC)

{{nonlemma}} non-optimalEdit

I noticed in one of your recent edits that you are adding {{nonlemma}} for alternative forms. That itself is fine, and no concerns from me. What is a concern, however, is the confusing format and output of this template. It says,

See etymology on the main entry.

... which links not to the main entry, as suggested by the format, but instead to Wiktionary:Lemmas, which I think will confuse many users. It's not immediately clear at all even what the "main entry" would be.

I'd like to propose updating {{nonlemma}} to, say, take the actual "main entry" term as an argument, and output a link? For the 苟且 (karisome) entry, it would then look more like:


Would you have any objection?

‑‑ Eiríkr Útlendi │Tala við mig 20:31, 24 August 2018 (UTC)

I agree that the link is misleading. I guess the main entry is already linked to in the rest of the entry though. —Suzukaze-c 20:37, 24 August 2018 (UTC)

Wikipedia has an article on:Edit

For and a hundred other articles, I added the template zh-wp which links to Chinese wikipedia. Although the content of the 不 article was not really related to the senses of 不 discussed on wiktionary, I thought that 1、不 is inherently related to 不 no matter the content in the articles and 2、"Wikipedia has an article on: 不" was a factual statement. I agree with your reservations and was hesitant to add the link, but for the two reasons stated above, I added it anyway. I'm not really too concerned either way; if you don't like some of the other zh-wp's I added, let me know. I will try to follow whatever established pattern or policy on relevance that we have. Also, let me know what you think of the pics I added. --Geographyinitiative (talk) 13:12, 1 September 2018 (UTC)

It's not related to any of the senses on the page though... If I see a link on Wiktionary saying "Chinese Wikipedia: 不", I might expect something on negative particles, not a South African song. IMO, it looks silly. —Suzukaze-c 00:18, 2 September 2018 (UTC)
The point of the Wikipedia links is to provide a source for encyclopedic information that doesn't belong in a dictionary. If the Wikipedia article doesn't elaborate on what the definitions refer to, it shouldn't be linked to from the entry. Chuck Entz (talk) 03:54, 2 September 2018 (UTC)
I understand your points completely. I agree the link looked silly. I see now that a link to a wikipedia article is only appropriate if the wikipedia article being linked 'elaborates on what the wiktionary definitions refer to'. I will only add these links if there is a connection between the wiktionary definitions and the content of the wikipedia article. --Geographyinitiative (talk) 11:17, 2 September 2018 (UTC)


I could explain my rationale for not creating that page, but it would sound silly. Looks fine. --Geographyinitiative (talk) 01:25, 3 September 2018 (UTC)

? It could be possible, although Wikipedia seems to be fine with 葉, and 葉 makes more sense semantically as well. I suppose it would also be normalized into 協 in simplified Chinese, as well. Being too cautious isn't bad though. —Suzukaze-c 01:29, 3 September 2018 (UTC)

Audio display issue with Template:zh-pronEdit

Not sure if you saw the ping on Discord, so I thought I'd leave you a message. Seeing as this isn't going to be dealt with any time soon, is there a stopgap measure that can be employed? Weirdly excessive spacing for some people is preferable to IPA being obscured by an audiofile for other people. —Μετάknowledgediscuss/deeds 04:02, 11 September 2018 (UTC)

Module:User:Suzukaze-c/zh-pron#non-template_model has a "fix" but it's weird and I don't know if it works in all browsers. I suppose it could be added to the live code if people determine that it's an OK hack. I can't figure out why the original audio player thing acts so terribly. —Suzukaze-c 04:14, 11 September 2018 (UTC)
It works on both Chrome and Safari for me (the current template works on neither for me). I think it's a vast improvement, but you'll have to poll the Chinese editorship before going live. —Μετάknowledgediscuss/deeds 04:26, 11 September 2018 (UTC)

Pinging @Wyang, Justinrleung, KevinUp. —Suzukaze-c 21:58, 11 September 2018 (UTC)

The suggested fix looks good to me. I like how compact the MC and OC readings look. It may be slightly cumbersome to click on a particular arrow to reveal its IPA reading/audio file but I think it is a good stopgap measure we can use for the time being. I suggest we put it live for a few days to see if there are any potential hiccups with it. KevinUp (talk) 00:06, 12 September 2018 (UTC)
Is this for the audio only or for the whole template? The non-template model at present seems a bit 單調 to me. If we want to overhaul the template, I really like this. Wyang (talk) 00:49, 12 September 2018 (UTC)
Just the audio, using the <div> around the [[File: element. Ignore everything else. —Suzukaze-c 01:26, 12 September 2018 (UTC)
Ah okay, (don't know what it will look like but) certainly, any improvement would be good. Wyang (talk) 04:55, 12 September 2018 (UTC)
@Wyang The new model on codepen looks really nice. I hope it can interact with the "Visibility" function in the sidebar. --Dine2016 (talk) 05:04, 12 September 2018 (UTC)

  DoneSuzukaze-c 04:55, 12 September 2018 (UTC)


Hi. I'm a bit confused about your edit here. I've never seen three whole sentences used as a definition in a Chinese entry before. Is there a way we can use standard formatting here? ---> Tooironic (talk) 04:43, 12 September 2018 (UTC)

My answer is the same as last time. I'd definitely like to replace it with a short English translation (rather than an "explanation") if there was one. —Suzukaze-c 04:47, 12 September 2018 (UTC)
Yeah, sorry for bugging you again about it. I just happened to come across it on my watchlist. I thanked Frank for his edit. I think it's a good compromise. ---> Tooironic (talk) 12:52, 18 September 2018 (UTC)
No worries. I like the new revision too. —Suzukaze-c 17:05, 18 September 2018 (UTC)

Trimming Google urlsEdit

I noticed you did this at [[hooker]].

What part of the link to a highlighted page is superfluous?

Also, how do I prevent the occasional accidental display to users of parts of a google url? (I don't have an example handy.)

Even a less-than-definitive answer (a rule of thumb) would be useful. Thanks in advance. DCDuring (talk) 12:57, 15 September 2018 (UTC)

I try deleting everything that doesn't look necessary; at hooker, I have left what appears to be
  1. a book id,
  2. a page number, and
  3. a search query,
and it still works.
I'm not sure what you mean by "occasional display"... —Suzukaze-c 21:13, 15 September 2018 (UTC)
Accidental display would result from a space in the URL, which causes everything after the space to be interpreted as part of the caption. Normally they would be converted to %20 or + in the URL itself, but modern browsers will let you get away with nonstandard formatting, and sometimes a space will get introduced in the copy-pasting process. Chuck Entz (talk) 21:56, 15 September 2018 (UTC)
Thanks. I have successfully applied your heuristic at [[skeeve]] (first cite).
I have a live example of the "occasional display": the 1993 cite at [[skeeve]]. I recall that Ruakh once helped me with the problem, but I don't recall how. DCDuring (talk) 22:46, 15 September 2018 (UTC)
Ah, that problem. The quotation marks are not being recognized as part of the URL for whatever reason, so they must be manually percent-encoded into %22 ([6]). Compare to the URL for the Lou Cameron quote. —Suzukaze-c 23:06, 15 September 2018 (UTC)
Excellent. Thank you. I'll try to get that into my PROM. DCDuring (talk) 23:15, 15 September 2018 (UTC)


  • ゐ、ゑ and を are a large important part of the historical kana orthography. About 200 entries were in each newly created "history spelled with" category.
  • I have not yet come up with how to track historical わ. But this does not mean ゐ、ゑ、を should not be tracked. If you don't know either, do not obstruct others.

Huhu9001 (talk) 03:24, 23 September 2018 (UTC)

Maybe a start would be having the module look for a headword or pagename containing わ and historical hiragana containing は, though I assume that sometimes わ and は do not correspond so there would be false positives. (This search query gives partial results: hastemplate:"Module:ja-headword" insource:/\{\{ja-[^|}]+\|[^|}]*わ[^|}]*\|hhira=[^|}]*は/.) — Eru·tuon 03:58, 23 September 2018 (UTC)
To Eru: I think that is a good idea. Maybe we can find out some methods to also track きやう → きょう, しやう → しょう, etc. simultaneously. Huhu9001 (talk) 08:20, 24 September 2018 (UTC)
I've added an easy-to-test function in Module:ja-headword/sandbox and started a list of examples at Module:ja-headword/sandbox/testcases. Could you help by adding some more examples of sound changes and possible category titles? — Eru·tuon 18:26, 24 September 2018 (UTC)
I'd like to point out that, without additional user-provided information, it can be impossible to programmatically determine whether a given instance of しやう etc. is an earlier spelling of a modern monophthong. For example, the kana spelling of 仕様 (shiyō, specification) is now しよう, from earlier しやう. I may be wrong, but I don't think this term was ever read as monophthong /ɕʲoː/. ‑‑ Eiríkr Útlendi │Tala við mig 18:50, 24 September 2018 (UTC)
If I understand you right, that shouldn't be an issue, because the function is comparing the modern spelling to the historical one; it can't do anything if either one is absent. — Eru·tuon 19:03, 24 September 2018 (UTC)
Yes, given the modern spelling, it should be an easy task to “parse” or “regex match” the historical spelling using a table such as Historical kana orthography#Complete tables of differences. The only issue I see is when the modern and the historical differ too much, e.g. あおぐ(仰ぐ) vs. あふぐ. --Dine2016 (talk) 15:07, 25 September 2018 (UTC) [EDIT: there are also irregular changes like がくかう→がっこう、てんわう→てんのう, etc. --Dine2016 (talk) 14:58, 26 September 2018 (UTC)]
Thank you both, I believe that fully addresses my concern. ‑‑ Eiríkr Útlendi │Tala við mig 16:16, 25 September 2018 (UTC)

I have worked out a code for this issue in Module:User:Huhu9001/000. You can test it like this: {{#invoke:User:Huhu9001/000|test|おんみょうじ|おむやうじ}} (no longer available). @Dine2016 @Eirikr @Erutuon Huhu9001 (talk) 14:59, 31 December 2018 (UTC)

Hm, if you're confident that it works, I think it is fine. —Suzukaze-c 23:44, 31 December 2018 (UTC)
@Huhu9001: Hi. Thanks for your work. However, I have proposed to move the historical kana spellings from headword templates to {{ja-ks}}. The problem with headword templates is that you have to repeat the historical kana spelling if a word has multiple parts of speech. Centralizing spelling information makes maintenance easier and pages less error-prone. --Dine2016 (talk) 00:29, 1 January 2019 (UTC)
To Dine2016: The code is not specific to module:ja-headword. If they are moved to module:ja-spellings, it should work as well. Huhu9001 (talk) 04:50, 1 January 2019 (UTC)

Care to be an administrator?Edit

I saw a few of your subpages in the {{delete}} list and was surprised to discover that you were not yet an administrator. Would you like to be? - TheDaveRoss 18:14, 2 November 2018 (UTC)

Not really, no. It would definitely be more convenient for me in many ways, but I'm not interested in having the title. Thank you though. —Suzukaze-c 19:42, 2 November 2018 (UTC)
Go on, become one. I dare you. --Wonderfool Dec 2018 (talk) 21:51, 1 January 2019 (UTC)
You first, mate. ;) —Suzukaze-c 22:00, 1 January 2019 (UTC)
What- you want him to delete the Main Page again? Chuck Entz (talk) 00:48, 2 January 2019 (UTC)
Start the New Year right. —Suzukaze-c 01:17, 2 January 2019 (UTC)

Question concerning recent 隔音符號 editEdit

Hello! I saw your recent edit to the 隔音符號 page ([7]) in which you removed the text '1=to divide syllables' from the 'zh-forms' module. The practical effect of this change was to edit the definition of the '隔音' in '隔音符號' from 'to divide syllables' to 'soundproof; to separate syllables'. In my view, this edit seems like an obvious degradation of the page rather than an improvement, because the '隔音' in the word '隔音符號' has nothing to do with the 'soundproof' definition (as far as I am aware). In the past, User Wyang has made changes on other pages very similar to your edit on 隔音符號 that also left me utterly befuddled. I would like to ask you why you believe that this edit makes an improvement to the 隔音符號 page. My best guess is that your edit reflects a 由来已久的 wiktionary policy that I don't have a grasp on yet. Thanks for any help. Sorry to bother. --Geographyinitiative (talk) 05:12, 7 November 2018 (UTC)

Hm. Including "soundproof" could definitely be confusing, but I somehow like the idea of leaving {{zh-forms}} to naively show all definitions from an entry. I'm terrible at explaining things, but I think my opinion has to do with curiosity (hm, this word has multiple senses) and common sense (this word has multiple senses but it is probably "this one" anyway). I also like to avoid hardcoding things (maybe the text at 隔音符號 would become out-of-sync with and disagree with 隔音 someday). I don't think there's any official policy on this. —Suzukaze-c 05:45, 7 November 2018 (UTC)
I understand what you are saying, but how do you feel about the definition given for the 生 character as found in 謀生 on the 謀生 page? I will give further response later. --Geographyinitiative (talk) 09:49, 7 November 2018 (UTC)
I think have been persuaded by your argument. But I think what I want is the ability to tell people which definition of 生 is being used in 謀生 with the word 'livelihood', and which meaning of 采 is being employed when 采 is used in 興高采烈 ('spirit'). (I remember doing something like this with 幅員 too.) Maybe the box above the character isn't the right place to do this- maybe it needs to be in an 'etymology' section? --Geographyinitiative (talk) 11:29, 7 November 2018 (UTC)
After writing the above, I had a new opinion about the nature of 隔音 in 隔音符號- it's SOP?? --Geographyinitiative (talk) 11:37, 7 November 2018 (UTC) (modified)
I do not treat manual glosses for individual characters as harshly since there are a lot of definitions displayed, and they are not from our entries anyway. If I have any complaints, it is that manual glosses do not immediately look any different from the usual generic glosses.
I think the general consensus is that zh-forms for compounds generally makes Etymology sections refundant, cf. the recent deletion of {{zh-compound}}.
As for verb+noun phrases, I think it is more complicated. We have entries like 喝酒 不知道 好用 etc. which are arguably SoP, but there are no spaces in Chinese 🤷 This time I really can't explain why I suppose verb+noun entries, but I do. (不+x, not so much, for now, TBH) —Suzukaze-c 07:39, 8 November 2018 (UTC)
I was not able to understand what you were saying in your first paragraph about the manual glosses and generic glosses. I think I know what those terms mean, but in my understanding, a manual gloss for an individual character would likely have only one or only a few definitions displayed (not 'a lot of definitions'), while the generic glosses would have many definitions displayed- telling you all the different meanings of the character. Therefore I couldn't understand what you meant in that paragraph.
In response to your second paragraph, what I mean to say is that Wyang previously liked the 'manual gloss' I added for the 生 character as it is used in 謀生, but Wyang didn't like other glosses I made that were based on analysis found in the dictionaries I look at. To me, the discussion is moot for the moment since the topic we were originally discussing was the 隔音 in 隔音符号, and I can't think of the specific examples that Wyang reverted. It was a long time ago. (Also, 'refundant' sounds like something you do over and over that is really fun, or perhaps a source of reoccurring 'funds'~~ funny!)
In response to your third paragraph, I made some edits to 喝酒, 不知道 & 好用 based on five/six dictionaries that I look at a lot. I came to the preliminary conclusion that hējiǔ and hǎoyòng were non-standard or nonsensical pinyin forms (but some dictionaries had the entry '不知道', so the pinyin forms 'bùzhīdao' & 'bùzhīdào' are tolerable enough though I have not yet confirmed their existence). If you want to revert my change at 隔音 and 隔音符号 and add the meaning 'to separate syllables', that's okay with me. I think this was first time I have ever used the SoP justification to delete something; I don't know what I'm doing. I called it a justification via SoP, but it was basically as a cloak for my ulterior reason, which was that I didn't find this meaning for 隔音 in the dictionaries I was looking at when I made that edit. Sorry if any of my response here was stupid. --Geographyinitiative (talk) 03:09, 10 November 2018 (UTC)
stream of consciousness response/elaboration:
  1. the glosses shown for characters (such as : "to be born; to give birth; life; to grow; student; raw") are not taken from 生#Definitions (they are from Module:zh/data/glosses)
  2. "to be born; to give birth; life; to grow; student; raw" is long and vague, and I support making it more specific,
    • unlike with entries like 隔音, since the content at 隔音 is more liable to change, and any changes would not be propagated to 隔音符号
    • →I like the edit at 謀生
  3. I think that it would be nice if our entries signaled to users that a manual gloss was placed in {{zh-forms}}
    • ←"an editor took the time to manually adjust the gloss"
    • →maybe if we did this, I might have greater support for adding manual glosses for "words" ("words" referring to 2 characters 以上): "a manual gloss was inserted here"→"check the original entry to see if anything is different"
      • this still would cause a discrepancy between the original entry (隔音) and the derived entry (隔音符号)
  4. (now I'm interested in the theoretical meaning of "refundant" as well……)
  1. The absence of 隔音 "to separate syllables" in other dictionaries might be suspicious, but we are not under obligation to follow them :)
  2. There must be documentation of the correct pinyin orthography for words/phrases(?) such as 喝酒 somewhere.
  3. thinking about it a bit, I don't really support every single theoretical 1-character-verb+1-character-noun collocation that exists. I don't know what my criteria are.
Suzukaze-c 04:22, 13 November 2018 (UTC)


Hi — I notice that you have added emboldened '''μπαίνω''' to Module:el-translit/testcases, as plain μπαίνω is already there I wondered why. — Saltmarsh. 06:50, 3 December 2018 (UTC)

I noticed a few days ago while browsing Recent changes that the ⟨mp-⟩ cluster is converted to /b-/ unless within bold formatting (as in a usage example), when it is transliterated to /mp-/, which strikes me as rather inconsistent and almost certainly undesirable. Revert if the code is indeed behaving correctly... —Suzukaze-c 07:00, 3 December 2018 (UTC)

Yes, we'd love to.Edit

Sure. If we ever meet, we'll shatter your skull, break your limbs, and incinerate the rest of your jaundice, chinky skin. ;) 2607:FB90:33D:3016:F453:7E5F:34D3:1DF0 23:40, 4 December 2018 (UTC)

break me daddy <3 —Suzukaze-c 23:41, 4 December 2018 (UTC)
Are you on drugs, little kid? Go see your pediatrician. 2607:FB90:33D:3016:F453:7E5F:34D3:1DF0 23:44, 4 December 2018 (UTC)
I was going to, but the people at the hospital told me I was too old this morning 😢 —Suzukaze-c 23:46, 4 December 2018 (UTC)
You sound homo. Seriously. And we bet that you have a 1-inch penis, you little Asian! 2607:FB90:33D:3016:F453:7E5F:34D3:1DF0 23:50, 4 December 2018 (UTC)
yeetus penis please daddy —Suzukaze-c 23:52, 4 December 2018 (UTC)

About Fuzhou languageEdit

Thank you for telling me. I am interested in this proofreading project, but I may only be able to take a little time to do this. I try my best.

(I don't know how to express this in English...) 顺便一提,"Dictionary of the Foochow Dialect"在Commons也有PDF文件,我想知道怎么处理这个文件,才能让它像"An English-Chinese Dictionary of the Foochow Dialect"一样,被切成一页一页,并可供校对?

"Dictionary of the Foochow Dialect" is also receiving crowdsourcing digitization. I think if this project is finalized and its results can be released under the appropriate copyright agreement, Wikisource can use it. Davidzdh (talk) 06:09, 10 December 2018 (UTC)

Cool :) I have been working on it, but I do not know Fuzhounese, and there probably are spelling mistakes.
For File:Dictionary of the Foochow Dialect.pdf, you should create s:en:Index:Dictionary of the Foochow Dialect.pdf.
I am also aware of, and I think that it is interesting. s:Index:English-Chinese Vocabulary of the Vernacular Or Spoken Language of Swatow.djvu was also imported from another source. —Suzukaze-c 06:18, 10 December 2018 (UTC)
Thank you for telling me! Davidzdh (talk) 10:46, 21 December 2018 (UTC)

Missing italics/bold.Edit

Thanks, A review of my efforts would also be much appreciated, as whilst I'm going by what's in entries, a second set of reviewing eyes and expertise would be appreciated.ShakespeareFan00 (talk) 11:12, 24 December 2018 (UTC)

^^ —Suzukaze-c 22:37, 24 December 2018 (UTC)


Bonjour! I'd like to say, I think I personally haven't heard sense 1 pronounced as wā... Dokurrat (talk) 04:36, 27 December 2018 (UTC)

Hm, then does |m_note=wa - particle need to be revised? —Suzukaze-c 04:44, 27 December 2018 (UTC)
I'd like to ask another person to make sure. @Tooironic Knock knock, bonjour, What is the pronunciation(s) you think you've heard for sense 1 "wow" of 哇? Dokurrat (talk) 05:00, 27 December 2018 (UTC)
Not sure. I guess I have heard wā and 哇哦. ---> Tooironic (talk) 05:11, 27 December 2018 (UTC)
@Tooironic: Thanks! Dokurrat (talk) 05:16, 27 December 2018 (UTC)


Sorry to hound you, but would you like to add a citation to the linked term? ←₰-→ Lingo Bingo Dingo (talk) 15:09, 27 December 2018 (UTC)

I might do it sometime in the future. —Suzukaze-c 19:11, 28 December 2018 (UTC)

CAO NI MA!!! ЦО НИ МА!!!Edit

Stop the Fuerdai vandal if you can, bitch on wheels!!

富二代! 富二代! 富二代!

Trump supporters must die (talk) 02:49, 14 January 2019 (UTC)

@Trump supporters must die spank me daddy —Suzukaze-c 02:50, 14 January 2019 (UTC)
You're a girl? Lol Trump supporters must die (talk) 02:53, 14 January 2019 (UTC)
12/f/thailand —Suzukaze-c 02:56, 14 January 2019 (UTC)

Simplified YanzipangEdit

Discussion moved to Template talk:zh-character component#Simplified Yanzipang.


I guess you made the changes here as the examples sentences were a few many. However, they are not "quotations" as suggested by the drop-down button, so that doesn't look right either. ---> Tooironic (talk) 11:38, 7 February 2019 (UTC)

Mm, indeed they are not quotations. It was for consistency though; several of the preceding usexes used #* formatting. The only thing I don't like is quotations (#*) sandwiched between usexes (#:). —Suzukaze-c 01:50, 8 February 2019 (UTC)

Japanese linking templateEdit

Discussion moved to Wiktionary talk:About Japanese#Japanese linking template.

Chinese Postal romanizationsEdit

Hey- I saw that you created the Chinkiang page recently, and I was wondering what you thought of my recent spate of postal romanization edits, both in Wiktionary and Wikipedia. Thanks for any pointers. If you look at my contributions, I started doing these edits on the 29th of January. --Geographyinitiative (talk) 02:36, 13 February 2019 (UTC)

I believe you should be using {{qualifier|postal romanization}} instead of {{sense|postal romabization}}, but otherwise I have no particular comments ^^ (also, I might have time to fix them myself later) —Suzukaze-c 03:02, 13 February 2019 (UTC)
I have just made that change on these pages: Gaoyou Zhenjiang. I will begin changing them all over to 'qualifier' later today. Please let me know if you develop any other concerns or have suggestions. Thanks! --Geographyinitiative (talk) 10:04, 13 February 2019 (UTC)

Re: 結婚指輪Edit

Hello. I wanted to reach out to you, re: 結婚指輪. I fixed it. Thank you. Johnnysama (talk) 05:11, 26 February 2019 (UTC)


IPs shouldn't be removing {{rfv}}- that should be done by whoever closes and/or archives it on rfv. That's my only objection. Chuck Entz (talk) 05:05, 28 February 2019 (UTC)

Mm, I see that it was indeed premature, but User:荒巻モロゾフ is not an IP, and IMO a wholesale rollback is a bit aggressive, since many improvements were made as well. —Suzukaze-c 05:10, 28 February 2019 (UTC)
Yes, I'm not IP. I wonce wrote in Wiktionary:Requests_for_verification/Non-English#彼女 that "Japanese custom don't treat ship as female." But I found lemmatized example of that in the dictionary, and checked the source of a quote in it, and wrote and translated the relevant part. Do we need someone who closes the rfv?--荒巻モロゾフ (talk) 11:32, 28 February 2019 (UTC)

some thoughts on JapaneseEdit

  • Japanese entries usually have multiple etymology sections, and {{ja-new}} can only help create the first. The other etymology sections must be created manually because {{ja-new}} hardcodes ==Japanese== and L3 POS headers. What about adding another parameter to make the template generate ===Etymology n=== and L4 POS headers instead?
  • From the reader's perspective, reading Japanese entries is like reading a txt or rtf file—an ocean of text and locating the information you want requires a great effort. The introduction of {{ja-spellings}} added visual guides on the right side and was the first step in making the structure of the page clearer. I think we can take the following additional steps:
    • Avoid a mixture of bitmap and ClearType-optimized font—change the Japanese font to something like Meiryo UI for Windows.
    • As an etymology section consists of “etymology + pronunciation + POS + inflection table”, format the pronunciation template and the inflection table as little boxes (like the Chinese {{zh-pron}} and {{zh-dial}}) to make the page 灰白相間、層次分明.

--Dine2016 (talk) 17:21, 6 March 2019 (UTC)

Sorry for the late reply. It sounds reasonable to me. —Suzukaze-c 03:02, 11 March 2019 (UTC)

Nice work on User:Suzukaze-c/template consistency. Here are some of my additions:

  • |rom=|tr=
  • Some form-of templates such as {{alternative form of}} supports both |t= and |3= while some such as {{short for}} only supports |3=.
  • For most languages, one parameter is enough to enter a word (e.g. {{m|en|English}}), but for Japanese, two parameters are often needed (e.g. {{ja-r|日本語|^にほんご}}). This leaves different ways to place the slots of those two parameters. For example, {{ja-compound|日本|^にほん|語|ご}} groups parameters by word, while {{ja-vp|見る|見える|みる|みえる|c=見せる|ck=みせる}} groups parameters by orthography. This is why I proposed a newer citation format of Japanese words KANJI:KANA (inspired by the format of {{zh-l}}) to make the syntax of Japanese templates more consistent and more predictable: {{ja-compound|日本:^にほん|語:ご}} and {{ja-vp|見る:みる|見える:みえる|c=見せる:みせる}}, and more in line with the general norm of one slot per word: {{compound|en|Japan|ese}}. --Dine2016 (talk) 05:46, 16 March 2019 (UTC)
  • Added!
  • Indeed. Editing templates to add support for |t= would also be possible, but we really need consistency, at any rate, and sometimes one is too lazy…
  • Ah, now I like it even more :) I also wonder how we could make things nicer for Korean hanja and Vietnamese han tu. The French Wiktionary has a |tradi= parameter that is used for Chinese and Korean. (oddly, it seems to be present only in fr:Template:trad, and not fr:Template:lien… but maybe they also need to think about consistency!)
Suzukaze-c 04:17, 17 March 2019 (UTC)

I can't believe you contributed to GNU Unifont, a project I have been admiring since junior high :) From their website: There is only a small degree of freedom how to draw an 'm' in a grid of 8x16 pixels so that you will not be dwelling on it for hours and progress much faster. I think part of the problem with Japanese entries is that there is too much freedom on what entries can look like, so that manual tweaking eats time and hampers the parsability of the page. For example

手工業 工業
inline float: right; (manual clearing, needs to group boxes with divs when there are many) floatright class (auto-clearing)
* {{ja-r|高麗 錦|^こま にしき|rom=-}}, {{ja-r|狛 錦|^こま にしき}}
* {{ja-r|こまにしき|高麗錦|狛錦|Koma nishiki}}
* {{ja-r|こまにしき}}
(auto fetching of kanji and romaji when there's no homophone)
Source of quotation outside {{ja-usex}}: a large number of templates, from {{quote-song}} to {{RQ:Taketori Monogatari}}, of which nobody can remember all the details Source of quotation inside {{zh-x}}: simple identifiers like Analects, or easy-to-type one-liners like '''1945''', {{w|Mao Zedong}}, ...

By giving up control of the finer details of the page we can automate many things :) @Eirikr --Dine2016 (talk) 15:49, 5 June 2019 (UTC)

Changing |rom= to |tr= clashes with 'transitivity' :( --Dine2016 (talk) 16:03, 5 June 2019 (UTC)
hm, but my username's been removed from the release notes. who told you _(:3」∠)_ pixel fonts are fun. I've wanted to make a decently comprehensive CJK bitmap font for a[n absurdly long] while, but I'm not smart enough _(:3」∠)_
I agree with 1 and 2. As for 3, I think I still prefer delegating quotation information to a second template. I do really like the short keywords, but I wonder if perhaps it could be more flexible (adding chapter, translator name, link, etc.) [The idea of choosing between ctext and Wikisource makes me uncomfortable though (;・∀・)] But perhaps, then we might as well create/use Template:R:Analects. Oh well.
And as for {{quote-song}} vs. manual wikiformatting: I personally use the quote- templates so that I don't have to think about formatting. We already have enough consistencies _(:3」∠)_
(I've wondered if we could use Template:Q for Chinese, since it already exists, but I don't think it would work.)
Suzukaze-c 16:52, 5 June 2019 (UTC)
Ah, you're right. If templates {{quote-song}} could retain semantic information in html then it's definitely superior to hand-formatting the citation.
It seems lemmatizing common wago at kanji has some support, so {{ja-spellings}} is a failure _(:3」∠)_ Maybe I should move the modern & hist kana to pronunciation section, and kanji spellings to {{ja-kanjitab}}:
Kanji in this term
Grade: 4
Alternative spelling 闘う
(I googled bing searched Umbreon126 the Script Importer on UTAU Lyrics Wiki before I realized it was you ...) --Dine2016 (talk) 14:12, 6 June 2019 (UTC)

Ah, I almost forgot this one:

=====Derived terms=====
* {{ja-r|掛け麹|かけこうじ}}
* {{ja-r|麹 黴|コウジ カビ|[[aspergillus]]}}
* {{ja-r|麹%菌|こうじ%きん|[[aspergillus]]}}
* {{ja-r|麹%酸|こうじ%-さん|[[kojic acid]]}}
* {{ja-r|麹%漬け|こうじ%-づけ}}
* {{ja-r|麹%花|こうじ%ばな}}
* {{ja-r|麹%町|^こうじ%-まち}}
* {{ja-r|麹%室|こうじ%-むろ}}
* {{ja-r|米 麹|こめ こうじ}}
* {{ja-r|甘%麹|あま%こうじ}}
* {{ja-r|支那 麹|^しな こうじ}}
* {{ja-r|白%麹|しろ%こうじ}}
* {{ja-r|種 麹|たね こうじ}}
* {{ja-r|練り麹|ねりこうじ|rom=-}}, {{ja-r|煉り麹|ねりこうじ}}
* {{ja-r|味噌 麹|みそ こうじ}}
* {{ja-r|麦 麹|むぎ こうじ}}
=====Derived terms=====
{{ja-der|掛け麹|麹黴:aspergillus|麹菌:aspergillus|麹酸:kojic acid|麹漬け|麹花|麹町|麹室|米麹|甘麹|支那麹|白麹|種麹|練り麹/煉り麹|味噌麹|麦麹}}

Similarly I hope quotations can take up only one line in the source. --Dine2016 (talk) 10:10, 9 June 2019 (UTC)

Lua error in Module:zh at line 404: [fill in the blank] is not a recognized language.Edit

I'm not sure exactly what went wrong with your edits to this module, but something did. Chuck Entz (talk) 03:51, 12 March 2019 (UTC)

@Chuck Entz: Nothing went wrong, actually. The entries were always formatted wrong, but the code didn't check. —Suzukaze-c 04:38, 12 March 2019 (UTC)
It's all fixed now, which was my only point in bringing it up- whatever works! Chuck Entz (talk) 06:34, 12 March 2019 (UTC)

lemma spelling of Japanese entriesEdit

  • Do you think wago compounds like 引き摺る and 見積もり should be lemmatized at the kana spelling? I think that, on one hand, they have a greater degree of variety in spelling (either part can be written in full kana, and okurigana for nouns and verb infinitives can be omitted for brevity) so they ought to be lemmatized at the kana spelling; on the other hand, they have a relatively fixed structure compared with single wago terms, making the choice of kanji narrower and the potential spellings less competing, so they can be lemmatized at the most common (or most regular) kanji spellings with no problem.
  • Kyūjitai is a tough problem not only because (1) wago terms involve different abstract kanji (みる→観・覧) and the same abstract kanji may have different forms (観→観・觀、覧→覧・覽), creating a two-tier hierarchy (sometimes three if you take Unicode codepoints into account) and (2) the poor font support (unless you resort to a Korean font, which is closer to the Kangxi printing style, or you resort to pictures, which have to be mass imported from GlyphWiki to Wikimedia Commons), but also because we have different degrees of oldness. For example, is still an extended shinjitai with no official status (according to ‎KevinUp). Should we list spellings such as 灯籠 as perfectly shinjitai or half-shin-half-kyū, given the existence of 灯篭?
  • Do you think {{ja-spellings}} should implicitly make the page title one of its arguments—that is, should みる read {{ja-spellings|h=みる|見る|観る|…}} or {{ja-spellings|みる|h=みる|見る|観る|…}}? The advantage of the former is brevity, and it's also what {{zh-forms}} do (using the page title as |t=), and the advantage of the latter is that you won't break things while moving entries.

--Dine2016 (talk) 07:10, 2 April 2019 (UTC)

  • I thought that 和語 compounds might be lemmatized at the kana spelling for consistency with non-compound 和語 terms. For example, the spelling of 引き摺る is surely rarer than 引きずる.
  • We could make shinjitai the canonical kanji spelling for simplicity, regardless of historical state. We also ought to include extended shinjitai if it's common, perhaps with a short {{qualifier}} noting that it might not be official.
  • I like the former. How often would we move pages in such a way that it {{{1}}} would need to be fixed?
Suzukaze-c 20:08, 3 April 2019 (UTC)
Ya, I too thought that the direction going forward was to lemmatize 和語 at the kana spellings (although I admit to a certain amount of inertia in that regard). Has that consensus (or at least, what I'd thought was consensus) changed in the past couple months? ‑‑ Eiríkr Útlendi │Tala við mig 00:13, 4 April 2019 (UTC)
@Eirikr: Hi. Welcome back! Progress has been slow in reaching a consensus on the new Japanese entry format. As Suzukaze puts it, "it would be a massive change, and we can't decide on the details, which is why discussions don't last" or "I think that part of the problem is that our current setup is 'alright' and Good Enough™, and other editors don't feel an urgent need to change." I have a lot of ideas about the new Japanese entry format (some of them are here), but I'm too lazy(ソシオフォビック) to push for changes. --Dine2016 (talk) 02:51, 4 April 2019 (UTC)
@Dine2016: It feels like we have been discussing things in multiple places, and I have been having trouble keeping track. Could we compile a single list of past discussions related to entry/template reform? —Suzukaze-c 04:56, 7 April 2019 (UTC)
Probably, but there are many unsolved issues (such as kanji and kana spellings, inflected forms, and how to present Middle / Old Japanese or whether to use unified Japanese). I'll compile a proposal to show to other Japanese editors sometime. --Dine2016 (talk) 05:33, 7 April 2019 (UTC)

I think the most urgent issue at the moment is to switch existing usages of {{ja-r}} to the inline format. The vertical metric configuration of Meiryo leaves horrible gaps between kanji and kana, and the matching is sometimes wrong: 昨日(きのう) (kinō). But even with these issues fixed, (1) the kanji is still too big compared with Japanese terms without ruby, causing disharmony, and the kana too small (as Eirikr reports), making uncomfortable reading. Also, Wyang said that templates like {{ja-r}} taking up too much vertical space would discourage editors to add more examples, synonyms, etc. (2) When citing wago, {{ja-r}} leaves no way to link to the kana spelling, put kana before kanji, or have multiple kanji spellings, etc., which is incompatible with the kana-centric approach.

As for entry/policy reform, I actually don't mind lemmatizing wago terms (especially those with stable kanji spellings) at kanji spellings if it's not because doing so would require both {{ja-spellings}} and {{ja-kanjitab}} which will take up too much space. This issue ({{ja-spellings}} + {{ja-kanjitab}} taking up too much space) also troubles kanji entries. I think the long-term solution is to combine the two templates into a single morphology-showing template like {{zh-forms}}. --Dine2016 (talk) 15:21, 7 April 2019 (UTC)

@Dine2016: (Well, if you want to combine {{ja-spellings}} and {{ja-kanjitab}}, perhaps now is a good time to think of it... —Suzukaze-c 20:38, 10 April 2019 (UTC))
What about this (conceptually)?
Usage: {{ja-forms|おう>おい はらう|h=おひ はらふ|追い 払う|追い はらう|追 払う}}. We can use a data module to automatically assert that :おう is a kun'yomi and provide the gloss.
Irregular reading types can be provided manually, e.g. {{ja-forms|かり そめ|仮 初め|仮 初|苟且-jukujikun}}. --Dine2016 (talk) 16:36, 27 April 2019 (UTC)
Hiragana modern おいはらう
historical おひはらふ
Kanji 追い払う
(おい < おう, kun'yomi) “to chase; to follow; to drive out”

(はらう, kun'yomi) “to drive away; to pay; to empty”

@Dine2016: ありだね。 —Suzukaze-c 06:36, 4 May 2019 (UTC)


Hi. Can you change the Japanese font to Meiryo or Meiryo UI for Windows?

  • The Chinese font has been changed to Microsoft JhengHei/YaHei and the Korean font has been changed to Malgun Gothic. Japanese is falling behind.
  • MS PGothic has only one weight, which means that bolding (the b element) has to be achieved by an increase of font size, causing disharmony:
    • 分的な太 (dadaism?)
    • コード switching (inconsistent weight and size).
  • If we change the Japanese font to a ClearType-optimized font, we can implement the b element by a true increase in font weight:
    • 分的な太
    • コード switching

--Dine2016 (talk) 15:43, 2 April 2019 (UTC)

Thanks. I think many usages of {{ja-r}} should be changed to an inline format. For example, the "See also" section of 気が重い should read

instead of

What do you think? --Dine2016 (talk) 02:49, 6 April 2019 (UTC)

I'd be fine with the second one if other editors prefer it as well. Perhaps adding a second form within the parentheses needs to be incorporated into Module:links itself, as I mentioned elsewhere. This would allow us to use templates like {{der}} "normally" without need for ...|-}} {{ja-l/new|..., and might be useful for languages like Korean as well (when adding hanja). —Suzukaze-c 04:44, 6 April 2019 (UTC)
  • One additional consideration -- bolded kanji can become hard to read. I'd actually thought that was why the templates used enlargement instead of bolding. I think any use of bold for kanji should be well-tested to ensure that the bolded characters are still legible. Turning things into blobs of color isn't very helpful. :)
Also, FWIW, the furigana in the lower "instead of" examples are so small I can't read them (laptop running Windows 10). ‑‑ Eiríkr Útlendi │Tala við mig 03:40, 7 April 2019 (UTC)
@Eirikr: Thanks for your reply. I have a bold idea: What about changing the behavior of {{ja-r}} to output the inline format by default? This way we don't need to mass-update entries in the mainspace.
By the way, my personal implementation of the new {{ja-l}} (inline citation template) supports the following functions: (1) putting the kana before kanji, or having multiple kanji spellings. (2) Automatic fetching of reading when given only kanji. Therefore {{ja-l|わぎも|吾妹|我妹|[[my]] [[dear]] (woman)|lit=my little sister}} gives わぎも (吾妹, 我妹, wagimo, “my dear (woman)”, literally “my little sister”), and {{ja-l|国際音声記号}} gives 国際音声記号 (こくさいおんせいきごう, Kokusai Onsei Kigō), but {{ja-l|東京}} gives 東京 [Reading?] because there are multiple readings. I think {{ja-r}} can be made to work like this without breaking things. Please see also #some thoughts on Japanese above for the new format KANJI:KANA in addition to KANJI|KANA. --Dine2016 (talk) 04:18, 7 April 2019 (UTC)

Can't add . in zh-x 求助Edit

Hey- just like I couldn't add a space into a Chinese example text a while back (四十埠), now I can't add a '.' into a Chinese example text. It's on the 地牛翻身 page- a '5.6' earthquake was written with a . Tshiánn-mn̄g, is there a way to fix this that you know of? To-siā. --Geographyinitiative (talk) 00:32, 4 April 2019 (UTC)

I used more HTML entities (&#46;), tricking {{zh-x}} into not seeing a period, but still rendering as a period. nei5 gok3 dak1 jyu4 ho4? —Suzukaze-c 00:40, 4 April 2019 (UTC)
Hó! --Geographyinitiative (talk) 00:47, 4 April 2019 (UTC)

The 将棋 entryEdit

Re: the 将棋 page: I restored the pronunciation with the right hiragana for that word. My apologies, sometimes my mind tends to go on autopilot for some reason. Johnnysama (talk) 05:20, 9 April 2019 (UTC)

Japanese rōmajiEdit

Why are you changing the rōmaji definitions for the pages I am creating? The pages to which I declare the definition state the page as the proper rōmaji. TE(æ)A,ea. (talk) 23:06, 13 April 2019 (UTC).

See WT:AJA#Romaji entries. —Suzukaze-c 00:03, 14 April 2019 (UTC)

موُمِنَاهِي at 木乃伊Edit

Discussion moved to Talk:木乃伊#موُمِنَاهِي.


Why did you remove my usage example? It is not only illustrative of the word's usage, but also teaches children important things about Armenia's fauna. --Vahag (talk) 15:20, 19 April 2019 (UTC)

Ehh 🤷 —Suzukaze-c 15:36, 19 April 2019 (UTC)
Is it better? Are you happy now? --Vahag (talk) 15:47, 19 April 2019 (UTC)
🤷 —Suzukaze-c 15:57, 19 April 2019 (UTC)

Min Nan shurufaEdit

Hey, sorry to bother you, but I'm tired of this ridiculous tailo input software system . I want to be able to switch between input of Jiaolo, Tailo or Hanzi with the click of a button or only a few clicks, and not be forced to use Tailo pinyin and do a billion clicks to switch between Tailo and Hanzi input. I want to be able to make the little dot after the letter o without copy pasting anything. This shurufa should exist somewhere.

I know I could probably ask other people, but I wanted to ask you to see what Min Nan input software is good, what is commonly used. I saw, looks promising. Who should I contact that would likely respond to such a low level question? I bet the answer is somewhere on Min Nan Wikipedia, but I don't know how/where to look or how to search for this answer.

If Min Nan Wikipedia uses Jiaolo and not Tailo, why the fuck would I want an input system that can't write Jiaolo?

Thanks for any help or suggestions

--Geographyinitiative (talk) 01:29, 24 April 2019 (UTC)

Mm, I don't know what other people use. I would suggest RIME, but I'm not sure if the existing Hokkien schema does what you want. It seems like you can certainly type Tai-lo and hanji, but not POJ. —Suzukaze-c 02:47, 24 April 2019 (UTC)
Lí hó!Just following up. I installed the program I mentioned above and it works GREAT. It doesn't force you to use Tailo- you can use POJ to type characters or just type out POJ. Consider this idealistic impossible fantasy realized. Chài-kiàn!--Geographyinitiative (talk) 07:27, 24 April 2019 (UTC)
RIME 大灋好。—Suzukaze-c 07:44, 24 April 2019 (UTC)


Discussion moved to Talk:대나무#Etymology.


Are you sure ㅿ is pronounced as 'z'? There are many other theories,too. B2V22BHARAT (talk) 02:56, 7 May 2019 (UTC)

Regardless of my opinion, Yale uses 'z'. —Suzukaze-c 03:19, 7 May 2019 (UTC)

OK. Thanks. B2V22BHARAT (talk) 03:28, 7 May 2019 (UTC)

Middle Korean (半齒音 如穰字初發聲) 穰發聲音: 唐音:njiÉ‘ng / njiÉ‘ĚŒng. 汉语拼音 :rĂĄng, / rÇŽng, / rĂŠng. B2V22BHARAT (talk) 03:48, 7 May 2019 (UTC)

@B2V22BHARAT: If was ng, then what was ?
For example, here, we find (ᅌᅥ), (ᅌᆑᇹ), (ᅀᅲ), (씨ᇫ), ().
Middle Chinese: (MC ŋɑX), (MC ŋʉɐt̚), (MC ȵɨʌ, ȵɨʌH), (MC d͡ʑɨ), (MC ɦʉɐŋX)
It seems particularly strange that should be ng in (씨ᇫ).
Suzukaze-c 21:06, 27 May 2019 (UTC)

According to Wiktionary, (MC ȵɨɐŋ, ȵɨɐŋX) was pronounced as ȵɨɐŋX in middle Chinese, so that's why I have put r or ng because ng is what Koreans are pronouncing for the Chinese Characters that have r phoneme in China right now. I don't know for sure how Chinese pronounced (MC ȵɨɐŋ, ȵɨɐŋX) when Hunmin jeongeum was made, so that's why I have put r or ng. Do you know the exact period of Middle Chinese(eg. AD xx~ AD xx)? How I see it is that seemed to have represented 'r' phoneme both in China and Korea back in the day, but changed to ng phoneme in Korea for the ease of pronunciation like 두음 법칙 (頭音法則, dueum beopchik). B2V22BHARAT (talk) 08:15, 28 May 2019 (UTC)

You're right. is ng, right? Then I think it's likely that have represented r phoneme for Chinese characters. I wasn't just sure of the period of Middle Chinese. B2V22BHARAT (talk) 08:18, 28 May 2019 (UTC)

Wikipedia pages seem to say that the Middle Chinese period ends along with the Song Dynasty, so we must look at later dialects, probably early Mandarin. I'm not familiar enough with 漢語音韻學 / Historical Chinese phonology or the history of Korean to confidently make further statements. :(
I note that 中原音韻#聲母 (Korean Wikipedia: 중원음운) mentions " ", so perhaps was already not ȵ by the time that 훈민정음 and 노걸대언해 were written. Then we can guess that might be something like ʒ ~ ɻ, or z ~ r.
By the way, do you know about Google Scholar? These articles are probably better than my amateur speculation. —Suzukaze-c 08:43, 28 May 2019 (UTC)

I'm just curious.. How can z pronunciation turn into r? Do you think it's logical? I understand s--> z part as in bus(z)iness but z..>r?? questionable.. B2V22BHARAT (talk) 09:41, 28 May 2019 (UTC)

Ah, I'm not saying that z turned into r, but that is a sound somewhat like z or r. What do you think of rǎng#Pronunciation or rì#Pronunciation? —Suzukaze-c 09:56, 28 May 2019 (UTC)

By the way, the Pinyin of is ráng, not rǎng. ráng#Pronunciation, rì#Pronunciation. B2V22BHARAT (talk) 11:15, 28 May 2019 (UTC) I don't hear any 'z' sound from these examples. Also, for rǎng, there's no 'z' sound, either. B2V22BHARAT (talk) 11:15, 28 May 2019 (UTC)

Also, in the end, r is just the letter of the Pinyin alphabet that someone chose for the consonant in 日, just like someone decided that 어 should be eo in the Revised Romanization. The actual sound in terms of phonetics is more important. —Suzukaze-c 10:00, 28 May 2019 (UTC)

So are you arguing that acutual phoneme of in China has 'z' sound in it? Can you prove me with the examples? B2V22BHARAT (talk) 11:22, 28 May 2019 (UTC)

By the way, I'm not using that site(DBpia) because I have to pay money to read the content. B2V22BHARAT (talk) 09:50, 28 May 2019 (UTC)

Paywalls are indeed troublesome... —Suzukaze-c 09:56, 28 May 2019 (UTC)

Yeah I agree.. By the way, if you want to use that site, you can enroll in the Korea National Open University, which costs only 700,000 won a year. Or you can apply for a library pass from a university nearby your place if you're in Korea and use it for free. B2V22BHARAT (talk) 09:59, 28 May 2019 (UTC)

Can you show me the "actual" examples of Chinese characters that have used in the past and have sound of 'z' in China? B2V22BHARAT (talk) 11:24, 28 May 2019 (UTC)

Oh never mind.. z was not pronounced as z.. it was just a symbol for r.. B2V22BHARAT (talk) 11:34, 28 May 2019 (UTC) This person is also misinterpreting the phoneme of z as z like I did.. B2V22BHARAT (talk) 11:38, 28 May 2019 (UTC) I made a mistake. you're right. B2V22BHARAT (talk) 11:44, 28 May 2019 (UTC)

But still, I don't understand why they have assigned phonetic symbol ʐ instead of r or ɹ on 人民日报 Rénmín Rìbào. It's kinda confusing..위키백과:IPA B2V22BHARAT (talk) 12:15, 28 May 2019 (UTC)

Hmmm... pretty political.. To me, it sounds more like j and z not r.. 5:40~ But anyway, thanks I learned something new today. B2V22BHARAT (talk) 14:31, 28 May 2019 (UTC)

There is actually different opinion regarding the r sound in modern Mandarin. See the footnotes at w:Help:IPA/Mandarin and w:Standard Chinese phonology#Consonants.
And if you think it sounds like j, then so did Wade-Giles ;) —Suzukaze-c 15:03, 28 May 2019 (UTC)
Thinking through the biomechanics of speech, [z] is a voiced alveolar sibilant. As the tip of the tongue moves further back along the top of the mouth, this shifts to [ʒ] or a voiced postalveolar fricative. From there, it's very easy to shift to a [ʐ] or voiced retroflex fricative sound, and then a further minor shift yields the [ɹ] or postalveolar approximant of the English /r/ sound. Considering the mouth shapes and broadly similar points of articulation, I could easily imagine that might have represented a sound in this same general family, perhaps closer to [ɹ] or closer to [z], which in Chinese later evolved into the [ʐ] of modern Mandarin.
Cheers, ‑‑ Eiríkr Útlendi │Tala við mig 17:28, 28 May 2019 (UTC)

Oh I see. That makes me clear now. Actually, I saw in the wikipedia page explaining z phoneme relation to r phoneme, but it was English(Norman, Latin?) so I just igonred it, but I guess it can be also applied to Asian language phenomenon as well. B2V22BHARAT (talk) 11:13, 29 May 2019 (UTC)

Middle Korean fontEdit

What are you using? I'm using, developed by Department of Information Computer Engineering at Pusan National University(AI Research Center) It's being co-produced by Nara Infotech and advised by Lee Sang-hyeok, a professor at Seoul National University.

I'm using NanumBarumGothic YetHangul and NanumMyeongjo YetHangul. —Suzukaze-c 05:06, 8 May 2019 (UTC)
Well, says that Korean Romanization is a way of Romanizing Korean, and has ①'Revised Romanization of Korean' (Republic of Korea standard, Ministry of Culture and Tourism Notice No. 2000-8, 2000. 7.7) ②'McCune-Reischauer Romanization' ③'Yale Romanization', Our romanization converter follows the above three schemes.

A method used in ① and ② is transcription, which represents the standard pronunciation of Korean language, while a method used in ③ is transliteration, which does not represent sound but only letters. So "YALE DOES NOT REPRESENT PRONUNCIATION BUT ONLY LETTERS." B2V22BHARAT (talk) 05:15, 8 May 2019 (UTC)

Yale is suitable for expressing the morphological structure of a word, as opposed to the McCune-Reischauer Romanization or the Revised Romanization of Korean, which focuses on making the pronunciation of the whole word similar, so Yale notation is commonly used for linguistic analysis. B2V22BHARAT (talk) 05:18, 8 May 2019 (UTC)

Any reply..? B2V22BHARAT (talk) 05:48, 8 May 2019 (UTC)

Well, I'm not sure what your comments on Yale have to do with fonts for Old Hangul (^_^;) —Suzukaze-c 05:50, 8 May 2019 (UTC)

You first asked me about the font. 04:38, 8 May 2019 →‎Etymology: mm, are you using the correct fonts?

You're saying that my translation is incorrect. But I'm saying that Yale itself does not consider actual pronunciation, but focus on morphological structure of a word. B2V22BHARAT (talk) 05:58, 8 May 2019 (UTC)

You said that middle Korean phonetic should follow the Yale style, so that's what I did. B2V22BHARAT (talk) 05:59, 8 May 2019 (UTC)

Hm, this is what I see on my computer. In Yale, 아래아 is 'o', not 'wi'. —Suzukaze-c 06:05, 8 May 2019 (UTC)

There seems to be Middle Yale Romanization(중세 예일) and Modern Yale Romanization(현대어 예일). This program( seems to be using Middle Yale version one. Did you notice this? B2V22BHARAT (talk) 06:11, 8 May 2019 (UTC)

OK. I think it is an error. states that the results presented by the Roman converter are automatic through the program, so there may be an error. Please point out any errors or omissions that I made next time. I'll fix the 아래아 part. Also, if there is any good automatic middle Korean translator progarm, please give me the link. It would save our time. Thanks. B2V22BHARAT (talk) 06:18, 8 May 2019 (UTC)

Yes, there must be something wrong with the website. The RR of ᄋᆞ is definitely not 'twi' either. —Suzukaze-c 06:19, 8 May 2019 (UTC)
You're using this one, is that correct? ^^ B2V22BHARAT (talk) 06:30, 8 May 2019 (UTC) I'll use this, too next time.
It is an interesting link. However, I am currently writing the romanization manually. _(:3 」∠ )_ So there might be mistakes in my text too. —Suzukaze-c 06:35, 8 May 2019 (UTC)
I see. You can refer to this link, too. I think it shows correct Yale romanization except for the Chinese character. B2V22BHARAT (talk) 06:47, 8 May 2019 (UTC)


Hi. What do you think about this claim? that 李's phonetics derived from 來? Because there was no source behind this argument, I have put a rfv on this claim.. Do you think you can back up this claim? B2V22BHARAT (talk) 10:56, 9 May 2019 (UTC)

I think this claim is plausible because of this reason: 李 is read 'li' and 來 is read 'lai'. So they're similar. However, in 木(mu) and 子(zi), there is no l sound.. so I think Wyang has a point, but just no source. Probably he read it from somewhere. It's unfortunate that he left. B2V22BHARAT (talk) 11:02, 9 May 2019 (UTC)

It's solved. @Geographyinitiative taught me where the source came from. B2V22BHARAT (talk) 12:10, 9 May 2019 (UTC)

Also, you should keep in mind that Chinese pronunciation has changed a lot over time. 子 was not always 'zi'. —Suzukaze-c 16:23, 9 May 2019 (UTC)

Oh as long as it does not contain l sound, it doesn't matter.. I was mostly interested in the 木(tree) part. B2V22BHARAT (talk) 17:03, 9 May 2019 (UTC)

What is m okmEdit

심토ᇰ (simthong). Do I need to use this format for middle Korean? Please explain. Thanks in advance. B2V22BHARAT (talk) 06:49, 3 June 2019 (UTC)

m is Template:m. {{m}} is like {{l}}, except {{l}} is used in Lists (like ===Synonyms===). {{m}} is for Mentions of words (like inside ===Etymology=== paragraphs).
okm is Middle Korean. (ja is Japanese, en is English, etc.)
Suzukaze-c 06:55, 3 June 2019 (UTC)
Thanks. B2V22BHARAT (talk) 07:03, 3 June 2019 (UTC)


Hello- I just want to say thanks for your years of dedication to this project. I'm sorry that I have come in conflict with you at various points. I know that you are a wise person and I thank you for the help you have given me as well as the criticism. I may seem erratic at times, but I will try to keep it to a minimum and do useful editing. Vigorous debate will increase the quality of the dictionary, not decrease it. Keep up your good work and keep fighting anything I do you think is wrong. Thanks again for your time and work. --Geographyinitiative (talk) 05:04, 12 June 2019 (UTC)

異形詞 exampleEdit

Hello again- once again, sorry for causing problems. Anyway, because I am a doofus, I don't know how to add a dash (-) in the Mandarin Hanyu Pinyin for the example given on the 異形詞 page. The reason I want to put a dash between "Dì" and "yī" is that adding a dash there not only conforms to the way we write the pinyin in zh-pron on the 第一 (dì-yī) page, it also conforms to normative practice for documents like this (for example: the first page of Second Chinese Character Simplification Scheme (Draft) published in May 1977 has a dash between "DI" and "ER"). I'm asking you because you have helped me with similar pinyin-related problems in the past. If you can help me this one time, I will add the example to the Template:zh-x page so that I don't have to ask you again in the future. If you don't know, I may need to go to the tea room. I thought I would ask you first. Thanks for any help. --Geographyinitiative (talk) 10:47, 16 June 2019 (UTC)

I don't have a workaround for this issue. —Suzukaze-c 23:53, 16 June 2019 (UTC)

Duplicate argumentsEdit

Thank you for helping out with these. :) —Rua (mew) 10:30, 20 June 2019 (UTC)

No problem! —Suzukaze-c 10:33, 20 June 2019 (UTC)

Rendering issuesEdit

Normally, for compounds in Traditional Chinese, a sans-serif font should be rendered in the page heading, while a serif font should be rendered in the heading in its corresponding Simplified Chinese page (e.g. 詞語词语 (cíyǔ) vs 词语). However, I've noticed the simplified font shows up in the headings of 桂河 and 生於斯,長於斯, at least when using a computer. I'm not sure if it's a client-side problem, or just a bug with Wiktionary. Can you suggest a way to fix it and get the Traditional Chinese font to be rendered? Thanks a lot. —RcAlex36 (talk) 14:59, 29 June 2019 (UTC)

You forgot the templates under the part-of-speech headers. They produce code that modifies the page header. —Suzukaze-c 01:08, 30 June 2019 (UTC)
Thank you! —RcAlex36 (talk) 03:44, 30 June 2019 (UTC)


こんにちは、MiiCiiです、女真文字のリンクをラテン文字にリダイレクトされる時に( is Private Use Unicode. on my machine it looks like 아ᇫ)と説明をなされて、心より感謝いたします。言われてみれば、女真文字は確かにハングルに似てますね。




duwin (Jurchen script: ) [※カッコを付けて、女真文字であることを説明した上、を入力する。「Jurchen script」には英語版ウィキペディアのリンクを付ける。]

1.four (4)
MiiCii (talk) 09:38, 8 July 2019 (UTC)

こんにちは。えーと、「女真文字がハングルに似ている」ということではなくて「 U+EDB7という文字の字形は私用面の文字である、つまり、フォントごとに異なる」ということです。そしてMiiCiiさん側ではちゃんと女真文字に見えるでしょう。女真文字は未だUnicodeでは収録されていないようですから仕方なくラテン文字の転写で命名した方が良いと思います。—Suzukaze-c 10:02, 8 July 2019 (UTC)
なお、見出し語に画像を置くことも可能です。エジプト語はUnicodeがいまいちとされているためそうしています(rḏj ḥr wꜣt)。—Suzukaze-c 10:08, 8 July 2019 (UTC)


I understand that my perspective is not generally accepted and I can take a good ribbing [8]. You are a great editor and I'm not worthy to edit on the website. I'm trying to explore what this website could be if our world were not as evil as it is- please be patient with me. I'm sharing my wacky perspective. You keep doing you man. You are truly awesome. --Geographyinitiative (talk) 23:01, 19 July 2019 (UTC)

collapsing in mobileEdit

Hi. Do you know how to push for making collapsing work in mobile view? If we can't make table collapsing work in mobile, maybe we can use the "NavFrame" framework instead, hmm…

--Dine2016 (talk) 11:39, 14 August 2019 (UTC)

I wonder why Wikimedia personally hasn't done anything about mw-collapsed. —Suzukaze-c 05:38, 15 August 2019 (UTC)
Thanks, but it's been proposed before :) I heard that table collapsing wasn't implemented in mobile view because it would require sending extra JS to mobile users (and cost more data/money).
In the meanwhile, what about switching to NavFrame as shown above? The advantage is that audio now works properly (and can be moved to the collapsed part). The disadvantage is that we need extra CSS to undo the default style of NavFrame (e.g. gray background, smaller font, bolding of title, etc.) @Wyang, Justinrleung --Dine2016 (talk) 06:54, 15 August 2019 (UTC)
Maybe feelings have changed since 2012. But personally I wonder about phab:T31118. —Suzukaze-c 00:17, 18 August 2019 (UTC)


Hey. We're phasing out the headers "abbreviation", "initialism" and "acronym". Please give this a different part of speech. Phrase? --Mélange a trois (talk) 21:08, 2 September 2019 (UTC)

Wiktionary:Tea_room/2019/August#SOHCAHTOA hasn't come to a decision, and I don't know what would be good either... —Suzukaze-c 01:16, 3 September 2019 (UTC)


This may have fallen through the cracks due to everyone being somewhere else over the weekend. I don't know that these are wrong, but based on geolocation (England) and the fact that they can't spell basic English ("earthan"? Really?), I suspect that they've somehow managed to get something wrong- probably the definitions at the very least. Chuck Entz (talk) 06:23, 3 September 2019 (UTC)

your revert at Edit

What do we do in this situation, when extra information is added to the translation of a usage example that is not present in the source? If it's not a gloss, how do we format that? Surely brackets are not enough. ---> Tooironic (talk) 02:35, 14 September 2019 (UTC)

Sometimes I use {{qualifier}}, but mostly I just use plain brackets. {{gloss}} doesn't feel semantically correct though. —Suzukaze-c 03:02, 14 September 2019 (UTC)
So in what situations should we use qualifier, and in what situations should be use gloss? ---> Tooironic (talk) 00:42, 15 September 2019 (UTC)
I guess the template names are self-explanatory. —Suzukaze-c 05:26, 15 September 2019 (UTC)

@Dine2016. —Suzukaze-c 03:06, 24 October 2019 (UTC)

A general-purpose template for additional information? --Dine2016 (talk) 04:26, 24 October 2019 (UTC)

acceleration templateEdit

On Wyang's last talk page (which got deleted), I mentioned the possibility of having some scripts that allow editors to edit the data model of an entry directly, by parsing the wikicode of the entry to get the data model, applying the changes, and encoding the data model again before saving the page. The assist code in translation tables on English entries may be considered an example of this. I recently discovered that template substitution can do this too.

The key observation is that when a substituting template reads the content of the current page, it reads the current version rather than the newly-saved version. As a result, one can write a substituting template that just returns mw.title.getCurrentTitle():getContent(). Then replacing the whole content of any entry with this template does not change the entry. If the template only returns the Japanese section of mw.title.getCurrentTitle():getContent(), then substituting the Japanese section of any entry (which is faster with AjaxEdit) does not change anything.

Now, make the template modify the source code after fetching it and before returning it, and you get a more efficient way to modify entries ("Ædit", Ctrl + A, Ctrl + V, save). I've used this quick method to add pronunciation sections and {{ja-ojad}} to entries. If the same method is used to accelerate new entries (e.g. drop-in replacement of {{ja-new}}), it might be able to automatically number the new etymology section (and when the new section is ===Etymology 2===, rename the older ===Etymology=== to ===Etymology 1=== and advance the level of subsequent sections by one), add multiple readings at once, as well as automatically handling ===References=== sections.

(Of course JS forms are better, but I haven't learned JS yet.) --Dine2016 (talk) 07:53, 17 September 2019 (UTC)

It sounds good to me.
It reminds me that I have also been thinking of a way to extract data from entries recently. Instead of using regex on raw wikitext to (for example) extract {{zh-pron}}, perhaps one could (1) s/{{zh-pron/{{extract:zh-pron/, and (2) use frame:preprocess.
{{extract:zh-pron}} would be a template that reformats the parameters of {{zh-pron}} in a way that makes Lua processing easier. After preprocess is applied, the results of {{extract:zh-pron}} should be easier to handle than raw wikitext.
I have't tried to implement this yet, though. —Suzukaze-c 00:45, 19 September 2019 (UTC)
Good idea. I had similar ideas when trying to improve the extract_gloss of Module:zh: instead of using patterns to extract the |2= or |t= parameter of the templates in definition lines, change the templates to corresponding "selectors" that returns its second or |t= parameter and frame:preprocess. I was probably inspired by TeX macros. --Dine2016 (talk) 08:34, 19 September 2019 (UTC)


Heya. Just thought you should know you forgot to add the simplified form at this entry. ---> Tooironic (talk) 02:39, 20 October 2019 (UTC)

Yah, sometimes I don't bother to do it right away and do it while tidying up "entries with uncreated simplified forms". I probably shouldn't be leaving the "uncreated" messages on the entry though 🙃 —Suzukaze-c 02:50, 20 October 2019 (UTC)

Reply to your question on 化学量論Edit

Yes, actually. As you can see from the Babel template on my user page, I have a basic understanding of the Japanese language. I know enough Japanese to get around (for travel), and I can read simple stories, but not so much for newspapers or novels, etc. I know all the Hiragana and Katakana. I also recognize the meaning of most kanji (they're not too different from Chinese characters), even if I have doubts about their pronunciation. And whenever in doubt, it's fairly easy for me to consult a Japanese-Chinese dictionary. ωικιωαrrιorᑫᑫ1ᑫ 11:28, 28 October 2019 (UTC)

then tell me the significance of the changes to the pronunciation section in [9]Suzukaze-c 14:54, 28 October 2019 (UTC)
There are several different ways to pronounce Japanese kanji. Go-on pronunciation is based on the Wu dialect of Chinese. Kan-on is based on the dialect spoken in Chang'an, the capital of the Tang Dynasty. Tō-on is based on Chinese pronunciation during the Song Dynasty. Kun'yomi pronunciation is the native pronunciation of a kanji, not borrowed from Chinese. Finally, Nanori pronunciations are used mostly in personal names. ωικιωαrrιorᑫᑫ1ᑫ 18:23, 29 October 2019 (UTC)
and the rest of it is? —Suzukaze-c 19:11, 29 October 2019 (UTC)

reply to emailEdit

insource:/sai[1-6\-]+ lou[1-6\-]+ zai[1-6\-]+/?

By the way I wonder if there can be some way to mark romanizations for indexing, e.g. <index g="jyutping">sai3 lou6 zai2</index>. Then MediaWiki can compile indexes like pinyin, jyutping, etc. semi-automatically. It's similar to how you can search derivatives and compounds in bold type in the midst of an entry in online dictionaries like the OED. --Dine2016 (talk) 02:10, 31 October 2019 (UTC)

Insource works but isn't practical :/
MediaWiki was not meant for such things :D —Suzukaze-c 02:18, 31 October 2019 (UTC)

Japanese Foreign Word of the Day nominationsEdit

There are many Japanese terms nominated for Foreign Word of the Day, but most of them aren't ready yet. The majority of those only lack a citation. Could you perhaps update one of these nominations once in a while? ←₰-→ Lingo Bingo Dingo (talk) 13:52, 22 November 2019 (UTC)

Maybe someday. Probably not soon. Sorry. —Suzukaze-c 06:28, 23 November 2019 (UTC)

JA koshiEdit

Curious about this set of edits. I'm not opposed, just curious as to your reason for moving the lemma from to こし.

I'd thought the proposal to lemmatize wago at the kana spellings had fizzled. With User:Dine2016's invention of {{ja-see}} and {{ja-see-kango}}, the technical need for doing so was somewhat lessened.

Also, if you're lemmatizing at こし, I'm a bit confused that etyms 2, 3, and 4 don't contain much of anything, yet also don't use {{ja-see}}? That seems ... suboptimal, and poor usability.

Cheers, ‑‑ Eiríkr Útlendi │Tala við mig 23:26, 16 December 2019 (UTC)

My understanding of matters is that it's not straight out banned, is it? I think I prefer it this way.
As for 2/3/4, they didn't have a lot of content in the first place... —Suzukaze-c 01:44, 17 December 2019 (UTC)
Devil's advocate: Rather than wasting time in endless debates like this, why not move to EDICT where lemmatization is not an issue at all, and return when Wiktionary acquires Wikidata support? --Dine2016 (talk) 03:08, 17 December 2019 (UTC)
Eh, I think I like Wiktionary better. Usage examples and whatever. Searching and entry layout have problems, but it's not enough to drive me away. —Suzukaze-c 03:57, 17 December 2019 (UTC)
Also, combining entries like 望む 臨む > のぞむ#Etymology 1 and 沸く 湧く > わく#Etymology 2 makes me feel Smart™. —Suzukaze-c 05:21, 17 December 2019 (UTC)
I totally agree about のぞむ. :) こし caught my eye as the body part generally just has the one kanji spelling, .
I'm not particularly worried about where things live. I just want to understand what I see other JA editors doing, so I can gauge if I should shift my own habits. :)
Re: Wikidata, I've watched the discussions for years, and the devs and editors for Wikidata seem to have no clear understanding of the kinds of multilingual lexicographical support and data normalization that would be required for a real Wikidata — every-language's-Wiktionary integration, in the kinds of complete terms that have been proposed in the past. I actually hold no hope of this happening. Not just in the near term, but at all.
In certain limited fashions, Wikidata could be used non-dysfunctionally in various Wiktionaries, such as for storing and sharing attributes of a given headword that don't require long-form explanations in the language of that Wiktionary (i.e. localized strings). These attributes could include:
  • Headword -- Just the headwords themselves. Whether or not a given Wiktionary builds out an entry for that headword is (potentially) orthogonal to whether a headword is listed in Wikidata. For instance, some Wiktionary editor communities might view certain headwords as SOP, whereas others might not.
  • Headword POS -- However, even this might be contentious. How does one treat POS for terms in vastly different languages? What is the Japanese POS 形容動詞 (keiyō dōshi) called in English? In Finnish? In Swahili? Does that change over time as the editor community changes? How easy is it to change the POS label for that term's type, and that Wiktionary's user language? Is that localized label identical to some other localized POS label in that user language? For instance, the EN Wiktionary community has called 形容動詞 (keiyō dōshi) different things over the years. Most recently, we appear to be gradually coalescing around calling these "adjectives", identical labeling in English for the 形容詞 (keiyōshi) POS, where we specify the differences in the inflection tables.
  • Synonyms / Antonyms -- This may be more straightforward. However, specifying which synonym or antonym applies to which sense(s) of a given term could require localized text, which gets complicated.
  • Alternative forms -- Perhaps the least bound by any localization issues of the individual Wiktionaries.
  • Pronunciation, at least for IPA -- Also presumably not bound by localization issues, aside from any explanatory remarks, or regional or other labels.
  • ... other attributes escape me at the moment. All other things I can think of are very localization-specific, which Wikidata cannot easily support -- if ever.
Anyway, back to the issue at こし, I'll have a go later at reworking etyms 2, 3, and 4; the current state just bothers me. :) ‑‑ Eiríkr Útlendi │Tala við mig 18:26, 17 December 2019 (UTC)
@Eirikr: We're already lagging behind the editors of EDICT in terms of efficiency. Their entry layout makes them advance very fast. If we want to catch up, we must fundamentally transform our entry layout. For example, {{ja-kanjitab}} must be eliminated (rather than improved, which is why I'm reluctant to add a label system to the |alt= parameter) in favor of a morpheme template like {{zh-forms}}, and the inflectional templates must be eliminated (rather than unified) in favor of {{ja-pron}} generating inflections. These changes would make the source of entries more Wikidata-like.
Once they are made, we can surpass EDICT in some other aspects, for example by covering all stages of Japanese (including Old Japanese) under a single ==Japanese== header (note: this does not mean ==Old Japanese== and its layout would go). We can also provide both 学校文法 and 日本語教育文法 info to English readers to help learners know their difference at an early stage. There are many more things we can do better than EDICT with the current template/module system, but unfortunately we're lacking a Wyang for Japanese (i.e. a Unified Japanese plan and technical resources).
What I expect from JA wikt:
* 国文法: ラ行五段活用 はし-る             [表示]
* 形態論: 子音語幹動詞(グループⅠ) hasir-  [表示]
BTW: If "infinitive" is unacceptable as a label for 連用形, what about "V-i" and "A-ku"? They are pretty self-evident, but most importantly they eliminate the need of "連用形 (ren'yōkei, continuative or stem form)", which is both tedious to type and tedious to read. --Dine2016 (talk) 09:00, 18 December 2019 (UTC)
  • One important consideration in comparing Wiktionary + Wikidata vs. EDICT is that EDICT is only targeting only English and Japanese readers, and only terms in English and Japanese, whereas Wiktionary and Wikidata purport to target pretty much everyone, supporting readers of all languages, and all terms in all languages (in theory, at least). The latter setup is incredibly more complicated, in ways that the Wikidata promoters haven't fully recognized, if past threads are any indication.
  • For the alternative analyses in conjugation, effectively kana-based for the 国文法 vs. phonetics-based for the 日本語教育文法, I'm all for including both. However, re: {{ja-pron}}, I'm confused why we'd have a pronunciation template generate inflections. That seems very strange to me. I think we'd be much better off creating something new with a different, and more purpose-oriented, name, rather than reusing {{ja-pron}} and adding lots of non-pronunciation stuff to it. I have no objection to reusing the code from {{ja-pron}}, but I think the name needs to be something distinct and clearly related to what it does. There's also the problem that, currently at least, the pronunciation is supposed to come above the senses, while the inflection is supposed to come below the senses. I don't see a way for a single template to handle this, unless it's supposed to also contain the senses -- which just seems messy and hard to work with.
  • Re: 連用形, I confess I don't like the super-short notation you propose. It actually comes across to me as obtuse and unclear, and even harder for users who may be less accustomed to this kind of thing. While such shortening might make sense for print dictionaries where space is at a premium, and aggressive abbreviation is the norm, I think it presents poor usability and a high barrier to entry, neither of which should we emulate. It's also inaccurate, as verbs in the 連用形 don't always end in -i (c.f. 下二段 and 下一段), and adjectives in the 連用形 don't always end in -ku (c.f. 形容動詞). There are also things that technically are neither verbs nor adjectives that have a 連用形, such as auxiliaries.
I don't find the "連用形 (ren'yōkei, continuative or stem form)" notation particularly tedious to read, but I take your point that you and others may. (Input is easily enough dealt with using edittools and other approaches.) I wish we could come up with a sensible English term that fits the same cognitive space. For adjectives, the 連用形 is pretty clearly an adverb, so "adverbial" is a good fit. But that doesn't work so well with verbs; the 連用形 here is sometimes functionally similar to an adverb, as when a clause ends in a verb in the 連用形, or when combining verbs into a compound-verb structure like 入れ込む, but then 連用形 verb forms used as nouns clearly aren't adverbial. Or perhaps we just use "ren'yōkei" and link to the entry to explain what this is? I'm loath to require users to click to some other page to understand things; perhaps we could create a simple template that plops in something like:
''[[連用形#Japanese|<abbr title="Continuative or stem form for verbs, adverb for adjectives: click to see a fuller explanation.">ren'yōkei</abbr>]]''
If the main 連用形 entry is the wrong place for a longer explanation, we could find or create some other glossary or appendix page.
  • While EDICT data may be easier to input, their user interface is ... not so good. For instance, have a look at this search for the English word "egg". We don't get an entry page, instead we get a paged list of everything that includes the string "egg". The expected simple translation isn't shown at first; I had to click through to the 11th page of matches to find .
I vastly prefer our presentation, and presentation capabilities. :)
Cheers, ‑‑ Eiríkr Útlendi │Tala við mig 19:51, 18 December 2019 (UTC)
(Well, Wiktionary searching isn't any better... —Suzukaze-c 02:07, 19 December 2019 (UTC))
No, not when searching that way. But if one searches for just "egg", or goes to the egg entry directly, one gets a list of translations -- which leads directly to the Japanese entry. That's not possible using EDICT, as best I can tell. ‑‑ Eiríkr Útlendi │Tala við mig 22:06, 19 December 2019 (UTC)

JA 師走 with the shihasu readingEdit

Re: diff, it's not so much a synonym as just a (slightly) different reading. More like /təˈmeɪtoʊ/ vs. /təˈmɑːtəʊ/, that kind of thing. It looks like @Poketalker added Etym 2 last December. Looking at the entry now, since both pronunciations are current, have the exact same pitch accent and exact same senses, I'd be tempted to collapse these into one etym and add an explanatory note about the は vs. わ pronunciation. Any strong opinions? ‑‑ Eiríkr Útlendi │Tala við mig 18:14, 18 December 2019 (UTC)


Typo? Chuck Entz (talk) 04:25, 23 December 2019 (UTC)

Yeah. I left a request for help on the Wiktionary Discord server, hoping that someone would fix it before you found it :p —Suzukaze-c 04:28, 23 December 2019 (UTC)
I put the poor page out of its misery. — Eru·tuon 04:41, 23 December 2019 (UTC)

bot requestEdit

Discussion moved to Wiktionary talk:About Japanese#Headword format.

餃子 (yum!)Edit

Heya, re: diff, I'd deliberately used {{ja-kanjitab}} as putting them in the headword template currently results in this confusing mess:

餃子 (ぎょうざ) or 餃子 (ギョウザ) or 餃子 (ギョーザ) (gyōza)

From the reader's point of view, we have three identical kanji representations, with tiny ruby that differ not in reading, but solely in choice of kana. What we want to make clear is that ギョウザ and ギョーザ are alternative forms, which {{ja-kanjitab}} currently does much better than the headword templates.

If you can fix the headline code, that'd be great! Barring that, though, I think {{ja-kanjitab|alt=...}} is the way to go. ‑‑ Eiríkr Útlendi │Tala við mig 19:38, 30 January 2020 (UTC)

@Eirikr: I don't have any particular opinions. @Dine2016, Huhu9001, Poketalker? —Suzukaze-c 22:55, 7 February 2020 (UTC)
@Eirikr: The fact that there are three headwords but one romaji leaves the reader no doubt that they are orthographical variants. That said, I have no problem moving the kana to somewhere else, but moving it to {{ja-kanjitab|alt=...}} has the following problems:
  1. The name of {{ja-kanjitab}} is no longer accurate, and we should replace it with a template like {{ja-spellings}} whose primary role is to show alternative spellings and whose secondary role is to show reading patterns of the kanji spellings. Or better, a morpheme template as in the 精神分裂病 example.
  2. {{ja-kanjitab}} or the new spellings/morpheme template is placed on the right of the page, which is inconvenient for readers with wide screens. I suggest either (1) make the new template not floating, but immediately below the ===Etymology x=== header, or (2) following the approach of English, Chinese, Korean, etc. and showing spelling info in pronunciation section. (Think of the "Pronunciation" as "Reading" (yomi).) --Dine2016 (talk) 04:57, 8 February 2020 (UTC)
@Eirikr: Currently, unnamed parameters in headers are for alternative readings, not alternative spellings. The unnamed parameters are already a "confusing mess" in this case. You need a new parameter, or the code can not tell them apart. -- Huhu9001 (talk) 06:16, 8 February 2020 (UTC)
Really? When I edited mod:ja-headword, there was code to determine whether the current kana is a new reading or a spelling variant of the previous reading. Maybe I deleted part of that code so that its intention was not clear? --Dine2016 (talk) 10:47, 8 February 2020 (UTC)

What should I do on char型Edit

Hello Suzukaze-c! I am unpaired sock.

I have a question with char(チャー)( がた) (chā gata). It is formed with English char + Japanese (かた) (kata). In this case, how should I do in etymology section? If you use Template:com, char will be linked as char#Japanese. But this should be linked as char#English.

Best Regards 片割れ靴下 (talk) 10:26, 7 February 2020 (UTC)

I edited the entry. Does it look good? —Suzukaze-c 22:52, 7 February 2020 (UTC)
Thank you for your cooperation! 片割れ靴下 (talk) 01:03, 9 February 2020 (UTC)


Kinda curious, which POS system should be followed when linking to words in {{ja-usex}}?

  • 学校文法[[行う|行っ]]てください.
  • 日本語教育文法[[行う|行って]]ください.
  • ??? → [[行う|行ってください]].

I prefer the second because it is very close to romaji.

By the way, I'm curious about how Japanese textbooks in the Anglosphere teach verb conjugation. Do they introduce the masu form or the dictionary form first? And what about -te form vs -ta form? --Dine2016 (talk) 04:43, 10 February 2020 (UTC)

  1. 🤷 My current point of view is [[行う|行わ]]ない、[[行う|行え]]る、[[行う|行い]]たい、[[行う|行っ]]た.
    Honestly, I'd rather link to 行って (or perhaps even 行ってください), but Category:Japanese verb forms is very empty.
  2. 🤷 I've actually never opened a Japanese textbook.
Suzukaze-c 05:20, 10 February 2020 (UTC)
Oh, I remember being in a classroom for a while and being baffled at how the dictionary form was being derived from the -masu form. —Suzukaze-c 05:44, 10 February 2020 (UTC)
It's been decades, but ya, English-language beginner-level materials for Japanese start off with the -masu form. I suspect it's because this is the socially safest register for a beginner.
Re: which form to link to, I'd push for [[行って]] over [[行っ]]て. The small-っ for gemination isn't a proper morpheme, so splitting there seems super weird to me. Also, English-language materials treat 行って and 行った as integral, indivisible forms, while ください is generally regarded as a wholly separate word. I'm also a fan of us actually populating the currently-missing entries for ~て, ~た, and other verb forms. ‑‑ Eiríkr Útlendi │Tala við mig 07:26, 10 February 2020 (UTC)

Also, [[言う|言っ]]てしまった、[[する|し]]てしまった、[[言う|言っ]]ちゃった、[[する|し]]ちゃった. —Suzukaze-c 05:02, 16 February 2020 (UTC)

And [[言う]] instead of [[言う|言]]う because it's easier. —Suzukaze-c 06:12, 21 February 2020 (UTC)

Crazy ideaEdit

@Eirikr: I have a crazy idea that would dispense with the need of filling Category:Japanese verb forms:

  1. Modify the inflection templates so that 行く is categorized as
    Category:Terms with form 行か,
    Category:Terms with form 行き,
    Category:Terms with form 行って,
    etc. (CSS may be used to hide the red links at the bottom of entries.)
  2. Then you get something like this.
  3. We can make the searching function even better by having it check Category:Terms with form X when the user searched X. This can be achieved by this mechanism.
    If we take this step, we can soft-redirect not only inflected forms, but all sorts of romaji as well. (In case the romaji leads to an entry in another language, you need to provide both "Go" and "Search" buttons.) Also, we can replace the categories with module tracks.
  4. Finally, we can modify the MediaWiki software so that /wiki/X (whether the page exists or not) automatically displays a list of pages in Category:Terms with form X, above the entry or page-does-not-exist message.

(Sorry for the late reply. I accidentally unwatched this talk page at some time.) --Dine2016 (talk) 17:52, 21 February 2020 (UTC)

Teochew tone sandhi issueEdit

I recently created the pages 走囝, and for some reason it's showing /t͡sau³³⁻²³ kĩã⁵²⁻²¹/ in the IPA section. Why is there tone sandhi in the second character? RcAlex36 (talk) 16:38, 13 February 2020 (UTC)

I'm not sure, but it appears to be a feature of Module:nan-pron, and not a bug. —Suzukaze-c 06:18, 14 February 2020 (UTC)
@justinrleung Just to confirm, is tone sandhi in the second character here an intended feature? RcAlex36 (talk) 04:05, 15 February 2020 (UTC)
@RcAlex36: It's not a bug, but not applicable to all dialects of Teochew. Chaozhou, Chenghai and Jieyang have this 後字變調 that occurs when the first character is 陰上 and the second character is 陰上, 陰去 or 陰入. — justin(r)leung (t...) | c=› } 06:28, 15 February 2020 (UTC)
@justinrleung: I see. Thanks for your reply! RcAlex36 (talk) 06:30, 15 February 2020 (UTC)

Requiring an editEdit

Hi, Suzukaze. Could you please fix and publish my last edit on くびながりゅう?. In a moment of not paying the due attention, I mistakenly use a wrong formatting, using romanization one instead of hiragana one. I tried to fix and appeared a message saying it was forbidden... —This unsigned comment was added by Cpt.Guapo (talkcontribs).

  DoneSuzukaze-c 00:32, 23 February 2020 (UTC)
Thanks a bunch! Have a nice weekend! Cpt.Guapo (talk) 00:35, 23 February 2020 (UTC)
you too! —Suzukaze-c 00:37, 23 February 2020 (UTC)

Just wanted to say thank youEdit

Hi Suzukaze-c, thank you for correcting my mistakes with the Japanese entries. I've been doing Japanese on Duolingo and sometimes I notice Duolingo gives a different translation to here, so that's why I've been editing them. Anyway, just wanted to thank you for all your effort on here :-) CcfUk2018 (talk) 16:26, 10 March 2020 (UTC)

Blockety block blockEdit

Hi. I've got a feeling this user is spamming lots of admins. Could you block the account and protect the project? Or just stand aside and see Wiktionary crumble under the user's terrible vandalism spree. --Vitoscots (talk) 19:41, 26 April 2020 (UTC)

not an admin ✌️ —Suzukaze-c 19:43, 26 April 2020 (UTC)

dummy outEdit

Hey, I just tried to reformat the etymology on the entry dummy out, but I'm not too sure how accurate the etymology is. Since I you're much more equipped with deal Japanese-based terms like this compared to me, can you have a look and fix it if you can? Thanks for helping! — oi yeah nah mate amazingJUSSO ... [ɡəˈdæɪ̯]! 00:38, 7 May 2020 (UTC)

I'm not familar with video game terminology. —Suzukaze-c
Return to the user page of "Suzukaze-c/archive".