sysklogd/test/unicode.sh

#!/bin/sh
# Currently only same as local.sh but with unicode messages
# From https://github.com/troglobit/sysklogd/issues/49
# shellcheck disable=SC1090
if [ x"${srcdir}" = x ]; then
    srcdir=.
fi

. ${srcdir}/lib.sh
setup -8

MSG="öäüÖÄÜß€¢§"
MSG2="…‘’•"

logger ${MSG}
grep ${MSG} "${LOG}" || FAIL "Cannot find: ${MSG}"

logger "${ALTSOCK}" ${MSG2}
grep ${MSG2} "${LOG}" || FAIL "Cannot find: ${MSG2}"

OK
Fix #49: add support for -8 command line option to allow 8-bit data This patch allows the user to disable the 8-bit data check in the log message validator. If you have experienced problems with logging any unicode (utf-8) messages after v1.6, this option is for you. The correct way to handle this is to add proper parser support for the Unicode BOM, defined in RFC5424[1], as NetBSD syslogd does[2], search for IS_BOM(). [1]: https://datatracker.ietf.org/doc/html/rfc5424#appendix-A.8 [2]: http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/syslogd/syslogd.c?rev=1.138 Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 2022-03-08 01:21:42 +05:30			`#!/bin/sh`
			`# Currently only same as local.sh but with unicode messages`
			`# From https://github.com/troglobit/sysklogd/issues/49`
			`# shellcheck disable=SC1090`
			`if [ x"${srcdir}" = x ]; then`
			`srcdir=.`
			`fi`
test: use new logger() function in all tests Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 2022-05-21 19:13:12 +05:30
Fix #49: add support for -8 command line option to allow 8-bit data This patch allows the user to disable the 8-bit data check in the log message validator. If you have experienced problems with logging any unicode (utf-8) messages after v1.6, this option is for you. The correct way to handle this is to add proper parser support for the Unicode BOM, defined in RFC5424[1], as NetBSD syslogd does[2], search for IS_BOM(). [1]: https://datatracker.ietf.org/doc/html/rfc5424#appendix-A.8 [2]: http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/syslogd/syslogd.c?rev=1.138 Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 2022-03-08 01:21:42 +05:30			`. ${srcdir}/lib.sh`
			`setup -8`

			`MSG="öäüÖÄÜß€¢§"`
			`MSG2="…‘’•"`

test: use new logger() function in all tests Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 2022-05-21 19:13:12 +05:30			`logger ${MSG}`
Fix #49: add support for -8 command line option to allow 8-bit data This patch allows the user to disable the 8-bit data check in the log message validator. If you have experienced problems with logging any unicode (utf-8) messages after v1.6, this option is for you. The correct way to handle this is to add proper parser support for the Unicode BOM, defined in RFC5424[1], as NetBSD syslogd does[2], search for IS_BOM(). [1]: https://datatracker.ietf.org/doc/html/rfc5424#appendix-A.8 [2]: http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/syslogd/syslogd.c?rev=1.138 Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 2022-03-08 01:21:42 +05:30			`grep ${MSG} "${LOG}" \|\| FAIL "Cannot find: ${MSG}"`

test: use new logger() function in all tests Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 2022-05-21 19:13:12 +05:30			`logger "${ALTSOCK}" ${MSG2}`
Fix #49: add support for -8 command line option to allow 8-bit data This patch allows the user to disable the 8-bit data check in the log message validator. If you have experienced problems with logging any unicode (utf-8) messages after v1.6, this option is for you. The correct way to handle this is to add proper parser support for the Unicode BOM, defined in RFC5424[1], as NetBSD syslogd does[2], search for IS_BOM(). [1]: https://datatracker.ietf.org/doc/html/rfc5424#appendix-A.8 [2]: http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/syslogd/syslogd.c?rev=1.138 Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 2022-03-08 01:21:42 +05:30			`grep ${MSG2} "${LOG}" \|\| FAIL "Cannot find: ${MSG2}"`

			`OK`