Open ronaldtse opened 4 years ago
I believe Clause 4 is supposed to say that the sequence of kanas こうし (ko, u, shi) can be こう•し for "lattice", or こ•うし for "calf". ko and u belong to the same morpheme in the former case (hence kôsi), but different morphemes in the latter (hence kousi).
I will assume that some preprocessing will use •
to mark all morpheme boundaries. This •
will block the application of long vowel rules. If morpheme boundaries are not marked, double letters will be transliterated as long vowels with circumflex.
I believe Clause 4 is supposed to say that the sequence of kanas こうし (ko, u, shi) can be こう•し for "lattice", or こ•うし for "calf". ko and u belong to the same morpheme in the former case (hence kôsi), but different morphemes in the latter (hence kousi).
Right, "calf" is こ•うし (kousi). My typo there.
I will assume that some preprocessing will use • to mark all morpheme boundaries. This • will block the application of long vowel rules. If morpheme boundaries are not marked, double letters will be transliterated as long vowels with circumflex.
Yes. The question is what sort of preprocessing methods we can apply to mark morpheme boundaries. These two examples of こ•うし (子牛) and こうし or こう•し (格子) have their morphemes from kanji usage.
The question is what sort of preprocessing methods we can apply to mark morpheme boundaries. These two examples of こ•うし (子牛) and こうし or こう•し (格子) have their morphemes from kanji usage. Unihan has fields for On/Kun Reading:
Kanji | Kun | On |
---|---|---|
子 | KO MI OTOKO | SHI SU |
牛 | USHI | GYUU |
格 | TADASU ITARU | KOU KAKU KYAKU |
For Kanji compounds / names, if both Kanji and Kana are provided, we can do a search from there:
|
^(こ|み|おとこ|し|す)(うし|ぎゅう)$
\1•\2
, else assume there is no detectable morpheme boundary.(Adjective and verb suffixes need to be handled separately.)
(@chaaklau I've updated the clauses above and they should be complete.)
It seems that morpheme boundaries are impossible to spot accurately unless the Kanji is provided (ML could be used to take context into account to improve accuracy, but not 100%).
The thing is, if the Kanji is provided, we can already derive the most of the Kana using a dictionary (but not all).
It is probably impractical to require people to provided both Kanji and Kana of the same text. Maybe the morpheme boundaries can be an enhancement later on.
The thing is, if the Kanji is provided, we can already derive the most of the Kana using a dictionary (but not all). It is probably impractical to require people to provided both Kanji and Kana of the same text.
This is true for lexical items, but not true for person names and geonames. E.g. 別府 can be べっぷ beppu (Oita prefecture) or べふ behu (Fukuoka prefecture), and the same surname in Kanji could have multiple pronunciations, e.g. 新垣 can be あらがき Aragaki, にいがき Niigaki, or しんがき Singaki.
Maybe the morpheme boundaries can be an enhancement later on.
Agree. Actually there will only be a couple of possible output forms. The sequence おう could only be ô
or ou
, nothing else. Instead of detecting morpheme boundaries, which is difficult in the first place, and is not a pure transliteration problem, how about returning multiple values? E.g. if the source is こうし, return '(kôsi|kousi)'
.
This is true for lexical items, but not true for person names and geonames. E.g. 別府 can be べっぷ beppu (Oita prefecture) or べふ behu (Fukuoka prefecture), and the same surname in Kanji could have multiple pronunciations, e.g. 新垣 can be あらがき Aragaki, にいがき Niigaki, or しんがき Singaki.
Right. I suppose we can allow providing a dual input of Kanji + Kana. Or Kana with pre-set morpheme boundaries?
Agree. Actually there will only be a couple of possible output forms. The sequence おう could only be ô or ou, nothing else. Instead of detecting morpheme boundaries, which is difficult in the first place, and is not a pure transliteration problem, how about returning multiple values? E.g. if the source is こうし, return '(kôsi|kousi)'.
I think it's reasonable to return multiple values. Sounds like a configuration option!
Excerpted from ISO 3602, Clause 2:
Clause 3:
Clause 4:
Clause 5:
Clause 6.