po plugin: added TODO about charset/encoding in new translations

Signed-off-by: intrigeri <intrigeri@boum.org>

diff --git a/doc/plugins/po.mdwn b/doc/plugins/po.mdwn
index 1412cfea2174a6491ea1c8bb89892129f9ea3794..9baa609642c7156408938520bf47b612d255ee3f 100644 (file)
--- a/doc/plugins/po.mdwn
+++ b/doc/plugins/po.mdwn
@@ -221,6 +221,10 @@ Security checks
 gettext/po4a rough corners
 --------------------------
 
+- new translations created in the web interface must get proper charset/encoding
+  gettext metadata, else the next automatic PO update removes any non-ascii
+  chars; possible solution: put such metadata into the Pot file, and let it
+  propagate
 - fix the duplicated PO header mysterious bug
 - fix the "duplicate message definition" error when updating a PO
   file; do PO files need normalizing? (may be a side effect of