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 - axin

#76
Quote from: jn0101 on 04. May 2010, 13:30:11
Quote from: Gert on 02. May 2010, 08:12:54
Or, would you like to have a dictionary download page similar as http://dictionarymid.sourceforge.net/dict.html, but better adapted to cell phones ? That means making something like a dictmobile.html where people can directly install the Jad/Jar-files (instead of first downloading a zip file).

+1 for making JAR and JADs available directly, as this would allow people to try out the dictionaries the and application from their desktop web browsers, before they install on their phone

+1: this would also speed up installation on Android (about 2x for larger dictionaries)

When this is done (so we have a central place with all the dictionaries in JAR/JAD), maybe we can get some people to help and regularly publish the dictionaries to phoload.com or getjar.com. It would be as easy as downloading and uploading them...

Achim
#77
Hi Jacob,

you are talking about the Android sources? (For reference: JavaME related stuff is documented here.)
(Please don't be intimidated if this explanation has too much information for you, it's just so that I can point anyone here who is asking about this later... ;) )

I'm using Eclipse Galileo with ADT Plugin. Then building can be done by right-clicking on the project, choosing Android Tools, then Export (Un)Signed Application Package...

My workspace looks as following: There are two projects, one is a SVN-Java-Project called DictionaryForMIDs (checkout of trunk/DictionaryForMIDs) and a SVN-Android-Project called DictionaryForMIDs_Android (checkout of trunk/Android). I added the project DictionaryForMIDs to the Java Build Path of DictionaryForMIDs_Android (Project -> Properties -> Java Build Path -> Projects -> Add) to make sure the compiler finds all the necessary code.

SVN-Java-Project stands for: Install Subclipse Plugin, then choose create new project from SVN (File -> New Project... -> SVN -> Checkout Projects from SVN and choose check out as Java project when asked...)

Hope that helps - and please tell me if anything is missing / unclear.
Achim
#78
Hi Jacob

Quote from: jn0101 on 29. April 2010, 16:11:00
3) This is most important:

A         DictionaryForMIDs/src/de/kugihan/dictionaryformids/translation/normation/NormationEpo.java

If you could do a new Android build released to Market with 3) included I would be very gratefull, as I could instruct Esperanto speakers to download it and ZIP files with the dictionaries.
If not, could you do a build and instruct me on how to install it on other user's phones?

I just committed the normation and pushed the updated version 0.12 (including Esperanto localization) to the Market.

Currently I don't have the JavaME source set up, but I guess Gert will have look as soon as he has a minute (@Gert...).
Could you post some steps on how to support microemu and how to create the jnlp files? Or refer me to the relevant documentation?

I really appreciate your work!
Achim
#79
Hi Jacob,

Quote from: jn0101 on 28. April 2010, 14:18:27
Sure, here it is.

BTW Ive made changes in a few places in the source tree.

thanks, I just committed all the Android related files.


Quote from: jn0101 on 28. April 2010, 14:24:06
Try this:
Open emulator at http://microemu.org/microemu-webstart/index.html
Open http://javabog.dk/filer/paroj/eo-en/ and drag JAD file to it.

Hey, that would make a cool demo on our website!

-Achim
#80
Hi Jacob,

thanks for your great update! Can you check the file Android/res/values-eo/strings.xml in your previous post again? It seems to be empty... Just upload it once more or send me an email, I'll push it together with your patch to the SVN.

To test a dictionary on Android, put the dictionary directory (the one with one DictionaryForMIDs.properties and many *.csv files) somewhere on the SD-card. You could also just put the jar file there, but speed will get significantly slower...

-Achim
#81
Quote from: jn0101 on 25. April 2010, 00:44:19
OK, here is first try:

Here is what I did:

lt-expand /home/j/esperanto/apertium/apertium-eo-en/apertium-eo-en.eo-en.dix > input0.txt

cat input0.txt | grep -v ':>:' | grep -v ':<:' | sed -re 's/<[^:]+:/:/g' | grep -v '><' | grep -v REGEX | grep -v '#' | sed -re "s/:/\t/g" | sed -e 's/</[/g' | sed -e 's/>/]/g' > input1.txt


