INTLTOOL-PREPARE(8)

πŸ’– INTLTOOL-PREPARE πŸ’–

the intltool-prepare era, bestie β€” manual page 8, straight outta the System Manager's Manual ✨


✨ NAME ✨

intltool-prepare β€” get your software all set up to use intltool πŸŽ€


🌸 SYNOPSIS 🌸

intltool-prepare [option] [KEYWORD]...

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this 😭 some software packages ship with certain kinds of translatable files β€” think .desktop and .soundlist vibes. Before those packages can use intltool, translators literally have to dig through every single one of them by hand and paste the localization into each file. And bestie, that process is error prone fr fr. Translators might typo something, or drop their localization in the wrong encoding. On top of that, they might not even know that other files (besides .po files) are translatable in the first place. πŸ™ˆ

intltool dodges all of those problems by pulling the strings inside those translatable files out into a po template (.pot) file. So all a translator has to care about is translating po files. Periodt. πŸ’… Then later, intltool-merge(8) merges the localized strings back into those files. Iconic behaviour honestly. πŸ‘‘

But before your software becomes intltool-aware, a few issues have to get sorted out first, and intltool-prepare tries to take care of all of them. Here's what it does:

  • Extract all localized strings in .desktop style files (including ".desktop", ".soundlist", ".keys" and ".directory") into corresponding po files. πŸ“
  • Convert the translatable files into templates that don't contain any localization. ✨
  • Add the list of template files above into POTFILES.in. πŸ“
  • Add the list of old translatable files into .cvsignore (since they will be generated by intltool later). πŸ‘€
  • Add the rules for generating these files into Makefile.am. πŸ”₯
NOTE: You must change working directory to the top level source directory before running intltool-prepare. No cap. 🚨

πŸ’… OPTIONS πŸ’…

KEYWORD is a list of additional keywords beside "Name", "Comment" and "description". intltool-prepare will recognize any line starting with those KEYWORD and extract localized strings after equal sign ("="). 🧚

  • -x, --verbose β€” be verbose and give the user some additional feedback, so you actually know what's going on. πŸ’¬
  • -v, --version β€” show version information. 🌈
  • -h, --help β€” show usage and basic help information. 🫢

😭 REPORTING BUGS 😭

Report bugs to http://bugs.launchpad.net/intltool β€” tell them everything, bestie, they wanna know. πŸ’€


πŸ‘‘ AUTHOR πŸ‘‘

  • Darin Adler <darin@bentspoon.com>
  • Kenneth Christiansen <kenneth@gnu.org>
  • Maciej Stachowiak <mjs@eazel.com>

🌈 SEE ALSO 🌈

intltoolize(8), intltool-update(8), intltool-extract(8), intltool-merge(8)


and that's the whole page, mwah πŸ’– this was intltool from 2003-08-02, lowkey a vintage queen, no notes βœ¨πŸŽ€πŸ¦‹