drahnier Posted December 8, 2006 at 09:34 AM Report Share Posted December 8, 2006 at 09:34 AM I love this program! Thanks for the 0.6.1 update. I discovered a problem with the annotator, although I am not sure wether it is caused by zdt or the adso dictionary I prefer to use. Please look at the attached image. Quote Link to comment Share on other sites More sharing options...
bogleg Posted December 8, 2006 at 06:44 PM Report Share Posted December 8, 2006 at 06:44 PM I think this is a known bug with the ZDT annotator parsing and has been there for awhile. Its not Adso related. Any words with a '儿' ending should exhibit this problem. I'll add it to my bug fix list. Thanks Chris Quote Link to comment Share on other sites More sharing options...
drahnier Posted December 13, 2006 at 07:03 AM Author Report Share Posted December 13, 2006 at 07:03 AM (see picture) Quote Link to comment Share on other sites More sharing options...
drahnier Posted December 14, 2006 at 11:40 AM Author Report Share Posted December 14, 2006 at 11:40 AM On startup I sometimes get a JDCB connection error: Quote Link to comment Share on other sites More sharing options...
bogleg Posted December 14, 2006 at 03:44 PM Report Share Posted December 14, 2006 at 03:44 PM The problem with the missing 的 is specific to the Adso database. It's missing certain common characters. I think David does auto generates these "missing" entries for his site, but they're not included in the sql script that he gives me. You'll have to ask him for more clarification. I know they're a bunch more missing characters and maybe i'll have to manually add them myself into the adso dictionary plugin. Regarding the latest post, either the program didn't shutdown correctly and delete the lock file or you're running two copies of the program at the same time. Try just shutting down the program and restarting and seeing if you still have the problem. If you do, then you'll have to manually delete the user.lck file. Chris Quote Link to comment Share on other sites More sharing options...
drahnier Posted December 16, 2006 at 04:30 PM Author Report Share Posted December 16, 2006 at 04:30 PM There is/was indeed a problem with the lock file in connection with the other errors I reported. Obviously, zdt had no chance to remove the lock file when it crashed, so the next start of zdt generated the database error. It would be fine if zdt checks for the lock file at startup and acts more gracefully, probably alearting the user. - But this truely is a minor issue. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and select your username and password later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.