Beta 2 Known Issues List

mikelove

皇帝
Staff member
Here's a list of major known issues / missing features in the 2.0 beta. This will be updated frequently, so make sure to check here (and preferably also other bug report threads) before reporting a problem.

General:

- Performance on Palm OS is slower than we'd like it to be; we're working to get some more of our core database/font code ported over to ARM, which should make it a lot faster, but for right now it will feel noticeably slower than 1.0.
- Many of the Preferences options don't work yet, so if you try out an option and it doesn't seem to make any difference that's probably why.
- Hardware button support is not implemented yet, so you're stuck with stylus navigation only for now.
- Screen resizing (particularly on landscape-oriented displays) is rather finicky and might leave you with some confusing layouts, so it's probably best to stick with a square or portrait orientation and not change it while running Pleco.
- There are still quite a few memory leaks we haven't tracked down, so you should exit / reopen frequently (ideally with a soft reset in between) to ensure that you don't run into out-of-memory errors.
- There are crashes aplenty, of course... not much else to say on that, but try not get too mad, we're doing our best :)
- The Palm OS font files are mostly unchanged from the previous version, so there's still no full-width pronunciation support; we have, however, finally made the difference between first-tone 'i' and toneless 'i' clear, so that's something to celebrate at least.
- Tap-hold text cut/copy/paste doesn't yet work on Pocket PC, and Pocket PC text fields will sometimes display a bit oddly (e.g. with narrow vertical lines between characters when highlighted) Also, we just added VGA support 2 days before the release of Beta 1 so there may still be a few more graphical glitches on that than on regular 240x240/240x320-screen models.
- Pocket PC font rendering tends to be on the slow side, too, especially on VGA, though this should improve considerably after another beta or two.
- Audio playback on Palm currently only plays the first syllable for multi-character words that it doesn't have audio for; on Pocket PC it should correctly break the word down and play each of its component syllables.

Dictionary:

- The 21st Century dictionary conversion is still very rough, so you'll likely find lots of glitches and may also occasionally run into trouble searching for words.
- The Standard Dictionary has a lot of rare characters (indicated by N???? codes) which we haven't gotten around to finding/coding in yet.
- The interface to access full-text search is rather fussy, basically you have to switch into the language mode for the search you want to do rather than the dictionary you want to do it in. Also, particularly with Chinese full-text searches some matches may be missing / not found.
- It's currently not possible to add/edit user dictionary entries on Pocket PC, and they don't work very well on Palm OS either. Though the user dictionaries will still (annoyingly) come up when cycling through dictionaries on a non-matching search.
- There's no support for reshuffling the dictionary search order yet.
- ZhuYin support should work in headwords everywhere, but the only dictionary that currently supports it in example sentences is the ABC.
- Pop-up definitions don't work on Pocket PC yet, and magnifying a character just gets you the Character Info screen.
- The embedded document reader palette in View Mode doesn't really do much at the moment, so it's probably best to just stay in Search Mode all the time for now.
- The Recent Queries list doesn't work yet, the functionality's actually in there but the UI doesn't know how to show you the previous entries' texts.
- The definition field doesn't update correctly in some cases, and on Pocket PC search inputs may occasionally fail to be processed too.

Flashcards:

- Audio flashcards don't work at all yet, nor does the flashcard statistics screen.
- English-Chinese flashcards don't work yet either, nor do tones-only multi-choice flashcards.
- Flashcard export is not suported yet, and import only works with text or PalmDoc files.
- As stated earlier, hardware button support is not implemented yet, so you have to tap on the onscreen buttons to navigate through flashcards.
- Some of the extra commands in Manage Flashcards don't work either, and a few of the search options (e.g. category search) are very flaky.
- There's no support yet for searching / filtering / etc based on sub- or sub-sub- categories.
- Multi-choice flashcards tend to misbehave when there's only a small set of possible choices, so make sure you're doing them with a lot of cards (several thousand or more would be ideal).
- Stroke order test flashcards will fill in in the direction it thinks your stylus was moving when you tapped on the stroke, so if you see a stroke going the wrong way that's probably why.
- Flashcard databases may still get lost on occasion on Pocket PC, though this time it's usually not due to data corruption but simply to files being marked as in use by the operating system; a soft reset and delete of the new file will restore your flashcards in most cases.
- On rare occasions, flashcard databases on Palm do become corrupted, in which case all we can suggest is that you restore from a backup or start a new flashcard set.
- FLASHCARD AND USER DICTIONARY DATA FORMATS WILL BE CHANGING IN THE FINISHED VERSION, so you will likely NOT be able to migrate flashcard/user dictionary data from the beta into that.

