- 1 To try Apertium
- 2 For those who want to install Apertium locally, and developers
- 2.1 Installing: a summary
- 2.2 Alternatives
- 3 Notes
- 4 Installation Videos
- 5 Minimal installation from SVN
To try Apertium
You can go online to the front page :)
There are several applications which work from the desktop without full installation. For these and more graphical user interfaces, services, plugins, etc. goto Tools.
If you would like install instructions for 'Apertium viewer', 'apy' (the Apertium server) etc. got to Tools. The install instructions can be found with the tool descriptions.
For those who want to install Apertium locally, and developers
Installing: a summary
Most people will need to,
Install Apertium Core by packaging/virtual environment
For translators: Install language data/dictionaries/pairs from repositories
Install language data using packaging, including hints about the Apertium package repository.
For language developers: Install language data/dictionaries/pairs by compiling
- Start a new language pair: How to bootstrap a new pair
- Work on an existing language pair: Install language data by compiling
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.
- 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'.
- 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.
- 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'.
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
Minimal installation from SVN
This page is deprecated, and the information split across other pages.
It used to contain instructions on how to compile Apertium core. For this, please see Install Apertium core by compiling
How to create language builds with new and exisiting repository information. Please see Install language data by compiling
And details about the HFST and CG modules. Please see Installation of grammar libraries
Or start from the information root at Installation?