summaryrefslogtreecommitdiffstats
path: root/regress/char/unicode
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2017-02-11 17:53:33 +0000
committerIngo Schwarze <schwarze@openbsd.org>2017-02-11 17:53:33 +0000
commit1c6b1bd072ddd94a39998c409fa8de8d1a614832 (patch)
tree3003882124dc9ea091f31e37cefe7de7b7622356 /regress/char/unicode
parentd0a4becb2dd9162163c151e4b73430fb2e29d7d2 (diff)
downloadmandoc-1c6b1bd072ddd94a39998c409fa8de8d1a614832.tar.gz
Disable three UTF-8 tests that expose bugs in wcwidth(3) in the
native C libraries of illumos, Oracle Solaris 11, and SunOS 5.10. While it is useful to catch wcwidth(3) regressions on OpenBSD, the purpose of the *portable* mandoc regression suite is not to check the C library of the host system; that would just hide genuine mandoc portability issues in the noise. The remaining UTF-8 tests are still sufficient to establish that mandoc does the right thing. Issues reported by Sevan Janiyan <venture37 at geeklan dot co dot uk> after testing on OmniOS.
Diffstat (limited to 'regress/char/unicode')
-rw-r--r--regress/char/unicode/Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/regress/char/unicode/Makefile b/regress/char/unicode/Makefile
index b6940f6e..85397299 100644
--- a/regress/char/unicode/Makefile
+++ b/regress/char/unicode/Makefile
@@ -6,7 +6,7 @@ SKIP_ASCII = man mdoc
# input and nogroff exhibit implementation dependent differences
# among wcwidth(3) on different systems
#UTF8_TARGETS = ${REGRESS_TARGETS}
-UTF8_TARGETS = ascii invalid latin1 latin1diff man mdoc named namediff
+UTF8_TARGETS = ascii invalid man mdoc namediff
HTML_TARGETS = ascii invalid latin1 latin1diff named namediff nogroff
LINT_TARGETS = input invalid