PO-FETCH(1)

πŸ’– PO-FETCH(1) πŸ’–

okay bestie, pull up a chair, we're reading the po-fetch manual page together and honestly? it's giving "small tool, big slay". this is po-fetch from the User Commands section of the manual, and by the end of this you're gonna know it like the back of your hand. 🫢

✨ NAME ✨

po-fetch β€” fetches a set of PO files from a translation project's site. that's it, that's the whole vibe. 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

po-fetch [OPTION...] TP DOMAIN

po-fetch [OPTION...] Weblate BASE-URL PROJECT COMPONENT

po-fetch [OPTION...] git BASE-URL BRANCH SUBDIR

three whole ways to call her, and she serves in all of them. πŸ’…


πŸ‘‘ DESCRIPTION πŸ‘‘

so basically: po-fetch goes out onto the internet, grabs a whole set of PO files (those are the ones your translators made, mwah 😘), pulls them down from a translation project's site, and then β€” and this is the part that lowkey eats β€” it updates the LINGUAS file to match. no manual bookkeeping, no tears, periodt.

the first argument is the vibe check. it tells her what kind of translation project we're dealing with:

  • TP β€” this one means the Translation Project (that's translationproject.org, iconic).
  • Weblate β€” this one means a Weblate instance. you know the one. πŸ’œ
  • git β€” this one means a web front-end to a git repository. so like, a gitweb instance, a cgit instance, or a GitLab, GitHub, or Forgejo instance. basically any of the git besties. 🌈

πŸŽ€ OPTIONS πŸŽ€

  • --git β€” makes the changes in the git index, so you're all set up to do a git commit. prepping the ~moment~, fr fr.

πŸ“ Output files location

the PO files and the LINGUAS file are stored in the current directory. yes, this directory. right here. look around. 🫣

πŸ“’ Informative output

  • --help β€” shows this help text. a little "here's how to use me" moment. πŸŽ€
  • --version β€” shows version and authorship information. the classic "who made me and when" flex. ✨

🧚 AUTHOR 🧚

Written by Bruno Haible. an absolute legend, no cap. πŸ‘‘


πŸ’€ REPORTING BUGS πŸ’€

found a bug? bestie, do NOT suffer in silence. report it in the bug tracker at <https://savannah.gnu.org/projects/gettext> or by email to <bug-gettext@gnu.org>. the devs want to know, fr. πŸ›


Copyright Β© 2002-2025 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>

this is free software: you are free to change and redistribute it. and hear me on this one β€” there is NO WARRANTY, to the extent permitted by law. like, none. zero. nada. 😭


πŸ‘€ SEE ALSO πŸ‘€

the full documentation for po-fetch is maintained as a Texinfo manual. if the info and po-fetch programs are properly installed at your site, the command

info po-fetch

should give you access to the complete manual. go read her, she's thorough. πŸ“–


πŸ’… that's the whole page, bestie. go fetch some PO files. you got this.

mwah β€” this was po-fetch, from GNU gettext-tools 1.0, dated January 2026. catch you in the next manpage, love u, bye!! πŸ’–βœ¨πŸ¦‹πŸŽ€πŸŒΈ

πŸ“¦ where this page comes from