cocopon/po-mini.vim — explained in plain English
Analysis updated 2026-08-04 · repo last pushed 2013-12-20
Automatically update the revision date and translator info in PO files each time you save a translation in Vim.
Maintain header metadata for gettext translation files without manually editing timestamps or names.
Streamline repetitive localization workflow when contributing translations to open source projects using Vim.
| cocopon/po-mini.vim | jianyuh/vimbackup | mna/nofrils | |
|---|---|---|---|
| Stars | 1 | — | — |
| Language | VimL | VimL | VimL |
| Last pushed | 2013-12-20 | 2016-09-19 | 2016-03-15 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | easy | easy | easy |
| Complexity | 1/5 | 1/5 | 1/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Install like any standard Vim plugin, no external dependencies beyond Vim itself.
If you've ever helped translate software, you may have encountered PO files, plain text files used by a translation system called gettext. They contain the original text and its translated equivalent, plus a header with metadata like who translated it and when. Keeping that header information up to date by hand is tedious and easy to forget. po-mini.vim is a plugin for the Vim text editor that handles this automatically for you. When you edit a PO file in Vim with this plugin installed, it updates three specific header fields for you: the revision date, the last translator's name, and the language team. So instead of manually fixing the timestamp or typing in your name every time you save a translation, the plugin fills those in. It does one small thing and stays out of your way otherwise. This is designed for people who translate or localize software and already use Vim as their editor. For example, if you maintain the Spanish translation of an open source project and regularly open PO files to update strings, this saves you a few repetitive steps each session. It's a narrow tool, it doesn't offer fuzzy matching, syntax checking, or any of the heavier features you'd find in a dedicated translation editor. It just keeps the header metadata current. The README is sparse, so there's not much detail on configuration or how the plugin decides what values to put in the translator and language team fields. There may be more in the included documentation file, but the overview only covers the core behavior. For someone who lives in Vim and works with gettext files occasionally, it's a lightweight convenience. For anyone needing a full translation workflow, a dedicated tool would make more sense.
A Vim plugin that automatically updates PO translation file headers, revision date, last translator, and language team, every time you edit and save a file.
Mainly VimL. The stack also includes Vim, VimL.
Dormant — no commits in 2+ years (last push 2013-12-20).
No license information is provided in the README, so usage terms are unclear.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.