Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: long vowels to and from hiragana transcriptions #17

Open
risseraka opened this issue Apr 4, 2020 · 1 comment
Open

Discussion: long vowels to and from hiragana transcriptions #17

risseraka opened this issue Apr 4, 2020 · 1 comment

Comments

@risseraka
Copy link
Collaborator

Hi there,

Me again cheers.

As per my understanding after a few readings (I admit, I started from Wikipedia and then did some more research), use of chōonpu in hiragana is extremely rare (e.g. in some manga to add emphasis).
Hence, it not being written down in src/hepburn.js in hiragana trigrams seems normal.

Moreover, Ō seems like it can be transcribed either as OU or OO in hiragana.
E.g. TŌKYŌ is actually TOUKYOU, whereas ŌZEKI is OOZEKI.

toHiragana("CHŌ")
// could be either
// ちょう
// or
// ちょお

That being said, the lib could probably take an extra step and transcribe some valid romaji when there is no ambiguity (i.e. A, E, I and U)
E.g.:

toHiragana("CHĀ")
// ちゃあ

On the other hand, repeated vowels in hiragana cannot safely be transcribed in romaji using the macron (eh) diacritic « ¯ ».
E.g.

fromKana("からあげ")
// KARAAGE
// 唐(から)揚(あ)げ
// KARĀGE would be wrong here

So, transcribing long vowels from romaji to hiragana and back could yield a different romaji, breaking symetrical transcription.

WDYT?

Cheers.

@lovell
Copy link
Owner

lovell commented Apr 11, 2020

I'm unsure if a true symmetric relationship is possible with transliteration, especially when attempting to deal with both spoken as well as written language.

Do the OO vs OU variants relate to wāpuro? https://en.wikipedia.org/wiki/W%C4%81puro_r%C5%8Dmaji

Definitely happy for improvements for situations where there is no ambiguity, as in the examples you point out. I'll add you as a contributor to this repo so you can help out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants