New dictionary format of firmware 2.14 - Page 17

ShellShock · 04-21-2013, 04:18 PM

I adjusted the size for my custom dictionary in the database, made no difference. I have not tried the date though, but I am not hopeful.

clsdclsd · 04-21-2013, 04:57 PM

Portuguese dictionary definitely does not work - and it's the only gzipped-plain-text one. The marisa index file seems to work (I can look up for words), but the definitions does not come up when I select one, it says "No dictionary entry found for ...".

The Kobo Desktop Software has the 13.680.662-size italian file what tshering mentioned, but the italian dictionary does not work with this file: same behavior as the portuguese or the custom ones.

I tried to put the unknown-format english dictionary from the 2.1.1 firmware to the device (zipped it first), it's OK, so the encryption(?) method did not change, but the non-encrypted dictionaries does not work anymore. :-(

tshering · 04-21-2013, 05:31 PM

Quote:

Originally Posted by ShellShock

I adjusted the size for my custom dictionary in the database, made no difference. I have not tried the date though, but I am not hopeful.

Thank you for trying!

Quote:

Originally Posted by clsdclsd

The Kobo Desktop Software has the 13.680.662-size italian file what tshering mentioned, but the italian dictionary does not work with this file: same behavior as the portuguese or the custom ones.

I just tried the same things. Replacing the plain Italian dictionary by the (old) encrypted dictionary makes it work. This led me to the same conclusion as what clsdclsd says:

Quote:

Originally Posted by clsdclsd

I tried to put the unknown-format english dictionary from the 2.1.1 firmware to the device (zipped it first), it's OK, so the encryption(?) method did not change, but the non-encrypted dictionaries does not work anymore. :-(

It looks like this is the end of custom dictionaries. I am sure the encryption is for copyright concerns and we will not be able to imitate this encryption. For me this means that I will remain on 2.4.0 as long as my touch survives. I hope by the time my touch stops working, there will be a reader by another brand that will satisfy my needs better.

ShellShock · 04-21-2013, 05:46 PM

I think you could be right...that this could be the end for us with custom dictionaries. Such a shame. I am thinking of going back to 2.4 too.

ShellShock · 04-21-2013, 06:18 PM

I have gone back to 2.4.0 and interestingly I have found that the html files in the dictionary support head and body tags, which I didn't know. I had added the head and body tags to try and get the dictionary to work on 2.5.0 (no luck) but they do work on 2.4.0.

AlPe · 04-22-2013, 03:23 AM

Yesterday night I did more or less what you guys reported here, and I had no luck.

I agree with the observation that probably now dictionaries (precisely, the content HTML files) have to be "encrypted/obfuscated" in order to be correctly used by Kobo.

If anyone from Kobo is reading: this is a very bad move.
I have been asked to "convert" dictionaries from people not able to use Penelope themselves or I have seen custom-made dictionaries in eReading forums for at least a dozen of language-combinations that are not covered by your dictionaries. For example: IT-DE, DE-IT, IT-ES, ES-IT, IT-FR, FR-IT, CS-CS, CS-EN, EN-CS, PL-EN, EN-PL, ZH-ZH, ZH-EN, EN-ZH, and more.
I understand the need of obfuscating the default dictionaries you ship with the devices, but removing the possibility of using custom-made dictionaries is simply non-sense. I would like you to understand the point and be smart, by reintroducing support for custom dictionaries and publishing official specs for them.

tshering · 04-22-2013, 04:50 AM

Quote:

Originally Posted by AlPe

If anyone from Kobo is reading: this is a very bad move.
I have been asked to "convert" dictionaries from people not able to use Penelope themselves or I have seen custom-made dictionaries in eReading forums for at least a dozen of language-combinations that are not covered by your dictionaries. For example: IT-DE, DE-IT, IT-ES, ES-IT, IT-FR, FR-IT, CS-CS, CS-EN, EN-CS, PL-EN, EN-PL, ZH-ZH, ZH-EN, EN-ZH, and more.
I understand the need of obfuscating the default dictionaries you ship with the devices, but removing the possibility of using custom-made dictionaries is simply non-sense. I would like you to understand the point and be smart, by reintroducing support for custom dictionaries and publishing official specs for them.

I fully subscribe to what AlPe says and would like to ask Kobo to rethink their decision.

A certain tendency to restrict the (presumably unintentional) support of custom dictionaries was noticable already in FW 2.4.0. The last move seems to indicate that this restriction is done with full purpose. I am asking myself what is the motive behind this? Does Kobo intend to start selling additional dictionaries?

AlPe · 04-22-2013, 05:07 AM

Still, they might have simply broken support for "plain-text" dictionaries during a code refactoring.

(I do not think they are going to sell dictionaries, for three reasons: 1) content is not their business; 2) selling dictionaries produces low profits; 3) "free", commercial-grade dictionaries are provided by almost all their competitors, and they are part of the "Kobo experience".)

tshering · 04-22-2013, 05:32 AM

Quote:

Originally Posted by AlPe

Still, they might have simply broken support for "plain-text" dictionaries during a code refactoring.

(I do not think they are going to sell dictionaries, for three reasons: 1) content is not their business; 2) selling dictionaries produces low profits; 3) "free", commercial-grade dictionaries are provided by almost all their competitors, and they are part of the "Kobo experience".)

I hope you are right.

ShellShock · 04-22-2013, 07:40 AM

Yes, they could have tidied up what they thought was redundant code not used by their dictionaries anymore, not realising that we were depending on it.

tshering · 04-22-2013, 08:03 AM

Quote:

Originally Posted by ShellShock

