mmutf8fix

Version 8.3.1 [v8-devel] 2014-04-24

• external message modification interface now support modifying message PRI
• “jsonmesg” property will include uuid only if one was previously generated
  This is primarily a performance optimization. Whenever the message uuid is gotten, it is generated when not already present. As we used the regular setter, this means that always the uuid was generated, which is quite time-consuming. This has now been changed so that it only is generated if it already exists. That also matches more closly the semantics, as “jsonmesg” should not make modifications to the message.
  Note that the same applies to “fulljson” passing mode for external plugins.
• added plugin to rewrite message facility and/or severity
  Name: fac-sever-rewrite.py
• permits to build against json-c 0.12
  Unfortunately, json-c had an ABI breakage, so this is necessary. Note that versions prior to 0.12 had security issues (CVE-2013-6370, CVE-2013-6371) and so it is desirable to link against the new version.
  Thanks to Thomas D. for the patch.
  Note that at least some distros have fixed the security issue in older versions of json-c, so this seems to apply mostly when building from sources.
• bugfix: using UUID property could cause segfault
• bugfix/mmexternal: memory leak
• bugfix: memory leak when using “jsonmesg” property
• bugfix: mmutf8fix did not detect two invalid sequences
  Thanks to Axel Rau for the patch.
• bugfix: build problems with lexer.l on some platforms
  For some reason, the strdup() prototype and others are missing. I admit that I don’t know why, as this happens only in 8.3.0+ and there is no indication of changes to the affected files. In any case, we need to fix this, and the current solution works at least as an interim one.