HFST-COMPOSE-INTERSECT(1)
π 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 isfalse). 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>
- hfst-compose-intersect home page: <https://github.com/hfst/hfst/wiki/HfstComposeIntersect>
- General help using HFST software: <https://github.com/hfst/hfst/wiki>
π COPYRIGHT π
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
- debian bookworm: hfst 3.16.0-5 Β· GPL-3.0-or-later
- debian trixie: hfst 3.16.2-1+b1 Β· GPL-3.0-or-later
- nixos 26.05: hfst 3.16.2
- opensuse-leap 16.0: hfst 3.16.0-bp160.1.11 Β· Apache-2.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND GPL-3.0-only
- ubuntu jammy: hfst 3.15.4-2 Β· GPL-3.0-or-later
- ubuntu noble: hfst 3.16.0-5build4 Β· GPL-3.0-or-later
- ubuntu questing: hfst 3.16.2-1
- ubuntu resolute: hfst 3.16.2-1build2 Β· GPL-3.0-or-later
- ubuntu stonking: hfst 3.17.1-6 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms