Install language data by compiling - Revision history

Marcriera: Add make langs

2024-07-09T17:38:39Z

Add make langs

Popcorndude: -get is installed by default now

2023-03-02T19:44:38Z

-get is installed by default now

Sushain: don't need SVN!

2018-12-11T04:07:03Z

don't need SVN!

Hectoralos at 04:55, 10 March 2018

2018-03-10T04:55:24Z

Shardulc: GitHub migration

2018-03-09T03:29:07Z

GitHub migration

Rcrowther at 15:36, 27 April 2017

2017-04-27T15:36:31Z

Rcrowther at 15:04, 27 April 2017

2017-04-27T15:04:01Z

Rcrowther at 15:05, 24 April 2017

2017-04-24T15:05:28Z

Rcrowther at 15:03, 24 April 2017

2017-04-24T15:03:38Z

Rcrowther at 15:00, 24 April 2017

2017-04-24T15:00:40Z

@@ Line 85: / Line 85: @@
 In some rare circumstances, an Apertium core is hand-compiled then placed at a custom prefix. The reasons you chose to do that may mean you need also to install language data at a custom prefix. In which case, we assume you know what you are doing...
+==== Simple build ====
+Once both monolingual packages and the pair are properly configured using <code>autogen.sh</code>, you can build everything with a single command from the pair (apertium-xxx-yyy):
+<pre>
+make langs
+</pre>
 ==Install (or not)==

@@ Line 40: / Line 40: @@
 ==== By script ====
 If you've already got the core tools installed and you download Apertium languages frequently, then there's a script that can download and setup a language data (pair + possible dependencies) for you. The script can look in trunk, staging, nursery, and incubator.
-Please consider that the script can not download a mono-dictionary.
 If you installed the <code>apertium-all-dev</code> package, you already have the script running from the commandline,
@@ Line 48: / Line 46: @@
 apertium-get
 </pre>
-To get the script and release execution permission, go to the directory where you want your Apertium data to be, and run,
-<pre>
-wget https://raw.githubusercontent.com/unhammer/apertium-get/master/apertium-get
-chmod +x apertium-get
-</pre>
-The <code>apertium-get</code> script is sophisticated enough to offer help,
-<pre>
-./apertium-get -h
-</pre>
 Wiki page on the script: [[Apertium-get]]

@@ Line 10: / Line 10: @@
 If you loaded Apertium core from packages, either from the Apertium or a public repository, then you will need compile tools. For a dictionary or pair, you will not need all the library installs needed for a full compile of Apertium. In operating systems/distros with a minimal build environment, you may only need,
-* subversion (SVN)
 * git
 * autoconf

@@ Line 25: / Line 25: @@
 git clone https://github.com/apertium/apertium-eo-en.git
 </pre>
+or also (and quicker):
+<pre>
+git clone --depth 1 https://github.com/apertium/apertium-eo-en.git
+</pre>
 To see the available 'mature' language mono dictionaries, go to git clone https://github.com/apertium/ and see the column 'languages'.

@@ Line 11: / Line 11: @@
 * subversion (SVN)
+* git
 * autoconf
 * automake
@@ Line 17: / Line 18: @@
 ==Download the language data==
-To see the available 'released' language pairs, go to https://svn.code.sf.net/p/apertium/svn/trunk/. Pairs in development are in the incubator/nursery/staging subdirectories of https://svn.code.sf.net/p/apertium/svn/.
+To see the available 'released' language pairs, go to https://apertium.github.io/apertium-on-github/source-browser.html and see the column 'trunk'. Pairs in development are in the 'incubator'/'nursery'/'staging' columns.
 e.g.
 <pre>
-svn checkout https://svn.code.sf.net/p/apertium/svn/trunk/apertium-eo-en
+git clone https://github.com/apertium/apertium-eo-en.git
 </pre>
-To see the available 'mature' language mono dictionaries, go to https://svn.code.sf.net/p/apertium/svn/languages/.
+To see the available 'mature' language mono dictionaries, go to git clone https://github.com/apertium/ and see the column 'languages'.
-* ''Note: please make sure that the directory where you put these files (i.e. where you run the <code>svn</code> command) doesn't contain spaces and other special characters. That may cause errors while compiling/linking.''
+* ''Note: please make sure that the directory where you put these files (i.e. where you run the <code>git</code> command) doesn't contain spaces and other special characters. That may cause errors while compiling/linking.''
@@ Line 116: / Line 117: @@
 To start work on the new translation pair, [[Apertium New Language Pair HOWTO]].
-If you have made changes and/or improvements to a pair, please see [[Contributing to an existing pair]]. You may even get to [[Using SVN]].
+If you have made changes and/or improvements to a pair, please see [[Contributing to an existing pair]]. You may even get to [[Using Git]].
 [[Category:Installation]]

← Older revision		Revision as of 15:36, 27 April 2017
Line 1:		Line 1:
			[[Installation minimale depuis SVN\|En français]]

	To start a new language pair, goto [[How to bootstrap a new pair]]. The instructions are very different. This page is for existing language data.		To start a new language pair, goto [[How to bootstrap a new pair]]. The instructions are very different. This page is for existing language data.

@@ Line 80: / Line 80: @@
 (where yyy is some language code).
-If this happens you must treat the missing language as part of a new pair. You can find full instructions at [[Install Create a new pair]]. In short, download the missing monodix and place it in the download with the missing language. <code>autogen.sh</code> then <code>make</code> both monodix folders then, in the bidex folder, run the binding configuration, then <code>make</code>,
+If this happens you must treat the missing language as part of a new pair. You can find full instructions at [[How to bootstrap a new pair]]. In short, download the missing monodix and place it in the download with the missing language. <code>autogen.sh</code> then <code>make</code> both monodix folders then, in the bidex folder, run the binding configuration, then <code>make</code>,
 <pre>
@@ Line 112: / Line 112: @@
 If you have not used Apertium before, try [[Modes introduction]] and [[Monodix basics]].
-To start the new translation pair, [[Apertium New Language Pair HOWTO]].
+To start work on the new translation pair, [[Apertium New Language Pair HOWTO]].
 If you have made changes and/or improvements to a pair, please see [[Contributing to an existing pair]]. You may even get to [[Using SVN]].