Language pair packages - Revision history

Jacob Nordfalk: /* List of ready-to-use packages */

2020-04-07T08:23:59Z

List of ready-to-use packages

Ilnar.salimzyan: /* Language pairs with external dependencies */

2015-03-08T17:59:25Z

Language pairs with external dependencies

Ilnar.salimzyan: /* Language pairs with external dependencies */

2015-03-08T17:59:13Z

Language pairs with external dependencies

Mikel: apertium-es-ast is now supported

2013-01-28T17:50:57Z

apertium-es-ast is now supported

Mikel at 17:34, 18 August 2012

2012-08-18T17:34:55Z

Mikel at 11:36, 15 August 2012

2012-08-15T11:36:11Z

Mikel: Created page with '{{TOCD}} Language pair packages are standalone JARs that can be run independently as well as used from other client apps like Apertium-Caffeine or Apertium-OmegaT. The on…'

2012-08-14T19:42:34Z

Created page with '{{TOCD}} Language pair packages are standalone JARs that can be run independently as well as used from other client apps like Apertium-Caffeine or Apertium-OmegaT. The on…'

New page

{{TOCD}}
Language pair packages are standalone JARs that can be run independently as well as used from other client apps like [[Apertium-Caffeine]] or [[Apertium-OmegaT]]. The only prerequisite to use them is a Java VM (apertium, lttoolbox or lttoolbox-java are NOT required), and they can work on practically any platform (Linux, OS X, Windows and even Android!).

== Internal structure ==

Since JAR files are nothing but renamed ZIP files, you can easily edit language pair packages to fit your needs. Note that the packages are ready to be used without any modification, so the vast majority of users will not get any notable advantage from doing it. In any case, editing packages could happen to be useful, for instance, in order to reduce their file size by removing unnecessary content.

The typical structure of a language pair package would be the following one:

*'''data/''': Directory containing the language pair itself. You could extract it and use with your local installation of Apertium.
*'''transfer_classes/''': Directory that contains the [[Bytecode_for_transfer|Java bytecode classes for transfer]]. This is only used when using the package from standard Java so, if you are going to use it exclusively from Android, you can delete it.
*'''org/''': Directory that contains the [[lttoolbox-java]] engine, which makes the package self-executable. If you are not interested on this feature (presumably, because you are going to use the package exclusively from client programs), you can delete it.
*'''META-INF/''': Directory that contains the MANIFEST.MF of this Jar, which is used by Java. It takes a few bytes and can rarely be removed, so please don't touch it unless you know what you are doing.
*'''classes.dex''': Dalvik bytecode of the transfer classes, used by Android instead of the standard Java bytecode classes at transfer_classes. If you are not going to use the package from Android, you can delete it.
*'''modes''': Text file that lists the path of the available modes inside the package that is used by lttoolbox-java. It takes a few bytes and can rarely be removed, so please don't touch it unless you know what you are doing.
*'''README''': Text file describing the content of the package.

== Creating language pair packages ==

