Notices


Reply
Thread Tools
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#81
Originally Posted by Rob1n View Post
I'll have a look at this next week, once the current version's into -testing. It should be easy enough to add command-line options to auto-remove entries from a blacklist. Then an integrated blacklist editor would allow interaction with the blacklist similarly to with the dictionary.
I've just uploaded version 0.0.8 onto -devel. This includes a blacklist feature. You can set the delete mode to "Blacklist" to move words from the main dictionary to the blacklist, or you can use the blacklist editor (via the main app menu) to add/remove words from the blacklist. The blacklist is split by language, in the same way as the main dictionary. Entries are saved either when you exit the blacklist editor, or when you save the main dictionary. Finally, you can apply the blacklist from the command line (without launching the GUI) or via a script, by calling "/opt/AutoCompleteEditor/AutoCompleteEditor.pt --apply-blacklist".

Currently the blacklist does an exact match for entries (all entries are lower-cased anyway), but I may look at allowing regex-based entries in a future version.
 

The Following 3 Users Say Thank You to Rob1n For This Useful Post:
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#82
Originally Posted by Rob1n View Post
As no-one's posted any new bugs over the weekend, I've now promoted 0.0.7 to extras-testing. Please give it a test and vote.
Thanks to those who've tested it. Unfortunately there are obviously still issues for several people (which indicates the parsing is still not correct), so I've flagged it for demotion again. Unfortunately none of those with issues have sent me example files, so unless I can manage to generate a failing case myself, there's no possibility of fixes either.
 
pelago's Avatar
Posts: 2,121 | Thanked: 1,540 times | Joined on Mar 2008 @ Oxford, UK
#83
Originally Posted by Rob1n View Post
Unfortunately none of those with issues have sent me example files.
As long as it's disabled by default and clearly described, maybe you could implement a feature where dodgy dictionary files can be automatically uploaded for analysis? For some people, having to delve into the Terminal is just one step too hard.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#84
Originally Posted by pelago View Post
As long as it's disabled by default and clearly described, maybe you could implement a feature where dodgy dictionary files can be automatically uploaded for analysis? For some people, having to delve into the Terminal is just one step too hard.
In all the cases so far, the issue has been (understandably) a concern about private data. I may revisit the error-handling code and think about what other alternatives I can offer the user though.
 
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#85
A prompt should suffice?

Anyway, mine no longer works, but is there an option to start fresh? I mean, instead of delete all, simply rewite a known good, empty dictionary.

Mine crashes right now on startup. Most likey because I disabled completion. Not sure.
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#86
Originally Posted by ndi View Post
Anyway, mine no longer works, but is there an option to start fresh? I mean, instead of delete all, simply rewite a known good, empty dictionary.

Mine crashes right now on startup. Most likey because I disabled completion. Not sure.
Deleting the dictionary file (/home/user/.osso/dictionaries/.personal.dictionary) and killing hildon-input-method will force it to create a new file. Not sure how this will work if you don't have auto-complete enabled though - I'll have to do some tests with that.

I've actually managed to create a dictionary file which won't load now, which gives me something to work on. Unfortunately it looks to be using a totally non-standard encoding for the characters (0x9A and 0x9E is what I've currently got) - they don't fit in any ISO8859 character set, nor are they valid UTF-8.
 
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#87
Well, I get that:
Attached Images
 
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#88
Originally Posted by ndi View Post
Well, I get that:
It works fine on mine with auto-complete disabled, and comes up with a missing file error if I've just deleted the dictionary file. Any chance you can upload the dictionary file (or email it to me - maemo at robinhill.me.uk)?
 
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#89
Sent. Please note that the sent dictionary contains passwords. The e-mail message contains all the needed info.
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#90
Originally Posted by Rob1n View Post
I've actually managed to create a dictionary file which won't load now, which gives me something to work on. Unfortunately it looks to be using a totally non-standard encoding for the characters (0x9A and 0x9E is what I've currently got) - they don't fit in any ISO8859 character set, nor are they valid UTF-8.
Apparently, they're using CP1252. Ho-hum. Looks like I'm definitely going to need a static lookup for the encodings to use as they seem to be being plucked out of thin air
 
Reply


 
Forum Jump


All times are GMT. The time now is 12:32.