Difference between revisions of "Installation"

From Apertium
Jump to navigation Jump to search
(windows :/)
(Snip VBox and Windows<10)
 
(66 intermediate revisions by 15 users not shown)
Line 1: Line 1:
[[Installation (français)|En français]]
{{Main page header}}
{{Main page header}}


= To try Apertium =
'''Unix''' users (GNU/Linux, Mac, BSD) who wish to hack on Apertium should follow these three stages to installing the core packages and language data:
== Online ==
# Install prerequisites specific to your operating system
#*[[Apertium on Ubuntu|Ubuntu or Debian]]
#*[[Apertium on openSUSE|openSUSE]]
#*[[Prerequisites for Mac OS X|Mac OS X]]
#*[[Apertium on Arch Linux|Arch Linux]]
#*[[Apertium on Fedora|Fedora]]
#*[[Apertium on Mandriva|Mandriva]]
# Install apertium and related packages from SVN
#*Follow [[Minimal installation from SVN]], this should be general enough to cover all operating systems
# Fix any problems :)
#* General [[Installation Troubleshooting]]


* https://apertium.org is the official site, and offers all the released language pairs
For '''Windows''' users, the best method is to run the [[Apertium VirtualBox]], which lets you run a Unix in your Windows (and comes with Apertium from SVN pre-installed). Alternatively, you can compile it for Windows using Cygwin; documentation for how to compile on Windows manually is at [[Apertium on Windows]] <small>(there is a simple script at [[Apertium guide for Windows users]], but it is currently out-of-date and in need of updating)</small>.