A simple bash script, [https://apertium.svn.sourceforge.net/svnroot/apertium/branches/gsoc2012/artetxem/apertium-pack-j apertium-pack-j], can be used to easily create language pair packages. It requires having the last version of [[lttoolbox-java]] as well as the [http://developer.android.com/sdk/index.html Android SDK], and their location must be specified by setting the <code>LTTOOLBOX_JAVA_PATH</code> and <code>ANDROID_SDK_PATH</code> environment variables. After that, you can simply run it passing the path to the mode files for which you want to generate the package as argument, and a ready-to-use package would be created by the script. For instance, the following command would create a ready-to-use package for the Esperanto ⇆ English language pair named <code>apertium-eo-en.jar</code> in my machine:

<pre>
export LTTOOLBOX_JAVA_PATH="/usr/local/share/apertium/lttoolbox.jar"
export ANDROID_SDK_PATH="/home/mikel/developer/android-sdk-linux"
./apertium-pack-j /usr/local/share/apertium/modes/eo-en.mode /usr/local/share/apertium/modes/en-eo.mode
</pre>

As you can see, I simply specify the correct location of lttoolbox-java and android-sdk in my machine, and pass the location of eo-en.mode and en-eo.mode (the main modes that correspond to the Esperanto ⇆ English language pair) as argument to apertium-pack-j.

== List of ready-to-use packages ==

Out of the 31 released pairs, the following 24 have fully working and ready-to-use packages that are maintained under the <code>builds/</code> directory at [[SVN]]. You can directly launch them in a Java enabled browser by clicking in the "JWS" links. You can also download the JARs and run them as standard Java applications or use them from a client application by clicking in the "JAR" links.

{|style="border: 0px solid #fbfbfb"
|style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
*Afrikaans ⇆ Dutch ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-af-nl/apertium-af-nl.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-af-nl/apertium-af-nl.jar JAR])
*Basque → English ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eu-en/apertium-eu-en.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eu-en/apertium-eu-en.jar JAR])
*Basque → Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eu-es/apertium-eu-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eu-es/apertium-eu-es.jar JAR])
*Catalan ⇆ Italian ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-ca-it/apertium-ca-it.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-ca-it/apertium-ca-it.jar JAR])
*English ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-ca/apertium-en-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-ca/apertium-en-ca.jar JAR])
*English ⇆ Galician ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-gl/apertium-en-gl.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-gl/apertium-en-gl.jar JAR])
|style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
*English ⇆ Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-es/apertium-en-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-es/apertium-en-es.jar JAR])
*Esperanto ← Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-ca/apertium-eo-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-ca/apertium-eo-ca.jar JAR])
*Esperanto ⇆ English ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-en/apertium-eo-en.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-en/apertium-eo-en.jar JAR])
*Esperanto ← French ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-fr/apertium-eo-fr.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-fr/apertium-eo-fr.jar JAR])
*Esperanto ← Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-es/apertium-eo-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-es/apertium-eo-es.jar JAR])
*French ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-ca/apertium-fr-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-ca/apertium-fr-ca.jar JAR])
|style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
*French ⇆ Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-es/apertium-fr-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-es/apertium-fr-es.jar JAR])
*Haitian → English ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-ht-en/apertium-ht-en.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-ht-en/apertium-ht-en.jar JAR])
*Occitan ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-oc-ca/apertium-oc-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-oc-ca/apertium-oc-ca.jar JAR])
*Occitan ⇆ Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-oc-es/apertium-oc-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-oc-es/apertium-oc-es.jar JAR])
*Portuguese ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-ca/apertium-pt-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-ca/apertium-pt-ca.jar JAR])
*Portuguese ⇆ Galician ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-gl/apertium-pt-gl.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-gl/apertium-pt-gl.jar JAR])
|style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
*Spanish ⇆ Aragonese ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-an/apertium-es-an.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-an/apertium-es-an.jar JAR])
*Spanish ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ca/apertium-es-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ca/apertium-es-ca.jar JAR])
*Spanish ⇆ Galician ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-gl/apertium-es-gl.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-gl/apertium-es-gl.jar JAR])
*Spanish ⇆ Portuguese ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-pt/apertium-es-pt.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-pt/apertium-es-pt.jar JAR])
*Spanish ← Romanian ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ro/apertium-es-ro.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ro/apertium-es-ro.jar JAR])
*Swedish → Danish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-sv-da/apertium-sv-da.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-sv-da/apertium-sv-da.jar JAR])
|-
|}

== Problematic language pairs ==

It is not possible to create a package for the last released version of Spanish ⇆ Asturian (apertium-es-ast), although, in principle, the pair is supposed to be compatible. The issue seems to be caused by unreasonably long rules in the transfer files that happen to be problematic due to the method size limitations of Java bytecode. Although the Java bytecode classes are now successfully generated, dx still hangs while trying to convert them to Dalvik bytecode. This means that, although the pair can be used from desktop applications, it would crash in Android, so creating a fully functional package for it is not possible yet.

== Language pairs with external dependencies ==

The following 6 released pairs depend on [[Apertium_and_Constraint_Grammar|CG]]:

*Breton → French (apertium-br-fr)
*Icelandic → English (apertium-is-en)
*Macedonian ⇆ Bulgarian (apertium-mk-bg)
*Macedonian → English (apertium-mk-en)
*Norwegian Nynorsk ⇆ Bokmål (apertium-nn-nb)
*Welsh → English (apertium-cy-en)

Invoking external programs is supported by language pair packages, so it is still possible to create packages for these pairs. However, you will need to install [[Apertium_and_Constraint_Grammar|CG]] in your machine for them to work. Due to this limitation, precompiled binaries are not offered for these pairs, but you can still create them by following the instructions in the previous section.

@@ Line 38: / Line 38: @@
 Out of the 31 released pairs, the following 25 have fully working and ready-to-use packages that are maintained under the <code>builds/</code> directory at [[SVN]]. You can directly launch them in a Java enabled browser by clicking in the ''JWS'' links. You can also download the JARs and run them as standard Java applications or use them from a client application by clicking in the ''JAR'' links.
+'''The list below is outdated.'''
+In 2020 the pairs can be found here: https://svn.code.sf.net/p/apertium/svn/builds/language-pairs
 {|style="border: 0px solid #fbfbfb"

@@ Line 74: / Line 74: @@
 == Language pairs with external dependencies ==
-The following 6 released pairs depend on [[Apertium_and_Constraint_Grammar|CG]]:
+The following 7 released pairs depend on [[Apertium_and_Constraint_Grammar|CG]]:
 *Breton → French (''apertium-br-fr'')

@@ Line 82: / Line 82: @@
 *Norwegian Nynorsk ⇆ Bokmål (''apertium-nn-nb'')
 *Welsh → English (''apertium-cy-en'')
+*Kazakh ⇆ Tatar (''apertium-kaz-tat'')
 Invoking external programs is supported by language pair packages, so it is still possible to create packages for these pairs. However, you will need to install [[Apertium_and_Constraint_Grammar|CG]] in your machine for them to work. Due to this limitation, precompiled binaries are not offered for these pairs, but you can still create them by following the instructions in the previous section.

@@ Line 37: / Line 37: @@
 == List of ready-to-use packages ==
-Out of the 31 released pairs, the following 24 have fully working and ready-to-use packages that are maintained under the <code>builds/</code> directory at [[SVN]]. You can directly launch them in a Java enabled browser by clicking in the ''JWS'' links. You can also download the JARs and run them as standard Java applications or use them from a client application by clicking in the ''JAR'' links.
+Out of the 31 released pairs, the following 25 have fully working and ready-to-use packages that are maintained under the <code>builds/</code> directory at [[SVN]]. You can directly launch them in a Java enabled browser by clicking in the ''JWS'' links. You can also download the JARs and run them as standard Java applications or use them from a client application by clicking in the ''JAR'' links.
 {|style="border: 0px solid #fbfbfb"
@@ Line 47: / Line 47: @@
 *English ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-ca/apertium-en-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-ca/apertium-en-ca.jar JAR])
 *English ⇆ Galician ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-gl/apertium-en-gl.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-gl/apertium-en-gl.jar JAR])
-|style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
 *English ⇆ Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-es/apertium-en-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-en-es/apertium-en-es.jar JAR])
+|style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
 *Esperanto ← Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-ca/apertium-eo-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-ca/apertium-eo-ca.jar JAR])
 *Esperanto ⇆ English ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-en/apertium-eo-en.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-en/apertium-eo-en.jar JAR])
