Apertium-init
You can the apertium-init tool to create ("bootstrap") a directory for quick development of a transducer or translation pair.
Contents
Installing apertium-init
If needed (note that apertium-init
should already be installed on the CS lab machines!), download apertium-init and install it:
-
cd ~/ling073; git clone https://github.com/apertium/apertium-init; cd apertium-init; PREFIX=$HOME make install
Creating a language module
Create an hfst-based apertium language module (in your ~/ling073
directory), replacing xyz
with the ISO code of your language in all occurrences:
-
apertium-init -a hfst xyz
Rename the module ling073-xyz
if you want (so that it matches what will be in github later, and any further instructions):
-
mv apertium-xyz ling073-xyz
Notes:
- If get an error about SVN and the directory not being a working copy, then you have an old version of apertium-init.
- If something goes wrong (e.g., you make a typo), delete any directories/files that were created and try the step again.
For the first day assignment, skip down to #Pushing to github
Bootstrapping a translation pair
To bootstrap a translation pair whose primary function is to translate from language xyz
to language abc
, do the following:
- Make sure you have a copy of both of the language modules you'll need (one for each language) and that they are both initialised and compiled.
- Check which formalism each transducer is written in.
- The transducer you've written so far in this class should be written using
lexd
. If the transducer that the module you cloned for the other language has a file likeapertium-abc.abc.dix
, then it's written using lttoolbox; if it has a file likeapertium-abc.abc.lexc
, then it's written using HFST.
- The transducer you've written so far in this class should be written using
- The following command will initialise the directory for the translation pair:
-
apertium-init --a1 lexd --a2 hfst -t rtx --prefix ling073 xyz-abc
- The
--a1
and--a2
arguments tellapertium-init
what formalism your transducers are written in. You may need to say "lttoolbox
" instead of "hfst
" for one or more of those options. (If you are pairing withapertium-eng
you will need--a2 lttoolbox
.) The-t
indicates which formalism you want to use for structural transfer.
-
- Create a
ling073-xyz-abc
repository in the semester's github group (Ling073-sp21), set a remote origin in your repo, and push (for the last two, see #Push to github below). Make sure all members of your group have access to the repository. - Initialise the compiler (needed once for each copy of the new directory, i.e., each member of the group will need to do it once they have a clone of the repository) with the following command:
-
./autogen.sh --with-lang1=/path/to/ling073-xyz --with-lang2=/path/to/apertium-abc
- You'll need to substitute
/path/to/ling073-xyz
and/path/to/apertium-abc
with the paths to the source-language transducer and the target-language transducers, respectively. If you have all the directories next to each other (recommended), these paths will be../ling073-xyz
and../apertium-abc
.
-
- Compile with
make
as always. Make sure each repository has been (initialised and) compiled recently first.- If you get an error about "
Empty set of final states.
", this just means your dictionary is empty and you need to add words to it.
- If you get an error about "
Pushing to github
If this is a language pair you would like to push to github, do the following ideally before modifying any files or compiling the module:
- Create an empty (no files) repository named
ling073-xyz
on github. - Make sure the repository really was created correctly by running
git log
. You should see a single commit named "initial commit". - Set the github repository you created as the remote origin:
-
git remote add origin git@github.swarthmore.edu:groupname/ling073-xyz.git
(replacing "groupname" and "xyz" as appropriate)
-
- Push the bootstrapped module to origin:
-
git push --set-upstream origin master
-
- After this you should be able to see the same files from the github web interface and in the directory. You should also be able to commit, push, pull, etc. all normally.