syntax_v2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| syntax_v2 [2026/06/20 13:30] – [Traditional and simplified characters] kbaiko | syntax_v2 [2026/08/29 19:10] (current) – [Technical details, and the use of {}] kbaiko | ||
|---|---|---|---|
| Line 50: | Line 50: | ||
| The Chinese word should consist of one or more Chinese characters, without any spaces in it. Both traditional and simplified forms should be provided, and the two must have the same length. | The Chinese word should consist of one or more Chinese characters, without any spaces in it. Both traditional and simplified forms should be provided, and the two must have the same length. | ||
| - | For an official mapping between simplified and traditional characters, one can refer to the 通用规范汉字表. | + | For an official mapping between simplified and traditional characters, one can refer to the 通用规范汉字表. |
| - | In particular, the traditional characters | + | CC-CEDICT prioritizes real-life usage over what the 通用规范汉字表 and various print dictionaries say. In particular, |
| < | < | ||
| Line 60: | Line 60: | ||
| </ | </ | ||
| - | For some more examples of how to parse the 通用规范汉字表 into CC-CEDICT entries, see https:// | + | (For more information on the " |
| - | In rare cases, characters are simplified based on "word-level simplification" | + | Another discrepancy lies in 睾 - the 通用规范汉字表 indicates the traditional and simplified forms are the same, but in Taiwan, this character is most commonly written as 睪, which does not appear in the 通用规范汉字表 at all, while 睾 is still used but less common. Consequently our entries are |
| - | | + | < |
| - | * 份子|分子[fen4zi3] - 份 does not officially simplify to 分 | + | 睪 睾 [[gao1]] /.../ |
| - | * 座標|坐标[zuo4biao1] - 座 does not officially simplify to 坐 | + | 睾 睾 [[gao1]] /variant of 睪|睾[gao1]/ |
| + | </ | ||
| + | |||
| + | For words with multiple characters, characters can be simplified one-by-one, for example 書畫 is simplified to 书画 by converting 書 to 书 and 畫 to 画. In a very small number of cases, we practice " | ||
| + | |||
| + | | ||
| + | * 份子|分子[fen4zi3] - 份 is not considered a traditional form of 分 | ||
| + | * 座標|坐标[zuo4biao1] - 座 is not considered a traditional form of 坐 | ||
| These entries introduce " | These entries introduce " | ||
| Line 282: | Line 289: | ||
| When parsing the traditional and simplified fields, Hanzi and numbers are treated as individual sections, while consecutive English letters are grouped together into a single section. For example a hypothetical headword " | When parsing the traditional and simplified fields, Hanzi and numbers are treated as individual sections, while consecutive English letters are grouped together into a single section. For example a hypothetical headword " | ||
| - | The pinyin is first split by spaces and punctuation, | + | The pinyin is first split by spaces and punctuation, |
| It is a requirement that the number of parsed sections in the Hanzi matches the number of parsed sections in the pinyin. For the vast majority of entries, this does not pose a problem. Almost all Chinese characters are one syllable in length, and due to how the parsing logic works, numbers and English letters will be parsed correctly as long as the pinyin is segmented correctly. Problems arise in rare situations such as | It is a requirement that the number of parsed sections in the Hanzi matches the number of parsed sections in the pinyin. For the vast majority of entries, this does not pose a problem. Almost all Chinese characters are one syllable in length, and due to how the parsing logic works, numbers and English letters will be parsed correctly as long as the pinyin is segmented correctly. Problems arise in rare situations such as | ||
syntax_v2.1781962223.txt.gz · Last modified: by kbaiko
