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'stranslationproject.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 π
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
- alpine 3.24: gettext-doc 1.0-r0 Β· GPL-3.0-or-later AND LGPL-2.1-or-later AND MIT
- arch rolling: gettext 1.0-2 Β· GFDL-1.2-only AND GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.0-only
- nixos 26.05: gettext 1.0
- nixpkgs unstable: gettext 1.0
- ubuntu stonking: gettext 1.0-3 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms