Messages

Yes - you can help a lot !!!

Just read this thread: http://dictionarymid.gottfried-signs.ch/index.php?topic=21.0

Could you then contact Donatas and support him on the task to make the dictionaries available on the latest version !?!

Thanks !
Gert

Hey, you have a 'big' PDA, but not 6 MB of free memory - just kidding.

Then I would say, that your 'invalid JAR-file' problem should be gone with version 3.1.0 !

So we only need to get all dictionaries to 3.1.0 (once the final 3.1.0 is released) ... well that job still needs to be done !

Regards,
Gert

Oliver,

Stebastian's HanDeDict from this page http://dictionarymid.sourceforge.net/development.html#Testversion

Thanks !
Gert

Hey, we had exactly the same idea !! Testversion #4 is the #3 version where I just copied a dictionary-folder inside.

Here are the differences compared to the versions that you can download from the dowload page:
1. our 'hand-made' versions were not created by JarCreator. JarCreator among other things takes care for the naming of the application, so that you can install more than one dictionary at the same time.
2. The new Testversions are based on the 3.1.0 baseline. Some changes had been made there compared to 3.0.3, for example in manifest.mf now the entry for the icons points to a real bitmap file.

Could you check if the 3.1.0 Chinese test dictionary runs on your device ?

Thanks !
Gert

Ok, I see, things are not so easy as I thought !

So ... what else may be wrong ??

I just had a look at the English-German DTS dictionary in the file manifest.mf: it seems this dictionary was not correcly built with JarCreator (on the other hand I can't see an error that would cause the 'invalid jarfile').

Can you try any dictionary other than the DTS ones ? For example the Testversion for 3.1.0 (Chinese dictionary) ?

Also, can you try:
http://www.kugihan.de/dict/download/test_versions/tao/4/DictionaryForMIDs.jar

Gert

It seems we already found the reason of the problem - not sure yet however.

To be sure, could you give a try to the following version:
http://www.kugihan.de/dict/download/test_versions/tao/3/DictionaryForMIDs.jar
If that one procudes the JAR-file error message again, then we have really found the problem.

Here is my guess: in the JAR-archive there is the file META-INF/MANIFEST.MF. In this file there is the line
MicroEdition-Configuration: CLDC-1.0
If you change this line to
MicroEdition-Configuration: CLDC-1.1
Then it works.

The correct value for DictionaryForMIDs is CLDC-1.0. CLDC-1.1 is used by DictionaryForMIDs if the device supports it; on devices that only support CLDC-1.0 no features of CLDC-1.1 are used.

If this proves to be the problem, then a simple script that would update the manifest.mf file with CLDC-1.1 would allow to run all dictionaries on the TAO Java VM.

Gert

P.S.: the application that you downloaded and installed is an 'empty' application without dictionaries. The dictionaries can be loaded from the file system, but this feature is currently not really useable (see FAQ, loadable dictionaries).

Please just deactivate in the Settings the "coloured display" and then try again !

Regards,
Gert

Here are the next test versions:
http://www.kugihan.de/dict/download/test_versions/tao/1/DictionaryForMIDs.jar
and
http://www.kugihan.de/dict/download/test_versions/tao/2/DictionaryForMIDs.jar (if positive, than that one will produce a class not found exception)

Could you please test these ?

Thanks !
Gert

That's good news !

There was a misunderstanding on "enlightened", you meant "smaller size", right ? Before I understood 'enriched with colours' (which you can do with DfM).

Puh, 'phone switched off' reads hard (if Siemens still produced phones you should complain at them )

I myself have a Siemens S65 and also that one switches off reproduceably under certain conditions - but it can handle file sizes much bigger than 1 MB !

Gert

Well, is there any chance to get the error message ?

Sure, coloured versions can be done - you should contact the person who did set up the dictionary - and maybe you can provide your support for him.

Gert

Oliver,

I believe you are doing everything right and the problem is related to the Tao SW. I received reports from people who had DictionaryForMIDs run successfully on Windows Mobile (an older version with a non-Tao Java VM) and couldn't run DictionaryForMIDs any more after they switched to a Windows Mobile PDA where the Tao SW was installed.

I should be able to provide a test version today or tomorrow (hopefully).
Gert

Oliver,

thanks for testing !

About the "the suite has requested access rights, that are not allowed" - that reads like the JAR/JAD-file was not correctly created with JarCreator (that dictionary will not run on most other devices neither) - I will check this lateron.

I assume that the MDA Compact II also runs the Tao Intent Java VM ?

Ok, when my PC is back to operation, then I will create a test version. Would be great if you could continue testing with that version (and the following versions ...) !

Greetings,
Gert

Yes, exactly, you can use the content-definitions for this.

Probably you will have two columns: one for Chinese and one for English (for example separated by a tab-character).

Then for the Chinese column you use the content-syntax such as in
[01Simplified] [02traditional] [03pronounciation]

However: Lars is already working to get CEDICT on the latest version of DictionaryForMIDs. Best you co-ordinate your activities directly with Lars.

Gert

Oliver,

yes, we urgently need your support to trace down that problem !

Is your Vario II running the Tao Intent software ?

Could you please just do a test with an older version of DictionaryForMIDs, for example the DictionaryForMIDs_2.4.0_EngSpa_freedict.zip ? Just to see if the problem also existed there.

Then, could you please test this version: http://www.kugihan.de/dict/download/test_versions/jsr75/DictionaryForMIDs.jar - just to see if it starts without the JAR error message.

If neither of the two work, then I will create a specific test version (which may take a while, because right now my PC is at repair).

I am sure we will find the reason of the problem - it may take a few turns to test however.

Thank you for testing !!
Gert

Well, yes, with that workaround it seemed that the OutOfMemoryError did not occur any more.

You can browse the old versions at http://sourceforge.net/project/showfiles.php?group_id=137316

Gert