summaryrefslogtreecommitdiffstats
path: root/regress/char/unicode/input.out_utf8
Commit message (Collapse)AuthorAgeFilesLines
* delete the two pairs of extra blank lines from expected man(7) terminalIngo Schwarze2021-06-281-4/+0
| | | | output that are no longer printed since man_term.c rev. 1.236
* test private use areas some more as they have proven fragileIngo Schwarze2021-06-021-0/+2
|
* Cleanup:Ingo Schwarze2021-06-021-15/+17
| | | | | | | | | | 1. Move invalid two-byte sequences after valid ones and make their descriptions easier to understand. 2. Replace the wrong and confusing expression "middle byte" with the correct term "start byte". 3. Add test lines for U+EFFFF and U+F0000. 4. Replace the unhelpful word "strange" with more descriptive terms. Arguably, nothing about this (or maybe everything?) is strange.
* The wcwidth(3) of Plane 15 and Plane 16 Private Use CharactersIngo Schwarze2021-06-021-1/+1
| | | | | was changed from 0 to 1. Adjust the test results accordingly. Issue reported by bluhm@
* Fix this test after the recent Unicode update in OpenBSD base.Ingo Schwarze2020-02-271-1/+1
| | | | | | | | | | The test uses U+07FF NKO TAMAN SIGN because it is the highest code point having a two-byte UTF-8 representation. This character is a new single-width punctuation character in Unicode 11, such that mandoc now does correct horizontal spacing. We already used the code point for the test before it was assigned, which resulted in weird spacing because wcwidth(3) returns -1 for unassigned code points.
* Finally port the OpenBSD regression suite.Ingo Schwarze2017-02-081-0/+67
Both kristaps@ and wiz@ repeated asked for this, literally for years.