I have gone back to 2.4.0 and interestingly I have found that the html files in the dictionary support head and body tags, which I didn't know. I had added the head and body tags to try and get the dictionary to work on 2.5.0 (no luck) but they do work on 2.4.0.

How do you use the head and body tags? I mean for what purpose can they be useful in a dictionary?

ShellShock · 04-22-2013, 02:42 PM

No use that I can see, but at least you can use a standard html page when authoring.

tshering · 04-22-2013, 03:45 PM

I see. Thank you, ShellShock

AlPe · 04-22-2013, 04:16 PM

Quick update: I exchanged some messages with KoboHelp staff, and their last one reads:

Quote:

Our Dev Team is aware of this issue and currently working on it. Thanks for the heads up.

which is promising, I guess. (I must say that they are very quick and polite.)

tshering · 04-22-2013, 04:46 PM

AlPe,
thank you for contacting the Kobo staff. I did not expect such a positive answer. Let us hope for the best.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
What's file format of dictionary	mnjkl	Kobo Reader	2	12-12-2011 08:48 AM
Dictionary format	jgray	Sony Reader	1	10-25-2010 09:52 AM
English Thesaurus in the dictionary format	osnova	Amazon Kindle	14	12-12-2009 06:42 PM
Dictionary: what version? can it be in firmware?	jedix	Sony Reader Dev Corner	7	12-05-2008 12:00 PM
Webster dictionary in DEPReader format	abigail	Reading and Management	0	08-10-2005 08:00 AM

04-21-2013, 04:18 PM	#241
ShellShock Wizard Posts: 1,176 Karma: 2431850 Join Date: Sep 2008 Device: IPad Mini 2 Retina	I adjusted the size for my custom dictionary in the database, made no difference. I have not tried the date though, but I am not hopeful.

04-21-2013, 04:57 PM	#242
clsdclsd Zealot Posts: 105 Karma: 37668 Join Date: Feb 2012 Device: Kobo Touch	Portuguese dictionary definitely does not work - and it's the only gzipped-plain-text one. The marisa index file seems to work (I can look up for words), but the definitions does not come up when I select one, it says "No dictionary entry found for ...". The Kobo Desktop Software has the 13.680.662-size italian file what tshering mentioned, but the italian dictionary does not work with this file: same behavior as the portuguese or the custom ones. I tried to put the unknown-format english dictionary from the 2.1.1 firmware to the device (zipped it first), it's OK, so the encryption(?) method did not change, but the non-encrypted dictionaries does not work anymore. :-(

04-21-2013, 05:46 PM	#244
ShellShock Wizard Posts: 1,176 Karma: 2431850 Join Date: Sep 2008 Device: IPad Mini 2 Retina	I think you could be right...that this could be the end for us with custom dictionaries. Such a shame. I am thinking of going back to 2.4 too.

04-21-2013, 06:18 PM	#245
ShellShock Wizard Posts: 1,176 Karma: 2431850 Join Date: Sep 2008 Device: IPad Mini 2 Retina	I have gone back to 2.4.0 and interestingly I have found that the html files in the dictionary support head and body tags, which I didn't know. I had added the head and body tags to try and get the dictionary to work on 2.5.0 (no luck) but they do work on 2.4.0.

04-22-2013, 03:23 AM	#246
AlPe Digital Amanuensis Posts: 727 Karma: 1446357 Join Date: Dec 2011 Location: Turin, Italy Device: Several eReaders and tablets	Yesterday night I did more or less what you guys reported here, and I had no luck. I agree with the observation that probably now dictionaries (precisely, the content HTML files) have to be "encrypted/obfuscated" in order to be correctly used by Kobo. If anyone from Kobo is reading: this is a very bad move. I have been asked to "convert" dictionaries from people not able to use Penelope themselves or I have seen custom-made dictionaries in eReading forums for at least a dozen of language-combinations that are not covered by your dictionaries. For example: IT-DE, DE-IT, IT-ES, ES-IT, IT-FR, FR-IT, CS-CS, CS-EN, EN-CS, PL-EN, EN-PL, ZH-ZH, ZH-EN, EN-ZH, and more. I understand the need of obfuscating the default dictionaries you ship with the devices, but removing the possibility of using custom-made dictionaries is simply non-sense. I would like you to understand the point and be smart, by reintroducing support for custom dictionaries and publishing official specs for them.

04-22-2013, 05:07 AM	#248
AlPe Digital Amanuensis Posts: 727 Karma: 1446357 Join Date: Dec 2011 Location: Turin, Italy Device: Several eReaders and tablets	Still, they might have simply broken support for "plain-text" dictionaries during a code refactoring. (I do not think they are going to sell dictionaries, for three reasons: 1) content is not their business; 2) selling dictionaries produces low profits; 3) "free", commercial-grade dictionaries are provided by almost all their competitors, and they are part of the "Kobo experience".)

04-22-2013, 07:40 AM	#250
ShellShock Wizard Posts: 1,176 Karma: 2431850 Join Date: Sep 2008 Device: IPad Mini 2 Retina	Yes, they could have tidied up what they thought was redundant code not used by their dictionaries anymore, not realising that we were depending on it.

04-22-2013, 02:42 PM	#252
ShellShock Wizard Posts: 1,176 Karma: 2431850 Join Date: Sep 2008 Device: IPad Mini 2 Retina	No use that I can see, but at least you can use a standard html page when authoring.

04-22-2013, 03:45 PM	#253
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	I see. Thank you, ShellShock

04-22-2013, 04:46 PM	#255
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	AlPe, thank you for contacting the Kobo staff. I did not expect such a positive answer. Let us hope for the best.

Advert

Advert