Duplicate entries despite traditional, simplified and Mandarin pronunciation fields matching

[awelotta]

The character 潘 has two entries for me, one which seems to have my user dictionaries and the other with non-user dictionaries. Usually when I have duplicate entries, I can fix it by changing simplified headword, traditional headword, or Mandarin pinyin to match. The pinyin is lowercase for both of them. Below is the two dictionary entries.

Below is the screenshot for editing one of the user dict ("SH", shanghainese). The first three fields match as far as I can tell.

The only difference that I can see is that the user dictionary lacks jyutping, but there seems to be no way to add jyutping to a user dictionary. The other thought is that it might be a compatibility character, but that doesn't seem to be the case.

 

[mikelove]

It's the capitalization - doesn't come through in Zhuyin, but the pinyin in the PLC entry for 潘 is capitalized and in the current version of Pleco we split on that. (we're moving away from this behavior in 4.0, but it's not the sort of thing we can do in a minor update since it's unexpected and will probably annoy some people)

Unfortunately, the only workaround in the meantime would be to change both of your user dictionaries to also capitalize the pinyin.

 

[awelotta]

Ah, you're right that it is capitalized. Anyways, I've now changed both my user dicts to be title case, and have changed my language settings to display pinyin, but they're still duplicated. Closing and reopening the app doesn't make a difference.

I tried disabling Cantonese (the first two settings, "Enable Cantonese" and "Enable Cantonese Search") to no effect.

Then I tried re-enabling Cantonese and then checking "autogenerate if missing", which was unchecked previously, but it still doesn't merge them.

 

[mikelove]

Hmm, it looks like there’s a bug that’s causing entries to be indexed as lowercase. So it would merge fine with a lowercase entry for 潘 like HYDCD’s, just not with this one. Unfortunately I don’t have any other workaround to suggest but this should get better in 4.0.