Reader:

- Resizing the definition palette in the full-screen document reader doesn't work yet, nor do the add to flash or audio controls.
- Document format support is rather limited, and it may not like documents with weird line breaks / encodings.
- Word lookups can be painfully slow in some cases.
- So just in general the document reader probably isn't something you want to make a lot of use of right now. (apologies to those of you who were really looking forward to it, but we completely rewrote it just a couple of weeks ago and it hasn't quite stabilized yet)

Character input:

- The ->chars modes don't work yet in the keyboard part of the input screen.
- The auto-recognize timer doesn't work in handwriting recognition.
- Full-screen handwriting input doesn't work yet on Pocket PC.
- The checkboxes for particular sets of radical characters don't work yet, though they do work in the handwriting recognizer part of the screen.

Character Info:

- Stroke order diagrams appear in a different style for traditional and simplified characters; this is simply the format of the data we're using and is not considered a bug (and isn't really something we can fix).
- The entries beginning / entries containing screen is very slow to come up, especially on Palm.
- This can't be activated from the menu or toolbar at the moment due to a late-breaking bug, so go to the Search Navigation section of Preferences and set it up as the action on definition tap (we really need to make these screens less confusing) and that will bring it up when you tap on a character.
 

ipsi

状元
Re: Known Issues List

Despite all the known issues, I'm still quite looking forward to the beta. I probably will continue to use 1.3, given the number of known issues (especially the changing of the flashcard DB format between 2.0B1 and 2.0), but it will be nice to show it off to all my friends and suchlike.

With regards to the multichoice flashcards, will it be possible to have it compare the actual text of an entry? As I have, in some cases, the same definition for a different set of characters (Mostly with regards to the definition of the name of a charcter in my textbook), which would make it possible to choose the right answer and still get it wrong.e

What sort of things do you want us to report? Anything that isn't in here would probably be a good start, but do you want us to report things like incorrect entries in the dictionaries? Also, when is the Beta actually coming out? It's currently Monday afternoon for me, so should I expect it Tuesday morning or Tuesday evening? Note that I'm about 17 hours ahead of you, assuming you really are in New York :).

EDIT: Also, you're up a bit late, aren't you?
 

mikelove

皇帝
Staff member
Re: Known Issues List

I expect most people will stick with the old version at least until Beta 2 or 3 comes out; October 1st was a good deadline to have something released, sharpened our focus a lot, but people who are champing at the bit to upgrade their dictionary may be somewhat disappointed by this first release.

The multi-choice system doesn't compare definition text yet, I suppose we could add this feature at some point but obviously we have a lot of more pressing things to fix at the moment :) It does, however, compare pronunciation and characters, so if you there's a particular pronunciation option given you can be pretty confident that only one of the character choices offered matches it.

As far as what we want reports of, honestly about all we're interested in right now is major, can't-use-the-software type bugs, along with hardware-specific problems (things we might not have noticed here) or conflicts with other software; we're a ways away with needing help with the smaller stuff. This will be described in more detail in one of the other posts I'll be making tomorrow.

The beta should be out Monday afternoon New York time, and yes, I am indeed up late.
 

gato

状元
Re: Known Issues List

