Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Installation of grammar libraries

From Apertium
(Difference between revisions)
Jump to: navigation, search
(New page to gather this information together)
 
(link updates)
Line 1: Line 1:
 
{{TOCD}}
 
{{TOCD}}
   
Some language pairs need code libraries which are not part of Apertium core. You may not know until a compile starts streaming messages.
+
Some language pairs need code libraries which are not part of Apertium core. You may not know until a compile sighs, 'fail, fail, fail'. You can tell if a package requires CG if it has an .rlx file, and HFST if it has a .lexc file.
   
Fortunately (for Debian-derivative users), these rule-builders are available through the [[Installation#The private repository packages]]. You can access and install the packages even if your Apertium is a compiled build. Otherwise, you may need to compile.
+
Fortunately (for those who use Apertium repositories), these rule-builders are available through the [[Install Apertium Core using packaging | private repository packages]]. You can access and install the packages even if your Apertium is a compiled build. Otherwise, you will need to compile.
   
   
Line 17: Line 17:
   
 
==== compiling ====
 
==== compiling ====
See [[Vislcg3#Installing_VISL_CG3]].
+
See [[Apertium and Constraint Grammar#Installing_VISL_CG3|installing vislcg3]].
   
 
Note that you have to have [http://site.icu-project.org/ ICU] installed beforehand (available through most GNU/Linux package managers, in Arch Linux as <code>icu</code>, in Debian/Ubuntu as <code>libicu-dev</code>, in Macports as <code>icu</code>).
 
Note that you have to have [http://site.icu-project.org/ ICU] installed beforehand (available through most GNU/Linux package managers, in Arch Linux as <code>icu</code>, in Debian/Ubuntu as <code>libicu-dev</code>, in Macports as <code>icu</code>).
Line 35: Line 35:
   
 
==== compiling ====
 
==== compiling ====
See [[HFST#Building and installing HFST]].
+
See [[HFST#Building and installing HFST|]].
   
 
[[Category:Installation]]
 
[[Category:Installation]]
  +
[[Category:Constraint Grammar]]
  +
[[Category:HFST]]
 
[[Category:Documentation in English]]
 
[[Category:Documentation in English]]

Revision as of 16:07, 22 April 2017

Contents

Some language pairs need code libraries which are not part of Apertium core. You may not know until a compile sighs, 'fail, fail, fail'. You can tell if a package requires CG if it has an .rlx file, and HFST if it has a .lexc file.

Fortunately (for those who use Apertium repositories), these rule-builders are available through the private repository packages. You can access and install the packages even if your Apertium is a compiled build. Otherwise, you will need to compile.


VISL CG3 ('vislcg3' / 'cg-proc' / 'cg-comp')

e.g. the Macedonian→English, Breton→French, Nynorsk-Bokmål pairs.

packages

Debian / Ubuntu Derivatives
wget http://apertium.projectjj.com/apt/install-nightly.sh -O - | sudo bash
sudo apt-get install cg3

compiling

See installing vislcg3.

Note that you have to have ICU installed beforehand (available through most GNU/Linux package managers, in Arch Linux as icu, in Debian/Ubuntu as libicu-dev, in Macports as icu).


HFST ('hfst-proc' / 'hfst-lexc' / 'hfst-twolc')

e.g. the Turkic and Saami pairs.

packages

Debian / Ubuntu Derivatives
wget http://apertium.projectjj.com/apt/install-nightly.sh -O - | sudo bash
sudo apt-get install hfst


compiling

See [[HFST#Building and installing HFST|]].

Personal tools