Module: check_mk Branch: master Commit: 7e6d75afd0c557199521ae3a68c6df27792a1e4a URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=7e6d75afd0c557… Author: Mathias Kettner &lt;mk(a)mathias-kettner.de&gt; Date: Mon Oct 27 16:01:29 2014 +0100 Updated formatting of Werk #1425 --- .werks/1425 | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.werks/1425 b/.werks/1425 index 0a91837..9b91d34 100644 --- a/.werks/1425 +++ b/.werks/1425 @@ -7,13 +7,14 @@ Date: 1414421080 Class: feature If you write your own check plugins you might know that a section -header can contain additional options separated by a colon.<br> -For example <tt><<<lnx_distro:sep(124):persist(141442125)>>></tt><br><br> +header can contain additional options separated by a colon. +For example <tt><<<lnx_distro:sep(124):persist(141442125)>>></tt> An additional option <tt>encoding</tt> has been introduced. Generally all check plugins should output valid utf-8 encoded text. In some instances this is not possible, because the plugin itself has its own hardcoded encoding. With the encoding option you can specify -the encoding for this entire section.<br> +the encoding for this entire section. + Check_MK will decode the given section output and recode it into utf-8 for further processing.