HFST-CONJUNCT(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-CONJUNCT ✨

okay bestie, welcome to hfst-conjunct(1) from the HFST crew — it lives in the User Commands section of the manual and it is genuinely one of the most useful little tools in the whole toolkit, no cap 💖

🎀 NAME 🎀

hfst-conjunct — Conjunct (intersect, AND) two transducers

like... it's the "AND" girlie of transducer land. both sides gotta agree or nothing gets through. periodt.

🌸 SYNOPSIS 🌸

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

🦋 DESCRIPTION 🦋

Conjunct (intersect, AND) two transducers 💅

that's it, that's the whole vibe. take two transducers, keep only the parts where both of them say yes. intersection core. main character energy only.

💜 Common options: 💜

  • -h, --help — Print help message. your girl when you're lost 🥺
  • -V, --version — Print version info. receipts, basically.
  • -v, --verbose — Print verbosely while processing. she talks you through it 🗣️
  • -q, --quiet — Only print fatal erros and requested output. yes it says "erros" in the original, we keep the sacred text exactly as it is 💀
  • -s, --silent — Alias of --quiet. same energy, different name ✨

🌈 Input/Output options: 🌈

  • -1, --input1=INFILE1 — Read first input transducer from INFILE1
  • -2, --input2=INFILE2 — Read second input transducer from INFILE2
  • -C, --do-not-convert — Do not allow transducers to be converted into the same type. like, no glow-ups, no makeovers, they stay exactly as they are 🚫💅
  • -o, --output=OUTFILE — Write results to OUTFILE

🧚 Flag diacritics: 🧚

  • -F, --harmonize-flags — Harmonize flag diacritics
  • -H, --do-not-harmonize — Do not harmonize
⚠️ real talk: if OUTFILE, or either INFILE1 or INFILE2 is missing or -, standard streams will be used. and INFILE1, INFILE2, or both, must be specified. you cannot just run it into the void, bestie 😭

the format of the result depends on the format of INFILE1 and INFILE2; both should have the same format. matching fits, matching energy 🫶

and here's the important structural tea: the operation is applied pairwise for INFILE1 and INFILE2 that must have the same number of transducers. but if INFILE2 has only one transducer, the operation is applied for each transducer in INFILE1 keeping the second transducer constant. so one side can just be the loyal constant gf while the other side cycles through 🔥

👑 EXAMPLES 👑

hfst-conjunct -o dog.hfst cat_or_dog.hfst dog_or_mouse.hfst

look at her go. cat_or_dog AND dog_or_mouse → dog. iconic. ate and left no crumbs 🐶

💀 REPORTING BUGS 💀

found a bug? spill it, don't sit on it:

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. like genuinely none, bestie, do not come for us 🙈

okay that's the whole page, you're all caught up 💖 this was the HFST girlies, HFST, August 2018, signing off — HFST-CONJUNCT(1) out, mwah 🎀✨

📦 where this page comes from