Difference between revisions of "Installation"

From Apertium
Jump to navigation Jump to search
Line 2: Line 2:
{{Main page header}}
{{Main page header}}


== To try Apertium ==
= To try Apertium =
You can go online to the [https://apertium.org front page] :)
You can go online to the [https://apertium.org front page] :)


Line 11: Line 11:




== For those who want to install Apertium locally, and developers==
= 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.
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.


Line 21: Line 21:
</ref>).
</ref>).


===Installing: a summary===
==Installing: a summary==
Most people will need Apertium core, after which they may choose to install precompiled language data or development language data.
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====
===Install Apertium Core by packaging/virtual environment===
Most people will need to install Apertium core.
Most people will need to install Apertium core.
* Linux systems: [[Install Apertium core using packaging]]
* Linux systems: [[Install Apertium core using packaging]]
* Windows and Apple systems: [[Apertium VirtualBox]]
* Windows and Apple systems: [[Apertium VirtualBox]]


==== For translators: Install language data/dictionaries/pairs from repositories ====
=== 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.
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 ====
=== For language developers: Install language data/dictionaries/pairs by compiling ===
Language developers may want to do one of the following:
Language developers may want to do one of the following:
* Start a new language pair: [[How to bootstrap a new pair]]
* Start a new language pair: [[How to bootstrap a new pair]]
* Work on an existing language pair: [[Install language data by compiling]]
* Work on an existing language pair: [[Install language data by compiling]]


===Alternatives===
==Alternatives==


====Installing Apertium core 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 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.
Line 47: Line 47:
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>
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 ==
= Notes =
<references/>
<references/>


== Installation Videos ==
= Installation Videos =


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

Revision as of 00:34, 2 May 2017

En français

Installation • Resources • Contact • Documentation • Development • Tools

Gnome-home.png Home Page • Bugs.png Bugs • Internet.png Wiki • Gaim.png Chat

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

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

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.

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:

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[3]

Notes

  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

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

Retrieved from "https://wiki.apertium.org/w/index.php?title=Installation&oldid=62936"