[CLOSED]

User avatar
fuzzball
Posts: 1827
Joined: Mon Jun 08, 2026 1:26 am

Re: [CLOSED]

Post by fuzzball »

deleted
Last edited by fuzzball on Sun Aug 26, 2018 7:32 am, edited 1 time in total.
F1ReB4LL
Posts: 3395
Joined: Mon Jun 08, 2026 1:26 am

Re: [CLOSED]

Post by F1ReB4LL »

fuzzball wrote:In the first place, why "ō" was "ou"?
Toukyou – written using kana spelling: ō as ou or oo (depending on the kana) and ū as uu. That is sometimes called wāpuro style, as it is how text is entered into a Japanese word processor by using a keyboard with Roman characters. The method most accurately represents the way that vowels are written in kana by differentiating between おう (as in とうきょう(東京), written Toukyou in this system) and おお (as in とおい(遠い), written tooi in this system). However, using this method makes the pronunciation of ou become ambiguous, either a long o or two different vowels: o and u.
https://en.wikipedia.org/wiki/Hepburn_r … Variations
Unlike Kunrei and Hepburn, wāpuro style is based on a one-to-one transcription of the kana.[1] Wāpuro thus does not represent some distinctions observed in spoken Japanese, but not in writing, such as the difference between /oː/ (long vowel) and /oɯ/ (o+u). For example, in standard Japanese the kana おう can be pronounced in two different ways: as /oː/ meaning "king" (王),[2] and as /oɯ/ meaning "to chase" (追う).[3] Kunrei and Hepburn spell the two differently as ō and ou, because the former is a long vowel while the latter has a o that happens to be followed by a u; however, wāpuro style simply transcribes the kana and renders them both as ou.
https://en.wikipedia.org/wiki/W%C4%81pu … c_accuracy
User avatar
fuzzball
Posts: 1827
Joined: Mon Jun 08, 2026 1:26 am

Re: [CLOSED]

Post by fuzzball »

closed
Last edited by fuzzball on Sun Aug 26, 2018 5:31 am, edited 1 time in total.
sarami
Posts: 1762
Joined: Mon Jun 08, 2026 1:27 am

Re: [CLOSED]

Post by sarami »

fuzzball wrote:おとうさん (お父さん) = otōsan = otoosan
おおかみ (大神/狼) = ōkami = ookami
F1ReB4LL wrote:But as far as I understand, No-Intro uses "Ou" for these with the exception for things like "ōkami", which transcription isn't "オーカミ", but "オオカミ".
http://www.mext.go.jp/b_menu/hakusho/nc … 01001.html

Code: Select all

6  次のような語は,オ列の仮名に「お」を添えて書く。

例  おおかみ  おおせ(仰)  おおやけ(公)  こおり(氷・郡△)  こおろぎ  ほお(頬*・朴△)  ほおずき  ほのお(炎)  とお(十)

いきどおる(憤)  おおう(覆)  こおる(凍)  しおおせる  とおる(通)  とどこおる(滞)  もよおす(催)

いとおしい  おおい(多)  おおきい(大)  とおい(遠)  おおむね  おおよそ

これらは,歴史的仮名遣いでオ列の仮名に「ほ」又は「を」が続くものであって,オ列の長音として発音されるか,オ・オ,コ・オのように発音されるかにかかわらず,オ列の仮名に「お」を添えて書くものである。

Code: Select all

(5)  オ列の長音

オ列の仮名に「う」を添える。

例  おとうさん  とうだい(灯台)

わこうど(若人)  おうむ

かおう(買)  あそぼう(遊)  おはよう(早)

おうぎ(扇)  ほうる(抛*)  とう(塔)

よいでしょう  はっぴょう(発表)

きょう(今日)  ちょうちょう(蝶*々)
That is to say, otōsan is otousan, ōkami is ookami.
DiscImageCreator, UmdImageCreator, Conv2multiBin, bin2wav, PS3Auth (needs login), [url=http://www.mediafire.com/file/5cgoy11x6ahc7qh/%2523recompressTo7z_20150109.bat/file]recompressTo7z_20150109.bat[/url]
User avatar
fuzzball
Posts: 1827
Joined: Mon Jun 08, 2026 1:26 am

Re: [CLOSED]

Post by fuzzball »

sarami wrote:That is to say, otōsan is otousan, ōkami is ookami.
It is not pronunciation.

By the way, I closed this topic.
Please do not comment.
Last edited by fuzzball on Sun Aug 26, 2018 7:30 am, edited 1 time in total.
F1ReB4LL
Posts: 3395
Joined: Mon Jun 08, 2026 1:26 am

Re: [CLOSED]

Post by F1ReB4LL »

Eh. Such discussions help to better understand Japanese, no need to be nervous about the questions. I think we should use the proper macrons in the main db and do the oo/ou conversions for the datfiles only, but there should be an agreement about the conversion rules. The problem is that all the Hepburn variants use macrons, so for the macrons => ASCII conversion we need to choose some other romanization variant as an additional one. No-Intro doesn't help on that matter at all, I've once tried to discuss the naming with them, ended with nothing - http://forums.no-intro.org/viewtopic.ph … 005#p18332
If you think we don't respect your opinion on the rules of your native language - that's not true, I can make you a mod, if you want, so you could fix all the titles by yourself, but we still need a strong naming convention (for both romanized and non-romanized titles) that would describe all the non-standard cases.
Post Reply