X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_add_wch.3x.html;h=f7f0c2432e05f27b9401122290a2718e07a58f0a;hp=cc670d3fdf4298755eade971df9823ece31b40cd;hb=336aa0803853f7961dd31f1e35cd688d861ffd64;hpb=bca50d0d8592defee6c584fdedd25f4b1a31345b
diff --git a/doc/html/man/curs_add_wch.3x.html b/doc/html/man/curs_add_wch.3x.html
index cc670d3f..f7f0c243 100644
--- a/doc/html/man/curs_add_wch.3x.html
+++ b/doc/html/man/curs_add_wch.3x.html
@@ -1,6 +1,6 @@
@@ -34,7 +34,7 @@
curs_add_wch 3x
-
+
@@ -138,7 +138,24 @@
WACS_VLINE 0x2502 | x vertical line
The wide-character configuration of ncurses also defines symbols for
- double-lines:
+ thick lines (acsc "J" to "V"):
+
+ ACSUnicodeASCIIacscGlyph
+ NameDefaultDefaultcharName
+ -----------------------------------------------------------------------
+ WACS_T_BTEE 0x253b + V thick tee pointing up
+ WACS_T_HLINE 0x2501 - Q thick horizontal line
+ WACS_T_LLCORNER 0x2517 + M thick lower left corner
+ WACS_T_LRCORNER 0x251b + J thick lower right corner
+ WACS_T_LTEE 0x252b + T thick tee pointing right
+ WACS_T_PLUS 0x254b + N thick large plus
+ WACS_T_RTEE 0x2523 + U thick tee pointing left
+ WACS_T_TTEE 0x2533 + W thick tee pointing down
+ WACS_T_ULCORNER 0x250f + L thick upper left corner
+ WACS_T_URCORNER 0x2513 + K thick upper right corner
+ WACS_T_VLINE 0x2503 | X thick vertical line
+
+ and for double-lines (acsc "A" to "I"):
ACSUnicodeASCIIacscGlyphNameDefaultDefaultcharName
@@ -155,28 +172,22 @@
WACS_D_URCORNER 0x2557 + B double upper right corner
WACS_D_VLINE 0x2551 | Y double vertical line
- and for thick lines:
+ Unicode's descriptions for these characters differs slightly from
+ ncurses, by introducing the term "light" (along with less important
+ details). Here are its descriptions for the normal, thick, and double
+ horizontal lines:
- ACSUnicodeASCIIacscGlyph
- NameDefaultDefaultcharName
- -----------------------------------------------------------------------
- WACS_T_BTEE 0x253b + V thick tee pointing up
- WACS_T_HLINE 0x2501 - Q thick horizontal line
- WACS_T_LLCORNER 0x2517 + M thick lower left corner
- WACS_T_LRCORNER 0x251b + J thick lower right corner
- WACS_T_LTEE 0x252b + T thick tee pointing right
- WACS_T_PLUS 0x254b + N thick large plus
- WACS_T_RTEE 0x2523 + U thick tee pointing left
- WACS_T_TTEE 0x2533 + W thick tee pointing down
- WACS_T_ULCORNER 0x250f + L thick upper left corner
- WACS_T_URCORNER 0x2513 + K thick upper right corner
- WACS_T_VLINE 0x2503 | X thick vertical line
+ o U+2500 BOX DRAWINGS LIGHT HORIZONTAL
+
+ o U+2501 BOX DRAWINGS HEAVY HORIZONTAL
+
+ o U+2550 BOX DRAWINGS DOUBLE HORIZONTAL
All routines return the integer ERR upon failure and OK on success.
- Functions with a "mv" prefix first perform a cursor movement using
+ Functions with a "mv" prefix first perform a cursor movement using
wmove, and return an error if the position is outside the window, or if
the window pointer is null.
@@ -186,71 +197,71 @@
- All of these functions are described in the XSI Curses standard, Issue
- 4. The defaults specified for line-drawing characters apply in the
+ All of these functions are described in the XSI Curses standard, Issue
+ 4. The defaults specified for line-drawing characters apply in the
POSIX locale.
- X/Open Curses makes it clear that the WACS_ symbols should be defined
+ X/Open Curses makes it clear that the WACS_ symbols should be defined
as a pointer to cchar_t data, e.g., in the discussion of border_set. A
few implementations are problematic:
o NetBSD curses defines the symbols as a wchar_t within a cchar_t.
o HPUX curses equates some of the ACS_ symbols to the analogous WACS_
- symbols as if the ACS_ symbols were wide characters. The misde-
- fined symbols are the arrows and other symbols which are not used
+ symbols as if the ACS_ symbols were wide characters. The misde-
+ fined symbols are the arrows and other symbols which are not used
for line-drawing.
X/Open Curses does not define symbols for thick- or double-lines. SVr4
- curses implementations defined their line-drawing symbols in terms of
- intermediate symbols. This implementation extends those symbols, pro-
+ curses implementations defined their line-drawing symbols in terms of
+ intermediate symbols. This implementation extends those symbols, pro-
viding new definitions which are not in the SVr4 implementations.
- Not all Unicode-capable terminals provide support for VT100-style
+ Not all Unicode-capable terminals provide support for VT100-style
alternate character sets (i.e., the acsc capability), with their corre-
- sponding line-drawing characters. X/Open Curses did not address the
- aspect of integrating Unicode with line-drawing characters. Existing
- implementations of Unix curses (AIX, HPUX, Solaris) use only the acsc
- character-mapping to provide this feature. As a result, those imple-
- mentations can only use single-byte line-drawing characters. Ncurses
- 5.3 (2002) provided a table of Unicode values to solve these problems.
+ sponding line-drawing characters. X/Open Curses did not address the
+ aspect of integrating Unicode with line-drawing characters. Existing
+ implementations of Unix curses (AIX, HPUX, Solaris) use only the acsc
+ character-mapping to provide this feature. As a result, those imple-
+ mentations can only use single-byte line-drawing characters. Ncurses
+ 5.3 (2002) provided a table of Unicode values to solve these problems.
NetBSD curses incorporated that table in 2010.
In this implementation, the Unicode values are used instead of the ter-
- minal description's acsc mapping as discussed in ncurses(3x) for the
- environment variable NCURSES_NO_UTF8_ACS. In contrast, for the same
+ minal description's acsc mapping as discussed in ncurses(3x) for the
+ environment variable NCURSES_NO_UTF8_ACS. In contrast, for the same
cases, the line-drawing characters described in curs_addch(3x) will use
only the ASCII default values.
- Having Unicode available does not solve all of the problems with line-
+ Having Unicode available does not solve all of the problems with line-
drawing for curses:
- o The closest Unicode equivalents to the VT100 graphics S1, S3, S7
- and S9 frequently are not displayed at the regular intervals which
+ o The closest Unicode equivalents to the VT100 graphics S1, S3, S7
+ and S9 frequently are not displayed at the regular intervals which
the terminal used.
- o The lantern is a special case. It originated with the AT&T 4410
- terminal in the early 1980s. There is no accessible documentation
+ o The lantern is a special case. It originated with the AT&T 4410
+ terminal in the early 1980s. There is no accessible documentation
depicting the lantern symbol on the AT&T terminal.
Lacking documentation, most readers assume that a stormlantern was
intended. But there are several possibilities, all with problems.
- Unicode 6.0 (2010) does provide two lantern symbols: U+1F383 and
- U+1F3EE. Those were not available in 2002, and are irrelevant
- since they lie outside the BMP and as a result are not generally
+ Unicode 6.0 (2010) does provide two lantern symbols: U+1F383 and
+ U+1F3EE. Those were not available in 2002, and are irrelevant
+ since they lie outside the BMP and as a result are not generally
available in terminals. They are not storm lanterns, in any case.
Most stormlanterns have a tapering glass chimney (to guard against
tipping); some have a wire grid protecting the chimney.
- For the tapering appearance, U+2603 was adequate. In use on a
+ For the tapering appearance, U+2603 was adequate. In use on a
terminal, no one can tell what the image represents. Unicode calls
it a snowman.
- Others have suggested these alternatives: S U+00A7 (section mark),
+ Others have suggested these alternatives: S U+00A7 (section mark),
O U+0398 (theta), O U+03A6 (phi), d U+03B4 (delta), U+2327 (x in a
- rectangle), U+256C (forms double vertical and horizontal), and
+ rectangle), U+256C (forms double vertical and horizontal), and
U+2612 (ballot box with x).