3.2.x Bug Report / Feedback Thread

G

goldyn chyld

状元
Question about Eng-Chi dictionaries: is there a way you could add a "search" option within an entry's definition? Sometimes I'd like to quickly find a certain phrase/example sentence with such phrase, and it's a bit cumbersome when you have to scroll through all the content.

It would be super useful if you could do something about it.
 
mikelove

mikelove

皇帝
Staff member
Why not just do a full-text search in the main search box (#whatever)? It should preview the selected text in the results list + scroll to it when you go into the definition screen.
 
Alexis

Alexis

状元
Alexis said:
Was mainly refering to Manage Dict Groups -> [Group] -> Choose Dictionaries

(I personally create custom groups in order to to seperate the Mandarin/Cantonese dictionaries)
Click to expand...

That being said, I probably wouldn't have a need for custom dictionary groups if there was a default "All Mandarin Dictionaries", just like there is for "All Cantonese Dictionaries".
 
ACardiganAndAFrown

ACardiganAndAFrown

状元
IMG_5761.PNG
 
ACardiganAndAFrown

ACardiganAndAFrown

状元
ABC, XHD, PLC, OCC, NHD, FHF, OXC, FHY, FHD, FHX, TCE, SCM, TL, DLW, GR, KEY, ZMC, KEF, HDC, GF, GH, LMA, GZP, GZH, ADS, HDD, CC, CF, CMT, CCY, BUD, MOE, LAC, ABY, UNI
 
Z

zhouyi

秀才
I just wanted to second the request for Ipad pro keyboard support for the arrow keys in the reader. I was disappointed that this feature did not come with the recent Pleco update.
 
A

Abun

榜眼
The head words for the 言者無心，聽者有意 and 言者諄諄，聽者藐藐 are not displayed correctly, at least not with traditional as main character set and simplified as supporting. I’m attaching screenshots.
Screenshot_yanzhe_wuxin.png Screenshot_yanzhe_zhunzhun.png

Interestingly enough, the entries appear correctly in the search history screen I get when I want to report a faulty entry so the problem may not be in the entries themselves.
 
Shun

Shun

状元
@Abun: It also displays correctly in a pop-up definition from Document Reader. (see screenshot; or rather, when tapping the curved right arrow from it) There must be something wrong with the way the Dictionary part of the app reads in the dictionary data.

yanzhe wuxin.png

An aside: This FZNewShuSong font surprisingly looks truly beautiful in Pleco, your screenshots just made me change to it. :)
 
A

Abun

榜眼
Shun said:
@Abun: It also displays correctly in a pop-up definition from Document Reader. (see screenshot; or rather, when tapping the curved right arrow from it) There must be something wrong with the way the Dictionary part of the app reads in the dictionary data.
Click to expand...
Probably. Although it’s not quite only the dictionary part: I forgot to mention earlier that the Traditional was also messed up when I saved it as a flashcard (to Anki) – i.e. it treated the characters after the slashes as variants and deleted them, resulting in 言者無心听聽有意. Unless of course the flashcard version is directly based on the dictionary display rather than the actual entry in the database.

Shun said:
An aside: This FZNewShuSong font surprisingly looks truly beautiful in Pleco, your screenshots just made me change to it. :)
Click to expand...
Yeah, I’d be using it, too, if I weren’t pretty much shut into HanaMin because I really need those Unicode CJK Extension B+ characters…
 
Shun

Shun

状元
Abun said:
Probably. Although it’s not quite only the dictionary part: I forgot to mention earlier that the Traditional was also messed up when I saved it as a flashcard (to Anki) – i.e. it treated the characters after the slashes as variants and deleted them, resulting in 言者無心听聽有意. Unless of course the flashcard version is directly based on the dictionary display rather than the actual entry in the database.
Click to expand...

That may well be. On second thought, it could have to do with the search index, which passes the mistake on to the Dictionary display, which passes it on to the Anki export, adding another mistake. :)

Abun said:
Yeah, I’d be using it, too, if I weren’t pretty much shut into HanaMin because I really need those Unicode CJK Extension B+ characters…
Click to expand...

That's interesting, because on iOS, another font, probably Source Han Sans, is substituted for rare characters. That should be an easy feature to add for Android: Selecting a main font and one for those characters the main font does not cover.
 
You must log in or register to reply here.
Top