[Unofficial] Feature Request / Suggestion List

Should also be customizable in 4.0, but as far as basic/default behavior goes we have a lot more users with totally incorrect pinyin who'd like it to nevertheless match something than users with rare pinyin readings they'd like the app to reject :)
 
Last edited:
Should also be customizable in 4.0, but as far as basic/default behavior goes we have a lot more users with totally incorrect pinyin who'd like it to nevertheless match something than people with rare pinyin readings they'd like the app to reject :)

:cool:

I e-mailed MoE by the way. I doubt they'll send me anything but one can always hope.
 
The feature I'd be most interested in, would be an addition to the stroke order page. Being able to enable a background box around the character, like on writing practice paper. That would help a lot learning to write. Thanks!
 

Attachments

  • ni.jpg
    ni.jpg
    5.8 KB · Views: 773
Inflexible pinyin interpretation errors

When "flexible pinyin splits" is off, some invalid syllables are still prioritized. E.g. searching "fanguan" is interpreted as "fang-uan" which gives no results, even though it could only mean "fan-guan", since "uan" is invalid pinyin for "wan". Similar for "yunian" (invalid for yun-yan), "jinguan" (jing-wan), "zuoer" (???), "jianguo" (jiang-wo), "xining" (xin-ying), etc.
 
Last edited:
Spaces breaking some searches

Searching "jin guan " (with 2 spaces, one after each syllable) does not include 尽管 (unless I switch to single dictionary mode).
 
Inflexible pinyin: yes, this is a known issue - with 'flexible pinyin' off it does a purely greedy breakdown. (as with so many other things this is fixable in 4.0)

Spaces: not seeing this issue here - are you sure you typed it correctly? What platform / version of Pleco are you using?
 
Pleco version: 3.2.75
Android version: 10

I only have ABC and Oxford dictionaries enabled in the "All Chinese Dicts" group, in that order, and this is the group I'm searching in. Swapping the order of them shows 尽管 but hides 金冠 and shows the wrong dictionary for everything under 尽管. (See attached screenshots)

I have another group with GF, MOE and Cross-Straits, which does work.

"Dictionary search order" is set to ”From Current”. All other "Search Engine" options are enabled, except:
- Flexible pinyin splits
- Search for umlauts on u's
- Sort Chinese by pinyin
- Jump to appended word
 

Attachments

  • Screenshot_20200914-185135.png
    Screenshot_20200914-185135.png
    409 KB · Views: 772
  • Screenshot_20200914-185234.png
    Screenshot_20200914-185234.png
    445.6 KB · Views: 795
Last edited:
If you tap on that 'gold crown' entry in the results without 尽管, do you see 尽管's definition listed under it? (looks like this might be a bug in the ABC database)
 
Yes, once i open that, first it shows the "gold crown" from ABC, then 尽管 from both ABC and Oxford.

(Perhaps something related to ABC'c hardcore pinyin sorting?)
 
I don't know if this is related, but I just searched *苧* (with asterisks) in the Pleco dictionary and got 3 seemingly identical entries at the bottom of the list: 荠苧〔薺薴〕
 
Another great improvement would be to add a setting in the OCR block of settings to choose which character base to use while doing OCR: Simplified, Traditional or Simplified+Traditional. If the user knows the fact that the text he tries to OCR contains only a definite set of characters, it would be reasonable to exclude all the other characters so that they would not interfere in the process and cause frustration, besides it would accelerate the execution of the OCR algorithm.
 
Last edited:
Are iOS 14 widgets now versatile enough for a Pleco lookup widget to make sense? I suppose I could just open Pleco from its place on the homescreen and search for a word that way, like an animal, but a lookup widget on my homescreen would save me a whole tap -- literally fractions of a second!
 
Another great improvement would be to add a setting in the OCR block of settings to choose which character base to use while doing OCR: Simplified, Traditional or Simplified+Traditional.

Not currently supported by our OCR engine, weirdly enough, but definitely something to add when we update or replace it.

Are iOS 14 widgets now versatile enough for a Pleco lookup widget to make sense? I suppose I could just open Pleco from its place on the homescreen and search for a word that way, like an animal, but a lookup widget on my homescreen would save me a whole tap -- literally fractions of a second!

They're actually totally non-interactive; they also made that change for Today widgets, so I'm glad I never invested the effort into building one of those :-) Hopefully this is just a technical constraint - something they didn't have time for in the midst of COVID - and will get better in iOS 15, but there's not much we can do with them as presently constituted.
 
hey, text is better in reader now (epub), spacing is improved! means more text fits on each page. great, thx. noticed that search in reader now points to erroneous pages, maybe it calculates page index according to the old layout?
 
Back
Top