poe: .po file editor

eaceed6 po.c(save_file): Save flags before msgid/msgstr for obsolete msgids instead of after (gettext behavior)

a month ago

eaceed6 po.c(save_file): Save flags before msgid/msgstr for obsolete msgids instead of after (gettext behavior)

a month ago

poe - .po file editor
=====================

Q: Why?
A: - There should be no need for GNOME to edit .po files.
   - Some folks prefer terminal to GUI.
   - No, plugin for vi(m) isn't enough.

Q: Why C?
A: Because <Go/Rust/whatever soydev language of the moment> sucks.

Q: Why is poe saying there are <N+1> messages in my file when 
   other editors say there are <N> messages?
A: Because poe takes into account (and allows editing of) the first,
   special msgid.

Q: This doesn't do X!
A: I might consider adding a feature if I have time, but already poe has all the
   major ones I planned. It is meant to be a simple .po editing program.

Q: Is this suckless?
A: Definitely not. Any TUI is not suckless. gettext is not suckless,
   and thus .po files are also not suckless. Despite that, some
   suggestions for a suckless approach to editing .po files are:
   vi, ed. Still, termbox, used by poe, is less bloated than ncurses.


License
-------

poe - .po file editor
Copyright (C) 2021, 2022  Страхиња Радић

This program is free software: you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation, either version 3 of the License, or (at your option) any later
version.

---

This program includes code from the termbox2 TUI library,

	https://github.com/termbox/termbox2

The file LICENSE.termbox applies to the portion of this program which is from
the termbox2 library. Currently, this includes only the file termbox.h.

~strahinja/poe