Module: check_mk
Branch: master
Commit: 57cdd6f0f177530abcc265fb7503cbd631635abd
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=57cdd6f0f17753…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Sat Aug 13 15:03:38 2011 +0200
Updated bug entries
---
.bugs/14 | 28 +++++++++++++++++++++-------
1 files changed, 21 insertions(+), 7 deletions(-)
diff --git a/.bugs/14 b/.bugs/14
index e4513b2..f47baea 100644
--- a/.bugs/14
+++ b/.bugs/14
@@ -1,14 +1,28 @@
-Title: UTF-8 Kodierung von Eurosymbol geht nicht
+Title: Livestatus: implement full UTF-8 support
Component: livestatus
-Benefit: 1
+Benefit: 2
State: open
Cost: 3
Date: 2010-12-21 12:12:58
Class: bug
-Livestatus: bestimmte UTF-8 Zeichen werden nicht korrekt kodiert, z.B. "€".
-Um das umzustellen, muss man wahrscheinlich einfach UTF-8 generell
-annehmen.
+Currently Livestatus correctly handles 2-Byte UTF-8
+sequences, assumes all other non-Ascii Characters to
+be Latin-1 encoded. While this works well for Western
+languages, other non-Latin1 languages not not supported.
-Die aktuelle Implementierung erkennt halbautomatisch eine Mischung
-aus Latin1 und UTF-8. Kann man bei Nagios einfach UTF-8 verlangen?
+We can do it the following way: We introduce a module
+option "data_encoding", which is either "mixed", "latin1"
or "utf-8".
+The default is "utf-8".
+
+the "mixed" mode is the current implementation. The "utf-8"
+mode assumes all Nagios-strings to be UTF-8 encoded and
+outputs the according escape sequences for JSON/Python.
+
+In mode "latin1" all characters are interpreted as one-byte
+Latin-1 encoded characters and the according escape
+codes for UTF-8 are produced.
+
+The programmer has to make sure, that this encoding matches
+the encoding used in COMMAND queries. Strings in that
+query are never transcoded but put 1:1 into Nagios.