Hey all I just purchased Plecodict, seems to be a great product. I'm using the NPCR textbook, and some of the vocab (ie: names) are not in the dictionaries. So I attempted to add them through the user customizable dictionary. I'm not having any trouble inputting the characters, but whenever I write something for the pinyin I just get "INVALID" Anyone know how I can solve this problem? Thanks
Creating User Defined entries for Plecodict
- Thread starter hdejarne
- Start date
hdejarne--Palm or PPC? Are you adding pinyin and hanzi or only pinyin?
Mike--could it be that, all this time, it's been the pinyin that corrupts my user DBs? (although, uhnlike hdejarne's problem, which begins immediately (apparently) mine takes a while to build up enough volume to make the corruption really painful.)
Sandra
Mike--could it be that, all this time, it's been the pinyin that corrupts my user DBs? (although, uhnlike hdejarne's problem, which begins immediately (apparently) mine takes a while to build up enough volume to make the corruption really painful.)
Sandra
I'm using the Palm OS version. Basically I take a word and input the characters and the definition, leaving the pinyin blank (hoping that it would just put it in automatically). When I view the card the pinyin says "INVALID." So then I tried writing something in the PinYin form like "Lu4Yu3Ping2," and it still comes up as invalid.
Mike confirmed in an earlier thread that the pinyin comes up "invalid" by design if you enter the characters and definition.
I asked about the same problem in this thread:
viewtopic.php?t=508
I asked about the same problem in this thread:
viewtopic.php?t=508
So the Pinyin is still coming up as invalid even when you've gone back and entered it correctly? That's odd - what happens when you create a new entry and enter the Pinyin for it right from the start? gato is correct that it's supposed to come up as INVALID if there's no Pinyin, but adding the Pinyin in is supposed to get rid of the INVALID.
sfrrr - it's doubtful that this relates to your problem, I think yours has more to do with the menagerie of beta software you're using and the inherent unreliability of the Pocket PC file system. Database systems for servers and other large-scale systems are designed to be "transactional", i.e., every operation performed on them is done in a single, coherent block so that it's impossible for the database to be left in a corrupted state if an operation doesn't complete. (Wikipedia uses the metaphor of a bank transfer - you want to deduct money from one account and add it to another in a single database transaction, so that it's impossible that the money could be deducted from the one account but not added to the other in the event of a system crash or other malfunction) Our database system wasn't designed like that, since we didn't think it was necessary to implement a transaction system for a database that would only ever be accessed by one user at a time. This worked fine on Palm OS, but it's caused a few problems on Windows Mobile, which is why we're now working to move over to a more reliable, server-like database system that's almost impossible to corrupt.
sfrrr - it's doubtful that this relates to your problem, I think yours has more to do with the menagerie of beta software you're using and the inherent unreliability of the Pocket PC file system. Database systems for servers and other large-scale systems are designed to be "transactional", i.e., every operation performed on them is done in a single, coherent block so that it's impossible for the database to be left in a corrupted state if an operation doesn't complete. (Wikipedia uses the metaphor of a bank transfer - you want to deduct money from one account and add it to another in a single database transaction, so that it's impossible that the money could be deducted from the one account but not added to the other in the event of a system crash or other malfunction) Our database system wasn't designed like that, since we didn't think it was necessary to implement a transaction system for a database that would only ever be accessed by one user at a time. This worked fine on Palm OS, but it's caused a few problems on Windows Mobile, which is why we're now working to move over to a more reliable, server-like database system that's almost impossible to corrupt.