APERTIUM(1)

Okay bestie, this is the manual page for apertium (APERTIUM(1), General Commands Manual) and it is about to be SO good 💖✨

✨ NAME ✨

apertium — machine translation application platform 🌸

🎀 SYNOPSIS 🎀

apertium [-au] [-d datadir] [-f format] language-pair [infile [outfile]]

💅 DESCRIPTION 💅

Okay so apertium is the app most people will actually use, because it makes the apertium/lt-toolbox tools way easier to use for machine translation. Main character energy 👑

It's giving one friendly front door 🚪. lt-toolbox handles all the lexical processing modules and tools, and apertium handles the rest of the engine, and this tool wraps both so the end user only has to deal with one thing 🫶.

The modules in the apertium machine translation architecture run in this order, and I'm obsessed with how they flow 🔥:

• de-formatter — Separates the text to be translated from the format information.
• morphological-analyser — Tokenizes the text in surface forms.
• part-of-speech tagger — Chooses one surface forms among homographs.
• lexical transfer module — Reads each source-language lexical form and delivers a corresponding target-language lexical form.
• structural transfer module — Detects fixed-length patterns of lexical forms (chunks or phrases) needing special processing due to grammatical divergences between the two languages and performs the corresponding transformations.
• morphological generator — Delivers a target-language surface form for each target-language lexical form, by suitably inflecting it.
• post-generator — Performs orthographical operations such as contractions and apostrophations.
• re-formatter — Restores the format information encapsulated by the de-formatter into the translated text and removes the encapsulation sequences used to protect certain characters in the source text.

🦋 OPTIONS 🦋

• -d datadir — Where the linguistic data lives 📚. If you don't set it, it just uses the expected installation path, so no stress.
• language-pair — The language pair, written as LANG1–LANG2 (for instance “es-ca” or “ca-es”) 🌈.
• -f format — Picks the format of the input and output files 🍓. Here are your options:
  • txt (default value) — Input and output files are plain text. Basic, but iconic 💜.
  • html — Input and output files are in “html” format. This is the one the vast majority of web browsers accept 🌐.
  • html-noent — Input and output files are in “html” format, but native encoding characters stay as they are instead of getting turned into HTML text entities ✨.
  • rtf — Input and output files are in “rtf” format. The accepted flavor is the one generated by Microsoft WordPad and Microsoft Office up to and including Office 97 🫠.
• -u — Turns off marking of unknown words with the ‘*’ character. Bye bye stars ⭐.
• -H — Turns on header-detection. This only works in some language pairs 🧚.

⚠️ Bestie, watch out: -H will lead to stray ‘❡’ characters in pairs that don't support it. Not a vibe.

• -a — Turns on marking of disambiguated words with the ‘=’ character 🎯.

📁 FILES 📁

These are the two files that can be used with this command 🗂️:

• -m memory.tmx — Uses a translation memory to recycle translations ♻️.
• -o direction — The translation direction used with the translation memory. By default, “direction” is used instead 🧠.
• -l — Lists the available translation directions and exits. The direction is typically LANG1–LANG2, but check modes.xml in language data if you want the deets 📜.
• infile — Input file. Defaults to stdin 📥.
• outfile — Output file. Defaults to stdout 📤.

🌸 SEE ALSO 🌸

apertium-tagger(1), lt-comp(1), lt-expand(1), lt-proc(1) 🔗

💖 COPYRIGHT 💖

Copyright © 2005, 2006 Universitat d'Alacant / Universidad de Alicante. This is free software 🫶. You can redistribute copies of it under the terms of the GNU General Public License: https://www.gnu.org/licenses/gpl.html.

🙈 BUGS 🙈

Many... lurking in the dark and waiting for you! 👻

Bye bestie, you're officially an apertium expert now 🦋💅 Apertium, March 8, 2006, APERTIUM(1) 🌈✨