Languages

If you are looking for the category, click here

Languages is a module of the SVN where monolingual language data lives. Monolingual language data in Apertium is slowly being moved to this new repository scheme. If you feel something is missing, please feel free to contact us.

It can be found here

Contents

Languages by coverage

Module	Language	Entries	Coverage
apertium-bak	Bashkir	46,501	~66%
apertium-chv	Chuvash	10,267	~85%
apertium-dan	Danish	-	-
apertium-gla	Scottish Gaelic	-	-
apertium-hbs	Serbo-Croatian	-	-
apertium-hye	Armenian	-	-
apertium-kaz	Kazakh	36,595	~94.5%
apertium-kir	Kyrgyz	14,424	~90.4%
apertium-kum	Kumyk	4,918	~90.2%
apertium-lvs	Latvian	-	-
apertium-mlt	Maltese	-	-
apertium-nog	Nogay	1,385	~81.4%
apertium-rus	Russian	-	-
apertium-sqi	Albanian	-	-
apertium-tat	Tatar	55,702	~91%
apertium-urd	Urdu	-	-

Languages by family

Languages still in incubator are in italics.

• Turkic:
  • Oguz: Turkish, Turkmen, Azeri
  • Kypchak: Kazakh, Kyrgyz, Tatar, Bashqort, Kumyk, Nogay, Qaraqalpaq
  • Other: Sakha, Tuvan, Uzbek, Chuvash
• Indo-European
  • Slavic: Russian, Serbo-Croatian, Macedonian, Czech, Bulgarian, Ukranian
  • Celtic: Scottish Gaelic
  • Germanic
    • West Germanic: Dutch
    • North Germanic: Danish, Icelandic, Norwegian (nno, nob), Swedish, Faroese
  • Indic: Urdu, Bengali, Hindi, Sanskrit
  • Iranian:
  • Baltic: Latvian
  • Other Indo-European: Albanian, Armenian, Greek
• Semitic: Maltese
• Uralic:

Requiring a monolingual package as a dependency of a pair

Say you want apertium-fie-bar to depend on some monolingual data from the apertium-bar package, e.g. apertium-bar/bar.lrx and maybe other such files.

Assuming apertium-bar is set up correctly, you can put the following lines into the configure.ac of apertium-fie-bar:

AC_ARG_VAR(BARSRC, "Source directory for apertium-bar")
AS_IF([test -z "$BARSRC"],
      [
          PKG_CHECK_MODULES([APERTIUM_BAR], [apertium-bar])
          BARSRC=`pkg-config --variable=srcdir apertium-bar`
      ],
      [echo "Using apertium-bar from $BARSRC"])

and in the Makefile.am, you can write rules like this:

bar-fie.lrx.bin: $BARSRC/bar.lrx
	lrx-comp $< $@

Now if you've typed "make install" apertium-bar before running autogen.sh in apertium-fie-bar, apertium-fie-bar will use the bar.lrx which is installed by apertium-bar in its compilation.

If you make a lot of changes to apertium-bar and want to avoid having to "make install" for each and every change, you can do this in apertium-fie-bar:

./autogen.sh BARSRC=/path/to/apertium-bar

(./configure BARSRC=/path/to/apertium-bar should also work). Now each time you make, the "BARSRC" variable will point to /path/to/apertium-bar instead of the "make install"-ed file. You can set it back to default by just running plain ./configure again.

Making a monolingual package dependable for pairs

In apertium-bar, there should be a file apertium-bar.pc.in. This has to have the following lines:

dir=@libdir@/apertium/apertium-bar
srcdir=@datarootdir@/apertium/apertium-bar

These should correspond to where the binaries and source files respectively are installed by Makefile.am (typically named apertium_bardir and apertium_bar_srcdir). The configure.ac should have a line saying something like AC_OUTPUT([Makefile apertium-bar.pc]). See https://svn.code.sf.net/p/apertium/svn/languages/apertium-nob for a working example.

See also

• Incubator
• Nursery
• Staging