Coffee emojis as audio buttons
- Thread starter miconazole
- Start date
澳
举人
https://www.plecoforums.com/threads/new-century-english-chinese-dictionary.5368/#post-41081
Yeah I came across this last year too
Yeah I came across this last year too
miconazole
秀才
Hahaha! So weird.
Paradox460
Member
One of my friends got that bug, but a bit more extensive; all the icons throughout the app were emojis.
It was fixed by going to Settings > Miscellaneous > Force re-download bundle files.
It was fixed by going to Settings > Miscellaneous > Force re-download bundle files.
Hello guys,
I was on Reddit just now and found a thread talking about the speaker icon next to words appearing as a cup of hot tea
Anyway, this can be two things :
A very rare occurrence of a mojibake between unicode and unicode, or my guess : Pleco uses a font that replaces 0x2615 with a speaker as the displayed glyph. Think of something like the old WingDings font, for example.
When you copy the "speaker" somewhere else like I've done above, it appears differently because in actuality it was a cup of tea, or whatever the original was.
Anyway, the 等闲 entry displays cup of tea instead of speaker icons.
Regards,
Philippe
I was on Reddit just now and found a thread talking about the speaker icon next to words appearing as a cup of hot tea
As you can hopefully see, I can reproduce the issue, since what I copied here appears as that cup of tea, what the original character is, indeed, the speaker icon in Pleco. (technically, it's the Hot Beverage character, with value 0x2615)
Anyway, this can be two things :
A very rare occurrence of a mojibake between unicode and unicode, or my guess : Pleco uses a font that replaces 0x2615 with a speaker as the displayed glyph. Think of something like the old WingDings font, for example.
When you copy the "speaker" somewhere else like I've done above, it appears differently because in actuality it was a cup of tea, or whatever the original was.
Anyway, the 等闲 entry displays cup of tea instead of speaker icons.
Regards,
Philippe
That is the reason, yes; at the time we wrote that we did not have a good reliable way to handle non-BMP Unicode characters (this was back in the wild early days of Android shipping with barely functional Unicode support). Since it's a pretty rare occurrence we're not in a great hurry to replace it as it's basically working invisibly most of the time, but it will go away in our big 4.0 update as we're consolidating more-or-less all of our text rendering code between iOS and Android.