HFST-COMPOSE(1)

📦
version 3.17.1 · 2 versions
  • 3.17.1 · debian bookworm, debian trixie, nixos 26.05, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 3.17.3 · nixpkgs unstable
, in debian bookworm, debian trixie, nixos 26.05, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

👑 HFST-COMPOSE — bestie, we're composing transducers ✨

okay so real talk: this page lives in the User Commands section of the manual, and it's all about hfst-compose. no cap, it's a whole vibe.

🌈 SYNOPSIS

hfst-compose [OPTIONS...] [INFILE1 [INFILE2]]

💖 DESCRIPTION

Compose two transducers. that's it. that's the whole job. and honestly? it eats. 🫶

🎀 Common options:

  • -h, --help — prints the help message, aka the "bestie explain" button 🙈
  • -V, --version — prints version info, so you know exactly what you're working with 💅
  • -v, --verbose — print verbosely while processing, like it's telling you its whole day 🗣️
  • -q, --quiet — only prints fatal errors and the output you actually asked for 🤫
  • -s, --silent — literally just an alias of --quiet. same energy, different letter ✨

🦋 Input/Output options:

  • -1, --input1=INFILE1 — read the first input transducer from INFILE1 📥
  • -2, --input2=INFILE2 — read the second input transducer from INFILE2 📥
  • -C, --do-not-convert — do not let transducers be converted into the same type. nope, not today 🚫
  • -o, --output=OUTFILE — write the results to OUTFILE 📤

🔥 Composition options:

  • -x, --xerox-composition=VALUE — controls whether flag diacritics are treated as ordinary symbols in composition (default is false). it's giving "do the rules even apply to me" energy 💀
  • -X, --xfst=VARIABLE — toggles the xfst compatibility option VARIABLE. flip the switch, bestie 🎚️

🌸 Harmonization:

  • -H, --do-not-harmonize — do not harmonize symbols. leave them exactly as they are, main character behavior 👑
  • -F, --harmonize-flags — harmonize flag diacritics. yes we're matching them up, it's a group chat now 🫂

okay so the important stuff about streams, no skipping: if OUTFILE, or either INFILE1 or INFILE2, is missing or -, then standard streams get used instead. but listen — INFILE1, INFILE2, or both must be specified. that part is not optional, periodt. 🙅

the format of the result depends on the format of INFILE1 and INFILE2, and bestie, both of them should have the same format. matching outfits only 💖

the operation is applied pairwise for INFILE1 and INFILE2, which must have the same number of transducers. and if INFILE2 has only one transducer? iconic — the operation gets applied to each transducer in INFILE1 while keeping that second transducer constant. one of them just gets to chill 😌

xfst variables are {flag-is-epsilon (default OFF)}. and VALUE can be one of these: [true|false], [yes|no] or [ON|OFF] — with false being the default. lowkey a lot of ways to say no but we respect the range 🌈

⭐ EXAMPLES

hfst-compose -o cat2dog.hfst cat2mouse.hfst mouse2dog.hfst

composes two automata 🐱➡️🐭➡️🐶 and yes, the glow-up pipeline is real.

😭 REPORTING BUGS

found a bug? don't suffer in silence, bestie. report bugs to <hfst-bugs@helsinki.fi> or directly to the bug tracker at: <https://github.com/hfst/hfst/issues> 🐛

Copyright © 2017 University of Helsinki, License GPLv3: GNU GPL version 3 <http://gnu.org/licenses/gpl.html>

this is free software: you are free to change and redistribute it. and there is NO WARRANTY, to the extent permitted by law. (fr fr, no warranty. read it and weep 🫠)

and that's the whole page, bestie!! this was the HFST manual page for hfst-compose, dated August 2018, written by the HFST girlies 💅✨ go compose something iconic, ily, bye!! 🎀🦋💖

📦 where this page comes from