[PATCH 21/34] Migrate from `NS`/`NE` to `RS`/`RE` and `EX`/`EE`.

[G. Branden Robinson]

* man/curs_attr.3x:
* man/curs_mouse.3x:
* man/infocmp.1m:
* man/ncurses.3x:
* man/new_pair.3x:
* man/scr_dump.5:
* man/tabs.1:
* man/term.5: Do it.  Drop consequently unused `NS` and `NE` macro
  definitions and the `CW` string definition `NS` requires.
---
 man/curs_attr.3x  |  32 ++++--------
 man/curs_mouse.3x |  32 ++++--------
 man/infocmp.1m    |  28 ++---------
 man/ncurses.3x    | 126 +++++++++++++++++++++++++---------------------
 man/new_pair.3x   |  32 ++++--------
 man/scr_dump.5    |  86 ++++++++++++++++---------------
 man/tabs.1        |  43 ++++++----------
 man/term.5        |  26 ++--------
 8 files changed, 166 insertions(+), 239 deletions(-)

diff --git a/man/curs_attr.3x b/man/curs_attr.3x
index e6db84bf..765cb990 100644
--- a/man/curs_attr.3x
+++ b/man/curs_attr.3x
@@ -34,25 +34,7 @@
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
 .el       .ds '' ''
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
+.
 .de bP
 .ie n  .IP \(bu 4
 .el    .IP \(bu 2
@@ -198,10 +180,12 @@ .SS Legacy window attributes
 For example,
 as long as that value fits into the \fBA_COLOR\fP mask,
 then these calls produce similar results:
-.NS
+.RS 4
+.EX
 attrset(A_BOLD | COLOR_PAIR(\fIpair\fP));
 attr_set(A_BOLD, \fIpair\fP, NULL);
-.NE
+.EE
+.RE
 .PP
 However, if the value does not fit, then the \fBCOLOR_PAIR\fP macro
 uses only the bits that fit.
@@ -213,10 +197,12 @@ .SS Legacy window attributes
 (or \fBchtype\fP).
 For example, the \fIinput\fP and \fIoutput\fP values in these statements
 would be the same:
-.NS
+.RS 4
+.EX
 int value = A_BOLD | COLOR_PAIR(\fIinput\fP);
 int \fIoutput\fP = PAIR_NUMBER(value);
-.NE
+.EE
+.RE
 .PP
 The \fBattrset\fP routine is a legacy feature predating SVr4 curses
 but kept in X/Open Curses for the same reason that SVr4 curses kept it:
diff --git a/man/curs_mouse.3x b/man/curs_mouse.3x
index 8e9dfba1..c807fdb3 100644
--- a/man/curs_mouse.3x
+++ b/man/curs_mouse.3x
@@ -34,25 +34,7 @@
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
 .el       .ds '' ''
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
+.
 .de bP
 .ie n  .IP \(bu 4
 .el    .IP \(bu 2
@@ -282,7 +264,8 @@ .SH PORTABILITY
 .bP
 the \*(``libcurses\*('' manual page lists functions for this feature
 which are prototyped in \fBcurses.h\fP:
-.NS
+.RS 4
+.EX
 extern int mouse_set(long int);
 extern int mouse_on(long int);
 extern int mouse_off(long int);
@@ -290,16 +273,19 @@ .SH PORTABILITY
 extern int map_button(unsigned long);
 extern void wmouse_position(WINDOW *, int *, int *);
 extern unsigned long getmouse(void), getbmap(void);
-.NE
+.EE
+.RE
 .bP
 the \*(``terminfo\*('' manual page lists capabilities for the feature
-.NS
+.RS 4
+.EX
 buttons           btns    BT       Number of buttons on the mouse
 get_mouse         getm    Gm       Curses should get button events
 key_mouse         kmous   Km       0631, Mouse event has occurred
 mouse_info        minfo   Mi       Mouse status information
 req_mouse_pos     reqmp   RQ       Request mouse position report
-.NE
+.EE
+.RE
 .bP
 the interface made assumptions (as does \fIncurses\fP) about the escape 
sequences
 sent to and received from the terminal.
diff --git a/man/infocmp.1m b/man/infocmp.1m
index 91fe9113..68b6ec5a 100644
--- a/man/infocmp.1m
+++ b/man/infocmp.1m
@@ -30,12 +30,6 @@
 .\"
 .\" $Id: infocmp.1m,v 1.95 2023/09/30 21:38:11 tom Exp $
 .TH @INFOCMP@ 1M 2023-09-30 "ncurses 6.4" "User commands"
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.
 .ie \n(.g .ds `` \(lq
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
@@ -46,22 +40,6 @@
 .el    .IP \(bu 2
 ..
 .
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
-.
 .ds n 5
 .ds d @TERMINFO@
 .SH NAME
@@ -466,9 +444,11 @@ .SS Other Options
 .IP
 For example, this prints the compiled terminfo value as a string
 which could be assigned to the \fBTERMINFO\fP environment variable:
-.NS
+.RS 4
+.EX
 @INFOCMP@ \-0 \-q \-Q2
-.NE
+.EE
+.RE
 .TP 5
 \fB\-q\fP
 This makes the output a little shorter:
diff --git a/man/ncurses.3x b/man/ncurses.3x
index 0b16b2a3..01339d4b 100644
--- a/man/ncurses.3x
+++ b/man/ncurses.3x
@@ -34,29 +34,7 @@
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
 .el       .ds '' ''
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.de bP
-.ie n  .IP \(bu 4
-.el    .IP \(bu 2
-..
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
+.
 .ds n 5
 .ds d @TERMINFO@
 .SH NAME
@@ -106,9 +84,11 @@ .SH DESCRIPTION
 .SS Initialization
 The library uses the locale which the calling program has initialized.
 That is normally done with \fBsetlocale\fP(3):
-.NS
+.RS 4
+.EX
 \fBsetlocale(LC_ALL, "");\fP
-.NE
+.EE
+.RE
 .PP
 If the locale is not initialized,
 the library assumes that characters are printable as in ISO\-8859\-1,
@@ -125,15 +105,19 @@ .SS Initialization
 To get character-at-a-time input without echoing (most
 interactive, screen oriented programs want this), the following
 sequence should be used:
-.NS
+.RS 4
+.EX
 \fBinitscr(); cbreak(); noecho();\fP
-.NE
+.EE
+.RE
 .PP
 Most programs would additionally use the sequence:
-.NS
+.RS 4
+.EX
 \fBintrflush(stdscr, FALSE);\fP
 \fBkeypad(stdscr, TRUE);\fP
-.NE
+.EE
+.RE
 .PP
 Before a \fBcurses\fP program is run, the tab stops of the terminal
 should be set and its initialization strings, if defined, must be output.
@@ -203,21 +187,27 @@ .SS Environment variables
 standard place.
 For example, if \fBTERM\fP is set to \fBatt4424\fP, then the
 compiled terminal definition is found in
-.NS
+.RS 4
+.EX
 \fB\*d/a/att4424\fP.
-.NE
+.EE
+.RE
 .PP
 (The \fBa\fP is copied from the first letter of \fBatt4424\fP to avoid
 creation of huge directories.)  However, if \fBTERMINFO\fP is set to
 \fB$HOME/myterms\fP, \fBcurses\fP first checks
-.NS
+.RS 4
+.EX
 \fB$HOME/myterms/a/att4424\fP,
-.NE
+.EE
+.RE
 .PP
 and if that fails, it then checks
-.NS
+.RS 4
+.EX
 \fB\*d/a/att4424\fP.
-.NE
+.EE
+.RE
 .PP
 This is useful for developing experimental definitions or when write
 permission in \fB\*d\fP is not available.
@@ -894,10 +884,12 @@ .SS ESCDELAY
 .SS HOME
 Tells \fBncurses\fP where your home directory is.
 That is where it may read and write auxiliary terminal descriptions:
-.NS
+.RS 4
+.EX
 $HOME/.termcap
 $HOME/.terminfo
-.NE
+.EE
+.RE
 .SS LINES
 Like COLUMNS, specify the height of the screen in characters.
 See COLUMNS for a detailed description.
@@ -906,11 +898,13 @@ .SS MOUSE_BUTTONS_123
 It specifies the order of buttons on the mouse.
 OS/2 numbers a 3-button mouse inconsistently from other
 platforms:
-.NS
+.RS 4
+.EX
 1 = left
 2 = right
 3 = middle.
-.NE
+.EE
+.RE
 .PP
 This variable lets you customize the mouse.
 The variable must be three numeric digits 1\-3 in any order, e.g., 123 or 321.
@@ -1110,14 +1104,18 @@ .SS TERMINFO
 .bP
 If \fBncurses\fP is built to use hashed databases,
 then each entry in this list may be the path of a hashed database file, e.g.,
-.NS
+.RS 4
+.EX
 /usr/share/terminfo.db
-.NE
+.EE
+.RE
 .IP
 rather than
-.NS
+.RS 4
+.EX
 /usr/share/terminfo/
-.NE
+.EE
+.RE
 .IP
 The hashed database uses less disk-space and is a little faster than the
 directory tree.
@@ -1134,10 +1132,12 @@ .SS TERMINFO
 \fBncurses\fP uses the remainder of that variable as a compiled terminal
 description.
 You might produce the base64 format using \fBinfocmp\fP(1M):
-.NS
+.RS 4
+.EX
 TERMINFO="$(infocmp \-0 \-Q2 \-q)"
 export TERMINFO
-.NE
+.EE
+.RE
 .IP
 The compiled description is used if it corresponds to the terminal identified
 by the \fBTERM\fP variable.
@@ -1181,18 +1181,22 @@ .SS TERMPATH
 .PP
 If the \fBTERMPATH\fP environment variable is not set,
 \fBncurses\fP looks in the files
-.NS
+.RS 4
+.EX
 /etc/termcap, /usr/share/misc/termcap and $HOME/.termcap,
-.NE
+.EE
+.RE
 .PP
 in that order.
 .PP
 The library may be configured to disregard the following variables when the
 current user is the superuser (root), or if the application uses setuid or
 setgid permissions:
-.NS
+.RS 4
+.EX
 $TERMINFO, $TERMINFO_DIRS, $TERMPATH, as well as $HOME.
-.NE
+.EE
+.RE
 .SH ALTERNATE CONFIGURATIONS
 Several different configurations are possible,
 depending on the configure script options used when building \fBncurses\fP.
@@ -1201,17 +1205,21 @@ .SH ALTERNATE CONFIGURATIONS
 .TP 5
 \-\-disable\-overwrite
 The standard include for \fBncurses\fP is as noted in \fBSYNOPSIS\fP:
-.NS
+.RS 4
+.EX
 \fB#include <curses.h>\fP
-.NE
+.EE
+.RE
 .IP
 This option is used to avoid filename conflicts when \fBncurses\fP
 is not the main implementation of curses of the computer.
 If \fBncurses\fP is installed disabling overwrite, it puts its headers in
 a subdirectory, e.g.,
-.NS
+.RS 4
+.EX
 \fB#include <ncurses/curses.h>\fP
-.NE
+.EE
+.RE
 .IP
 It also omits a symbolic link which would allow you to use \fB\-lcurses\fP
 to build executables.
@@ -1222,14 +1230,18 @@ .SH ALTERNATE CONFIGURATIONS
 puts the header files in a different subdirectory.
 All of the library names have a \*(``w\*('' appended to them,
 i.e., instead of
-.NS
+.RS 4
+.EX
 \fB\-lncurses\fP
-.NE
+.EE
+.RE
 .IP
 you link with
-.NS
+.RS 4
+.EX
 \fB\-lncursesw\fP
-.NE
+.EE
+.RE
 .IP
 You must also enable the wide-character features in the header file
 when compiling for the wide-character library
diff --git a/man/new_pair.3x b/man/new_pair.3x
index 6fd7bef2..61ca4ded 100644
--- a/man/new_pair.3x
+++ b/man/new_pair.3x
@@ -35,29 +35,11 @@
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
 .el       .ds '' ''
+.
 .de bP
 .ie n  .IP \(bu 4
 .el    .IP \(bu 2
 ..
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
 .SH NAME
 \fB\%alloc_pair\fP,
 \fB\%find_pair\fP,
@@ -95,16 +77,20 @@ .SH DESCRIPTION
 with only a few dozen color combinations,
 it is convenient to use the maximum number of combinations
 as the limit on color pairs:
-.NS
+.RS 4
+.EX
 \fBCOLORS\fI * \fBCOLORS\fR
-.NE
+.EE
+.RE
 .bP
 Terminals which support \fIdefault colors\fP distinct
 from \*(``ANSI colors\*(''
 add to the possible combinations, producing this total:
-.NS
+.RS 4
+.EX
 \fI( \fBCOLORS\fI + 1 ) * ( \fBCOLORS\fI + 1 )\fR
-.NE
+.EE
+.RE
 .bP
 An application might use up to a few dozen color pairs to
 implement a predefined color scheme.
diff --git a/man/scr_dump.5 b/man/scr_dump.5
index 1e024530..fecd30e1 100644
--- a/man/scr_dump.5
+++ b/man/scr_dump.5
@@ -33,25 +33,7 @@
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
 .el       .ds '' ''
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
+.
 .de bP
 .ie n  .IP \(bu 4
 .el    .IP \(bu 2
@@ -80,17 +62,22 @@ .SS ncurses6
 that requires a new magic number
 was unused by other applications.
 This 16-bit number was unused:
-.NS
+.RS 4
+.EX
 0x8888 (octal \*(``\e210\e210\*('')
-.NE
+.EE
+.RE
 .IP
 but to be more certain, this 32-bit number was chosen:
-.NS
+.RS 4
+.EX
 0x88888888 (octal \*(``\e210\e210\e210\e210\*('')
-.NE
+.EE
+.RE
 .IP
 This is the pattern submitted to the maintainers of the \fBfile\fP program:
-.NS
+.RS 4
+.EX
 #
 # ncurses5 (and before) did not use a magic number,
 # making screen dumps "data".
@@ -98,7 +85,8 @@ .SS ncurses6
 # ncurses6 (2015) uses this format, ignoring byte-order
 0    string    \e210\e210\e210\e210ncurses    ncurses6 screen image
 #
-.NE
+.EE
+.RE
 .bP
 The screen dumps are written in textual form,
 so that internal data sizes are not directly related to the dump-format, and
@@ -177,31 +165,37 @@ .SS Unix System V
 The \fBWINDOW\fP data and the lines of text follow, all in binary form.
 .PP
 The Solaris curses source has these definitions:
-.NS
+.RS 4
+.EX
 /* terminfo magic number */
 #define MAGNUM  0432
 
 /* curses screen dump magic number */
 #define SVR2_DUMP_MAGIC_NUMBER  0433
 #define SVR3_DUMP_MAGIC_NUMBER  0434
-.NE
+.EE
+.RE
 .PP
 That is, the feature was likely introduced in SVr2 (1984),
 and improved in SVr3 (1987).
 The Solaris curses source has no magic number for SVr4 (1989).
 Other operating systems (AIX and HPUX) use a magic number which would
 correspond to this definition:
-.NS
+.RS 4
+.EX
 /* curses screen dump magic number */
 #define SVR4_DUMP_MAGIC_NUMBER  0435
-.NE
+.EE
+.RE
 .PP
 That octal number in bytes is 001, 035.
 Because most Unix vendors use big-endian hardware,
 the magic number is written with the high-order byte first, e.g.,
-.NS
+.RS 4
+.EX
 \001\035
-.NE
+.EE
+.RE
 .PP
 After the magic number, the \fBWINDOW\fP structure and line-data are
 written in binary format.
@@ -247,9 +241,11 @@ .SS PDCurses
 but begins the file with its three-byte identifier \*(``PDC\*('',
 followed by a one-byte version,
 e.g.,
-.NS
+.RS 4
+.EX
        \*(``PDC\e001\*(''
-.NE
+.EE
+.RE
 .SS NetBSD
 As of April 2017, NetBSD curses does
 not support \fBscr_dump\fP and \fBscr_restore\fP
@@ -271,7 +267,8 @@ .SS NetBSD
 .SH EXAMPLE
 Given a simple program which writes text to the screen
 (and for the sake of example, limiting the screen-size to 10x20):
-.NS
+.RS 4
+.EX
 #include <curses.h>
 
 int
@@ -296,10 +293,12 @@ .SH EXAMPLE
     endwin();
     return 0;
 }
-.NE
+.EE
+.RE
 .PP
 When run using ncurses6, the output looks like this:
-.NS
+.RS 4
+.EX
 \e210\e210\e210\e210ncurses 6.0.20170415
 _cury=5
 _curx=11
@@ -322,7 +321,8 @@ .SH EXAMPLE
 8:\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es
 9:\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es
 10:\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es\es
-.NE
+.EE
+.RE
 .PP
 The first four octal escapes are actually nonprinting characters,
 while the remainder of the file is printable text.
@@ -341,7 +341,8 @@ .SH EXAMPLE
 .ne 10
 .PP
 Running the same program with Solaris \fIxpg4\fP curses gives this dump:
-.NS
+.RS 4
+.EX
 MAX=10,20
 BEG=0,0
 SCROLL=0,10
@@ -375,7 +376,8 @@ .SH EXAMPLE
 9,0,0,1,
 9,19,0,0,
 CUR=11,5
-.NE
+.EE
+.RE
 .PP
 Solaris \fBgetwin\fP requires that all parameters are present, and
 in the same order.
@@ -386,7 +388,8 @@ .SH EXAMPLE
 On the other hand, the SVr4 curses library does know about the background 
color.
 However, its screen dumps are in binary.
 Here is the corresponding dump (using \*(``od \-t x1\*(''):
-.NS
+.RS 4
+.EX
 0000000 1c 01 c3 d6 f3 58 05 00 0b 00 0a 00 14 00 00 00
 0000020 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
 0000040 00 00 b8 1a 06 08 cc 1a 06 08 00 00 09 00 10 00
@@ -409,7 +412,8 @@ .SH EXAMPLE
 0001620 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 *
 0002371
-.NE
+.EE
+.RE
 .SH AUTHORS
 Thomas E. Dickey
 .br
diff --git a/man/tabs.1 b/man/tabs.1
index b264d916..c70df2ec 100644
--- a/man/tabs.1
+++ b/man/tabs.1
@@ -38,25 +38,6 @@
 .ie n  .IP \(bu 4
 .el    .IP \(bu 2
 ..
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
 .
 .ds n 5
 .SH NAME
@@ -69,9 +50,11 @@ .SH DESCRIPTION
 This uses the terminfo \fBclear_all_tabs\fP and \fBset_tab\fP capabilities.
 If either is absent, \fB@TABS@\fP is unable to clear/set tab-stops.
 The terminal should be configured to use hard tabs, e.g.,
-.NS
+.RS 4
+.EX
 stty tab0
-.NE
+.EE
+.RE
 .PP
 Like \fB@CLEAR@\fP(1), \fB@TABS@\fP writes to the standard output.
 You can redirect the standard output to a file (which prevents
@@ -86,9 +69,11 @@ .SH DESCRIPTION
 database, the result is unpredictable.
 Before running curses programs,
 you should either reset tab-stops to the standard interval
-.NS
+.RS 4
+.EX
 tabs \-8
-.NE
+.EE
+.RE
 .PP
 or use the \fB@RESET@\fP program,
 since the normal initialization sequences do not ensure that tab-stops
@@ -132,17 +117,21 @@ .SS Explicit Lists
 The values in the list must be in increasing numeric order,
 and greater than zero.
 They are separated by a comma or a blank, for example,
-.NS
+.RS 4
+.EX
 tabs 1,6,11,16,21
 tabs 1 6 11 16 21
-.NE
+.EE
+.RE
 .PP
 Use a \*(``+\*('' to treat a number
 as an increment relative to the previous value,
 e.g.,
-.NS
+.RS 4
+.EX
 tabs 1,+5,+5,+5,+5
-.NE
+.EE
+.RE
 .PP
 which is equivalent to the 1,6,11,16,21 example.
 .SS Predefined Tab-Stops
diff --git a/man/term.5 b/man/term.5
index c06b4c5d..68745a9d 100644
--- a/man/term.5
+++ b/man/term.5
@@ -35,25 +35,7 @@
 .el       .ds '' ''
 .ie \n(.g .ds ^  \(ha
 .el       .ds ^  ^
-.ie n .ds CW R
-.el   \{
-.ie \n(.g .ds CW CR
-.el       .ds CW CW
-.\}
-.de NS
-.ie n  .sp
-.el    .sp .5
-.ie n  .in +4
-.el    .in +2
-.nf
-.ft \*(CW
-..
-.de NE
-.fi
-.ft R
-.ie n  .in -4
-.el    .in -2
-..
+.
 .de bP
 .ie n  .IP \(bu 4
 .el    .IP \(bu 2
@@ -352,14 +334,16 @@ .SS Mixed-case terminal names
 .SH EXAMPLE
 As an example, here is a description for the Lear-Siegler
 ADM\-3, a popular though rather stupid early terminal:
-.NS
+.RS 4
+.EX
 adm3a|lsi adm3a,
         am,
         cols#80, lines#24,
         bel=\*^G, clear=\e032$<1>, cr=\*^M, cub1=\*^H, cud1=\*^J,
         cuf1=\*^L, cup=\eE=%p1%{32}%+%c%p2%{32}%+%c, cuu1=\*^K,
         home=\*^\*^, ind=\*^J,
-.NE
+.EE
+.RE
 .PP
 and a hexadecimal dump of the compiled terminal description:
 .PP
-- 
2.30.2

signature.asc
Description: PGP signature