Alternative installations:
Some language pairs require extra packages like '''Constraint Grammar''' (vislcg3) or '''HFST''' in addition to apertium/lttoolbox/apertium-lex-tools. See the section on [[Apertium and Constraint Grammar#Installing_VISL_CG3|installing vislcg3]] and [[HFST]], respectively. You can tell if a package requires CG if it has an .rlx file, and HFST if it has a .lexc file.


* http://aplica.prompsit.com/ – Prompsit is a company heavily involved in development of the Apertium platform, and also offers a simple web interface to the released language pairs
There are released tarball packages on the [http://www.apertium.org/?id=downloading official download page]. These are meant for packagers, and user who are ''not'' going to develop on apertium. These are installed like the SVN packages, except you use <code>./configure</code> instead of <code>./autogen.sh</code>.
* https://www.softcatala.org/traductor/ – Softcatalà works on Catalan localisation and offers the Catalan←→* language pairs here
* http://jorgal.uit.no/ – the University of Tromsø works on Saami language pairs; this site runs the latest in-development version of Northern Saami→Norwegian Bokmål
* http://gtweb.uit.no/tolkimine/ – another site by University of Tromsø, the latest in-development version of Estonian←→Finnish
* https://softaragones.org/traductor/ - Apertium Luengas d'Aragón - Softaragonés offers here the language pairs between the three native languages of Aragon: Aragonese - Catalan - Spanish


== Offline, desktop ==
'''Android''' users can download the [https://play.google.com/store/apps/details?id=org.apertium.android Apertium offline translator app], more info at [[Apertium Android]].


There are several applications which work from the desktop without full installation.

The easiest solution for Windows and Mac users is [[Apertium Simpleton UI]]. You can install translator packages from within that program (though only the pairs that are on the website, not the "in development" pairs).

[[Tools#Tools for users / translators]] has more graphical user interfaces for translators, though you'll have to install translator packages separately.

To install translator packages, see the following section [[#For those who want to install Apertium locally, and developers]]

== Offline, mobile ==

* https://play.google.com/store/apps/details?id=org.apertium.android – Simple offline translations for Android (not all released pairs supported yet), see [[Apertium Android]]
* http://www.mitzuli.com/en/ – More fully-featured offline translations app for Android (not all released pairs supported yet), see [[Mitzuli]]
* https://www.softcatala.org/programes/traductor-softcatala/ – Catalan translation app for Android/iPhone

= For those who want to install Apertium locally, and developers=
How to install Apertium core<ref>Apertium is a big system. There are many plugins, scripts, and extension projects. The core, the code which translates, is a multi-step set of tools joined by a stream format and, nowadays, invoked by scripts called 'modes'. You may also see the names 'lt-toolbox'/'lt-tools', 'apertium-lex-tools', and the simple title 'apertium'. These refer to groupings of the tools.

Packaged or compiled, these tools can be installed as one unit. From here on, we call them 'Apertium core'.
</ref> and language data on your system (developers may also want to consider their operating environment<ref>
Apertium is written to be platform-independent. However, it can be difficult to maintain platform-independence over a project this wide. If you intend to do something deep with Apertium, you will gain more help from the tools if you use the [http://ubuntu.com Ubuntu], or a similar Debian-based, operating system.

In no way does this mean that the Apertium project favours this platform.
</ref>).

==Installing: a summary==
Most people will need Apertium core, after which they may choose to install precompiled language data or development language data.

===Install Apertium Core by packaging/virtual environment===
Most people will need to install Apertium core.
* Linux systems: [[Install Apertium core using packaging]]
* Windows (10 or newer): Use WSL. First follow https://docs.microsoft.com/en-us/windows/wsl/install-win10 then continue with [[Install Apertium core using packaging]]
* macOS: [[Apertium on Mac OS X]]

=== For translators: Install language data/dictionaries/pairs from repositories ===
Translators will probably want to [[install language data using packaging]], including hints about the Apertium package repository.

=== For language developers: Install language data/dictionaries/pairs by compiling ===
Language developers may want to do one of the following:
* Start a new language pair: [[How to bootstrap a new pair]]
* Work on an existing language pair: [[Install language data by compiling]]

==Alternatives==

===Installing Apertium core by compiling===

Apertium maintains a package repository that is up-to-date and reliable. If you do not want to work in core, or develop languages, please use either packaging or a virtual environment. The packages stay up-to-date and are stable. A compile will waste your time.

However, if you are planning to work on Apertium core, or have an operating system not covered above, go right ahead, [[Install Apertium core by compiling]]<ref name="about installing">Most people know the word 'install'. It means 'put code in my operating system'. When developing, it is not usual to fully 'install'. You get the code working enough to get results.

This is relevant to Apertium, which needs a rapid cycle for re-compiles. If you follow instructions to compile code, you will be discouraged from 'installing' builds. When we use the word 'install', we mean 'get code working on my computer'.</ref>

= Notes =
<references/>

= Installation Videos =

Most of these videos have been produced by Google Code-In students.

* Using Apertium Virtualbox on Windows: https://youtu.be/XCUWMCJkRDo
* Installing Apertium on Ubuntu (Romanian, English): https://www.youtube.com/watch?v=vy7rWy2u_m0
* Ubuntu'ya Apertium Kurulumu / Apertium installation on Ubuntu (Turkish, English subtitles): https://www.youtube.com/watch?v=I__-BiQe7zg
* Apertium on Slitaz (English): https://youtu.be/fCluA03oIXY
* How to Install Apertium On Macintosh: https://www.youtube.com/watch?v=oSuovCCsa68


[[Category:Installation]]
[[Category:Installation]]

Latest revision as of 12:51, 1 April 2024

En français

InstallationResourcesContactDocumentationDevelopmentTools

Gnome-home.png Home PageBugs.png BugsInternet.png WikiGaim.png Chat


To try Apertium[edit]

Online[edit]

Alternative installations:

  • http://aplica.prompsit.com/ – Prompsit is a company heavily involved in development of the Apertium platform, and also offers a simple web interface to the released language pairs
  • https://www.softcatala.org/traductor/ – Softcatalà works on Catalan localisation and offers the Catalan←→* language pairs here
  • http://jorgal.uit.no/ – the University of Tromsø works on Saami language pairs; this site runs the latest in-development version of Northern Saami→Norwegian Bokmål
  • http://gtweb.uit.no/tolkimine/ – another site by University of Tromsø, the latest in-development version of Estonian←→Finnish
  • https://softaragones.org/traductor/ - Apertium Luengas d'Aragón - Softaragonés offers here the language pairs between the three native languages of Aragon: Aragonese - Catalan - Spanish

Offline, desktop[edit]

There are several applications which work from the desktop without full installation.

The easiest solution for Windows and Mac users is Apertium Simpleton UI. You can install translator packages from within that program (though only the pairs that are on the website, not the "in development" pairs).

Tools#Tools for users / translators has more graphical user interfaces for translators, though you'll have to install translator packages separately.

To install translator packages, see the following section #For those who want to install Apertium locally, and developers

Offline, mobile[edit]

For those who want to install Apertium locally, and developers[edit]

How to install Apertium core[1] and language data on your system (developers may also want to consider their operating environment[2]).

Installing: a summary[edit]

Most people will need Apertium core, after which they may choose to install precompiled language data or development language data.

Install Apertium Core by packaging/virtual environment[edit]

Most people will need to install Apertium core.

For translators: Install language data/dictionaries/pairs from repositories[edit]

Translators will probably want to install language data using packaging, including hints about the Apertium package repository.

For language developers: Install language data/dictionaries/pairs by compiling[edit]

Language developers may want to do one of the following:

Alternatives[edit]

Installing Apertium core by compiling[edit]

Apertium maintains a package repository that is up-to-date and reliable. If you do not want to work in core, or develop languages, please use either packaging or a virtual environment. The packages stay up-to-date and are stable. A compile will waste your time.

However, if you are planning to work on Apertium core, or have an operating system not covered above, go right ahead, Install Apertium core by compiling[3]

Notes[edit]

  1. Apertium is a big system. There are many plugins, scripts, and extension projects. The core, the code which translates, is a multi-step set of tools joined by a stream format and, nowadays, invoked by scripts called 'modes'. You may also see the names 'lt-toolbox'/'lt-tools', 'apertium-lex-tools', and the simple title 'apertium'. These refer to groupings of the tools. Packaged or compiled, these tools can be installed as one unit. From here on, we call them 'Apertium core'.
  2. Apertium is written to be platform-independent. However, it can be difficult to maintain platform-independence over a project this wide. If you intend to do something deep with Apertium, you will gain more help from the tools if you use the Ubuntu, or a similar Debian-based, operating system. In no way does this mean that the Apertium project favours this platform.
  3. Most people know the word 'install'. It means 'put code in my operating system'. When developing, it is not usual to fully 'install'. You get the code working enough to get results. This is relevant to Apertium, which needs a rapid cycle for re-compiles. If you follow instructions to compile code, you will be discouraged from 'installing' builds. When we use the word 'install', we mean 'get code working on my computer'.

Installation Videos[edit]

Most of these videos have been produced by Google Code-In students.