Support and General Use > Plugins/Viewers
Working with the Dictionary plugin (was: sanse e250)
bascule:
Llorean gave you the exact name of the Wiki page:
--- Quote from: Llorean on January 05, 2009, 10:11:28 PM ---Check the RockboxDictionary wiki page ...
--- End quote ---
http://www.rockbox.org/twiki/bin/view/Main/WebHome?topic=RockboxDictionary
itan95:
i went to that link and downloaded: WNprolog-2.0.tar.gz, and i went to this link and it downloaded something... now what? i am clueless. it won't let me put any of the stuff i downloaded on to my player.
Chronon:
--- Quote from: itan95 on January 07, 2009, 01:34:14 PM --- it won't let me put any of the stuff i downloaded on to my player.
--- End quote ---
What is "it" exactly? You should be able to put any file you like on your Sansa in MSC mode since it just appears as a UMS (USB Mass Storage) device.
I will mention that the archive that you downloaded contains tools to help you create your own dictionary index. You can also download already prepared dictionary resources from the bottom of the page.
BdN3504:
i don't understand how to use the dict plugin properly either.
Copying the two files already mentioned dict.desc and dict.index into the apps directory works fine. However this leaves me being able to use an english-english dictionary only. What do i have to do if i want to incorporate say the german de-en.txt translation file posted on the wiki into the plugin? and what about other languages?
EDIT: I just found out about the "new Dict Plugin" on flyspray, made a custom build and now i can simply use different dictionaries found on various sources found on the Stardict Sourceforge Project Website. When is this plugin going to be accepted into the svn? i am not encountering any bugs, it's easy to use and now synced. So why is this only available on the patchtracker?
Llorean:
As with many patches that aren't accepted yet: The person(s) maintaining this patch hasn't done much beyond posting it to the patch tracker and updating it there.
Once someone who is willing to do further work on the patch thinks it may be good enough, they should post to the -dev mailing list that they'd like to try to get it committed (and possibly come to IRC and say the same thing when many core devs are around).
Then they'll need to fix up any problems / objections the devs have and more or less do any cleanup that is deemed necessary. Basically, getting it accepted is the un-fun part. Doing what other people require of you, rather than doing what you want.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version