HFST-STRINGS2FST(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-strings2fst ✨

okay bestie, so this is the manual page for hfst-strings2fst πŸ’– it's a User Command, it lives in the HFST family, and it's about to be your new fave.


🌸 NAME 🌸

hfst-strings2fst β€” =Compile string pairs and pair-strings into transducer(s)

(yes the = is literally in there, no I did not add it, we keep it πŸ’…)


πŸŽ€ SYNOPSIS πŸŽ€

hfst-strings2fst [OPTIONS...] [INFILE]

πŸ¦‹ DESCRIPTION πŸ¦‹

Compile string pairs and pair-strings into transducer(s). that's the whole vibe. you feed it strings, it hands you back a transducer (or several), no cap.

🌈 Common options:

  • -h, --help β€” print the help message, aka the "wait what does this do" button
  • -V, --version β€” print version info, so you know exactly which era of this software you're living in
  • -v, --verbose β€” print verbosely while processing, she's chatty and that's iconic
  • -q, --quiet β€” only print fatal erros and requested output (yes, "erros", that's the manpage's own spelling, we're leaving it πŸ’€)
  • -s, --silent β€” alias of --quiet, same energy, different letter

🌟 Input/Output options:

  • -i, --input=INFILE β€” read input strings from INFILE
  • -o, --output=OUTFILE β€” write output transducer to OUTFILE

πŸ’œ String and format options:

  • -f, --format=FMT β€” write result in FMT format
  • -j, --disjunct-strings β€” disjunct all strings instead of transforming each string into a separate transducer
  • --norm β€” divide each weight by sum of all weights (only does anything with option -j)
  • --log β€” take negative natural logarithm of each weight
  • --log10 β€” take negative 10-based logarithm of each weight
  • -p, --pairstrings β€” input is in pairstring format
  • -S, --has-spaces β€” input has spaces between symbols/symbol pairs
  • -e, --epsilon=EPS β€” interpret string EPS as epsilon
  • -m, --multichar-symbols=FILE β€” strings that must be tokenized as one symbol

🫢 housekeeping, bestie, listen up: If OUTFILE or INFILE is missing or -, standard streams will be used. the classic. FMT can be { foma, openfst-tropical, openfst-log, sfst, optimized-lookup-weighted, optimized-lookup-unweighted }. six options, all gorgeous. If EPS is not defined, the default representation of @0@ is used. Option --norm precedes option --log. order matters, don't be chaotic. The FILE of option -m lists all multichar-symbols, each symbol on its own line. Backslash '\' may be used to escape ':', tab and itself. For any other symbol x, '\x' means x literally, i.e. is the same as 'x'. The weight of a string can be given after the string separated by a tabulator. ⚠️ The weight cannot be zero. like, at all. zero is not the move here.

πŸ”₯ EXAMPLES πŸ”₯

honestly these are so satisfying to look at:

echo "cat:dog" | hfst-strings2fst

create cat:dog fst πŸ’…

echo "c:da:ot:g" | hfst-strings2fst -p

same as pairstring ✨

echo "c:d a:o t:g" | hfst-strings2fst -p -S

same as pairstring with spaces 🌸

echo "c a t:d o g" | hfst-strings2fst -S

same with spaces πŸ¦‹


πŸ™ˆ REPORTING BUGS πŸ™ˆ

found something cursed? Report bugs to <hfst-bugs@helsinki.fi> or directly to our bug tracker at: <https://github.com/hfst/hfst/issues> β€” they genuinely wanna hear it, fr fr.


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. (read it again. no warranty. she said what she said.)


and that's the whole page, bestie πŸ’– this was the HFST hfst-strings2fst(1) manual, dated August 2018, from the HFST project β€” go forth and compile those string pairs, you absolute main character πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from