You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just realized that there is a problem that the romanization spelling used in the Cantonese section of the 開放辭典 is the Yale. Since the data is originally in the Yale scheme, some of the pronunciation elements (e.g., eo, eu, ep, and oe) that exist in Jyutping cannot be converted correctly (perfect correspondingly), and as a result, some words and phrases may be distorted after being converted.
Share some references from other research:
耶魯拼音中,/a/ 喺開音節用 a 表示,閉音節用 aa。/ɐ/ 喺閉音節中用 a 表示,無法表示開音節 /ɐ/。
耶魯方案唔區分 /ɵ/ 同埋 /œ/,兩者都用 eu 嚟表示。亦都因爲噉耶魯拼音無法表示 /ɛːu/ 呢個音。
耶魯用附加符號 ˉˊ 同埋字母 h 嚟表示聲調(新版本加入咗數字標調)。
睡 /sɵi˨/
掉 /tɛːu˨/
𠰲 /œt˨/
耶魯
seuih
無法表示
無法表示
粵拼
seoi6
deu6
oet6
To avoid the continuation of this issue, it is recommended that the 開放詞典 convert all Yale in original data to standard Jyutping, and from then on use Jyutping for new words and phrases, so as to avoid the distortion of conversion between spelling systems by adding new words and phrases with continuing use of Yale.
The text was updated successfully, but these errors were encountered:
I just realized that there is a problem that the romanization spelling used in the Cantonese section of the 開放辭典 is the Yale. Since the data is originally in the Yale scheme, some of the pronunciation elements (e.g., eo, eu, ep, and oe) that exist in Jyutping cannot be converted correctly (perfect correspondingly), and as a result, some words and phrases may be distorted after being converted.
Share some references from other research:
To avoid the continuation of this issue, it is recommended that the 開放詞典 convert all Yale in original data to standard Jyutping, and from then on use Jyutping for new words and phrases, so as to avoid the distortion of conversion between spelling systems by adding new words and phrases with continuing use of Yale.
The text was updated successfully, but these errors were encountered: