Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - jn0101

#1
Hi Gert, long time no see!

My understanding is that Achim would like to do the server part and SF hosting part, in PHP.
This is very fine for me as PHP and SF hosting isnt anyhing I know much about.

I don't know about the progress, sorry

Yours,
Jacob
#2
Quote from: axin on 28. October 2010, 13:06:40
Hi Jacob,

Quote from: jn0101 on 23. October 2010, 23:45:21
I'd like to publish a seperate version of DfM myself. For several reasons it wont work well if I ask you to do it in your name:

thanks for the heads-up. From my side you are welcome to do that (as long as you comply with GPL of course, publish the source, etc.), just one remark: I feel it would be great to keep a common code base as far as possible, so that we benefit from joint efforts in fixing bugs and adding new features.

Hey, I'm really happy to hear that!
Of course, any changes I will make will be incorporated into DfM. I have no intention of making a fork.



Quote from: axin on 28. October 2010, 13:06:40
Independent of your plans, how about using a shared e-mail address for the current DfM on the Market? This way you and all interested developers can provide support and get feedback? Maybe there is even a feature on sourceforge to coordinate that...

The feedback I would recieve would probably be in Esperanto or Danish.

BTW if you really want feedback, then consider making a 'contact the developer' menu item. I have something like:

  void kontaktUdvikler(String emne, String txt) {
      Intent emailIntent = new Intent(android.content.Intent.ACTION_SEND);
      emailIntent.setType("plain/text");
      emailIntent.putExtra(android.content.Intent.EXTRA_EMAIL, new String[]{"jacob.nordfalk@gmail.com"});
      emailIntent.putExtra(android.content.Intent.EXTRA_SUBJECT, emne);
      emailIntent.putExtra(android.content.Intent.EXTRA_TEXT, txt);
      aktivitet.startActivity(Intent.createChooser(emailIntent, "Send mail..."));
  }

  void reportException(Exception e) {
        kontaktUdvikler("Fejl i Teoriprøveapp", "Skriv evt her der skete:\n\n\n---\n"
            +"\nModel: "+Build.MODEL
            +"\n"+Build.PRODUCT
            +"\nAndroid v"+Build.VERSION.RELEASE
            +"\nsdk: r"+Build.VERSION.SDK_INT
            +"\nFejlspor;\n"+Log.getStackTraceString(e));
  }



Quote from: axin on 28. October 2010, 13:06:40
As mentioned earlier, I was working on this auto-installation of a default dictionary. It feels quite stable now, the only thing I'm not really sure of is how to deal with the situation of multiple installed DfM-apps. I uploaded a beta version with the da-eo dictionary set as default here:
http://dictionarymid.sourceforge.net/android/DfM_da-eo-0.13b.apk

I tried it. Looks good!!!
Its a little confusing that all the other dicts appear in the background, before the popup question appears (well I know, its a beta).

Jacob
#3
Ive of course looked but I cant say for sure what happens.
There is a lot of memory garbage collection going on and suddenly a lot of services die, whereafter the emulator reboots.

Probably its some sort of memory leak or massive memory consumption. Ive inserted debug statements (you have absolutely no logging in your code - how can you live like that?) and I think its during unpacking of the ZIP files.

Im working on the non-free esperanto-Danish dictionary.
You can try yourself:

   public static DownloadDictionaryItem bickLarsen =
      new DownloadDictionaryItem(1000,
         "Dansk-Esperanto ordbog", "http://javabog.dk/esperanto/Dansk-Esperanto_BickLarsen.zip", "Dansk-Esperanto", 1575696);

....

      dictionaries.add(bickLarsen);


Im running Android 2.2 without Google APIs

Yours,
Jacob
#4
Hi Achim,

I'd like to publish a seperate version of DfM myself. For several reasons it wont work well if I ask you to do it in your name:

1) The lernu! dictionaries are barely used. This is becaurse there is no app in the Android Market that pops up when searching for 'Esperanto' or 'lernu'.
I'd like to make a dedicated version of DfM with the Lernu! logo and presentation text in Esperanto and where I appear as the 'developer to contact' in Android Market, so I will get feedback directly for these specific dictionaries. I'll clearly state that the app is your work and link to your DfM version, of course.

2) I am even thinking of making a paid version for 2-3 euro, to get compensated for (and thereby continuing to do) development/maintenance of the Lernu! dictionaries.
Again, I'll clearly state that you and Gert are the authors of the engine and that the 'tip' will go to me to maintain the Lernu! dictionaries and fix stuff that pops up.

I suggest you also make a 'DfM donation version' which is the same app but lets happy users easily donate you some money for your work.

3) The closed source 'Danish Esperanto' dict should be easily usable. This means that an app called 'Dansk-Esperanto ordbog' should be on the market, which should automatically download the  closed source 'Danish Esperanto' dict on the first run.

Let me hear what you think.

Yours,
Jacob
#5
Achim,

I just downloaded the SVN version.
It seems it crashes the emulator if you download a large dictionary (> 1.5 MB).
Can you confirm that?

Jacob
#6
Oops, I forgot to add it to SVN. Ive fixed that now (revision 313).
Look in DictionaryGeneration/src/de/kugihan/dictionaryformids/dictgen/dictionaryupdate
#7
General discussions / Re: Build environment
15. June 2010, 14:56:29
I agree that build environment should be one shared ZIP file (Windows users that cannot open a ZIP file probably also cant do the other steps).

WRT whether to do one command or two I think most Linux/UNIX/Mac users will probably try to run the commands one by one if something fails, and scroll up the screen to see the first error.

Windows users will be attempted to double click and wont see errors. You can add
PAUSE   Prompt the user to press any key to continue.
in the end to make the windows stay open.


Jacob
#8
General discussions / Re: Build environment
14. June 2010, 13:31:37
Here is a script for Linux and Mac users.
The 'advanced' script should be put in the Advanced subdirectory

Jacob
#9
Quote from: axin on 11. June 2010, 17:47:09
Hi Jacob,

Quote from: jn0101 on 11. June 2010, 17:03:15
Pls see http://dictionarymid.sourceforge.net/forum/index.php?topic=215.msg1271#msg1271

Achim, I'd like to distribute this dictionary on the Android market, under the name... "Danish Esperanto dictionary".

Actually I was thinking of something similar in the beginning, too: Creating apk's for the Market that already include a specific dictionary. The problem with that was, that performance was rather bad (because the dictionary files somehow first have to be extracted internally). Your idea solves the performance problem, as we download the (up-to-date) dictionary on first start to sdcard. Simple but cunning idea :)
Do you want to start working on this? If not, I'll probably have some time over the weekend... And of course I'll publish almost every DfM apk on the Market you ask me to ;)

Great.

I'd be very happy if you did it and published it.
Please do a fresh build as the encryption stuff has been updated a week ago.

The app description would be in Danish and Esperanto. Neither of those languages are suppported in the Market. Danish apps usually have Danish text, but the text is marked as English text (as this is the only way to get Danish text descriptions visible in Denmark).

I'll write the text and send you on monday and give you the exact URL for the dictionary to initially download. I'll make sure its 325 characters.

Jacob
#10
Ive shipped the dictionary and wont look anymore at this right now.

Gert, at some time in the future when you have time, I'd be happy to go into this and find out why the indexes were so large.

Jacob
#11
Pls see http://dictionarymid.sourceforge.net/forum/index.php?topic=215.msg1271#msg1271

Achim, I'd like to distribute this dictionary on the Android market, under the name... "Danish Esperanto dictionary".
I know I can do that without asking (its GPL :-) but I'll ask anyway, of course.

What I imagine is that I just publish your app on the market as "Danish Esperanto dictionary" and then makes it download that dict to the SD card. I know, I could ask people to search for DfM, install, download Danish Esperanto dictionary to SD card, open it from the app etc, but thats gonna make a lot of people stop in vain.

It also makes sense for people searching the market for 'Esperanto' to see the 'dictionary' and install it.
That its not really the 'dictionary' that they install but a program that downloads a dictionary and shows it, probably doesent matter for most.

In general, Achim, I can see others are practicing publishing the same app several times with different language data. This makes sense from a user searching for dictionary apps for a specific language. So, I suggest you either mention all the languages in the app description, or consider poblishing several 'apps'.


Jacob
#12
Evrything works fine with your 3.5.1 build, Gert. I think I more or less finished my work.

Achim, I'd like to distribute this dictionary on the Android market.

What I imagine is that I just publish your app on the market as "Danish Esperanto dictionary" and then makes it download that dict to the SD card. I know, I could ask people to search for DfM, install, download Danish Esperanto dictionary to SD card, open it from the app etc, but thats gonna make a lot of people stop in vain.

It also makes sense for people searching the market for 'Esperanto' to see the 'dictionary' and install it.
That its not really the 'dictionary' that they install but a program that downloads a dictionary and shows it, probably doesent matter for most.

In general, Achim, I can see others are practicing publishing the same app several times with different language data. This makes sense from a user searching for dictionary apps for a specific language. So, I suggest you either mention all the languages in the app description, or consider poblishing several 'apps'.


Jacob
#13
I am still suffering from very large indexes on the Esperanto side in the Danish-Esperanto dictionary. I was able to halve the size of my dictionary, from 3184999 byte to 1575605 byte, by one simple step, namely excluding multiwords from from being indexed:

public class DictionaryUpdateEpo extends DictionaryUpdate {

   public void updateKeyWordVector(Vector keyWordVector)
            throws DictionaryException {

      int elementCount = 0;
      if (keyWordVector.size() > 1) {
         do {
            String keyWord = ((IndexKeyWordEntry) keyWordVector.elementAt(elementCount)).keyWord;
            //System.err.println("keyWord = " + keyWord);
            if (keyWord.contains(" ")) {
               keyWordVector.removeElementAt(elementCount);
            }
            else {
               ++elementCount;
            }
         }
         while (elementCount < keyWordVector.size());
      }
   }



BTW the printouts looks strange. No wonder the total size is doubled....

keyWord = uzo } uzateco {{}} por privata uzo {{}} {{tr}} uzi, fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = uzateco {{}} por privata uzo {{}} {{tr}} uzi, fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = por privata uzo {{}} {{tr}} uzi, fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = privata uzo {{}} {{tr}} uzi, fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = uzo {{}} {{tr}} uzi, fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = tr}} uzi, fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = uzi, fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = fari uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = uzon el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = el {{}} {{itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = itr}} eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = eluziĝi, elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = elmodiĝi {{}} {{tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = tr}} bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = bezoni {{}} {{tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = tr}} ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = ekuzi {{}} {{itr}} esti uzata {{}} bieno
keyWord = itr}} esti uzata {{}} bieno


I didnt try with the 3.5.3 stuff.

Jacob
#14
Quote from: Gert on 05. June 2010, 14:49:55
QuoteHmm. What I really need is just to remove evrything in [0x ..  ]'s. Is there no easy way to do this?
I'd expect most dictionaries needs exactly this, to filter out explanations etc...

Hmmm, yes, probably indeed for most [0x...], these need to be excluded from indexing. But really not all of them..

Hey, heres an idea: Why not make an option in the properties to omit specific tags. For example,
language2Content01OmitFromIndex: true
language2Content02OmitFromIndex: true
language2Content04OmitFromIndex: true

then [03 ...] stuff would be indexed and the rest not. That would probably solve almost all needs wrt marked text going/not going to be indexed.


Quote from: Gert on 05. June 2010, 14:49:55
Hey, what if nested {{ and }} were supported; that would solve your problem ? People easily could replace [ with {{[ and ] with ]}} as you do with sed. That would work for you, right ?

Yes, that'd work just fine for me, also :-)

Jacob
#15
Just checked again. Indeed the duplications goes away if I remove all nested {{ and }}s.

Hmm. What I really need is just to remove evrything in [0x ..  ]'s. Is there no easy way to do this?
I'd expect most dictionaries needs exactly this, to filter out explanations etc...

Jacob