PO-File Editor vs Poedit: Do the Same Job Without Installing Anything
A task-by-task parity manual rather than a verdict. Sixteen Poedit actions mapped to their browser equivalent — nine at full parity, three partial, four absent — with the pattern that falls out of it: editing reached parity, catalog management did not, and everything missing involves the file's relationship to something else. Walks the same twenty-string fix through both tools, then covers the three things Poedit does that a browser editor cannot: a local translation memory spanning every project, updating a catalog against changed source, and compiling the MO on save. The fuzzy flag gets its own section because it decides what ships — msgfmt excludes flagged entries from the binary, so a corrected translation on a still-flagged entry never reaches your users — with what to insist on from any editor and three ways to clear flags by hand when yours hides them. Plus the three things the browser genuinely does better, the seven-step handoff pattern for using both, a situation-to-tool table, and why a PO file edited in either is the same file.