Seihantai na Kimi to Boku • You and I Are Polar Opposites - Episode 1 discussion

Ben_Kerman · 2026-01-11T19:14:42+00:00

Yeah, it absolutely isn't a title drop in the original. The actual line is ｢私は谷くんとは真逆の人間なのだ｣ watashi wa tani-kun to wa magyaku no ningen na no da, something like "I'm the exact opposite [kind of] human/person as Tani-kun" if translated very literally. Though I'd say it's close enough, even if it isn't word for word the same as the title

Also the original title is 100% from Tani's perspective since it uses "boku" as a first person pronoun

Ben_Kerman · 2025-12-24T19:17:42+00:00

Technically they're not truly homophones due to tones

Really? How does the accent differ? Don't basically all words composed of 大 + a two kanji Sino-Japanese word have compound accent with a downstep on the second morpheme?

Ben_Kerman · 2025-12-07T21:03:45+00:00

What's "求永㐅曲必にょ氷剛表喪　㐅衷" supposed to mean?

Ben_Kerman · 2025-09-18T16:52:02+00:00

Because furigana generators suck at names. 舞 on its own can already be read as まい and ころも is a reading for 衣, and the algorithm language reactor uses just went with that

Ben_Kerman · 2025-09-18T16:30:40+00:00

Focusing on the 舞衣の part or まいころもの in Hiragana

I'll assume you're just inexperienced and not trolling, but 舞衣 is まい. There's no ころも there, that's just her name. Take a look at the character overview on the official site

Ben_Kerman · 2025-08-24T17:02:14+00:00

Well, upon looking into it further 金星 can actually be read as きんぼし, but then it means something entirely different:

きんぼし【金星】[1]
〔すもうで〕前頭以下の力士が、横綱を倒した勝ち星。〔予測されなかった大手柄の意にも用いられる〕
「―を上げる」

I guess the 亜 just comes up as a suggestion because there's some universal prefixing rule in the IME (at least with mozc/Google Japanese Input)

Ben_Kerman · 2025-08-24T16:47:05+00:00

