Login

View change log entry

Navigation:  ◀ 94706  94708 ▶ 

Change log entry 94707
Processed by: kbaiko (2026-04-17 14:08:49 UTC)
Comment: << review queue entry 86759 >>
[[{...}]] messes up the preprocessor that splits the pinyin for the output data set. Use [[..]] or [...]. These were the only characters in the current output data with pinyin that did not have spaces. (And subsequently broke something I was using.)

Note 1: Additionally, I tried to search on this site for '[[{' but I get nothing. I'm not sure if there is a way to do literals or regex or get the current full export to check for other similar issues.

Note 2: It doesn't help me to search the final data set because most of the extra characters in the pinyin gets removed before the final csv output. Feels like a data standardizer script should rip through here and force a convention for some things and flag the rest. (probably for all sorts of things. and then archive the scripts for reuse.)

----------
Editor:

>[[{...}]] messes up the preprocessor
>(And subsequently broke something I was using.)

If this is your own script, I suggest you update your code to handle this case.
If it's a 3rd party tool, I suggest you contact their developer to do so.

>These were the only characters in the current output data with pinyin that did
not have spaces

I'm not sure what you mean by this. None of the single-character entries have
spaces in the pinyin, and the majority of v2 two-character entries do not have
spaces either.

>I'm not sure if there is a way to do literals or regex or get the current full
export to check for other similar issues.

You can download the full dictionary[1] (it's just a text file) and search it.
But to save you some time, the entries in this submission, along with

{coser} {coser} [[{coser}]] /cosplayer/

are the only ones with {} in the pinyin.

>Note 2: It doesn't help me to search the final data set because most of the
extra characters in the pinyin gets removed before the final csv output

I don't know what "final data set" or "final csv output" refer to here, but
again, if this is a program you are developing yourself, you will have to handle
the case of {} in the pinyin

[1] https://cc-cedict.org/editor/editor.php?handler=Download
Diff:
# - 兡 兡 [[{bai3ke4}]] /(old) contracted variant of 百克[bai3ke4]/
# + 兡 兡 [[bai3ke4]] /(old) contracted variant of 百克[bai3ke4]/
 
# - 粨 粨 [[{bai3mi3}]] /(old) contracted variant of 百米[bai3mi3]/
# + 粨 粨 [[bai3mi3]] /(old) contracted variant of 百米[bai3mi3]/
 
# - 瓸 瓸 [[{bai3wa3}]] /(old) contracted variant of 百瓦[bai3wa3]/
# + 瓸 瓸 [[bai3wa3]] /(old) contracted variant of 百瓦[bai3wa3]/
 
# - 兝 兝 [[{fen1ke4}]] /(old) contracted variant of 分克[fen1ke4]/
# + 兝 兝 [[fen1ke4]] /(old) contracted variant of 分克[fen1ke4]/
 
# - 瓰 瓰 [[{fen1wa3}]] /(old) contracted variant of 分瓦[fen1wa3]/
# + 瓰 瓰 [[fen1wa3]] /(old) contracted variant of 分瓦[fen1wa3]/
 
# - 兞 兞 [[{hao2ke4}]] /(old) contracted variant of 毫克[hao2ke4]/
# + 兞 兞 [[hao2ke4]] /(old) contracted variant of 毫克[hao2ke4]/
 
# - 瓱 瓱 [[{hao2wa3}]] /(old) contracted variant of 毫瓦[hao2wa3]/
# + 瓱 瓱 [[hao2wa3]] /(old) contracted variant of 毫瓦[hao2wa3]/
 
# - 兣 兣 [[{li2ke4}]] /(old) contracted variant of 釐克|厘克[li2ke4]/
# + 兣 兣 [[li2ke4]] /(old) contracted variant of 釐克|厘克[li2ke4]/
 
# - 兛 兛 [[{qian1ke4}]] /(old) contracted variant of 千克[qian1ke4]/
# + 兛 兛 [[qian1ke4]] /(old) contracted variant of 千克[qian1ke4]/
 
# - 瓩 瓩 [[{qian1wa3}]] /(old) contracted variant of 千瓦[qian1wa3]/
# + 瓩 瓩 [[qian1wa3]] /(old) contracted variant of 千瓦[qian1wa3]/
 
# - 兙 兙 [[{shi2ke4}]] /(old) contracted variant of 十克[shi2ke4]/
# + 兙 兙 [[shi2ke4]] /(old) contracted variant of 十克[shi2ke4]/
 
# - 瓧 瓧 [[{shi2wa3}]] /(old) contracted variant of 十瓦[shi2wa3]/
# + 瓧 瓧 [[shi2wa3]] /(old) contracted variant of 十瓦[shi2wa3]/
By MDBG 2026
Privacy and cookies
Help wanted: the CC-CEDICT project is looking for new volunteer editors!