Btw, you got the languages mixed up: language1 seems to be Esperanto...

Good work though, I tried on Android and it looks fine!

Achim
#82
Hi Jacob, hi Gert,

Quote from: Gert on 23. April 2010, 19:25:57
Cause your dictionaries are available under GPL we can put them on the DictionaryForMIDs web site for public download.
Concerning the list of dictionaries for Android: the Android version as well as the list of dictionaries for Android is maintained by Achim. Achim will have to speak on this.
As soon as the dictionaries are available on the DictionaryForMIDs website I add the new links to the OTA installation system. They'll then immediately be available for automatic installation on Android devices. (You may need to drop me a quick note or it may take some time for me to realize that there are new files available...)

It's that easy  8)

Cheers,
Achim
#83
Quote from: Gert on 30. March 2010, 20:01:33
Quote
Sure, it's quite a pain to find a specific language pair in the current UI, the list just gets too long. We should think about a different way to present this to the user...

For Java ME I implemented the following: if the dictionary contains a big number of languages, then in the settings dialogue the radio buttons for selecting the language are replaced by combo boxes. See the attached screenshot.


Looks good, the combo boxes are much better for those huge dictionaries... it's on my TODO now ;)

Cheers,
Achim
#84
I just tried it on Android: That's an amazing number of languages in just one dictionary! And it's good to test how the app handles them...
I ran some random searches (never really used wiktionary before), the results seem to be fine, and now I really can see the importance of removeTranslationsWithEmptyToTexts.

I found a small problem, not sure if it comes from the dictionary or the Android implementation (as I'm involved in the Android implementation I'll make sure I blame the dictionary first :P ):
There are some strange entries where fromTexts and toTexts both are Err:508. I found that during multiple searches, e.g. search German -> Latin or German -> Japanese for * and check the results.

Sure, it's quite a pain to find a specific language pair in the current UI, the list just gets too long. We should think about a different way to present this to the user...

Anyways, good job!
Achim
#85
I see, thanks for clarifying! I'll check how to use that on Android, probably we can just copy those language names over to the xml file...

-Achim
#86
Hi,

I was wondering how the languages included in a dictionary are localized?
For example, a English - German dictionary opened on a German system should display "Englisch -> Deutsch" instead of "English -> German".
Is this already handled in the J2ME version? How?

If not, I suggest we use a simple text-replace feature and include a list of all available languages into our localization files (DictionaryForMIDs.languages / strings.xml):
When the dictionary is loaded, the program would read out the languageXDisplayText property for the English name and search a language lookup table for that name and its corresponding localized name. This way we could automatically support many of the available dictionaries without recompiling them. If an entry cannot be found in the lookup table, it will of course fall back to using the original languageXDisplayText.

This approach could also support dictionaries like "SMS shorthand <> Definition" or "German zip codes <> City" (by adding "SMS shorthand", "Definition", "German zip codes", "City" as entries to the language lookup table) but we could also say that the SMS shorthand dictionary requires English anyways (as all entries are in English only), so we don't include it into the lookup table.

Please reply as soon as possible as helpful people are already beginning to translate the localization files...

-Achim
#87
I just added Android to supported operating systems. It would be cool to have some information about the features, the icon, maybe a screenshot... Anyone with some spare time...?

-Achim
#88
General discussions / Re: Selection of UI language
13. February 2010, 13:40:07
Starting with revision 254 / version 0.11 the Android version supports manually language selection.

I guess it makes no sense to release an update to the market before we actually have a different language to switch to... What do you think?

-Achim
#89
Hi kopecky,

I guess you are not talking about the Android platform, are you?
If you (or anyone else) need special IMEs on Android: Beginning with version 1.5, the Android platform features installation of third-party IMEs and the Android Market already provides quite a few of them. Just search for ime and/or the language you are missing!

-Achim
#90
General discussions / Re: Selection of UI language
08. February 2010, 16:56:13
Quote from: Sabine Emmy Eller on 07. February 2010, 21:46:22
Do I have the possibility to chose any of the UI languages present in DfM, let's say Neapolitan, even if the UI of my mobile phone is German?
The Android version does not have that feature yet, but I'll add it till the end of the week.

-Achim