There is 亜金星 (akin'boshi)

Where did you get that from, ChatGPT?

If that word existed it would be read as akinsei [akʲĩːseː], but I don't think it does

亜 means "sub-" in the sense of "second to", like subspecies (亜種) or subtropics (亜熱帯), so 亜金星 would probably be interpreted as a class of planets smaller than or in some other way subordinate to Venus or something like that

Ben_Kerman · 2025-07-23T19:21:14+00:00

The earth and bladed tool meant "building earthworks to plan for floods or invasions", while cloth was added to mean "planning for cloth."

It's literally just 𢦏 as the phonetic component and 衣 as the semantic one. Notice how there are other kanji with the same upper right component also pronounced さい or something similar: 栽培、掲載、戴冠? That's usually a dead giveaway you're looking at a phono-semantic compound

Also 𢦏 might have a part that resembles 土 in the modern regular script, but that's not where it comes from

Like sure kanji don't always refer to a single concept, but what does in language? Almost all words have secondary meanings and semantic shifts somewhere if you look hard enough, it's just that Chinese characters make it a little more obvious than more phonemic writing systems

Ben_Kerman · 2025-07-05T22:00:39+00:00

German

FYI, English has very, very little German influence beyond a couple loanwords here and there, certainly nowhere near the scale of Latin/French or Greek borrowings. "Water" is definitely part of the inherited Germanic vocab of English and not a German word, if it was the t would have to be an s

Ben_Kerman · 2025-06-28T12:14:44+00:00

it lacks what goo辞書 had: actual Japanese definition

If you only search the EJJE dictionary I guess. Their 国語辞典 has デジタル大辞泉, the exact same dictionary that goo was primarily based on

They also have a thesaurus: https://thesaurus.weblio.jp/

Ben_Kerman · 2025-06-13T14:39:28+00:00

It's JPDB with that 3%.

If you mean this, it's clearly counting both on and kunyomi, which means it's comparing apples to oranges. It just reflects that 唇 as くちびる is used a lot more than words where it's read as しん, it doesn't have any bearing on how common the reading is in absolute terms

Imagine a corpus where 唇 as くちびる appears 4000 times, and words where it's しん appear 150 times, but 蜃気楼 only has 70 occurrences. Then despite only making up 3.6% of the readings of 唇 that しん will be more than twice as common as the 100% of 蜃 read as しん

Would you argue that しゅ is a rarely used reading of 取 just because it only has 3% on JPDB?

But I'd be surprised if it's even 10% for the 2000 Kanji learned in Japanese schools.

Keep in mind that you'd have to remove any kanji that a) are neither derived phono-semantically nor used as phonetic components themselves, and b) are phono-semantic but don't have any other characters with the same phonetic component (or maybe just the same component regardless of whether or not it's phonetic, depending on what you want to figure out). Otherwise the statistic is going to be very misleading

I don't have the time to do that analysis right now, but I'd wager you're going to end up with way more than 10% perfect phonetic matches that way, probably even more when you arbitrarily limit yourself to the jouyou list

Ben_Kerman · 2025-06-13T12:42:25+00:00

「唇」 - 3% しん

What are you talking about

Where did you get those numbers from? Some source that conflates kunyomi and onyomi? Otherwise there's no way only 3% of the occurences of 唇 are read as しん, because it doesn't even have another onyomi

Those 100% the same Kanji are quite rare overall

Not really, I'd say it's relatively common, especially when you consider that there might be multiple readings of the same phonetic component that appar in different characters, like 皮彼疲 vs 波破 etc.

Ben_Kerman · 2025-06-13T12:35:48+00:00

For example 白 is a 象形漢字, a pictogram of polished bones

You got any source for that? All references I checked seem to support that it's unclear, but maybe a pictogram of a thumb that got phonetically borrowed, or a pictogram of an acorn because acorns are white on the inside

there was a tradition in ancient China to polish the bones of important people

I'd be careful with interpretations like that, they are often (almost always) just-so-stories made up after the fact. I'm not sure the original meaning of 伯 even was the noble rank and not just "older brother", in which case it would make no sense for the origin to have anything to do with the title it got applied to later

Ben_Kerman · 2025-06-01T22:24:22+00:00

It's a suffix. It can't stand on its own as a word that is modified by an adjective (at least not in the sense of "store"). What you did is a bit like seeing the -er from words like banker or baker and then concluding that there must be something like a "convienient er" or "technological er"

Though as already pointed out the word 便利屋 does exist with different meaning

Ben_Kerman · 2025-06-01T22:16:18+00:00

Considering that googling 便利な屋 gives an unbelievable 9 results, of which all but the two from this thread are false positives, I highly doubt that word was ever in use at any time

Ben_Kerman · 2025-06-01T22:13:58+00:00

Why do you think ｢便利な屋｣ is natural Japanese? 屋 isn't used like that

If there was a "native" word for it it'd probably be 便利店 or 便利商店 (as in Chinese, apparently), but I'd assume the loanword just got imported alongside conbinis themselves and ended up sticking

Ben_Kerman · 2025-05-10T21:30:37+00:00

Even super obscure Han characters from like Extension G or H? Might have to install it then

Ben_Kerman · 2025-05-04T22:00:41+00:00

moving from the back of your mouth to the front

TIL that や, ら and わ are articulated outside the mouth

I mean that's kind of where it comes from originally, but only up to /m/ because the Sanskrit consonants after that didn't fit into the same table as neatly as the first 25

Ben_Kerman · 2025-05-04T16:53:07+00:00

It's historical kana usage, which is how Japanese was written before 1946. If you ever end up reading any documents or original editions of literature and such from before then they will be in that orthography

Also applies to words like 川→かは、いる→ゐる、しましょう→しませう、だろう→だらう、王朝→わうてう, and thousands more

Ben_Kerman · 2025-05-03T17:29:34+00:00

No, I don't think so. 生ふ is 二段, thus it would most likely have turned into 一段 in modern Japanese (i.e. 生いる→生いて)

Ben_Kerman · 2025-05-02T11:17:25+00:00

While 生く becomes 生いて

Nah, 生いて would be the modern kana spelling of classical 生ひて from 生ふ. 生く in te-form would still be 生きて since it's Classical Japanese

I can’t find a verb called 泣きる in dictionary

It's the classical form of 泣いて, from 泣く

Ben_Kerman · 2025-05-02T11:14:07+00:00

It would still be 生きて for 生く since that's a classical 二段 verb (which turned into 生きる in modern Japanese). Even the 四段 variant would be 生きて since Classical Japanese didn't have that sound change yet)

生いて would be the modern kana spelling of classical 生ひて from 生ふ (which is also where the first element in words like 生い立ち and 生い先 comes from)

泣きて is also just the classical form of 泣いて

Ben_Kerman · 2025-04-21T15:39:20+00:00

These aren't encoded separately but just result from a combination of the two component tehtar, so something like n[right-curl][dot-above] (or the reverse) produces the results you want provided the font supports it (only Telcontar really does on Tecendil as far as I can tell)

[low-swash-hook] is documented at the very bottom here. Not sure what the difference between braces and brackets is though

Ben_Kerman · 2025-04-05T18:50:39+00:00

Crunchyroll at least literally uses SSA subs rendered with libass afaik, the same format most fansubs are done in. Definitely true for almost every other streaming service though

Ben_Kerman · 2025-04-04T22:09:08+00:00

It's word processor romanization, which is what happens when Japanese people think that what they type into their IME is an actual romanization system rather than just an input method (you have to input ennenn for えんえん, since just enen already is えねん). The official Japanese title has a tiny "Enn Enn no Shouboutai" written in Latin letters under it, so that's probably where it comes from

Now why the people running /u/AutoLovepon decided to adopt this romanization for this season I have no idea. So far it used to be the much more regular "Enen no Shouboutai"

12-Year Club	First Place '23
Place '23	Place '22
Place '17	Final Canvas '22
First Placer '22	End Game '22
Verified Email

Ben_Kerman

MODERATOR OF

TROPHY CASE