fst-parse(1)

✨ fst-parse ✨

okay bestie, so this is the manual page for fst-parse(1) — yeah, section 1, we're in user commands territory 💅 and she is the girl who runs a whole pipeline of transducers over your input. let's get into it 🦋

🌸 SYNOPSIS 🌸

fst-parse file1 [ file [ file ] ]

like, give her at least one file, and you can keep piling more on there. she's flexible like that 🫶

🎀 OPTIONS 🎀

• -t file — adds the transducer stored in file at the end of the pipeline. and yes, you can use this one MULTIPLE times, she's not gonna stop you 💅
• -h — prints the usage information. the classic "help me bestie" move 🙈
• -q — quiet mode 🤫
• -d — debugging mode 🔍

💖 DESCRIPTION 💖

so here's the tea 🍵 — you must use fst-parse instead of fst-infl if you have several transducers that need to be composed online in order to produce an analysis. that's the whole reason she exists, the main character of this situation 👑

otherwise? fst-parse is literally identical to fst-infl. same girl, different name tag ✨

and fr fr, the -t option can be used multiply. stack those transducers, bestie 🌈

💀 BUGS 💀

No bugs are known so far. 😌✨ (iconic behaviour honestly, we stan a flawless queen)

🦋 SEE ALSO 🦋

• fst-infl
• fst-compiler

go read those too, iykyk 💜

👑 AUTHOR 👑

Helmut Schmid, Institute for Computational Linguistics, University of Stuttgart, Email: schmid@ims.uni-stuttgart.de. This software is available under the GNU Public License. respect the queen's lineage 🎀

and that's the whole page, babe — this version is from October 2003, and the source/version stamp on it is fst-parse(1) from the fst-parse manual. go compose something gorgeous 💖🌸✨