Change log entry 80721 | |
---|---|
Processed by: | richwarm (2023-11-06 00:58:19 UTC) |
Comment: |
<< review queue entry 74915 - submitted by 'encn' >> 我提议稍微修改 CC-CEDICT 格式,为一些词条增加“变体行”,列出变体。 变体行以"VAR:"开头,繁体简体用"|"隔开,不必写出拼音;如果存在多个变体,则用逗号","分隔。 这么改的好处:1、词典用户不用去查单字(比如本例中的“占”),就能看到变体;2、词典软件开发者(愿意的话)可以解析"VAR:擠佔|挤占",获得另一个 headword “擠佔”供用户查询。3、此修改不会造成任何破坏。 ---------------------------------- Editor: The format you propose is one way to do it. Other dictionaries have equivalent approaches: 挤占[擠佔/-] ... {ABC style} 擠占 挤占 ... 也作「擠佔| 挤占」。 {兩岸詞典 style} and so on. But obviously, we have taken a minimalist approach, trying to avoid including elements that could be regarded as redundant. App developers can, even now, if they choose, a) display a note that there is a variant 擠佔 when a user looks up 擠占 b) display the entry for 擠占 when a user looks up 擠佔 by having the app check whether either of the component characters of the search term has a variant form. ... or by generating an expanded version of cc-cedict in which there is an entry for 擠佔 derived from the following two entries: 擠占 挤占 [ji3 zhan4] /to seize/to push aside and occupy/ 佔 占 [zhan4] /variant of 占[zhan4]/ (and so on for other variants) ... and using the expanded version for their app rather than using cc-cedict in its raw form. You may well have a counterargument, and I'd be open to listening, but use email rather than posting via the reviewing queue. How would you propose to add the VAR-column data? All in one go, automatically? If so, what's to stop app developers doing so themselves? |
Diff: |
# - 擠占 挤占 [ji3 zhan4] /to seize/to push aside and occupy/ # + 擠占 挤占 [ji3 zhan4] /to seize; to push aside and occupy/VAR:擠佔|挤占/ |