As far as what we want reports of, honestly about all we're interested in right now is major, can't-use-the-software type bugs, along with hardware-specific problems (things we might not have noticed here) or conflicts with other software; we're a ways away with needing help with the smaller stuff. This will be described in more detail in one of the other posts I'll be making tomorrow.
It might be useful to provide a format for bug reports, listing the kind of information needed to track the problem down.
 

ipsi

状元
Re: Known Issues List

Yes, I do see a rather large number of things that definitely need to be working before that :).

Afternoon New York time... Hmm... Should be about 9am New Zealand time or so. :) Sweet. I'll be able to get the Beta before I head into Uni for the day, assuming there are no unanticipated problems.

Also, will it be possible to download the sound files seperately? I'd certainly hope so... While I technically have broadband, it's not very fast, especially when downloading from the States, or some other distant place.
 

sfrrr

状元
Re: Known Issues List

Gato--that's a good idea. One of the programs I'm testing maintains an online bug sheet for testers to fill in when they find a bug. It's hard to forget some element when you're filling out an online form (actually a row in an Excel spreadsheet). Accessible to beta testers and no one else.

Sandra
 

sfrrr

状元
Re: Known Issues List

I know I'm an idiot, but would someone please refresh me about how we buy all the upgrade features. I want to have access to every new little bit available as soon as it becomes available. Please and thanks.

Sandra
 

ipsi

状元
Re: Known Issues List

You can't, yet. It should all be available Monday afternoon/evening/Tuesday (if you're far enough away from the US), and then it should be the same as 1.3. I'm sure Mike will post decent instructions when we can start buying / downloading the beta. :)
 

mikelove

皇帝
Staff member
Re: Known Issues List

gato - good idea, yes, though really we're only going to be looking for reports of a few very specific things in this first beta. Honestly, we're releasing this one as much for you guys' benefit as for ours, though some early publicity would certainly be nice; we have so many bugs to work on that we're only interested in very serious problems for the moment.

ipsi - yes, the sound files will be in a separate download, and actually we're not even posting the full ~340 MB set of them initially since we don't want to overload our server and there's a good chance we might be changing the format a few times over the course of the beta; for now we'll only be uploading an 80 MB subset which includes all of the single Pinyin syllables plus about 7000 common multi-syllable words (early HSK vocabulary and the like).

sfrrr - once you activate your software on the 2.0 My Orders page there'll be a list of links to order upgrades, just as with the current My Orders page. I'll also post a link to a hidden catalog entry for the Linguist bundle, for people who've been waiting for that to be ready before buying our software at all; buying that will also get you a license for 1.0 with only the ABC dictionary (and no E-C title), which might be a useful fallback if 2.0 does in fact prove unusable on your system.
 
Re: Known Issues List

Thanks for everything Mike!

From reading the forums one can pretty much tell that the reason you are releasing 2.0 Beta 1 this early, and even though it has so many known issues/bugs/features you are still working on getting fixed or included in the application is because of your loyal PlecoDict customers (me included) who have been chomping at the bit for such a long time for you to release it.

Hopefully it was worth it for you too. And, I guess, as you mentioned earlier on that it did make a good target date for you and the team/contractors.

Anyway, thanks again!

Darrol
 

mikelove

皇帝
Staff member
Re: Known Issues List

Thanks! And yes, it was a good target date, I don't think we'd be this far along if we hadn't had a specific day we needed to have something publicly-usable ready by...
 

weight

举人
Re: Known Issues List

I'm trying to install pleco to an SD card. I've copied all the palm files to a /palm/launcher directory on the SD card except for the following : "Any files except for PlecoDict.prc, the two handwriting recognizer files (palmhwr folder)." Although, I couldn't find "PlecoDict.prc." I assume that this file and "Pleco Engine.prc" are one and the same ... Is this correct? Anyway I click on "Pleco Engine" and I get a reset. Any ideas?
 

mikelove

皇帝
Staff member
Re: Known Issues List

Yep, that's Pleco Engine, probably should have updated the installation instructions when we changed the name... if you're getting a reset on startup, about all I can suggest for the moment is that you delete everything and try again, there may be a conflict involving duplicate copies of something.
 
Top