alanmd said:
I just noticed a small bug with the pasteboard reader and document editor. If I type or paste text with Emoji characters, when I switch from 'edit' to 'read' those characters disappear. At this point, I can't click on the character after the one that just disappeared (although I can select it by selecting a character further away, and using the previous/next arrows). Not a big deal, might be a more general problem with a simple fix so I thought I'd mention it...
Might have something to do with the way Apple's encoding those characters - we'll check it out, thanks.
insighter said:
1) Cannot continue a flashcard session because of glitches with the testing interface - This usually happens when you are in a testing session when one goes to edit a card (set a new dictionary entry, create a custom card, etc). For example, the test may require you to write the character based on the pinyin and definition provided but there is suddenly now way for you to progress because the 'done' and 'reveal card' button are obscured/absent. There may be other manifestations that make the interface temporarily unusable in similar ways, but this is the most common. My solution so far has been to exit the session and see if the test incorrect cards session is still usable. If not then that session can be saved, exited out of and restarted which usually solves the problem.
Hmm... could be a timing issue with the user interface control updates on iOS 5 (are you on iOS 5?) I'm not quite following the process here, though - the "card info" button shouldn't even be available until you finish entering your answer on a fill-in-the-blanks test - could you give me a slightly more specific example of the actions you take to cause the interface to get screwed up?
insighter said:
2) Large space created between letter keyboard and tones entry numbers - This seems to happen randomly as far as I can tell and it makes viewing the flashcard headword and any information below really difficult because the white background viewing space has been cut in half with the testing session's green 繁体字 green background taking over that space.
Are you referring to the normal Pleco background texture (blue-green with characters on it)? Is it a bare patch of that or are there buttons / tabs on top of it?
insighter said:
3) Halt in score changes- When I first set up a profile to do SRS testing I set one of the testing parameters to deduct 10% of the cards score each time a card was answered incorrectly. This caused all card scores to receive no changes to them whether they were scored right or wrong. In other words, no matter how many times I tested them the scores always remained 100. After removing the deduct 10% function card review scoring returned to normal, which is fine by me because this function isn't important to me.
So you were doing a test with "manual" scoring and it wouldn't raise or lower the scores? The refusal to go below 100 might be because that's configured as a minimum score, but I don't know why it would also refuse to increase - what percentage had you configured the system to add on a correct answer?
insighter said:
4) Incorrect card selection on re-tests- I have my flashcard test session set to retest me on cards I scored incorrectly on the first time. They re-test me on loop until I get the card correct. Sometimes the cards it chooses to retest me on are cards I know I answered correctly. This seemed to be a bigger problem before but maybe less so now. I would 3-5% of the cards it chooses to retest me on are ones that I actually answered correctly. Not sure what's going on there.
That one has been widely reported; we'll fix it in the next update, but to work around it in the meantime, after you've gone "back" to look at a previous card, tap on the "lightbulb" tab to instantly jump back to your current card (rather than simply tapping "forward" until you get back to it).
insighter said:
One last one is more of an incorrect entry note. The card 伤 in the PLC dictionary this card is marked as having no tone while all other dictionaries (ABC, CC, etc.) mark the character correctly as having a first tone.
Yeah, that does look wrong - thanks.
多伦多人 said:
I just noticed that in the male audio, the pronunciation of "多么" sounds like duo1mo, instead of duo1me.
Almost sounds like "duomwa" to me... very odd.
多伦多人 said:
Also, in the Guifan dictionary, some of the entries seem to have missing characters (which appear as question marks), e.g.:
That's because they're characters that our fonts don't cover - rare renderings and components and other such things. Tricky to fix, though we're talking with them about updating to the latest edition of Guifan, which should have some more nicely-formatted data that will make adding in those characters a lot easier. (but we'd rather not fix it before then since we'd have to throw away all of that work when we updated)