HFST-COMPOSE-INTERSECT(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-INTERSECT β€” the manual page, but make it cute

okay bestie so you found the hfst-compose-intersect page, and I'm about to explain it to you like we're texting at 1am πŸ’– it's a User Commands page, section 1, and it's giving "glue two transducers together and make it look effortless."


✨ NAME ✨

hfst-compose-intersect β€” compose a lexicon with one or more rule transducers. that's it, that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

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

πŸ’… DESCRIPTION πŸ’…

Compose a lexicon with one or more rule transducers. literally what it says on the tin, no cap.

πŸŽ€ Common options: πŸŽ€

  • -h, --help β€” print the help message. your lil emergency handbook 🫢
  • -V, --version β€” print version info. receipts, but make it software ✨
  • -v, --verbose β€” print verbosely while processing. she's chatty and we love that
  • -q, --quiet β€” only print fatal errors and requested output. main character silence πŸ’€
  • -s, --silent β€” alias of --quiet. same energy, different name, iconic

πŸ¦‹ 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 allow transducers to be converted into the same type. she said "no conversions, we're keeping the original format" πŸ’…
  • -o, --output=OUTFILE β€” write results to OUTFILE

🌈 Composition options: 🌈

  • -I, --invert β€” compose the intersection of the rules with the lexicon instead of composing the lexicon with the intersection of the rules. yes, the order flips, and yes, it matters πŸ‘€
  • -f, --fast β€” faster compose intersect using more memory. speed demon mode, but she eats RAM for breakfast πŸ”₯
  • -e, --encode-weights β€” encode weights when minimizing (default is false). default is lowkey off, so opt in if you want it
  • -a, --harmonize β€” harmonize symbols. besties matching outfits but for symbols ✨

okay so listen: if OUTFILE, or either INFILE1 or INFILE2, is missing or -, standard streams will be used. πŸ‘‘

INFILE1, INFILE2, or both, must be specified. the format of INFILE1 and INFILE2 must be the same; the result will have the same format as these. fr fr, they gotta match.

INFILE1 (the lexicon) must contain exactly one transducer. INFILE2 (rule file) may contain several transducers. one lexicon, many rules β€” she's a social butterfly like that πŸ¦‹


🌟 EXAMPLES 🌟

hfst-compose-intersect -o analyzer.hfst lexicon.hfst rules.hfst

compose rules with lexicon. periodt. πŸŽ€


πŸ™ˆ REPORTING BUGS πŸ™ˆ

found a bug? not her fault, tell the devs bestie:

Report bugs to <hfst-bugs@helsinki.fi> or directly to our 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. There is NO WARRANTY, to the extent permitted by law. NO WARRANTY. say it with me. 🫢


and that's the whole page, bestie πŸ’œ this one ships from HFST, dated August 2018 β€” go forth and compose, you absolute legend πŸ‘‘βœ¨

πŸ“¦ where this page comes from