poreencode(1)

πŸ’– poreencode πŸ’–

okay so bestie, meet poreencode β€” she's a lil Translate Toolkit icon whose whole job is re-encoding every file in a PO directory to whatever encoding you want. that's it. that's the gig. and she ate. πŸ’…


✨ NAME ✨

poreencode β€” re-encode all files of a PO directory to the specified encoding πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

poreencode encoding PO-directory

so like, encoding is the encoding you wanna convert to, bestie β€” think UTF-8 energy ✨ β€” and PO-directory is a directory full of existing PO files. that's the whole vibe check.


🌸 DESCRIPTION 🌸

you hand her a directory of existing PO files, and she converts them all to a given encoding. literally that simple. no notes. πŸ‘‘


🌈 OPERATION 🌈

okay so here's the tea on how she actually does it β˜•βœ¨

poreencode is out here making use of the Gettext tool msgconv(1) to do her thing. she traverses the PO directory, finds all the PO files, and then uses msgconv(1) to convert each PO file from whatever encoding it was in to the new encoding. no cap. 🫢


πŸ’€ BUGS πŸ’€

ngl, like most Gettext tools, they do a little bit more than what's documented πŸ™ˆ. msgconv(1) will decide which strings are in fact fuzzy and delete the fuzzy marking β€” not a lot, but bestie, you do need to diff. πŸ’…

this is probably related to #, fuzzy entries that aren't placed in the place Gettext expects them. so like. yeah. not me warning you twice. 😭

⚠️ fr fr: diff your files after running this. the fuzzy marking situation is real and it will lowkey catch you off guard.

that's the whole page bestie, go forth and re-encode πŸ’œ

this has been poreencode(1) from Translate Toolkit 1.10.0 β€” mwah, ily, go slay πŸŽ€βœ¨πŸ’–