From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: Fix this test after the recent Unicode update in OpenBSD base.
Date: Wed, 26 Feb 2020 19:36:51 -0500 (EST) [thread overview]
Message-ID: <11fef7999c88764b@mandoc.bsd.lv> (raw)
Log Message:
-----------
Fix this test after the recent Unicode update in OpenBSD base.
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.
Modified Files:
--------------
mandoc/regress/char/unicode:
input.out_utf8
Revision Data
-------------
Index: input.out_utf8
===================================================================
RCS file: /home/cvs/mandoc/mandoc/regress/char/unicode/input.out_utf8,v
retrieving revision 1.1
retrieving revision 1.2
diff -Lregress/char/unicode/input.out_utf8 -Lregress/char/unicode/input.out_utf8 -u -p -r1.1 -r1.2
--- regress/char/unicode/input.out_utf8
+++ regress/char/unicode/input.out_utf8
@@ -23,7 +23,7 @@ D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
0xc278 ?x ASCII continuation
U+0080 0xc280 �� lowest two-byte
0xc2c380 ?À high continuation
- U+07FF 0xdfbf ߿߿ highest two-byte
+ U+07FF 0xdfbf ߿߿ highest two-byte
T\bTh\bhr\bre\bee\be-\b-b\bby\byt\bte\be r\bra\ban\bng\bge\be
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2020-02-27 0:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11fef7999c88764b@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).