User talk:Fish bowl/archive

Latest comment: 2 months ago by in topic ポケットモンスター




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

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



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)Reply

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)Reply
Oops. It's better this way, note 度{dou6}:
  1. 阿伯成日喺度食煙到死 [Cantonese, trad.]
    阿伯成日喺度食烟到死 [Cantonese, simp.]
    jau5 go3 aa3 baak3 seng4 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)Reply
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)Reply
No worries, updated the doc. --Anatoli T. (обсудить/вклад) 03:04, 21 January 2015 (UTC)Reply
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)Reply

I see (´∀`;) Updated documentation would be good. —umbreon126 05:41, 11 March 2015 (UTC)Reply
Your edit was right because it's a proper noun (exception) :) --Anatoli T. (обсудить/вклад) 05:55, 11 March 2015 (UTC)Reply
ah. oops —umbreon126 05:57, 11 March 2015 (UTC)Reply
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)Reply

Explanation for edit version at


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

See the edit history (summary?) —umbreon126 05:00, 28 March 2015 (UTC)Reply
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)Reply
It's fine :) —umbreon126 05:05, 28 March 2015 (UTC)Reply



4 :]

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

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

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)Reply
-@[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)Reply


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

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)Reply



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

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



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,icReply

下單 and 落單


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)Reply


edit entrycreator dunworkwel4zh>contctYAIRAND? 08:54, 14 June 2015 (UTC)Reply

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)Reply

pl.vluk at


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)Reply

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



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

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



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)Reply

"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)Reply




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

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


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)Reply

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

Chinese chemical element articles and


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)Reply

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):

"Compounds" section - conversion to traditional character words error


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)Reply

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


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)Reply

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)Reply




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)Reply

Got it. —suzukaze (tc) 00:15, 13 July 2015 (UTC)Reply
(I feel that it would be beneficial for 異體字 pages like 𢇅 though...) —suzukaze (tc) 00:40, 13 July 2015 (UTC)Reply
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)Reply
@Atitarev What about , 𫔭, and ? —suzukaze (tc) 05:39, 29 July 2015 (UTC)Reply‎


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)Reply

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

The citation of ふいんき


 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)Reply

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)Reply
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)Reply
Go ahead. —suzukaze (tc) 08:48, 3 August 2015 (UTC)Reply
Thank you for your cooperation and I apologize to you for this trouble. --エリック・キィ (talk) 04:03, 11 August 2015 (UTC)Reply


POS at


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)Reply

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)Reply



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,abrviatedvrsnReply

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

Overlapping kanji readings and kana?


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)Reply

口走る 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)Reply
  • 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)Reply



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)Reply

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)Reply


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

需#Chinese and the Old Chinese gloss


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)Reply

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)Reply

Some things I want to talk about


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)Reply

  • {{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)Reply




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

Hello again!


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)Reply

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)Reply

Hello again (again)!


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)Reply

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)Reply



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

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)Reply
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)Reply
リア充 (someone with a fulfilling life in the real world) + 爆発する (to explode) + しろ (imperative form of する) —suzukaze (tc) 01:43, 31 October 2015 (UTC)Reply
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)Reply
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)Reply
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)Reply
@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)Reply
  • @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)Reply

Hakka Dictionary


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)Reply

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

Atitarev's removal of Chinese section from


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)Reply

A common courtesy...


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)Reply

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)Reply

Korean word article edit reversions


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)Reply

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)Reply
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)Reply
Better examplesuzukaze (tc) 14:51, 31 December 2015 (UTC)Reply
Okay, I obviously was totally confused about the situation with those word spellings. Bumm13 (talk) 06:02, 1 January 2016 (UTC)Reply

Vietnamese Nouns in Han Script


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)Reply

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)Reply
Then you could examine {{ko-noun}} for ideas. --Lo Ximiendo (talk) 04:53, 10 January 2016 (UTC)Reply
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)Reply
@Lo Ximiendo

Module:ja-kanjitab table layout


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)Reply

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)Reply
  • 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)Reply
It should be good now (ゝω・)b —suzukaze (tc) 22:45, 18 January 2016 (UTC)Reply



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

Thanks for your editing!


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)Reply

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

ow2mov pp?

edit 21:11, 28 January 2016 (UTC)Reply

"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)Reply

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



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)Reply
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)Reply

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

Possible bug in Template:zh-pron


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)Reply

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)Reply

frame/()<wotmeanin pl?


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)Reply
I'm not sure what you mean by "frame" :( —suzukaze (tc) 10:02, 7 February 2016 (UTC)Reply

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

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)Reply

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



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

[2]suzukaze (tc) 10:08, 7 February 2016 (UTC)Reply
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)Reply
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)Reply

canu'v aluk?

edit 12:45, 10 February 2016 (UTC)Reply

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)Reply

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



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)Reply

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)Reply
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)Reply
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)Reply



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)Reply

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

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


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)Reply

Wiktionary:Requests for deletion


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

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)Reply
Ah, ok. What a relief :-) --Robbie SWE (talk) 10:39, 2 March 2016 (UTC)Reply

歌 vs 唄

edit --kc_kennylau (talk) 14:52, 7 March 2016 (UTC)Reply

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)Reply

Extended shinjitai and Asahi characters


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)Reply



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

The site is displaying errors for me. —suzukaze (tc) 02:48, 21 March 2016 (UTC)Reply
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)Reply
I'm just following the file talk page and file description. —suzukaze (tc) 04:39, 22 March 2016 (UTC)Reply



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)Reply

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)Reply
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)Reply
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)Reply
(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)Reply
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)Reply



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)Reply

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)Reply
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)Reply
The list is super long though; is diff okay? It's still in alphabetical pinyin order. —suzukaze (tc) 09:30, 27 March 2016 (UTC)Reply
Genius! I will edit this way in the future for long lists. Many thanks. ---> Tooironic (talk) 09:33, 27 March 2016 (UTC)Reply

Triad of /


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


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

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


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)Reply

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

ZH 石綿


I'm curious about your recent revert. The ZH WP article itself lists 石綿石绵 (shímián) 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)Reply

I assumed Wyang knew what he was doing. Perhaps I should've checked first :/ —suzukaze (tc) 21:51, 25 April 2016 (UTC)Reply

Character compounds


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)Reply

Pseudo-Japanese BS


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)Reply

display of measure words


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)Reply

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)Reply



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)Reply



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

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

對唔住,我唔識法文。 —suzukaze (tc) 21:51, 23 May 2016 (UTC)Reply
@Fête Phung: I've helped you asked the deleter. --kc_kennylau (talk) 02:10, 12 June 2016 (UTC)Reply
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)Reply

new sense at 溫馨


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

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)Reply

Something you might want to see


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)Reply

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



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



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)Reply

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)Reply
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)Reply
Alas Wiktionary is not a database... —suzukaze (tc) 05:49, 16 June 2016 (UTC)Reply
こうしょう#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)Reply

Module error at


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)Reply

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

On my reverted edit


 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)Reply時&diff=next&oldid=38585994suzukaze (tc) 21:30, 17 June 2016 (UTC)Reply

Music Memory?

Discussion moved to User talk:Lo Ximiendo.

Sort args in etymologies


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)Reply

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)Reply

Kanji entries that lack Chinese entries


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)Reply

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)Reply
Or do you mean Japanese kanji entries without Chinese? There's this. —suzukaze (tc) 23:41, 30 June 2016 (UTC)Reply
The latter, yes, thanks! ---> Tooironic (talk) 04:12, 1 July 2016 (UTC)Reply

hiragana to kanji pages


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)Reply

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


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)Reply

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)Reply



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

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)Reply



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)Reply

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)Reply

Thank you for your thanks!


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)Reply

Japanese renyoukei


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

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)Reply
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)Reply
  • 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)Reply
PS: @Suzukaze, sorry for the lag -- I never saw the ping.

JA misspellings


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)Reply

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



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

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

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


edit 02:48, 8 August 2016 (UTC)Reply

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


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)Reply

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)Reply



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

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



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


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



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)Reply

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)Reply



Incomplete sentence?


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)Reply



   (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)Reply



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)Reply

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)Reply

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

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

breakfast cereal


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)Reply

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 templates


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)Reply

Julien Daux (talk) 17:29, 12 September 2016 (UTC)Reply
@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)Reply
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)Reply

Yeah, no.


   (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)Reply

@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)Reply

Reason for reversion at ?


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

@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)Reply

Japanese combining forms


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)Reply

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



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

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)Reply

Curious about Korean reading "evolutions"


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)Reply

@Bumm13 User talk:Atitarev#Question regarding '>' on hanja entries. —suzukaze (tc) 06:32, 11 October 2016 (UTC)Reply
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)Reply

Zen Buddhism


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

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

Mandarin reading


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)Reply

Possible bug in Module:nan-pron


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)Reply

@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)Reply

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


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)Reply

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



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)Reply

"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)Reply
Can 咱們 be replaced with 我們? 我們 seems more common. – AWESOME meeos * (「欺负」我01:36, 8 November 2016 (UTC)Reply

(@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))Reply

Data for Middle Chinese


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)Reply

@Awesomemeeos: I'm not sure. Wyang is the one who set up the system. —suzukaze (tc) 00:30, 9 November 2016 (UTC)Reply
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)Reply

Module errors due to Module:ja etc.


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

Category:Zhuang Sawndip forms


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

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)Reply

Incomplete Dubeolsik support


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)Reply

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)Reply

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)Reply

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)Reply

Silly translation


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)Reply

禮拜 [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)Reply

Min Nan readings


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)Reply

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)Reply
@Bumm13: TBH, it's not a very common character. Here's what I found so far:
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)Reply



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

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

Template:za-sawndip form of


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)Reply

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



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

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



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)Reply

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

Translingual Braille


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)Reply

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)Reply
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)Reply




A' 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)Reply
  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)Reply
suzukaze (tc) 10:03, 22 January 2017 (UTC)Reply
@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)Reply
  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)Reply

Irregular Korean pronunciation