@@ Line 54: / Line 54: @@
 *Esperanto ← Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-es/apertium-eo-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-eo-es/apertium-eo-es.jar JAR])
 *French ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-ca/apertium-fr-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-ca/apertium-fr-ca.jar JAR])
+*French ⇆ Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-es/apertium-fr-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-es/apertium-fr-es.jar JAR])
 |style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
-*French ⇆ Spanish ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-es/apertium-fr-es.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-fr-es/apertium-fr-es.jar JAR])
 *Haitian → English ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-ht-en/apertium-ht-en.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-ht-en/apertium-ht-en.jar JAR])
 *Occitan ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-oc-ca/apertium-oc-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-oc-ca/apertium-oc-ca.jar JAR])
@@ Line 61: / Line 61: @@
 *Portuguese ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-ca/apertium-pt-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-ca/apertium-pt-ca.jar JAR])
 *Portuguese ⇆ Galician ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-gl/apertium-pt-gl.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-pt-gl/apertium-pt-gl.jar JAR])
+*Spanish ⇆ Aragonese ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-an/apertium-es-an.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-an/apertium-es-an.jar JAR])
 |style="width:11%; border: 0px solid #fbfbfb; font-size:95%; background:#fbfbfb; vertical-align: top;"|
-*Spanish ⇆ Aragonese ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-an/apertium-es-an.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-an/apertium-es-an.jar JAR])
+*Spanish ⇆ Asturian ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ast/apertium-es-ast.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ast/apertium-es-ast.jar JAR])
 *Spanish ⇆ Catalan ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ca/apertium-es-ca.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-ca/apertium-es-ca.jar JAR])
 *Spanish ⇆ Galician ([https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-gl/apertium-es-gl.jnlp JWS], [https://apertium.svn.sourceforge.net/svnroot/apertium/builds/apertium-es-gl/apertium-es-gl.jar JAR])
@@ Line 70: / Line 71: @@
 |-
 |}
-== Problematic language pairs ==
-It is not possible to create a package for the last released version of Spanish ⇆ Asturian (''apertium-es-ast''), although, in principle, the pair is supposed to be compatible. The issue seems to be caused by unreasonably long rules in the transfer files that happen to be problematic due to the method size limitations of Java bytecode. Although the Java bytecode classes are now successfully generated, dx still hangs while trying to convert them to Dalvik bytecode. This means that, although the pair can be used from desktop applications, it would crash in Android, so creating a fully functional package for it is not possible yet.
 == Language pairs with external dependencies ==

@@ Line 19: / Line 19: @@
 == Creating language pair packages ==
-A simple bash script, [https://apertium.svn.sourceforge.net/svnroot/apertium/branches/gsoc2012/artetxem/apertium-pack-j apertium-pack-j], can be used to easily create language pair packages. It requires having the last version of [[lttoolbox-java]] as well as the [http://developer.android.com/sdk/index.html Android SDK], and their location must be specified by setting the <code>LTTOOLBOX_JAVA_PATH</code> and <code>ANDROID_SDK_PATH</code> environment variables. After that, you can simply run it passing the path to the mode files for which you want to generate the package as argument, and a ready-to-use package would be created by the script. For instance, the following command would create a ready-to-use package for the Esperanto ⇆ English language pair named <code>apertium-eo-en.jar</code> in my machine:
+In order to create language pair packages, a working installation of the last version of [[lttoolbox-java]] at [[SVN]] is required. Provided that you meet this requirement, you simply need to run <code>apertium-pack-j</code> passing the mode files for which you want to generate the package as argument. For instance, the following command would create a ready-to-use package for the Esperanto ⇆ English language pair named <code>apertium-eo-en.jar</code> (the first argument determines the name of the output file):
+ apertium-pack-j /usr/local/share/apertium/modes/eo-en.mode /usr/local/share/apertium/modes/en-eo.mode
+=== Creating Android compatible packages ===
+In order to create Android compatible packages, you need a working installation of the [http://developer.android.com/sdk/index.html Android SDK]. Once you have it, you need to specify its location by setting the <code>ANDROID_SDK_PATH</code> environment variable as follows:
 <pre>
-export LTTOOLBOX_JAVA_PATH="/usr/local/share/apertium/lttoolbox.jar"
 export ANDROID_SDK_PATH="/home/mikel/developer/android-sdk-linux"
-./apertium-pack-j /usr/local/share/apertium/modes/eo-en.mode /usr/local/share/apertium/modes/en-eo.mode
 </pre>
+You will need to replace <code>/home/mikel/developer/android-sdk-linux</code> with the right path of your Android SDK installation.
-As you can see, I simply specify the correct location of [[lttoolbox-java]] and the [http://developer.android.com/sdk/index.html Android SDK] in my machine, and pass the location of <code>eo-en.mode</code> and <code>en-eo.mode</code> (the main modes that correspond to the Esperanto ⇆ English language pair) as argument to [https://apertium.svn.sourceforge.net/svnroot/apertium/branches/gsoc2012/artetxem/apertium-pack-j apertium-pack-j].
+Once you have done it, simply run <code>apertium-pack-j</code> as explained above, and the generated package will be compatible with Android devices.
 == List of ready-to-use packages ==

@@ Line 1: / Line 1: @@
 {{TOCD}}
+[[Image:Language_pair_packages_screenshot1.png|thumb|350px|right|The English ⇆ Spanish package running as a standalone Java application. The same file could be used from other client applications like [[Apertium-Caffeine]] or [[Apertium-OmegaT]].]]
-Language pair packages are standalone JARs that can be run independently as well as used from other client apps like [[Apertium-Caffeine]] or [[Apertium-OmegaT]]. The only prerequisite to use them is a Java VM (apertium, lttoolbox or lttoolbox-java are NOT required), and they can work on practically any platform (Linux, OS X, Windows and even Android!).
+'''Language pair packages''' are standalone JARs that can be run independently as well as used from other client applications like [[Apertium-Caffeine]] or [[Apertium-OmegaT]]. The only prerequisite to use them is Java 6 or better (apertium, lttoolbox or lttoolbox-java are ''NOT'' required), and they can work on practically any platform (Linux, OS X, Windows and even Android!).
 == Internal structure ==
@@ Line 11: / Line 12: @@
 *'''transfer_classes/''': Directory that contains the [[Bytecode_for_transfer|Java bytecode classes for transfer]]. This is only used when using the package from standard Java so, if you are going to use it exclusively from Android, you can delete it.
 *'''org/''': Directory that contains the [[lttoolbox-java]] engine, which makes the package self-executable. If you are not interested on this feature (presumably, because you are going to use the package exclusively from client programs), you can delete it.
-*'''META-INF/''': Directory that contains the MANIFEST.MF of this Jar, which is used by Java. It takes a few bytes and can rarely be removed, so please don't touch it unless you know what you are doing.
+*'''META-INF/''': Directory that contains the <code>MANIFEST.MF</code> of this Jar, which is used by Java. It takes a few bytes and can rarely be removed, so please don't touch it unless you know what you are doing.
-*'''classes.dex''': Dalvik bytecode of the transfer classes, used by Android instead of the standard Java bytecode classes at transfer_classes. If you are not going to use the package from Android, you can delete it.
+*'''classes.dex''': Dalvik bytecode of the transfer classes, used by Android instead of the standard Java bytecode classes at <code>transfer_classes/</code>. If you are not going to use the package from Android, you can delete it.
-*'''modes''': Text file that lists the path of the available modes inside the package that is used by lttoolbox-java. It takes a few bytes and can rarely be removed, so please don't touch it unless you know what you are doing.
+*'''modes''': Text file that lists the path of the available modes inside the package that is used by [[lttoolbox-java]]. It takes a few bytes and can rarely be removed, so please don't touch it unless you know what you are doing.
 *'''README''': Text file describing the content of the package.
@@ Line 26: / Line 27: @@
 </pre>
-As you can see, I simply specify the correct location of lttoolbox-java and android-sdk in my machine, and pass the location of eo-en.mode and en-eo.mode (the main modes that correspond to the Esperanto ⇆ English language pair) as argument to apertium-pack-j.
+As you can see, I simply specify the correct location of [[lttoolbox-java]] and the [http://developer.android.com/sdk/index.html Android SDK] in my machine, and pass the location of <code>eo-en.mode</code> and <code>en-eo.mode</code> (the main modes that correspond to the Esperanto ⇆ English language pair) as argument to [https://apertium.svn.sourceforge.net/svnroot/apertium/branches/gsoc2012/artetxem/apertium-pack-j apertium-pack-j].
 == List of ready-to-use packages ==
-Out of the 31 released pairs, the following 24 have fully working and ready-to-use packages that are maintained under the <code>builds/</code> directory at [[SVN]]. You can directly launch them in a Java enabled browser by clicking in the "JWS" links. You can also download the JARs and run them as standard Java applications or use them from a client application by clicking in the "JAR" links.
+Out of the 31 released pairs, the following 24 have fully working and ready-to-use packages that are maintained under the <code>builds/</code> directory at [[SVN]]. You can directly launch them in a Java enabled browser by clicking in the ''JWS'' links. You can also download the JARs and run them as standard Java applications or use them from a client application by clicking in the ''JAR'' links.
 {|style="border: 0px solid #fbfbfb"
@@ Line 66: / Line 67: @@
 == Problematic language pairs ==
-It is not possible to create a package for the last released version of Spanish ⇆ Asturian (apertium-es-ast), although, in principle, the pair is supposed to be compatible. The issue seems to be caused by unreasonably long rules in the transfer files that happen to be problematic due to the method size limitations of Java bytecode. Although the Java bytecode classes are now successfully generated, dx still hangs while trying to convert them to Dalvik bytecode. This means that, although the pair can be used from desktop applications, it would crash in Android, so creating a fully functional package for it is not possible yet.
+It is not possible to create a package for the last released version of Spanish ⇆ Asturian (''apertium-es-ast''), although, in principle, the pair is supposed to be compatible. The issue seems to be caused by unreasonably long rules in the transfer files that happen to be problematic due to the method size limitations of Java bytecode. Although the Java bytecode classes are now successfully generated, dx still hangs while trying to convert them to Dalvik bytecode. This means that, although the pair can be used from desktop applications, it would crash in Android, so creating a fully functional package for it is not possible yet.
 == Language pairs with external dependencies ==
@@ Line 72: / Line 73: @@
 The following 6 released pairs depend on [[Apertium_and_Constraint_Grammar|CG]]:
-*Breton → French (apertium-br-fr)
+*Breton → French (''apertium-br-fr'')
-*Icelandic → English (apertium-is-en)
+*Icelandic → English (''apertium-is-en'')
-*Macedonian ⇆ Bulgarian (apertium-mk-bg)
+*Macedonian ⇆ Bulgarian (''apertium-mk-bg'')
-*Macedonian → English (apertium-mk-en)
+*Macedonian → English (''apertium-mk-en'')
-*Norwegian Nynorsk ⇆ Bokmål (apertium-nn-nb)
+*Norwegian Nynorsk ⇆ Bokmål (''apertium-nn-nb'')
-*Welsh → English (apertium-cy-en)
+*Welsh → English (''apertium-cy-en'')
 Invoking external programs is supported by language pair packages, so it is still possible to create packages for these pairs. However, you will need to install [[Apertium_and_Constraint_Grammar|CG]] in your machine for them to work. Due to this limitation, precompiled binaries are not offered for these pairs, but you can still create them by following the instructions in the previous section.