poe

Уређивач .po фајлова
Дневник | Датотеке | Референце | ПРОЧИТАЈМЕ | ЛИЦЕНЦА

чување b87114bd6e5f1874da1d7209e582b7022f4e81d4
родитељ 2d4c598721850cd3e21294556d6cc5945254ec80
Аутор: Страхиња Радић <contact@strahinja.org>
Датум:   Mon, 12 Jul 2021 20:43:00 +0200

Updated README

Signed-off-by: Страхиња Радић <contact@strahinja.org>

Diffstat:
MREADME | 14+++++++++++---
измењених датотека: 1, додавања: 11(+), брисања: 3(-)

diff --git a/README b/README @@ -6,9 +6,6 @@ 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: This doesn't do X! -A: See TODO for a list of implemented and planned features. - Q: Why C? A: Because <Go/Rust/whatever soydev language of the moment> sucks. @@ -16,6 +13,17 @@ Q: Why is poe saying there are <N+1> messages in my file when other editors say there are <N> messages? A: Because poe counts (and allows editing of) the first, special msgid. +Q: This doesn't do X! +A: See TODO for a list of implemented and planned features. I might consider + adding a feature if I have time, but already poe has all the major features 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: vi, ed. termbox is less bloated than + ncurses, though. + License -------