From groff-admin  Fri Jun  2 11:04:26 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id LAA15274
	for <groff@ffii.org>; Fri, 2 Jun 2000 11:04:19 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AA06392 for groff@ffii.org; Thu, 1 Jun 2000 08:36:56 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Thu, 1 Jun 2000 08:16:49 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: "Bates, Rod" <Rod.Bates@wichita.boeing.com>, Ted.Harding@nessie.mcc.ac.uk
Cc: "'groff@ffii.org'" <groff@ffii.org>
Subject: Re: [Groff] Help with umlauts
In-Reply-To: <XFMail.000531194207.Ted.Harding@nessie.mcc.ac.uk>
Message-Id: <Pine.LNX.4.10.10006010811010.9821-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
Content-Length: 1506
Lines: 50

Yesterday, Bates, Rod schrieb:

> I have an old input file and its corresponding .ps file, both of
> which came to me from long ago and far away.  I can get groff 
> to regenerate the .ps, except it complains about a few occurrences
> of umlauted characters.  For example, in the input file, there
> is a \*U which shows as capital U with umlaut in the original
> .ps file.  Using groff, I get the message: 
> 
> warning: can't find special character `U:' 
[snip]

> What do I need to do to get these characters? 

Yesterday, Ted.Harding@nessie.mcc.ac.uk schrieb:

[snip]
> Presumably the file's creator wanted to simplfy typing by defining
> 
>   .ds U \(U:
> 
> so that \*U is equivalent to \(U:, and so on.
> 
> For more details, and for other accents (acute, grave, circumflex,
> cedilla, etc) have a look right at the end of the tmac.s file
> (under the '.AM' macro).

Maybe I'm mistaken, but I've been a troff user for some time now (>15 y.?)
and I remember that when I shifted from DWB troff to groff (a great
shift, that goes without saying), I found out that all accents and
dieresis marcs, cedillas, etc. are inverted under groff. That is:

    ditroff              groff
    \(a`                 \('a
    \(U:                 \(:U
    \(c,                 \(,c
    etc.                 etc.

So I had to filter text in oder to put the correct accents. Could
this be the same problem?

nicb
 

+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+



From groff-admin  Fri Jun  2 14:38:37 2000
Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id OAA18368
	for <groff@ffii.org>; Fri, 2 Jun 2000 14:38:37 +0200
Received: from tedistan.annex.umist.ac.uk ([194.66.22.200] ident=root)
	by probity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 12xRsV-000Kzd-00; Thu, 1 Jun 2000 11:07:04 +0100
Received: (from efh@localhost)
	by tedistan.annex.umist.ac.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id LAA26787;
	Thu, 1 Jun 2000 11:04:41 +0100
Message-ID: <XFMail.000601110441.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="_=XFMail.1.3.p0.Linux:000601110441:2745=_"
In-Reply-To: <Pine.LNX.4.10.10006010811010.9821-100000@ax-nicb.axnet.it>
Date: Thu, 01 Jun 2000 11:04:41 +0100 (BST)
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: Nicola Bernardini <nicb@axnet.it>
Subject: Re: [Groff] Help with umlauts
Cc: "groff@ffii.org" <groff@ffii.org>, Bates@tedistan.annex.umist.ac.uk,
        Rod <Rod.Bates@wichita.boeing.com>
Status: O
Content-Length: 9014
Lines: 319

This message is in MIME format
--_=XFMail.1.3.p0.Linux:000601110441:2745=_
Content-Type: text/plain; charset=iso-8859-1

On 01-Jun-00 Nicola Bernardini wrote:
> 
> Maybe I'm mistaken, but I've been a troff user for some time now (>15
> y.?) and I remember that when I shifted from DWB troff to groff (a
> great shift, that goes without saying), I found out that all accents
> and dieresis marcs, cedillas, etc. are inverted under groff. That is:
> 
>     ditroff              groff
>     \(a`                 \('a
>     \(U:                 \(:U
>     \(c,                 \(,c
>     etc.                 etc.
> 
> So I had to filter text in oder to put the correct accents. Could
> this be the same problem?

In the case of the file that gave Rod Bates the problems, quite possibly.

I'm not now in a position to verify what names DWB gave to accented
characters. However, the groff situation is as follows:

In the font files (e.g. .../groff/devps/TR) the accented characters
which have names defined in these files do indeed have the accent
first, as in

  `A      722,890 2       0300    Agrave
  char192 "
  'A      722,890 2       0301    Aacute
  char193 "
  ^A      722,886 2       0302    Acircumflex
  char194 "
  ~A      722,850 2       0303    Atilde
  char195 "
  :A      722,835 2       0304    Adieresis

so that, without any additional provision, you get 'Adieresis'
by using \(:A etc.

This is unsatisfactory in various respects. In 'tmac.s', the
macro .AM was introduced to enable users to do it the other
way round if they wish so that (as explained in my previous
mail) the umlaut-over accent is defined in the string \*:
which enables the user to define characters with names such as

\(A: = A\*:  \(O: = O\*:  \(U: = U\*:  and so on (and similar
for other accents such as  \(c, = c\*,  \(A` = A\*`  etc)

Rather than filtering original text which has the name in the
order \(<letter><accent> in order to make it conform to groff's
primitive name \(<accent><letter> it is, in my view, actually
better to set up your private macro package once and for all
in order to define the characters \(<letter><accent> which
you need (you're going to have to do something like that anyway
whenever you need an accented character which is not one of those
in the font file).

For this purpose, the .AM macro can be lifted straight out of
tmac.s if you don't want to use the ms macros; or, if you are
using the ms macros, then your private macros only need to
invoke '.AM' before you use the accented character.

I'm attaching two files:

1. The .AM macro in my tmac.s
   (I slightly modified this a long time ago)

2. The "accents" excerpt from my private macro file tmac.ted

Between the two of these, you should be able to find out how to
make any accented character you want!

Best wishes to all,
Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 01-Jun-00                                       Time: 11:04:41
------------------------------ XFMail ------------------------------

--_=XFMail.1.3.p0.Linux:000601110441:2745=_
Content-Disposition: attachment; filename="AM_macro"
Content-Transfer-Encoding: 7bit
Content-Description: AM_macro
Content-Type: text/plain; charset=iso-8859-1; name=AM_macro; SizeOnDisk=975

.de AM
.acc*over-def ' \'
.acc*over-def ` \`
.acc*over-def ^ ^
.acc*over-def ~ ~
.acc*over-def : \(ad
.acc*over-def v \(ah
.acc*over-def _ \(a-
.acc*over-def o \(ao
.acc*under-def , \(ac
.\"The following modified by EFH so that it looks right in Italics
.acc*under-def . \h'(u;-\En[.csk])'\s[\En[.s]*8u/10u]\v'.2m'.\v'-.2m'\s0
.acc*under-def hook \(ho
.acc*slash-def / /
.char \[hooko] o\\\\*[hook]
.ds q \[hooko]
.ds 3 \[yogh]
.ds D- \(-D\"                   Icelandic uppercase eth
.ds d- \(Sd\"                   Icelandic lowercase eth
.ds Th \(TP\"                   Icelandic uppercase thorn
.ds th \(Tp\"                   Icelandic lowercase thorn
.ds 8 \(ss\"                    German double s
.ds Ae \(AE\"                   AE ligature
.ds ae \(ae\"                   ae ligature
.ds Oe \(OE\"                   OE ligature
.ds oe \(oe\"                   oe ligature
.ds ? \(r?\"                    upside down ?
.ds ! \(r!\"                    upside down !
..

--_=XFMail.1.3.p0.Linux:000601110441:2745=_
Content-Disposition: attachment; filename="accents"
Content-Transfer-Encoding: 7bit
Content-Description: accents
Content-Type: text/plain; charset=iso-8859-1; name=accents; SizeOnDisk=4390

.\" Accented and Foreign Characters
.\" Improved accent marks installed by evoking .AM (TMAC.S) below.
.AM
.acc*over-def dot \(a.
.acc*over-def breve \(ab
.acc*over-def ring \(ao
.acc*over-def ; \(a"
.\" ------------------------------------------------
.\" Azeri upside-down e and E
.ds eupsidedown "\h'\w'e'u'\v'-0.45m'\X'ps: exec gsave currentpoint \
2 copy translate -180.0000 rotate neg exch neg exch \
translate'e\X'ps: exec grestore'\h'-\w'e'u'\v'0.45m'
.char \(eu \*[eupsidedown]
.char \(EU \s+'\\n[.ps]/2'\(eu\s0
.\" ------------------------------------------------
.\" Underlined Middle Eastern Transcription Characters
.char \(dh \Z'dh'\v'.125m'\D'l \w'dh'u 0'\v'-.125m'
.char \(Dh \Z'Dh'\v'.125m'\D'l \w'Dh'u 0'\v'-.125m'
.char \(DH \Z'DH'\v'.125m'\D'l \w'DH'u 0'\v'-.125m'
.char \(dj \Z'dj'\v'.125m'\D'l \w'dj'u 0'\v'-.125m'
.char \(Dj \Z'Dj'\v'.125m'\D'l \w'Dj'u 0'\v'-.125m'
.char \(DJ \Z'DJ'\v'.125m'\D'l \w'DJ'u 0'\v'-.125m'
.char \(gh \Z'gh'\v'.125m'\D'l \w'gh'u 0'\v'-.125m'
.char \(Gh \Z'Gh'\v'.125m'\D'l \w'Gh'u 0'\v'-.125m'
.char \(GH \Z'GH'\v'.125m'\D'l \w'GH'u 0'\v'-.125m'
.char \(kh \Z'kh'\v'.125m'\D'l \w'kh'u 0'\v'-.125m'
.char \(Kh \Z'Kh'\v'.125m'\D'l \w'Kh'u 0'\v'-.125m'
.char \(KH \Z'KH'\v'.125m'\D'l \w'KH'u 0'\v'-.125m'
.char \(sh \Z'sh'\v'.125m'\D'l \w'sh'u 0'\v'-.125m'
.char \(Sh \Z'Sh'\v'.125m'\D'l \w'Sh'u 0'\v'-.125m'
.char \(SH \Z'SH'\v'.125m'\D'l \w'SH'u 0'\v'-.125m'
.char \(th \Z'th'\v'.125m'\D'l \w'th'u 0'\v'-.125m'
.char \(Th \Z'Th'\v'.125m'\D'l \w'Th'u 0'\v'-.125m'
.char \(TH \Z'TH'\v'.125m'\D'l \w'TH'u 0'\v'-.125m'
.char \(zh \Z'zh'\v'.125m'\D'l \w'zh'u 0'\v'-.125m'
.char \(Zh \Z'Zh'\v'.125m'\D'l \w'Zh'u 0'\v'-.125m'
.char \(ZH \Z'ZH'\v'.125m'\D'l \w'ZH'u 0'\v'-.125m'
.\" ------------------------------------------------
.\" Definition of codes for other accented characters
.\" Acute vowels
.char \(a' a\*'
.char \(A' A\*'
.char \(e' e\*'
.char \(E' E\*'
.char \(i' \\(.i\*'
.char \(I' I\*'
.char \(o' o\*'
.char \(O' O\*'
.char \(u' u\*'
.char \(U' U\*'
.char \(y' y\*'
.char \(Y' Y\*'
.\" Grave vowels
.char \(a` a\*`
.char \(A` A\*`
.char \(e` e\*`
.char \(E` E\*`
.char \(i` \\(.i\*`
.char \(I` I\*`
.char \(o` o\*`
.char \(O` O\*`
.char \(u` u\*`
.char \(U` U\*`
.char \(y` y\*`
.char \(Y` Y\*`
.\" Circumflexes
.char \(a^ a\*^
.char \(A^ A\*^
.char \(e^ e\*^
.char \(E^ E\*^
.char \(i^ \\(.i\*^
.char \(I^ I\*^
.char \(o^ o\*^
.char \(O^ O\*^
.char \(u^ u\*^
.char \(U^ U\*^
.char \(y^ y\*^
.char \(Y^ Y\*^
.\" Umlauts
.char \(a: a\*:
.char \(A: A\*:
.char \(e: e\*:
.char \(E: E\*:
.char \(i: \\(.i\*:
.char \(I: I\*:
.char \(o: o\*:
.char \(O: O\*:
.char \(u: u\*:
.char \(U: U\*:
.char \(y: y\*:
.char \(Y: Y\*:
.\" Slashed characters
.char \(o/ \(/o
.char \(O/ \(/O
.\" Macron-accents
.char \(a_ a\*_
.char \(A_ A\*_
.char \(e_ e\*_
.char \(E_ E\*_
.char \(i_ \(.i\*_
.char \(I_ I\*_
.char \(o_ o\*_
.char \(O_ O\*_
.char \(u_ u\*_
.char \(U_ U\*_
.\" Tildes
.char \(a~ a\*~
.char \(A~ A\*~
.char \(g~ g\*~
.char \(G~ G\*~
.char \(n~ n\*~
.char \(N~ N\*~
.char \(u~ u\*~
.char \(U~ U\*~
.\" Haceks
.char \(av a\*v
.char \(Av A\*v
.char \(cv c\*v
.char \(Cv C\*v
.char \(ev e\*v
.char \(Ev E\*v
.char \(rv r\*v
.char \(Rv R\*v
.char \(sv s\*v
.char \(Sv S\*v
.char \(uv u\*v
.char \(Uv U\*v
.char \(zv z\*v
.char \(Zv Z\*v
.\" Cedillas
.char \(c, c\*,
.char \(C, C\*,
.char \(s, s\*,
.char \(S, S\*,
.char \(t, t\*,
.char \(T, T\*,
.\" Overdots
.char \(c. c\*[dot]
.char \(C. C\*[dot]
.char \(e. e\*[dot]
.char \(E. E\*[dot]
.char \(G. G\*[dot]
.char \(I. I\*[dot]
.char \(g. g\*[dot]
.char \(z. z\*[dot]
.char \(Z. Z\*[dot]
.\" Underdots
.char \(d! d\*.
.char \(D! D\*.
.char \(h! h\*.
.char \(H! H\*.
.char \(k! k\*.
.char \(K! K\*.
.char \(s! s\*.
.char \(S! S\*.
.char \(t! t\*.
.char \(T! T\*.
.char \(z! z\*.
.char \(Z! Z\*.
.\" Acute Consonants
.char \(c' c\*'
.char \(C' C\*'
.char \(d' d\*'
.char \(D' D\*'
.char \(r' r\*'
.char \(R' R\*'
.char \(s' s\*'
.char \(S' S\*'
.char \(t' t\*'
.char \(T' T\*'
.\" Ring-above
.char \(io \(.i\*[ring]
.char \(Io I\*[ring]
.char \(uo u\*[ring]
.char \(Uo U\*[ring]
.\" Breves
.char \(au a\*[breve]
.char \(Au A\*[breve]
.char \(gu g\*[breve]
.char \(Gu G\*[breve]
.char \(uu u\*[breve]
.char \(Uu U\*[breve]
.\" Miscellaneous Accents
.\" Hungarian umlaut
.char \(o= o\*;
.char \(O= O\*;
.\" Turkish dotless i
.char \(i. \(.i
.\" ------------------------------------------------

--_=XFMail.1.3.p0.Linux:000601110441:2745=_--
End of MIME message


From groff-admin  Sun Jun  4 16:06:26 2000
Received: from garm.bart.nl (garm.bart.nl [194.158.170.13])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA22410
	for <groff@ffii.org>; Sun, 4 Jun 2000 16:06:25 +0200
Received: from daemon.ninth-circle.org (lucifer.is.an.elder.of.the.ninth-circle.org [195.38.216.226])
	by garm.bart.nl (8.10.1/8.10.1) with ESMTP id e54EHOO38717
	for <groff@ffii.org>; Sun, 4 Jun 2000 16:17:24 +0200 (CEST)
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id QAA45828
	for groff@ffii.org; Sun, 4 Jun 2000 16:17:23 +0200 (CEST)
	(envelope-from asmodai)
Date: Sun, 4 Jun 2000 16:17:23 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Groff Mailinglist <groff@ffii.org>
Message-ID: <20000604161723.K5228@daemon.ninth-circle.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="t0UkRYy7tHLRMCai"
Content-Disposition: inline
User-Agent: Mutt/1.2i
Organisation: Ninth-Circle Enterprises
Subject: [Groff] groff_mm.man patch
Status: O
Content-Length: 17412
Lines: 490

--t0UkRYy7tHLRMCai
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Find it attached.

This is a FreeBSD supplied patch by Kaneda Hiloshi
<vanitas@ma3.seikyou.ne.jp>

-- 
Jeroen Ruigrok vd Werven/Asmodai    asmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
You confuse me in a way that I've never known...

--t0UkRYy7tHLRMCai
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="groff.patch"

--- contrib/mm/groff_mm.man.orig	Sun Jun  4 16:10:09 2000
+++ contrib/mm/groff_mm.man	Sun Jun  4 16:13:05 2000
@@ -72,6 +72,7 @@
 a double-quote. (Strings are used in the text as \fB\e*[YYY]\fP.)
 .sp
 \fBSpecial formatting of number registers\fP
+.br
 A number register is printed with normal digits if no format has been
 given.
 Set the format with \fBaf\fP:
@@ -119,7 +120,7 @@
 .B "AF [name of firm]"
 Authors firm, should be called before \fBAU\fP, see also \fBCOVER\fP.
 .TP
-.B "AL [type [text-indent [1]]]]"
+.B "AL [type [text-indent [1]]]"
 Start autoincrement list. Items are numbered beginning on one.
 The \fItype\fP argument controls the type of numbers.
 .in +.5i
@@ -186,8 +187,8 @@
 .B "AU [name [initials [loc [dept [ext [room [arg [arg [arg]]]]]]]]]"
 Author information, specifies the author of the memo or paper, and
 will be printed on the cover sheet and on other similar places.
-\fBAU\fP must appear before \fBTL\fP. The author information
-can contain intials, location, department, telephone extension,
+\fBAU\fP must not appear before \fBTL\fP. The author information
+can contain initials, location, department, telephone extension,
 room number or name and up to three extra arguments.
 .TP
 .B "AV [name [1]]"
@@ -198,14 +199,14 @@
 .B "AVL [name]"
 Letter signature, generates a line with place for signature. 
 .TP
-.B "B [bold-text [prev-font-tex [bold...]]]"
-Begin boldface
+.B "B [bold-text [prev-font-text [bold...]]]"
+Begin boldface.
 No limit on the number of arguments.
 All arguments will be concatenated to one word, the first, third and so
 on will be printed in boldface.
 .TP
 .B B1
-Begin box (as the ms macro)
+Begin box (as the ms macro).
 Draws a box around the text. The text will be indented one character,
 and the right margin will be one character shorter.
 .TP
@@ -215,7 +216,7 @@
 .B BE
 End bottom block, see \fBBS\fP.
 .TP
-.B "BI [bold-text [italic-text [bold-text [...]]]"
+.B "BI [bold-text [italic-text [bold-text [...]]]]"
 Bold-italic.
 No limit on the number of arguments, see \fBB\fP.
 .TP
@@ -228,15 +229,15 @@
 A third argument will prohibit printing of a blank line before each
 item.
 .TP
-.B "BR [bold-text [roman-text [bold-text [...]]]"
+.B "BR [bold-text [roman-text [bold-text [...]]]]"
 Bold-roman.
 No limit on the number of arguments.
 .TP
 .B BS
-Bottom block start. Begins the definition of a text block wich is
+Bottom block start. Begins the definition of a text block which is
 printed at the bottom of each page. Block ends with \fBBE\fP.
 .TP
-.B BVL
+.B "BVL text-indent [mark-indent [1]]"
 Start of 
 broken variable-item list.
 Broken variable-item list has no fixed mark, it assumes that
@@ -299,7 +300,7 @@
 Displays are printed at the end of each section (when section-page
 numbering is active) or at the end of the document.
 .T2 1
-A new display will be printed on the current page is there is enough
+A new display will be printed on the current page if there is enough
 space, otherwise it will be printed at the end of the document.
 .T2 2
 One display will be printed at the top of each page or column
@@ -322,8 +323,6 @@
 after a dash. \fIText-indent\fP changes the default indentation
 of the list items set by
 number register \fBPi\fP.
-A third argument will prohibit printing of a blank line before each
-item.
 A second argument prevents the empty line between each list item
 to be printed. See \fBLI\fP.
 .TP
@@ -460,7 +459,7 @@
 List of Exhibits, default is \fILIST OF EXHIBITS\fP.
 The List of Exhibits will only be printed if number register \fBLx\fP
 is 1, default 1.
-The string \fBLiex\fP contains the word \fIExhibit\fP, wich
+The string \fBLiex\fP contains the word \fIExhibit\fP, which
 is printed before the number.
 If \fIrefname\fP is used, then the exhibit number is saved with
 \&\fB.SETR\fP, and can be retrieved with \fB.GETST\fP \fIrefname\fP.
@@ -499,7 +498,7 @@
 .sp
 .fi
 .DT
-Argument greater than or equal to 11 is considered as arg 0.
+Argument greater than 11 is considered as arg 0.
 Default for m@TMAC_M_PREFIX@m is 10.
 .TP
 .B FE
@@ -534,13 +533,13 @@
 .B "GETHN refname [varname]"
 Includes the headernumber where the corresponding \fBSETR\fP \fIrefname\fP
 was placed. Will be X.X.X. in pass 1. See \fBINITR\fP.
-If varname is used, \fBGETHN\fP sets the stringvariable \fIvarname\fP to the 
+If \fIvarname\fP is used, \fBGETHN\fP sets the stringvariable \fIvarname\fP to the 
 headernumber.
 .TP
 .B "GETPN refname [varname]"
 Includes the pagenumber where the corresponding \fBSETR\fP \fIrefname\fP
 was placed. Will be 9999 in pass 1. See \fBINITR\fP.
-If varname is used, \fBGETPN\fP sets the stringvariable \fIvarname\fP
+If \fIvarname\fP is used, \fBGETPN\fP sets the stringvariable \fIvarname\fP
 to the pagenumber.
 .TP
 .B "GETR refname"
@@ -600,6 +599,7 @@
 .br
 Indentation of the text after the heading is controlled by number
 register \fBHi\fP, default value 0.
+.sp
 \fBHi\fP
 .in +.5i
 .T2 0
@@ -620,7 +620,7 @@
 \fBFont control of the heading\fP
 .br
 The font of each heading level is controlled by string \fBHF\fP.
-It contains a fontnumber or fontnam for each level. Default
+It contains a fontnumber or fontname for each level. Default
 is \fB2\ 2\ 2\ 2\ 2\ 2\ 2\fP (all headings in italic).
 Could also be written as \fBI\ I\ I\ I\ I\ I\ I\fP.
 All omitted values are presumed to be a 1.
@@ -641,7 +641,7 @@
 the counter for each heading level.
 The values are printed using arabic numerals, this can be changed
 with the macro \fBHM\fP (see below).
-All marks ar concatenated before printing. To avoid this, set
+All marks are concatenated before printing. To avoid this, set
 number register \fBHt\fP to 1. That will only print the current
 heading counter at each heading.
 .sp
@@ -693,6 +693,7 @@
 might be used to change indentation.
 .sp
 \fBHZ\ \fP\fIdlevel\ rlevel\ heading-text\fP
+.br
 \fBHZ\fP is called after the printing of the heading, just before
 \fBH\fP or \fBHU\fP exits.
 Could be used to change the page header according to the section heading.
@@ -701,7 +702,7 @@
 Set hyphenation character.
 Default value is \e%.
 Resets to the default if called without argument.
-Hyphenation can be turned by setting number
+Hyphenation can be turned off by setting number
 register \fBHy\fP to 0 in the beginning of the file.
 .TP
 .B "HM [arg1 [arg2 [... [arg7]]]]"
@@ -747,7 +748,7 @@
 Called just after printing the header.
 See \fBH\fP.
 .TP
-.B "I [italic-text [prev-font-text [italic-text [...]]]"
+.B "I [italic-text [prev-font-text [italic-text [...]]]]"
 Italic.
 Changes the font to italic if called without arguments.
 With one argument it will set the word in italic.
@@ -755,15 +756,15 @@
 word in italic and the second in the previous font.
 There is no limit on the number of argument, all will be concatenated.
 .TP
-.B "IA [addressee-name [title]]
+.B "IA [addressee-name [title]]"
 Begins specification of the addressee and addressee's address in
 letter style.
 Several names can be specified with empty \fBIA\fP/\fBIE\fP-pairs, but
 only one address.
 See \fBLT\fP.
 .TP
-.B "IB [italic-text [bold-text [italic-text [...]]]"
-Italic-bold
+.B "IB [italic-text [bold-text [italic-text [...]]]]"
+Italic-bold.
 Even arguments is printed in italic, odd in boldface.
 See \fBI\fP.
 .TP
@@ -834,8 +835,8 @@
 adding \fB-rIso=1\fP on the command line.
 Reverts to old date format if argument is \fB0\fP.
 .TP
-.B "IR [italic-text [roman-text [italic-text [...]]]"
-Italic-roman
+.B "IR [italic-text [roman-text [italic-text [...]]]]"
+Italic-roman.
 Even arguments is printed in italic, odd in roman.
 See \fBI\fP.
 .TP
@@ -887,7 +888,7 @@
 \fBLB\fP itself will print \fILB-space\fP blank lines. Default is 0.
 .TP
 .B "LC [list-level]"
-List-status clear
+List-status clear.
 Terminates all current active lists down to \fIlist-level\fP, or 0
 if no argmuent is given. This is used by \fBH\fP to clear any
 active list.
@@ -898,7 +899,7 @@
 if an argument is given.
 .TP
 .B "LI [mark [1]]"
-List item precedes every item in a list. Without argument \fBLS\fP
+List item precedes every item in a list. Without argument \fBLI\fP
 will print the mark determined by the current list type. By giving
 \fBLI\fP one argument, it will use that as the mark instead.
 Two arguments to \fBLI\fP will make \fImark\fP a prefix to
@@ -949,7 +950,7 @@
 Style\fP
 .T2 BL
 Blocked. Date line, return address, writer's address and closing
-begins at the center of the line. All other lines begins at the left margin.
+begins at the center of the line. All other lines begin at the left margin.
 .T2 SB
 Semi-blocked. Same as blocked, except that the first line in every
 paragraph is indented five spaces.
@@ -957,7 +958,7 @@
 Full-blocked. All lines begin at the left margin.
 .T2 SP
 Simplified. Almost the same as the full-blocked style. Subject and
-the writer'sidentification is printed in all-capital.
+the writer's identification are printed in all-capital.
 .in
 .TP
 .B "LO type [arg]"
@@ -965,8 +966,8 @@
 This is a list of the standard options:
 .in +.5i
 .T2 CN
-Confidential notation. Prints \fBRESTRICTED\fP on the second line
-below the date line. Any argument replaces \fBRESTRICTED\fP.
+Confidential notation. Prints \fBCONFIDENTIAL\fP on the second line
+below the date line. Any argument replaces \fBCONFIDENTIAL\fP.
 See also string variable \fBLetCN\fP.
 .T2 RN
 Reference notation. Prints \fBIn reference to:\fP and the argument
@@ -1005,7 +1006,7 @@
 Memorandum type.
 The \fIarg\fP is part of a filename in \fI@TMAC_MDIR@/*.MT\fP.
 Memorandum type 0 thru 5 are supported, including \fI"string"\fP.
-\fIAddresse\fP just sets a variable, used in the AT&T macros.
+\fIAddressee\fP just sets a variable, used in the AT&T macros.
 .br
 \fBarg\fP
 .in +.5i
@@ -1033,11 +1034,11 @@
 .B "MULB cw1 space1 [cw2 space2 [cw3 ...]]"
 Begin a special multi-column mode. Every columns width must be specified.
 Also the space between the columns must be specified. The last column
-does not need any space-definition. MULB starts a diversion and MULE
+does not need any space-definition. \fBMULB\fP starts a diversion and \fBMULE\fP
 ends the diversion and prints the columns.
-The unit for width and space is 'n', but MULB accepts all 
+The unit for width and space is 'n', but \fBMULB\fP accepts all 
 normal unitspecifications like 'c' and 'i'.
-MULB operates in a separate environment.
+\fBMULB\fP operates in a separate environment.
 .TP
 .B "MULN"
 Begin the next column. This is the only way to switch column.
@@ -1046,7 +1047,7 @@
 End the multi-column mode and print the columns.
 .TP
 .B "nP [type]"
-Print numbered paragraph with header level two. Se \fB.P\fP.
+Print numbered paragraph with header level two. See \fB.P\fP.
 .TP
 .B "NCOL"
 Force printing to the next column, don't use this together with
@@ -1148,8 +1149,8 @@
 to change linelength, pagelength and pageoffset instead. Sorry.)
 .TP
 .B PGNH
-No header is printed on the next page. Used to get rid off
-the header in letters or other special texts
+No header is printed on the next page. Used to get rid of
+the header in letters or other special texts.
 This macro must be used before any text to inhibit the pageheader
 on the first page.
 .TP
@@ -1190,7 +1191,7 @@
 Roman.
 Return to roman font, see also \fBI\fP.
 .TP
-.B "RB [roman-text [bold-text [roman-text [...]]]"
+.B "RB [roman-text [bold-text [roman-text [...]]]]"
 Roman-bold.
 Even arguments is printed in roman, odd in boldface.
 See \fBI\fP.
@@ -1207,16 +1208,16 @@
 Reference end. Ends a reference definition and returns to normal
 processing. See \fBRS\fP.
 .TP
-.B "RI [roman-text [italic-text [roman-text [...]]]"
-Even arguments is printed in roman, odd in italic.
+.B "RI [roman-text [italic-text [roman-text [...]]]]"
+Even arguments are printed in roman, odd in italic.
 See \fBI\fP.
 .TP
 .B "RL [text-indent [1]]"
-Reference list start
+Reference list start.
 Begins a list where each item is preceded with a automatically
 incremented number between
 square brackets.
-\fIText-indent\fP changes the default indentation
+\fIText-indent\fP changes the default indentation.
 .TP
 .B "RP [arg1 [arg2]]"
 Produce reference page.
@@ -1224,7 +1225,7 @@
 document. It is not needed if \fBTC\fP is used to produce
 a table of content. The reference page will then be printed automatically.
 .sp
-The reference counter will not be resetted if \fIarg1\fP is 1.
+The reference counter will not be reset if \fIarg1\fP is 1.
 .sp
 \fIArg2\fP tells \fBRP\fP whether to eject a page or not.
 .br
@@ -1271,7 +1272,7 @@
 justification.
 .TP
 .B "SETR refname [string]"
-Remember the current header and page-number as refname.
+Remember the current header and page-number as \fIrefname\fP.
 Saves \fIstring\fP if \fIstring\fP is defined. \fIstring\fP is retrieved
 with \fB.GETST\fP.
 See \fBINITR\fP.
@@ -1281,10 +1282,11 @@
 The argument will be appended to the reference data, printed
 at either the first or last author. The reference data is the location,
 department and initials specified with \fB.AU\fP.
-It will be printed at the first author, otherwise at the last.
+It will be printed at the first author if the second argument is given,
+otherwise at the last.
 No reference data will be printed if the author(s) is specifed
 thru \fB.WA\fP/\fB.WE\fP.
-See \fBLetter internals\fP.
+See \fBINTERNALS\fP.
 .TP
 .B "SK [pages]"
 Skip pages.
@@ -1354,7 +1356,7 @@
 in each level.
 .sp
 All texts can be redefined, new stringvariables 
-\fILifg\fP, \fILitb\fP, \fILiex\fP, \fILiec\fP and \fILicon\fP contains
+\fILifg\fP, \fILitb\fP, \fILiex\fP, \fILiec\fP and \fILicon\fP contain
 "Figure", "TABLE", "Exhibit", "Equation" and "CONTENTS".
 These can be redefined to other languages.
 .TP
@@ -1367,10 +1369,10 @@
 be printed again if a page-break occurs.
 Argument \fIN\fP isn't implemented yet.
 .TP
-.B TL [charging-case number(s) [filing-case number(s)]
+.B TL [charging-case number(s) [filing-case number(s)]]
 Begin title of memorandum.
 All text up to the next \fBAU\fP is included in the title.
-\fICharging-case number\fP and \fIfiling-case\fP is saved
+\fICharging-case number\fP and \fIfiling-case\fP are saved
 for use in the front page processing.
 .TP
 .B TM [num1 [num2 [...]]]
@@ -1408,7 +1410,7 @@
 The pointsize can be changed with
 the second argument. By specifying the font-argument
 it is possible to use another font instead of courier.
-\fIflag\fP control several special features.
+\fIflag\fP controls several special features.
 It contains the sum of all wanted features.
 .in +.5i
 .T2 Value
@@ -1417,9 +1419,9 @@
 Disable the escape-character (\e). This is normally turned on during
 verbose output.
 .T2 2
-Add en empty line before the verbose text.
+Add an empty line before the verbose text.
 .T2 4
-Add en empty line after the verbose text.
+Add an empty line after the verbose text.
 .T2 8
 Print the verbose text with numbered lines. This adds four digitsized
 spaces in the beginning of each line. Finer control is available with
@@ -1444,7 +1446,7 @@
 .B "VM [top [bottom]]"
 Vertical margin.
 .TP
-.B "WA [writer-name [title]]
+.B "WA [writer-name [title]]"
 Begins specification of the writer and writer's address.
 Several names can be specified with empty \fBWA\fP/\fBWE\fP-pairs, but
 only one address.
@@ -1538,10 +1540,10 @@
 Contains "Yours very truly,", used in \fB.FC\fP.
 .TP
 .B Letapp
-Contains "APPROVED:", used in \fB.AV.\fP.
+Contains "APPROVED:", used in \fB.AV\fP.
 .TP
 .B Letdate
-Contains "Date", used in \fB.AV.\fP.
+Contains "Date", used in \fB.AV\fP.
 .TP
 .B LetCN
 Contains "CONFIDENTIAL", used in \fB.LO CN\fP.
@@ -1753,7 +1755,6 @@
 Default 99.
 .TP
 .B Lsp
-.TP
 The size of an empty line. Normally 0.5v, but it is 1v 
 if \fBn\fP is set (\fB.nroff\fP).
 .TP
@@ -1771,7 +1772,7 @@
 4\ ==\ page header is removed on the first page.
 .br
 5\ ==\ "section-page" and "section-figure" numbering enabled.
-Se also the number-register Sectf and Sectp.
+See also the number-register Sectf and Sectp.
 .TP
 .B Np
 Numbered paragraphs, default 0.
@@ -1822,11 +1823,11 @@
 .TP
 .B Sectf
 Flag controlling "section-figures". A non-zero value enables this.
-Se also register N.
+See also register N.
 .TP
 .B Sectp
 Flag controlling "section-page-numbers". A non-zero value enables this.
-Se also register N.
+See also register N.
 .TP
 .B Si
 Display indent, default 5.
@@ -1842,7 +1843,7 @@
 the letter type. The name of the submacro has the letter type
 as suffix. It is therefore possible to define other letter types, either
 in the national macro-file, or as local additions.
-\&\fB.LT\fP will set the number variables \fBPt\fP and \fBPi\fP to 5 and 0.
+\&\fB.LT\fP will set the number variables \fBPt\fP and \fBPi\fP to 0 and 5.
 The following strings and macros must be defined for a new letter type:
 .TP
 \fBlet@init_\fP\fItype\fP

--t0UkRYy7tHLRMCai--


From groff-admin  Sun Jun  4 23:46:36 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id XAA25273
	for <groff@ffii.org>; Sun, 4 Jun 2000 23:46:36 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sun, 4 Jun 2000 23:57:43 +0200
Received: from rigel.univie.ac.at (dial-143182.HRZ.Uni-Dortmund.DE [129.217.143.182])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id XAA03588;
	Sun, 4 Jun 2000 23:57:41 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id VAA02258;
	Sun, 4 Jun 2000 21:42:08 GMT
Date: Sun, 04 Jun 2000 21:42:08 +0000 (GMT)
Message-Id: <20000604.214208.35472571.sx0005@gnu.org>
To: asmodai@wxs.nl, vanitas@ma3.seikyou.ne.jp
Cc: groff@ffii.org
Subject: Re: [Groff] groff_mm.man patch
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000604161723.K5228@daemon.ninth-circle.org>
References: <20000604161723.K5228@daemon.ninth-circle.org>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 258
Lines: 14

From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Subject: [Groff] groff_mm.man patch
Date: Sun, 4 Jun 2000 16:17:23 +0200

> Find it attached.
> 
> This is a FreeBSD supplied patch by Kaneda Hiloshi
> <vanitas@ma3.seikyou.ne.jp>

Applied, thanks.


    Werner


From groff-admin  Mon Jun  5 19:20:19 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id TAA14675
	for <groff@ffii.org>; Mon, 5 Jun 2000 19:20:17 +0200
Received: from datenbus.mayn.de (root@datenbus.mayn.de [194.145.150.20])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id NAA29609
	for <groff@gnu.org>; Mon, 5 Jun 2000 13:31:26 -0400
Received: (from bwarken@localhost)
	by datenbus.mayn.de (8.9.3/8.9.3) id TAA12441
	for groff@gnu.org; Mon, 5 Jun 2000 19:31:27 +0200
Date: Mon, 5 Jun 2000 19:31:27 +0200
From: Bernd Warken <bwarken@mayn.de>
To: groff@gnu.org
Message-ID: <20000605193127.A12410@mayn.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
Subject: [Groff] \rk, \lk
Status: O
Content-Length: 266
Lines: 8

The brace building characters \(rk and \(lk do not have suitable Unicode
characters so far.  But Unicode 3.1 will newly integrate 25 `Compatibility
brace pieces'.  These will be placed under 239B..23B3.  I do not know
more details.

Bernd Warken <bwarken@mayn.de>



From groff-admin  Tue Jun  6 16:31:00 2000
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [12.13.247.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA05350
	for <groff@ffii.org>; Tue, 6 Jun 2000 16:30:59 +0200
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id JAA21100
	for <groff@ffii.org>; Tue, 6 Jun 2000 09:42:07 -0500 (CDT)
Received: from stl-hub-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.9.2/8.9.2) with ESMTP id JAA08450
	for <groff@ffii.org>; Tue, 6 Jun 2000 09:42:01 -0500 (CDT)
Received: from xch-wchbh-02.ks.boeing.com by stl-hub-01.boeing.com with ESMTP for groff@ffii.org; Tue, 6 Jun 2000 09:41:47 -0500
Received: by xch-wchbh-02.ks.boeing.com with Internet Mail Service (5.5.2650.21)
	id <MJTAYV33>; Tue, 6 Jun 2000 09:41:46 -0500
Message-Id: <6C7E2A10BB01D111929500400B406DDE057EBE40@xch-wch-02.ks.boeing.com>
From: "Bates, Rod" <Rod.Bates@Wichita.BOEING.com>
To: "'groff@ffii.org'" <groff@ffii.org>
Date: Tue, 6 Jun 2000 09:41:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Subject: [Groff] RE: help with umlauts
Status: O
Content-Length: 170
Lines: 6

Thanks for the help with umlauts.  

In my case, I only had 4 occurrences, so it was easy
to just manually edit them to \(:U, etc., once I knew
what to change them to. 


From groff-admin  Tue Jun  6 22:50:52 2000
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id WAA08902
	for <groff@ffii.org>; Tue, 6 Jun 2000 22:50:51 +0200
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA03327
	for <groff@ffii.org>; Tue, 6 Jun 2000 17:02:03 -0400 (EDT)
Received: from sol.eng.fore.com (sol.pit.comms.marconi.com [169.144.155.73])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA20250
	for <groff@ffii.org>; Tue, 6 Jun 2000 17:02:04 -0400 (EDT)
Received: from pss-pc.eng.fore.com (root@pss-pc [169.144.32.90])
	by sol.eng.fore.com (8.8.8/8.8.8) with ESMTP id RAA01300
	for <groff@ffii.org>; Tue, 6 Jun 2000 17:02:04 -0400 (EDT)
Received: from pss-pc.eng.fore.com (IDENT:pss@localhost [127.0.0.1])
	by pss-pc.eng.fore.com (8.9.3/8.8.7) with ESMTP id RAA28821
	for <groff@ffii.org>; Tue, 6 Jun 2000 17:02:40 -0400
Message-Id: <200006062102.RAA28821@pss-pc.eng.fore.com>
To: groff@ffii.org
Reply-to: pragnesh.sampat@marconi.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 06 Jun 2000 17:02:39 -0400
From: Pragnesh Sampat <pss@fore.com>
Subject: [Groff] ms versus mm macros
Status: O
Content-Length: 913
Lines: 42

Hello,

I am new to groff.  I have an internal document here in ms macros, but I am
wondering if I should use the mm macros instead.  It seems to have nicer
features, at least for code displays (VERBON/VERBOFF) and seems to be a
superset of ms macros.

For example, I am currently using pipeline:

% cat file | pic | tbl | eqn | groff -ms -U > file.ps

(The -U is for .PSPIC macro to include a logo.)

For code displays, I am using the following macros (I realize that I could use
the DS, DE commands):

.\" troff macros for code start/stop
.de CS
.sp
.ps -2
.ft CW
.nf
..

.de CE
.fi
.ft
.ps +2
.sp
..

The output is ok, but I would like to have more control like line numbers,
etc. without having to do it in troff myself.  So I am thinking maybe using mm
is better.  I am also curious about what are your experiences with either of
these.

I am using Redhat Linux 6.2, groff version 1.15.

Thanks,

-Pragnesh


From groff-admin  Wed Jun  7 21:11:55 2000
Received: from baoule.ath.cx (daemon@ppp-44-32-169.wmar.club-internet.fr [213.44.32.169])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id VAA32375
	for <groff@ffii.org>; Wed, 7 Jun 2000 21:11:51 +0200
Received: (from gael@localhost)
	by baoule.ath.cx (8.10.0/8.10.0) id e57JMrQ18544
	for groff@ffii.org; Wed, 7 Jun 2000 21:22:53 +0200
Date: Wed, 7 Jun 2000 21:22:53 +0200
From: Gael Queri <gqueri@mail.dotcom.fr>
To: groff@ffii.org
Message-ID: <20000607212253.A17444@baoule.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.11i
X-Operating-System: Linux 2.2.15
Subject: [Groff] [PATCH] ISO_8859-15/latin9 support via a new -Tlatin9
Status: O
Content-Length: 16270
Lines: 716

Hello,
here is a patch which (tries to) add support for the latin9 charset
which is intended to replace latin1.
It was necessary because -Tlatin1 uses the acute accent as \' which was
replaced by Zcaron in latin9, so we need to return back to '.

This also adds support for the new characters included in latin9:
Zcaron, zcaron, Scaron, scaron, OE, oe, Euro and Ydieresis.

I had to add two more troff codes for Euro and Ydieresis:  \(Eu and \(:Y
Eu is the ISO mnemonic code for the Euro sign
and :Y is the (inverted) mnemonic code as found in the other
groff codes.
(well, actually :Y was already in the PS fonts)

I also modified the utf8 font to take into account Eu and :Y

For devps and devdvi it seems that we'll have to add some Euro
fonts, like the ones from Adobe. I have also some METAFONT sources
for Euro fonts, but I don't know which one is the most widely used.

Also I don't know what to do with the X fonts, because these seem
to be coded in 8859-1, and I don't want to add 4 more devices for
8859-15 X.

And the html uses the SGML entities, which should theoritically
be right but I heard that most of the overbloated browsers in
use (for example Netscape) automatically switch to 8859-1 when they see
them. But lynx works well with them so I will maybe add them.

Finally there are lbp and lj4 which already support :Y but I
don't know how to add Euro support on these.

The diff is against groff-1.16. I couldn't grab the CVS version
due to my slow connection, but I checked with the current diff and
it applies fine with it.

Please tell me what do you think about it...
Regards, gael

Here's the diff (times are POSIX UTC)

diff -urN groff-1.16/Makefile.in groff-1.16.gael/Makefile.in
--- groff-1.16/Makefile.in	Sun May 14 23:47:25 2000
+++ groff-1.16.gael/Makefile.in	Wed Jun  7 13:35:14 2000
@@ -48,8 +48,8 @@
 # DEVICE is the default device.
 DEVICE=ps
 
-# TTYDEVDIRS is either `font/devascii font/devlatin1 font/devutf8' (for
-# ASCII) or `font/devcp1047' (for EBCDIC).
+# TTYDEVDIRS is either `font/devascii font/devlatin1 font/devlatin9
+# font/devutf8' (for ASCII) or `font/devcp1047' (for EBCDIC).
 TTYDEVDIRS=@TTYDEVDIRS@
 
 # PSPRINT is the command to use for printing a PostScript file,
@@ -341,6 +341,7 @@
 ALLTTYDEVDIRS=\
   font/devascii \
   font/devlatin1 \
+  font/devlatin9 \
   font/devutf8 \
   font/devcp1047
 OTHERDIRS=\
diff -urN groff-1.16/aclocal.m4 groff-1.16.gael/aclocal.m4
--- groff-1.16/aclocal.m4	Tue May  2 00:39:37 2000
+++ groff-1.16.gael/aclocal.m4	Wed Jun  7 13:32:54 2000
@@ -455,7 +455,7 @@
  AC_MSG_RESULT(yes)
  AC_DEFINE(IS_EBCDIC_HOST),
 groff_cv_ebcdic="no"
- TTYDEVDIRS="font/devascii font/devlatin1 font/devutf8"
+ TTYDEVDIRS="font/devascii font/devlatin1 font/devlatin9 font/devutf8"
  AC_MSG_RESULT(no))
 AC_SUBST(TTYDEVDIRS)])dnl
 dnl
diff -urN groff-1.16/configure groff-1.16.gael/configure
--- groff-1.16/configure	Tue May  2 00:39:37 2000
+++ groff-1.16.gael/configure	Wed Jun  7 13:33:51 2000
@@ -1021,7 +1021,7 @@
   cat conftest.$ac_ext >&5
   rm -rf conftest*
   groff_cv_ebcdic="no"
- TTYDEVDIRS="font/devascii font/devlatin1 font/devutf8"
+ TTYDEVDIRS="font/devascii font/devlatin1 font/devlatin9 font/devutf8"
  echo "$ac_t""no" 1>&6
 fi
 rm -f conftest*
diff -urN groff-1.16/font/devlatin9/DESC.proto groff-1.16.gael/font/devlatin9/DESC.proto
--- groff-1.16/font/devlatin9/DESC.proto	Thu Jan  1 00:00:00 1970
+++ groff-1.16.gael/font/devlatin9/DESC.proto	Sun Feb  6 09:35:23 2000
@@ -0,0 +1,8 @@
+res 240
+hor 24
+vert 40
+unitwidth 10
+sizes 10 0
+fonts 4 R I B BI
+tcommand
+postpro grotty
diff -urN groff-1.16/font/devlatin9/Makefile.sub groff-1.16.gael/font/devlatin9/Makefile.sub
--- groff-1.16/font/devlatin9/Makefile.sub	Thu Jan  1 00:00:00 1970
+++ groff-1.16.gael/font/devlatin9/Makefile.sub	Wed Jun  7 13:31:44 2000
@@ -0,0 +1,32 @@
+DEV=latin9
+FONTS=R I B BI
+DEVFILES=$(FONTS) DESC
+CLEANADD=$(FONTS) DESC
+
+RES=240
+CPI=10
+LPI=6
+
+$(FONTS): R.proto
+	@echo Making $@
+	@-rm -f $@
+	@(charwidth=`expr $(RES) / $(CPI)` ; \
+ 	 sed -e "s/^name [A-Z]*$$/name $@/" \
+	     -e "s/^\\([^	]*\\)	[0-9]+	/\\1	$$charwidth	/" \
+	     -e "s/^spacewidth [0-9]+$$/spacewidth $$charwidth/" \
+	     -e "s/^internalname .*$$/internalname $@/" \
+	     -e "/^internalname/s/BI/3/" \
+	     -e "/^internalname/s/B/2/" \
+	     -e "/^internalname/s/I/1/" \
+	     -e "/^internalname .*[^ 0-9]/d" \
+	     $(srcdir)/R.proto >$@)
+
+DESC: DESC.proto
+	@echo Making $@
+	@-rm -f $@
+	@sed -e "s/^res .*$$/res $(RES)/" \
+	    -e "s/^hor .*$$/hor `expr $(RES) / $(CPI)`/" \
+	    -e "s/^vert .*$$/vert `expr $(RES) / $(LPI)`/" \
+	    -e "s/^fonts .*$$/fonts `set $(FONTS); echo $$#` $(FONTS)/" \
+	    $(srcdir)/DESC.proto >$@
+
diff -urN groff-1.16/font/devlatin9/R.proto groff-1.16.gael/font/devlatin9/R.proto
--- groff-1.16/font/devlatin9/R.proto	Thu Jan  1 00:00:00 1970
+++ groff-1.16.gael/font/devlatin9/R.proto	Wed Jun  7 16:53:18 2000
@@ -0,0 +1,358 @@
+name R
+internalname 0
+spacewidth 24
+charset
+!	24	0	0041
+"	24	0	0042
+dq	"
+lq	"
+rq	"
+#	24	0	0043
+sh	"
+$	24	0	0044
+Do	"
+%	24	0	0045
+&	24	0	0046
+'	24	0	0047
+aa	"
+fm	"
+aq	"
+cq	"
+(	24	0	0050
+)	24	0	0051
+*	24	0	0052
+**	"
++	24	0	0053
+pl	"
+,	24	0	0054
+\-	24	0	0055
+mi	"
+-	"
+hy	"
+en	"
+.	24	0	0056
+/	24	0	0057
+sl	"
+f/	"
+0	24	0	0060
+1	24	0	0061
+2	24	0	0062
+3	24	0	0063
+4	24	0	0064
+5	24	0	0065
+6	24	0	0066
+7	24	0	0067
+8	24	0	0070
+9	24	0	0071
+:	24	0	0072
+;	24	0	0073
+<	24	0	0074
+la	"
+fo	"
+=	24	0	0075
+eq	"
+>	24	0	0076
+ra	"
+fc	"
+?	24	0	0077
+@	24	0	0100
+at	"
+A	24	0	0101
+*A	"
+B	24	0	0102
+*B	"
+C	24	0	0103
+D	24	0	0104
+E	24	0	0105
+*E	"
+F	24	0	0106
+G	24	0	0107
+H	24	0	0110
+*Y	"
+I	24	0	0111
+*I	"
+J	24	0	0112
+K	24	0	0113
+*K	"
+L	24	0	0114
+M	24	0	0115
+*M	"
+N	24	0	0116
+*N	"
+O	24	0	0117
+ci	"
+*O	"
+P	24	0	0120
+*R	"
+Q	24	0	0121
+R	24	0	0122
+S	24	0	0123
+T	24	0	0124
+*T	"
+U	24	0	0125
+V	24	0	0126
+W	24	0	0127
+X	24	0	0130
+*X	"
+Y	24	0	0131
+*U	"
+Z	24	0	0132
+*Z	"
+[	24	0	0133
+lB	"
+\	24	0	0134
+rs	"
+]	24	0	0135
+rB	"
+a^	24	0	0136
+^	"
+ha	"
+_	24	0	0137
+ru	"
+ul	"
+`	24	0	0140
+oq	"
+ga	"
+a	24	0	0141
+b	24	0	0142
+c	24	0	0143
+d	24	0	0144
+e	24	0	0145
+f	24	0	0146
+g	24	0	0147
+h	24	0	0150
+i	24	0	0151
+.i	"
+j	24	0	0152
+k	24	0	0153
+l	24	0	0154
+m	24	0	0155
+n	24	0	0156
+o	24	0	0157
+*o	"
+p	24	0	0160
+q	24	0	0161
+r	24	0	0162
+s	24	0	0163
+t	24	0	0164
+u	24	0	0165
+v	24	0	0166
+w	24	0	0167
+x	24	0	0170
+y	24	0	0171
+z	24	0	0172
+lC	24	0	0173
+{	"
+ba	24	0	0174
+or	"
+bv	"
+br	"
+|	"
+lb	"
+lc	"
+lf	"
+lk	"
+lt	"
+rb	"
+rc	"
+rf	"
+rk	"
+rt	"
+rC	24	0	0175
+}	"
+a~	24	0	0176
+~	"
+ap	"
+ti	"
+r!	24	0	0241
+char161	"
+ct	24	0	0242
+char162	"
+Po	24	0	0243
+char163	"
+Eu	24	0	0244
+char164	"
+Ye	24	0	0245
+char165	"
+vS	24	0	0246
+char166	"
+sc	24	0	0247
+char167	"
+vS	24	0	0250
+char168	"
+co	24	0	0251
+char169	"
+Of	24	0	0252
+char170	"
+Fo	24	0	0253
+char171	"
+no	24	0	0254
+char172	"
+shc	24	0	0255
+char173	"
+rg	24	0	0256
+char174	"
+a-	24	0	0257
+char175	"
+de	24	0	0260
+char176	"
+ao	"
++-	24	0	0261
+char177	"
+S2	24	0	0262
+char178	"
+S3	24	0	0263
+char179	"
+vZ	24	0	0264
+char180	"
+*m	24	0	0265
+char181	"
+ps	24	0	0266
+char182	"
+pc	24	0	0267
+md	"
+char183	"
+vz	24	0	0270
+char184	"
+S1	24	0	0271
+char185	"
+Om	24	0	0272
+char186	"
+Fc	24	0	0273
+char187	"
+OE	24	0	0274
+char188	"
+oe	24	0	0275
+char189	"
+:Y	24	0	0276
+char190	"
+r?	24	0	0277
+char191	"
+`A	24	0	0300
+char192	"
+'A	24	0	0301
+char193	"
+^A	24	0	0302
+char194	"
+~A	24	0	0303
+char195	"
+:A	24	0	0304
+char196	"
+oA	24	0	0305
+char197	"
+AE	24	0	0306
+char198	"
+,C	24	0	0307
+char199	"
+`E	24	0	0310
+char200	"
+'E	24	0	0311
+char201	"
+^E	24	0	0312
+char202	"
+:E	24	0	0313
+char203	"
+`I	24	0	0314
+char204	"
+'I	24	0	0315
+char205	"
+^I	24	0	0316
+char206	"
+:I	24	0	0317
+char207	"
+-D	24	0	0320
+char208	"
+~N	24	0	0321
+char209	"
+`O	24	0	0322
+char210	"
+'O	24	0	0323
+char211	"
+^O	24	0	0324
+char212	"
+~O	24	0	0325
+char213	"
+:O	24	0	0326
+char214	"
+mu	24	0	0327
+char215	"
+/O	24	0	0330
+char216	"
+`U	24	0	0331
+char217	"
+'U	24	0	0332
+char218	"
+^U	24	0	0333
+char219	"
+:U	24	0	0334
+char220	"
+'Y	24	0	0335
+char221	"
+TP	24	0	0336
+char222	"
+ss	24	0	0337
+char223	"
+`a	24	0	0340
+char224	"
+'a	24	0	0341
+char225	"
+^a	24	0	0342
+char226	"
+~a	24	0	0343
+char227	"
+:a	24	0	0344
+char228	"
+oa	24	0	0345
+char229	"
+ae	24	0	0346
+char230	"
+,c	24	0	0347
+char231	"
+`e	24	0	0350
+char232	"
+'e	24	0	0351
+char233	"
+^e	24	0	0352
+char234	"
+:e	24	0	0353
+char235	"
+`i	24	0	0354
+char236	"
+'i	24	0	0355
+char237	"
+^i	24	0	0356
+char238	"
+:i	24	0	0357
+char239	"
+Sd	24	0	0360
+char240	"
+~n	24	0	0361
+char241	"
+`o	24	0	0362
+char242	"
+'o	24	0	0363
+char243	"
+^o	24	0	0364
+char244	"
+~o	24	0	0365
+char245	"
+:o	24	0	0366
+char246	"
+di	24	0	0367
+char247	"
+/o	24	0	0370
+char248	"
+`u	24	0	0371
+char249	"
+'u	24	0	0372
+char250	"
+^u	24	0	0373
+char251	"
+:u	24	0	0374
+char252	"
+'y	24	0	0375
+char253	"
+Tp	24	0	0376
+char254	"
+:y	24	0	0377
+char255	"
diff -urN groff-1.16/font/devutf8/R.proto groff-1.16.gael/font/devutf8/R.proto
--- groff-1.16/font/devutf8/R.proto	Fri May 19 05:06:00 2000
+++ groff-1.16.gael/font/devutf8/R.proto	Wed Jun  7 16:09:53 2000
@@ -309,6 +309,7 @@
 /l	24	0	0x0142
 OE	24	0	0x0152
 oe	24	0	0x0153
+:Y	24	0	0x0178
 Fn	24	0	0x0192
 ah	24	0	0x02C7
 ab	24	0	0x02D8
@@ -390,6 +391,7 @@
 fc	24	0	0x203A
 rn	24	0	0x203E
 f/	24	0	0x2044
+Eu	24	0	0x20AC
 Im	24	0	0x2111
 wp	24	0	0x2118
 Re	24	0	0x211C
diff -urN groff-1.16/tmac/Makefile.sub groff-1.16.gael/tmac/Makefile.sub
--- groff-1.16/tmac/Makefile.sub	Mon May  1 23:47:49 2000
+++ groff-1.16.gael/tmac/Makefile.sub	Wed Jun  7 13:26:51 2000
@@ -12,8 +12,8 @@
 NORMALFILES=\
   tmac.mandoc tmac.andoc tmac.pic tmac.ps tmac.psnew tmac.psold tmac.pspic \
   tmac.psatk tmac.dvi tmac.tty tmac.tty-char tmac.X tmac.Xps tmac.latin1 \
-  tmac.lj4 eqnrc troffrc troffrc-end tmac.safer tmac.html tmac.markup \
-  tmac.arkup tmac.a4 tmac.trace tmac.me tmac.mdoc
+  tmac.latin9 tmac.lj4 eqnrc troffrc troffrc-end tmac.safer tmac.html \
+  tmac.markup tmac.arkup tmac.a4 tmac.trace tmac.me tmac.mdoc
 SPECIALFILES=tmac.an tmac.s tmac.man tmac.ms
 STRIPFILES=tmac.e tmac.doc tmac.doc.old
 MDOCFILES=doc-common doc-ditroff doc-nroff doc-syms
diff -urN groff-1.16/tmac/eqnrc groff-1.16.gael/tmac/eqnrc
--- groff-1.16/tmac/eqnrc	Sun Apr 30 05:12:51 2000
+++ groff-1.16.gael/tmac/eqnrc	Wed Jun  7 13:21:48 2000
@@ -51,6 +51,7 @@
 
 ifdef ascii ! define n %1% !
 ifdef latin1 ! define n %1% !
+ifdef latin9 ! define n %1% !
 ifdef utf8 ! define n %1% !
 ifdef cp1047 ! define n %1% !
 ifdef n !
diff -urN groff-1.16/tmac/tmac.X groff-1.16.gael/tmac/tmac.X
--- groff-1.16/tmac/tmac.X	Sat Apr 22 13:17:46 2000
+++ groff-1.16.gael/tmac/tmac.X	Wed Jun  7 13:22:48 2000
@@ -37,6 +37,7 @@
 .if !c\(ah .char \(ah \v'-.55m'\s[\En[.s]/2u]v\s0\v'.55m'
 .if !c\(ao .char \(ao \v'-.55m'\s[\En[.s]*6u/10u]\D'c .25m'\s0\v'.55m'
 .if !c\(ho .char \(ho \s[\En[.s]/2u]\v'.4m'c\v'-.4m'\s0
+.if !c\(Eu .char \(Eu Eu
 .if !c\(lh .tr \(lh\(lA
 .if !c\(rh .tr \(rh\(rA
 .if !c\(bq .tr \(bq,
diff -urN groff-1.16/tmac/tmac.dvi groff-1.16.gael/tmac/tmac.dvi
--- groff-1.16/tmac/tmac.dvi	Tue May 23 22:08:24 2000
+++ groff-1.16.gael/tmac/tmac.dvi	Wed Jun  7 13:23:08 2000
@@ -137,6 +137,7 @@
 .dvi-achar \(:u \(ad u u
 .dvi-achar \('y \' y y
 .dvi-achar \(:y \(ad y y
+.dvi-achar \(:Y \(ad Y y
 .if !c\(,C .char \(,C \o'\(acC'
 .hcode \(,Cc
 .if !c\(,c .char \(,c \o'\(acc'
diff -urN groff-1.16/tmac/tmac.latin9 groff-1.16.gael/tmac/tmac.latin9
--- groff-1.16/tmac/tmac.latin9	Thu Jan  1 00:00:00 1970
+++ groff-1.16.gael/tmac/tmac.latin9	Wed Jun  7 13:25:54 2000
@@ -0,0 +1,101 @@
+.nr _C \n(.C
+.cp 0
+.de latin9-tr
+.if c\\$2 .if !c\\$1 .tr \\$1\\$2
+..
+.latin9-tr \[char161] \(r!
+.latin9-tr \[char162] \(ct
+.latin9-tr \[char163] \(Po
+.latin9-tr \[char164] \(Eu
+.latin9-tr \[char165] \(Ye
+.latin9-tr \[char166] \(vS
+.latin9-tr \[char167] \(sc
+.latin9-tr \[char168] \(vs
+.latin9-tr \[char169] \(co
+.latin9-tr \[char170] \(Of
+.latin9-tr \[char171] \(Fo
+.latin9-tr \[char172] \(no
+.latin9-tr \[char173] \[shc]
+.latin9-tr \[char174] \(rg
+.latin9-tr \[char175] \(a-
+.latin9-tr \[char176] \(de
+.latin9-tr \[char177] \(+-
+.latin9-tr \[char178] \(S2
+.latin9-tr \[char179] \(S3
+.latin9-tr \[char180] \(vZ
+.latin9-tr \[char181] \(*m
+.latin9-tr \[char182] \(ps
+.latin9-tr \[char183] \(pc
+.latin9-tr \[char184] \(vz
+.latin9-tr \[char185] \(S1
+.latin9-tr \[char186] \(Om
+.latin9-tr \[char187] \(Fc
+.latin9-tr \[char188] \(OE
+.latin9-tr \[char189] \(oe
+.latin9-tr \[char190] \(:Y
+.latin9-tr \[char191] \(r?
+.latin9-tr \[char192] \(`A
+.latin9-tr \[char193] \('A
+.latin9-tr \[char194] \(^A
+.latin9-tr \[char195] \(~A
+.latin9-tr \[char196] \(:A
+.latin9-tr \[char197] \(oA
+.latin9-tr \[char198] \(AE
+.latin9-tr \[char199] \(,C
+.latin9-tr \[char200] \(`E
+.latin9-tr \[char201] \('E
+.latin9-tr \[char202] \(^E
+.latin9-tr \[char203] \(:E
+.latin9-tr \[char204] \(`I
+.latin9-tr \[char205] \('I
+.latin9-tr \[char206] \(^I
+.latin9-tr \[char207] \(:I
+.latin9-tr \[char208] \(-D
+.latin9-tr \[char209] \(~N
+.latin9-tr \[char210] \(`O
+.latin9-tr \[char211] \('O
+.latin9-tr \[char212] \(^O
+.latin9-tr \[char213] \(~O
+.latin9-tr \[char214] \(:O
+.latin9-tr \[char215] \(mu
+.latin9-tr \[char216] \(/O
+.latin9-tr \[char217] \(`U
+.latin9-tr \[char218] \('U
+.latin9-tr \[char219] \(^U
+.latin9-tr \[char220] \(:U
+.latin9-tr \[char221] \('Y
+.latin9-tr \[char222] \(TP
+.latin9-tr \[char223] \(ss
+.latin9-tr \[char224] \(`a
+.latin9-tr \[char225] \('a
+.latin9-tr \[char226] \(^a
+.latin9-tr \[char227] \(~a
+.latin9-tr \[char228] \(:a
+.latin9-tr \[char229] \(oa
+.latin9-tr \[char230] \(ae
+.latin9-tr \[char231] \(,c
+.latin9-tr \[char232] \(`e
+.latin9-tr \[char233] \('e
+.latin9-tr \[char234] \(^e
+.latin9-tr \[char235] \(:e
+.latin9-tr \[char236] \(`i
+.latin9-tr \[char237] \('i
+.latin9-tr \[char238] \(^i
+.latin9-tr \[char239] \(:i
+.latin9-tr \[char240] \(Sd
+.latin9-tr \[char241] \(~n
+.latin9-tr \[char242] \(`o
+.latin9-tr \[char243] \('o
+.latin9-tr \[char244] \(^o
+.latin9-tr \[char245] \(~o
+.latin9-tr \[char246] \(:o
+.latin9-tr \[char247] \(di
+.latin9-tr \[char248] \(/o
+.latin9-tr \[char249] \(`u
+.latin9-tr \[char250] \('u
+.latin9-tr \[char251] \(^u
+.latin9-tr \[char252] \(:u
+.latin9-tr \[char253] \('y
+.latin9-tr \[char254] \(Tp
+.latin9-tr \[char255] \(:y
+.cp \n(_C
diff -urN groff-1.16/tmac/tmac.ps groff-1.16.gael/tmac/tmac.ps
--- groff-1.16/tmac/tmac.ps	Sun Feb  6 09:39:55 2000
+++ groff-1.16.gael/tmac/tmac.ps	Wed Jun  7 13:23:24 2000
@@ -46,6 +46,7 @@
 .if !c\[ij] .char \[ij] ij
 .if !c\[IJ] .char \[IJ] IJ
 .if !c\[tm] .char \[tm] \s-3\v'-.3m'TM\v'+.3m'\s+3
+.if !c\[Eu] .char \[Eu] Eu
 .\" pic tests this register to see whether it should use \X'ps:...'
 .nr 0p 1
 .cp \n(_C
diff -urN groff-1.16/tmac/tmac.tty-char groff-1.16.gael/tmac/tmac.tty-char
--- groff-1.16/tmac/tmac.tty-char	Sun Apr 30 05:12:51 2000
+++ groff-1.16.gael/tmac/tmac.tty-char	Wed Jun  7 15:59:16 2000
@@ -1,8 +1,8 @@
 .\" This file defines standard troff characters and some groff characters for
-.\" use with -Tascii, -Tlatin1, -Tutf8, and -Tcp1047.
+.\" use with -Tascii, -Tlatin1, -Tlatin9, -Tutf8, and -Tcp1047.
 .\"
 .\" These definitions are chosen so that, as far as possible, they:
-.\" - work with all of -Tascii, -Tlatin1, -Tutf8, and -Tcp1047.
+.\" - work with all of -Tascii, -Tlatin1, -Tlatin9, -Tutf8, and -Tcp1047.
 .\" - work on devices that display only the last overstruck character
 .\"   as well as on devices that support overstriking
 .\" - represent the character's graphical shape (not its meaning)
@@ -196,7 +196,9 @@
 .tty-char \(Tp \zpb
 .tty-char \(:y \z"y
 .\"tty-char \(:y \ij
+.\"tty-char \(:Y \IJ
 .tty-char \[arrowvertex] |
+.tty-char \(Eu E
 .cp \n(_C
 .if !'\*(.T'cp1047' \
 .	do mso tmac.latin1
diff -urN groff-1.16/tmac/troffrc groff-1.16.gael/tmac/troffrc
--- groff-1.16/tmac/troffrc	Sun Apr 30 05:12:51 2000
+++ groff-1.16.gael/tmac/troffrc	Wed Jun  7 13:24:36 2000
@@ -12,6 +12,7 @@
 .do ds troffrc!X100-12 tmac.X
 .do ds troffrc!ascii tmac.tty
 .do ds troffrc!latin1 tmac.tty
+.do ds troffrc!latin9 tmac.tty
 .do ds troffrc!utf8 tmac.tty
 .do ds troffrc!cp1047 tmac.tty
 .do ds troffrc!lj4 tmac.lj4


From groff-admin  Fri Jun  9 09:42:07 2000
Received: from ns.omnitel.it (ns.omnitel.it [194.20.65.11])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with SMTP id JAA12231
	for <Groff@ffii.org>; Fri, 9 Jun 2000 09:42:03 +0200
Received: by ns.omnitel.it; (5.65v4.0/1.3/10May95) id AA09565 for Groff@ffii.org; Fri, 9 Jun 2000 09:52:55 +0200
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Date: Fri, 9 Jun 2000 09:48:15 +0200 (CEST)
From: Nicola Bernardini <nicb@axnet.it>
To: Groff@ffii.org
Message-Id: <Pine.LNX.4.10.10006090944000.303-100000@ax-nicb.axnet.it>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Groff] [PATCH] compiling error on grolbp with latest CVS update
Status: O
Content-Length: 2131
Lines: 40

Last night I updated my groff sandbox from CVS and trying to compile
it I got this compiling error:

make[2]: Entering directory `/usr/local/user/nicb/tr/src/groff-CVS/src/devices/grolbp'
g++ -mcpu=k6 -I. -I/usr/local/user/nicb/tr/src/groff-CVS/src/devices/grolbp -I/usr/local/user/nicb/tr/src/groff-CVS/src/include -I/usr/local/user/nicb/tr/src/groff-CVS/src/include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRINGS_H=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARES_PCLOSE=1 -DRET_TYPE_SRAND_IS_VOID=1 -DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_UNISTD_H=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_FMOD=1 -DHAVE_STRTOL=1 -DHAVE_GETCWD=1 -DHAVE_STRERROR=1 -DHAVE_PUTENV=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 -DSYS_SIGLIST_DECLARED=1  -g -O2  -c lbp.cc
lbp.cc:37: declaration of C function `int strncasecmp(const char *, const char *, int)' conflicts with
/usr/include/strings.h:52: previous declaration `int strncasecmp(const char *, const char *, unsigned int)' here
make[2]: *** [lbp.o] Error 1
make[2]: Leaving directory `/usr/local/user/nicb/tr/src/groff-CVS/src/devices/grolbp'
make[1]: *** [src/devices/grolbp] Error 2
make[1]: Leaving directory `/usr/local/user/nicb/tr/src/groff-CVS'
make: *** [all] Error 2

With all evidence, there's a typo in the lbp.cc file. Here's a patch for
it:

-8<---------------------------------------------------------------------
--- src/devices/grolbp/lbp.cc.orig	Fri Jun  9 09:38:24 2000
+++ src/devices/grolbp/lbp.cc	Fri Jun  9 09:38:27 2000
@@ -31,7 +31,7 @@
 #include "lbp.h"
 #include "charset.h"
 
-#ifdef HAVE_STRNCASECMP
+#ifndef HAVE_STRNCASECMP
 extern "C" {
   // SunOS's string.h fails to declare this.
   int strncasecmp(const char *, const char *, int);
-8<---------------------------------------------------------------------

hope this helps.

nicb

+----------------------+
|Nicola Bernardini     |
|E-mail: nicb@axnet.it |
+----------------------+



From groff-admin  Sat Jun 10 12:35:27 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id MAA05809
	for <Groff@ffii.org>; Sat, 10 Jun 2000 12:35:27 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 10 Jun 2000 12:46:57 +0200
Received: from rigel.univie.ac.at (dial-143130.HRZ.Uni-Dortmund.DE [129.217.143.130])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id MAA08729;
	Sat, 10 Jun 2000 12:46:55 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id KAA10493;
	Sat, 10 Jun 2000 10:33:03 GMT
Date: Sat, 10 Jun 2000 10:33:03 +0000 (GMT)
Message-Id: <20000610.103303.78073704.sx0005@gnu.org>
To: nicb@axnet.it
Cc: Groff@ffii.org, <kst@sdsc.edu>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
 update
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <Pine.LNX.4.10.10006090944000.303-100000@ax-nicb.axnet.it>
References: <Pine.LNX.4.10.10006090944000.303-100000@ax-nicb.axnet.it>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 807
Lines: 26

> lbp.cc:37: declaration of C function `int strncasecmp(const char *,
>            const char *, int)' conflicts with 
> /usr/include/strings.h:52: previous declaration `int
>            strncasecmp(const char *, const char *, unsigned int)' here 
> 
> With all evidence, there's a typo in the lbp.cc file. Here's a patch for
> it:
> 
> -#ifdef HAVE_STRNCASECMP
> +#ifndef HAVE_STRNCASECMP
>  extern "C" {
>    // SunOS's string.h fails to declare this.
>    int strncasecmp(const char *, const char *, int);

This is the wrong patch.  The very problem is that certain old
versions of Sun's compiler actually has strncasecmp() but no prototype
for it.

The right fix would be to use `size_t' instead of `int'.  Ken, can you
please check whether `size_t' works?

Or is there a better solution?


    Werner


From groff-admin  Sat Jun 10 15:28:29 2000
Received: from baoule.ath.cx (daemon@ppp-44-70-204.wly.club-internet.fr [213.44.70.204])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA07084
	for <Groff@ffii.org>; Sat, 10 Jun 2000 15:28:27 +0200
Received: (from gael@localhost)
	by baoule.ath.cx (8.10.0/8.10.0) id e5ADdja16118
	for Groff@ffii.org; Sat, 10 Jun 2000 15:39:45 +0200
Date: Sat, 10 Jun 2000 15:39:45 +0200
From: Gael Queri <gqueri@mail.dotcom.fr>
To: Groff@ffii.org
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS update
Message-ID: <20000610153945.A16079@baoule.ath.cx>
References: <Pine.LNX.4.10.10006090944000.303-100000@ax-nicb.axnet.it> <20000610.103303.78073704.sx0005@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.11i
In-Reply-To: <20000610.103303.78073704.sx0005@gnu.org>; from sx0005@sx2.HRZ.Uni-Dortmund.DE on Sat, Jun 10, 2000 at 10:32:41AM +0000
X-Operating-System: Linux 2.2.16
Status: O
Content-Length: 7024
Lines: 204

On Sat, Jun 10, 2000 at 10:32:41AM +0000, Werner LEMBERG wrote:
> This is the wrong patch.  The very problem is that certain old
> versions of Sun's compiler actually has strncasecmp() but no prototype
> for it.
> 
> The right fix would be to use `size_t' instead of `int'.  Ken, can you
> please check whether `size_t' works?
Well, there will certainly be an OS where the prototype doesn't work.
> 
> Or is there a better solution?
Yes, I think it's better to use autoconf to wheck whether
strncasecmp is declared, like the tests for putenv(), hypot() etc
So I took from GNU bfd a generic test for that and I replaced
the previous checks.

	Regards, gael

diff -x Makefile -x configure -x Imakefile -ur groff-1.16/Makefile.in groff-1.16.gael/Makefile.in
--- groff-1.16/Makefile.in	Sat Jun 10 15:26:43 2000
+++ groff-1.16.gael/Makefile.in	Sat Jun 10 15:22:59 2000
@@ -170,14 +170,16 @@
 # -DHAVE_STRDUP			if you have strdup()
 # -DHAVE_STRSEP			if you have strsep()
 # -DHAVE_STRCASECMP		if you have strcasecmp()
-# -DSTDLIB_H_DECLARES_PUTENV	if your C++ <stdlib.h> declares putenv()
-# -DSTDIO_H_DECLARES_POPEN	if your C++ <stdio.h> declares popen()
-# -DSTDIO_H_DECLARES_PCLOSE	if your C++ <stdio.h> declares pclose()
+# -DNEED_DECLARATION_HYPOT	if your C++ <math.h> doesn't declare hypot()
+# -DNEED_DECLARATION_PUTENV	if your C++ <stdlib.h> doesn't declare putenv()
+# -DNEED_DECLARATION_POPEN	if your C++ <stdio.h> doesn't declare popen()
+# -DNEED_DECLARATION_PCLOSE	if your C++ <stdio.h> doesn't declare pclose()
+# -DNEED_DECLARATION_STRNCASECMP
+#			if your C++ <string.h> doesn't declare strncasecmp()
 # -DRET_TYPE_SRAND_IS_VOID	if your srand() returns void or int
 # -DHAVE_SYS_NERR		if you have sysnerr in <errno.h> or <stdio.h>
 # -DHAVE_SYS_ERRLIST		if you have sys_errlist in <errno.h> or
 #				<stdio.h>
-# -DMATH_H_DECLARES_HYPOT	if you have hypot() in <math.h>
 # -DTRADITIONAL_CPP		if your C++ compiler uses a traditional
 #				(Reiser) preprocessor
 # -DLONG_FOR_TIME_T		if localtime() takes a long * not a time_t *
diff -x Makefile -x configure -x Imakefile -ur groff-1.16/aclocal.m4 groff-1.16.gael/aclocal.m4
--- groff-1.16/aclocal.m4	Sat Jun 10 15:26:43 2000
+++ groff-1.16.gael/aclocal.m4	Sat Jun 10 15:16:10 2000
@@ -517,3 +517,37 @@
 fi
 rm -f conftest.defs
 ])
+
+dnl See whether we need a declaration for a function.
+dnl stolen from GNU bfd
+AC_DEFUN(GROFF_NEED_DECLARATION,
+[AC_MSG_CHECKING([whether $1 must be declared])
+AC_LANG_SAVE
+AC_LANG_CPLUSPLUS
+AC_CACHE_VAL(groff_cv_decl_needed_$1,
+[AC_TRY_COMPILE([
+#include <stdio.h>
+#ifdef HAVE_STRING_H
+#include <string.h>
+#else
+#ifdef HAVE_STRINGS_H
+#include <strings.h>
+#endif
+#endif
+#ifdef HAVE_STDLIB_H
+#include <stdlib.h>
+#endif
+#ifdef HAVE_UNISTD_H
+#include <unistd.h>
+#endif
+#ifdef HAVE_MATH_H
+#include <math.h>
+#endif],
+[char *(*pfn) = (char *(*)) $1],
+groff_cv_decl_needed_$1=no, groff_cv_decl_needed_$1=yes)])
+AC_MSG_RESULT($groff_cv_decl_needed_$1)
+if test $groff_cv_decl_needed_$1 = yes; then
+  AC_DEFINE([NEED_DECLARATION_]translit($1, [a-z], [A-Z]))
+fi
+AC_LANG_RESTORE])dnl
+
diff -x Makefile -x configure -x Imakefile -ur groff-1.16/configure.in groff-1.16.gael/configure.in
--- groff-1.16/configure.in	Sat Jun 10 15:26:43 2000
+++ groff-1.16.gael/configure.in	Sat Jun 10 14:27:35 2000
@@ -18,16 +18,18 @@
 GROFF_CSH_HACK(SH_SCRIPT_SED_CMD='1s/.*/:/', SH_SCRIPT_SED_CMD='')
 AC_SUBST(SH_SCRIPT_SED_CMD)
 dnl checks for headers
-AC_CHECK_HEADERS(unistd.h dirent.h limits.h sys/dir.h stdlib.h strings.h)
+AC_CHECK_HEADERS(stdlib.h unistd.h dirent.h limits.h sys/dir.h stdlib.h \
+		 string.h strings.h math.h)
 GROFF_ISC_SYSV3
 GROFF_POSIX
-GROFF_PUTENV
-GROFF_POPEN
-GROFF_PCLOSE
 GROFF_SRAND
+GROFF_NEED_DECLARATION(hypot)
+GROFF_NEED_DECLARATION(popen)
+GROFF_NEED_DECLARATION(pclose)
+GROFF_NEED_DECLARATION(putenv)
+GROFF_NEED_DECLARATION(strncasecmp)
 GROFF_SYS_NERR
 GROFF_SYS_ERRLIST
-GROFF_HYPOT
 GROFF_OSFCN_H
 GROFF_LIMITS_H
 dnl checks for typedefs
diff -x Makefile -x configure -x Imakefile -ur groff-1.16/src/devices/grolbp/lbp.cc groff-1.16.gael/src/devices/grolbp/lbp.cc
--- groff-1.16/src/devices/grolbp/lbp.cc	Sat Jun 10 15:26:44 2000
+++ groff-1.16.gael/src/devices/grolbp/lbp.cc	Sat Jun 10 15:32:43 2000
@@ -32,11 +32,13 @@
 #include "charset.h"
 
 #ifdef HAVE_STRNCASECMP
+#ifdef NEED_DECLARATION_STRNCASECMP
 extern "C" {
   // SunOS's string.h fails to declare this.
   int strncasecmp(const char *, const char *, int);
 }
-#endif
+#endif /* NEED_DECLARATION_STRNCASECMP */
+#endif /* HAVE_STRNCASECMP */
 
 static short int papersize = -1,  // papersize
 		 orientation = -1 , // orientation
diff -x Makefile -x configure -x Imakefile -ur groff-1.16/src/include/lib.h groff-1.16.gael/src/include/lib.h
--- groff-1.16/src/include/lib.h	Sat Jun 10 15:26:44 2000
+++ groff-1.16.gael/src/include/lib.h	Sat Jun 10 15:19:19 2000
@@ -36,17 +36,17 @@
 FILE *xtmpfile(char **namep=0, char *postfix=0, int do_unlink=1);
 char *xtmptemplate(char *extension=0);
 
-#ifndef STDIO_H_DECLARES_POPEN
+#ifdef NEED_DECLARATION_POPEN
 
 extern "C" { FILE *popen(const char *, const char *); }
 
-#endif /* not STDIO_H_DECLARES_POPEN */
+#endif /* NEED_DECLARATION_POPEN */
 
-#ifndef STDIO_H_DECLARES_PCLOSE
+#ifdef NEED_DECLARATION_PCLOSE
 
 extern "C" { int pclose (FILE *); }
 
-#endif /* not STDIO_H_DECLARES_PCLOSE */
+#endif /* NEED_DECLARATION_PCLOSE */
 
 int interpret_lf_args(const char *p);
 
diff -x Makefile -x configure -x Imakefile -ur groff-1.16/src/preproc/grn/hgraph.cc groff-1.16.gael/src/preproc/grn/hgraph.cc
--- groff-1.16/src/preproc/grn/hgraph.cc	Sat May 13 01:27:29 2000
+++ groff-1.16.gael/src/preproc/grn/hgraph.cc	Sat Jun 10 15:33:07 2000
@@ -6,11 +6,11 @@
 
 #include "gprint.h"
 
-#ifndef MATH_H_DECLARES_HYPOT
+#ifdef NEED_DECLARATION_HYPOT
 extern "C" {
   double hypot(double, double);
 }
-#endif
+#endif /* NEED_DECLARATION_HYPOT */
 
 #define MAXVECT	40
 #define MAXPOINTS	200
diff -x Makefile -x configure -x Imakefile -ur groff-1.16/src/preproc/pic/pic.h groff-1.16.gael/src/preproc/pic/pic.h
--- groff-1.16/src/preproc/pic/pic.h	Sun Feb  6 10:38:00 2000
+++ groff-1.16.gael/src/preproc/pic/pic.h	Sat Jun 10 15:33:31 2000
@@ -24,11 +24,11 @@
 #include <stdlib.h>
 #include <errno.h>
 
-#ifndef MATH_H_DECLARES_HYPOT
+#ifdef NEED_DECLARATION_HYPOT
 extern "C" {
   double hypot(double, double);
 }
-#endif
+#endif /* NEED_DECLARATION_HYPOT */
 
 #include "assert.h"
 #include "cset.h"
diff -x Makefile -x configure -x Imakefile -ur groff-1.16/src/roff/groff/groff.cc groff-1.16.gael/src/roff/groff/groff.cc
--- groff-1.16/src/roff/groff/groff.cc	Tue May  2 01:47:24 2000
+++ groff-1.16.gael/src/roff/groff/groff.cc	Sat Jun 10 14:32:14 2000
@@ -44,11 +44,11 @@
 // specified
 #define XREG ".X"
 
-#ifndef STDLIB_H_DECLARES_PUTENV
+#ifdef NEED_DECLARATION_PUTENV
 extern "C" {
   int putenv(const char *);
 }
-#endif /* not STDLIB_H_DECLARES_PUTENV */
+#endif /* NEED_DECLARATION_PUTENV */
 
 const int SOELIM_INDEX = 0;
 const int REFER_INDEX = SOELIM_INDEX + 1;


From groff-admin  Sat Jun 10 21:26:15 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id VAA10004
	for <Groff@ffii.org>; Sat, 10 Jun 2000 21:26:15 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sat, 10 Jun 2000 21:37:52 +0200
Received: from rigel.univie.ac.at (dial-143159.HRZ.Uni-Dortmund.DE [129.217.143.159])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id VAA13940;
	Sat, 10 Jun 2000 21:37:41 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id PAA11665;
	Sat, 10 Jun 2000 15:32:35 GMT
Date: Sat, 10 Jun 2000 15:32:35 +0000 (GMT)
Message-Id: <20000610.153235.64840345.sx0005@gnu.org>
To: gqueri@mail.dotcom.fr
Cc: Groff@ffii.org
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
 update
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000610153945.A16079@baoule.ath.cx>
References: <Pine.LNX.4.10.10006090944000.303-100000@ax-nicb.axnet.it>
	<20000610.103303.78073704.sx0005@gnu.org>
	<20000610153945.A16079@baoule.ath.cx>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 343
Lines: 13

> > Or is there a better solution?

> Yes, I think it's better to use autoconf to wheck whether
> strncasecmp is declared, like the tests for putenv(), hypot() etc So
> I took from GNU bfd a generic test for that and I replaced the
> previous checks.

Thanks a lot!  This is indeed a better solution.  I'll include your
changes.


    Werner


From groff-admin  Sat Jun 10 21:41:19 2000
Received: from baoule.ath.cx (daemon@ppp-44-30-160.wmar.club-internet.fr [213.44.30.160])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id VAA10124
	for <Groff@ffii.org>; Sat, 10 Jun 2000 21:41:17 +0200
Received: (from gael@localhost)
	by baoule.ath.cx (8.10.0/8.10.0) id e5AJqZs01619
	for Groff@ffii.org; Sat, 10 Jun 2000 21:52:35 +0200
Date: Sat, 10 Jun 2000 21:52:34 +0200
From: Gael Queri <gqueri@mail.dotcom.fr>
To: Groff@ffii.org
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS update
Message-ID: <20000610215234.A1581@baoule.ath.cx>
References: <Pine.LNX.4.10.10006090944000.303-100000@ax-nicb.axnet.it> <20000610.103303.78073704.sx0005@gnu.org> <20000610153945.A16079@baoule.ath.cx> <20000610.153235.64840345.sx0005@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.11i
In-Reply-To: <20000610.153235.64840345.sx0005@gnu.org>; from sx0005@sx2.HRZ.Uni-Dortmund.DE on Sat, Jun 10, 2000 at 03:32:13PM +0000
X-Operating-System: Linux 2.2.16
Status: O
Content-Length: 717
Lines: 20

On Sat, Jun 10, 2000 at 03:32:13PM +0000, Werner LEMBERG wrote:
> > > Or is there a better solution?
> > Yes, I think it's better to use autoconf to wheck whether
> > strncasecmp is declared, like the tests for putenv(), hypot() etc So
> > I took from GNU bfd a generic test for that and I replaced the
> > previous checks.
> 
> Thanks a lot!  This is indeed a better solution.  I'll include your
> changes.

Sure, this is cleaner... Also I made a stupid mistake: I added
stdlib.h while it was already there...

Regards, gael

PS: what do you think about my latin9 patch? is 8-bit char encoding
considered obsolete?
There is another solution: simply not using the acute in latin1...
It wasn't intended for quotes...


From groff-admin  Sun Jun 11 05:06:53 2000
Received: from postal.sdsc.edu (IDENT:Hdk3RrhdBslmBEJeDSGwRdQtOyVEN9jE@postal.sdsc.edu [132.249.40.114])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id FAA13851
	for <Groff@ffii.org>; Sun, 11 Jun 2000 05:06:52 +0200
Received: from elmak (elmak.sdsc.edu [132.249.52.146])
	by postal.sdsc.edu (8.9.3/8.9.3/SDSCserver-16) with SMTP id UAA14155;
	Sat, 10 Jun 2000 20:18:32 -0700 (PDT)
From: Keith Thompson <kst@SDSC.EDU>
Received: by elmak (SMI-8.6/1.11-client)
	id UAA21118; Sat, 10 Jun 2000 20:18:31 -0700
Message-Id: <200006110318.UAA21118@elmak>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
To: wl@gnu.org
Date: Sat, 10 Jun 2000 20:18:31 -0700 (PDT)
Cc: nicb@axnet.it, Groff@ffii.org, kst@SDSC.EDU
In-Reply-To: <20000610.103303.78073704.sx0005@gnu.org> from "Werner LEMBERG" at Jun 10, 2000 10:33:03 AM
Organization: San Diego Supercomputer Center
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 2538
Lines: 78

> > lbp.cc:37: declaration of C function `int strncasecmp(const char *,
> >            const char *, int)' conflicts with 
> > /usr/include/strings.h:52: previous declaration `int
> >            strncasecmp(const char *, const char *, unsigned int)' here 
> > 
> > With all evidence, there's a typo in the lbp.cc file. Here's a patch for
> > it:
> > 
> > -#ifdef HAVE_STRNCASECMP
> > +#ifndef HAVE_STRNCASECMP
> >  extern "C" {
> >    // SunOS's string.h fails to declare this.
> >    int strncasecmp(const char *, const char *, int);
> 
> This is the wrong patch.  The very problem is that certain old
> versions of Sun's compiler actually has strncasecmp() but no prototype
> for it.
> 
> The right fix would be to use `size_t' instead of `int'.  Ken, can you
> please check whether `size_t' works?
> 
> Or is there a better solution?
> 
> 
>     Werner

s/Ken/Keith/

Ok, I changed "int" to "size_t" (for the third argument, not the
return type!), and it compiled, linked, and installed without error.

Which is more correct is an interesting question.  There's no
declaration for strncasecmp() in any system header under SunOS 4.1.3.
The man page says:

     int strncasecmp(s1, s2, n)
     char *s1, *s2;
     int n;

Oddly, <sys/stdtypes.h> declares:

    typedef int             size_t;         /* ??? */

(Yes, the ??? is there in the header.)

On SunOS 5.7, the third argument is size_t, which is either unsigned
long or unsigned int:

    #ifndef _SIZE_T
    #define _SIZE_T
    #if defined(_LP64) || defined(_I32LPx)
    typedef unsigned long   size_t;         /* size of something in bytes */
    #else
    typedef unsigned int    size_t;         /* (historical version) */
    #endif
    #endif  /* !_SIZE_T */

In lbp.cc, there's only one call to strncasecmp(), and its third
argument is the literal 4; since all the types in question ([un]signed
(int|long) and size_t) are 32 bits in SunOS 4.1.3, it should work
either way.

BTW, I don't have a Canon CAPSL laser printer, so I can't test
the code.

I'd guess that any system that has a strncasecmp function but doesn't
bother to declare it in a header is likely to use int rather than
size_t for the third argument -- but it's also likely to make int and
size_t the same size.  I'd be inclined to use size_t, and configure
it if a system shows up where size_t doesn't work.

(BTW, strncasecmp is not defined in ISO C; is it POSIX?)

-- 
Keith Thompson, San Diego Supercomputer Center  kst@sdsc.edu
<http://www.sdsc.edu/~kst/>
Welcome to the last year of the 20th century.


From groff-admin  Sun Jun 11 08:24:37 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id IAA14522
	for <Groff@ffii.org>; Sun, 11 Jun 2000 08:24:37 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Sun, 11 Jun 2000 08:36:14 +0200
Received: from rigel.univie.ac.at (dial-143130.HRZ.Uni-Dortmund.DE [129.217.143.130])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id IAA21035;
	Sun, 11 Jun 2000 08:36:12 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id GAA16171;
	Sun, 11 Jun 2000 06:21:35 GMT
Date: Sun, 11 Jun 2000 06:21:35 +0000 (GMT)
Message-Id: <20000611.062135.105169863.sx0005@gnu.org>
To: gqueri@mail.dotcom.fr
Cc: Groff@ffii.org
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
 update
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000610215234.A1581@baoule.ath.cx>
References: <20000610153945.A16079@baoule.ath.cx>
	<20000610.153235.64840345.sx0005@gnu.org>
	<20000610215234.A1581@baoule.ath.cx>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 1159
Lines: 33

> PS: what do you think about my latin9 patch? is 8-bit char encoding
> considered obsolete?

Your patch is OK, but I don't know how to proceed.  Creating more and
more directories for the various encodings + devices isn't a valid
solution, so I will postpone your changes.

A guy is trying to make Unicode input possible (BTW, any results
meanwhile?), and I will try to remove input encoding stuff from the
font description files.

I'll probably introduce a kind of `fonts.dir' file to register the
(font) encoding of the fonts for a particular device to have the
following chain:

  groff glyph -> lookup the device's fonts.dir
              -> search a font which covers the input encoding
              -> check font shape, slant, etc.
              -> if no results, check the special fonts

For example, having `devX100' and `latin2', let's assume that the font
for shape `Roman bold italic' is called TBI2.  In fonts.dir, this
would be mapped to `TBI', and everything works as expected.

Such an approach of course assumes that a particular font covers a
given input encoding, but anything else would be much more
complicated.

Comments?


    Werner


From groff-admin  Mon Jun 12 07:54:57 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id HAA07267
	for <Groff@ffii.org>; Mon, 12 Jun 2000 07:54:57 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 12 Jun 2000 08:06:32 +0200
Received: from rigel.univie.ac.at (dial-143160.HRZ.Uni-Dortmund.DE [129.217.143.160])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id IAA08604;
	Mon, 12 Jun 2000 08:06:29 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id UAA16486;
	Sun, 11 Jun 2000 20:02:43 GMT
Date: Sun, 11 Jun 2000 20:02:43 +0000 (GMT)
Message-Id: <20000611.200243.06276429.sx0005@gnu.org>
To: kst@SDSC.EDU
Cc: nicb@axnet.it, Groff@ffii.org
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <200006110318.UAA21118@elmak>
References: <20000610.103303.78073704.sx0005@gnu.org>
	<200006110318.UAA21118@elmak>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 562
Lines: 24

> > The right fix would be to use `size_t' instead of `int'.  Ken, can you
> > please check whether `size_t' works?

> s/Ken/Keith/

Oops :-)

> Ok, I changed "int" to "size_t" (for the third argument, not the
> return type!), and it compiled, linked, and installed without error.

May I ask you to test

  ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz

This should work even better since it provides only declarations if
there aren't declarations in the header files.

> (BTW, strncasecmp is not defined in ISO C; is it POSIX?)

BSD 4.3


    Werner


From groff-admin  Mon Jun 12 09:48:08 2000
Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA08034
	for <groff@ffii.org>; Mon, 12 Jun 2000 09:48:08 +0200
Received: from beta by smtp.hccnet.nl
	via uds175-117.dial.hccnet.nl [193.173.117.175] with SMTP for <groff@ffii.org>
	id KAA06254 (8.8.5/1.13); Mon, 12 Jun 2000 10:00:08 +0200 (MET DST)
Message-ID: <002401bfd444$39e46fc0$af75adc1@beta>
From: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
To: <groff@ffii.org>
Date: Mon, 12 Jun 2000 10:00:05 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
Disposition-Notification-To: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Subject: [Groff] groff ms-windows
Status: O
Content-Length: 223
Lines: 9

An MS-Windows version of Groff 1.16,  with Grap 1.05 included, and compiled with the
Cygwin-library, has been put at

 ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Zeelenberg_Kees/B20/index.html

 Kees




From groff-admin  Mon Jun 12 13:12:22 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id NAA10622
	for <groff@ffii.org>; Mon, 12 Jun 2000 13:12:21 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 12 Jun 2000 13:24:21 +0200
Received: from rigel.univie.ac.at (dial-143168.HRZ.Uni-Dortmund.DE [129.217.143.168])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id NAA14209;
	Mon, 12 Jun 2000 13:24:19 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id KAA16732;
	Mon, 12 Jun 2000 10:25:23 GMT
Date: Mon, 12 Jun 2000 10:25:23 +0000 (GMT)
Message-Id: <20000612.102523.13024436.sx0005@gnu.org>
To: c.zeelenberg@hccnet.nl
Cc: groff@ffii.org
Subject: Re: [Groff] groff ms-windows
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <002401bfd444$39e46fc0$af75adc1@beta>
References: <002401bfd444$39e46fc0$af75adc1@beta>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 501
Lines: 16

This is good news!  Is this a permanent location?  If yes, I'll add it
to the MORE.STUFF file.

> An MS-Windows version of Groff 1.16, with Grap 1.05 included, and
> compiled with the Cygwin-library, has been put at

   ftp://ftp.franken.de/pub/win32/develop/gnuwin32/
         cygwin/porters/Zeelenberg_Kees/B20/index.html
                ^^^^^^^

Seeing the word `porters' I assume that certain fixes were necessary.
Can you send it to me so that I can decide whether to integrate it?


    Werner


From groff-admin  Mon Jun 12 16:37:48 2000
Received: from postal.sdsc.edu (IDENT:/GtL2pcUmHsGUzGIgiOKhJLVLLP6NmD0@postal.sdsc.edu [132.249.40.114])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA13286
	for <Groff@ffii.org>; Mon, 12 Jun 2000 16:37:47 +0200
Received: from elmak (elmak.sdsc.edu [132.249.52.146])
	by postal.sdsc.edu (8.9.3/8.9.3/SDSCserver-16) with SMTP id HAA27751;
	Mon, 12 Jun 2000 07:49:45 -0700 (PDT)
From: Keith Thompson <kst@SDSC.EDU>
Received: by elmak (SMI-8.6/1.11-client)
	id HAA00117; Mon, 12 Jun 2000 07:49:44 -0700
Message-Id: <200006121449.HAA00117@elmak>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
To: wl@gnu.org
Date: Mon, 12 Jun 2000 07:49:44 -0700 (PDT)
Cc: kst@SDSC.EDU, nicb@axnet.it, Groff@ffii.org
In-Reply-To: <20000611.200243.06276429.sx0005@gnu.org> from "Werner LEMBERG" at Jun 11, 2000 08:02:43 PM
Organization: San Diego Supercomputer Center
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 589
Lines: 16

> May I ask you to test
> 
>   ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz
> 
> This should work even better since it provides only declarations if
> there aren't declarations in the header files.

It compiles without error on both SunOS 4.1.3 and SunOS 2.5.1, using
gcc 2.95.2 in both cases.  The single test case I tried (formatting
a man page to PostScript) worked correctly on both systems.

-- 
Keith Thompson, San Diego Supercomputer Center  kst@sdsc.edu
<http://www.sdsc.edu/~kst/>  Office: 858-822-0853  Fax: 858-534-5077
Welcome to the last year of the 20th century.


From groff-admin  Mon Jun 12 19:33:46 2000
Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id TAA14639
	for <groff@ffii.org>; Mon, 12 Jun 2000 19:33:46 +0200
Received: from beta by smtp.hccnet.nl
	via uds165-117.dial.hccnet.nl [193.173.117.165] with SMTP
	id TAA15109 (8.8.5/1.13); Mon, 12 Jun 2000 19:45:40 +0200 (MET DST)
Message-ID: <003201bfd496$06849b80$a575adc1@beta>
From: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
To: "Werner LEMBERG" <wl@gnu.org>
Cc: <groff@ffii.org>
References: <002401bfd444$39e46fc0$af75adc1@beta> <20000612.102523.13024436.sx0005@gnu.org>
Subject: Re: [Groff] groff ms-windows
Date: Mon, 12 Jun 2000 19:44:34 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
Disposition-Notification-To: "Kees Zeelenberg" <c.zeelenberg@hccnet.nl>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Status: O
Content-Length: 1200
Lines: 39

Yes, ftp.franken.de is a permanent location for Cygwin software.
And there were no fixes necessary! (apart from setting, in the makefile, the prefix to
Progra~1\Groff and the paper size to A4, and adding the suffix .exe to the executables). In
fact, with Cygwin, many Gnu-software compiles without any changeS.

Kees


----- Oorspronkelijk bericht -----
Van: "Werner LEMBERG" <sx0005@sx2.HRZ.Uni-Dortmund.DE>
Aan: <c.zeelenberg@hccnet.nl>
CC: <groff@ffii.org>
Verzonden: maandag 12 juni 2000 12:25
Onderwerp: Re: [Groff] groff ms-windows


>
> This is good news!  Is this a permanent location?  If yes, I'll add it
> to the MORE.STUFF file.
>
> > An MS-Windows version of Groff 1.16, with Grap 1.05 included, and
> > compiled with the Cygwin-library, has been put at
>
>    ftp://ftp.franken.de/pub/win32/develop/gnuwin32/
>          cygwin/porters/Zeelenberg_Kees/B20/index.html
>                 ^^^^^^^
>
> Seeing the word `porters' I assume that certain fixes were necessary.
> Can you send it to me so that I can decide whether to integrate it?
>
>
>     Werner
>
> _______________________________________________
> Groff maillist  -  Groff@ffii.org
> http://ffii.org/mailman/listinfo/groff
>



From groff-admin  Mon Jun 12 19:55:38 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id TAA14791
	for <Groff@ffii.org>; Mon, 12 Jun 2000 19:55:38 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Mon, 12 Jun 2000 20:07:23 +0200
Received: from rigel.univie.ac.at (dial-143187.HRZ.Uni-Dortmund.DE [129.217.143.187])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id UAA19123;
	Mon, 12 Jun 2000 20:07:21 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id RAA17260;
	Mon, 12 Jun 2000 17:49:53 GMT
Date: Mon, 12 Jun 2000 17:49:53 +0000 (GMT)
Message-Id: <20000612.174953.77323284.sx0005@gnu.org>
To: kst@SDSC.EDU
Cc: nicb@axnet.it, Groff@ffii.org
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <200006121449.HAA00117@elmak>
References: <20000611.200243.06276429.sx0005@gnu.org>
	<200006121449.HAA00117@elmak>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 395
Lines: 14

> > May I ask you to test
> > 
> >   ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz
> 
> It compiles without error on both SunOS 4.1.3 and SunOS 2.5.1, using
> gcc 2.95.2 in both cases.  The single test case I tried (formatting
> a man page to PostScript) worked correctly on both systems.

Thanks a lot for testing -- do you have a change to try Sun's C++
compiler also?


    Werner


From groff-admin  Tue Jun 13 02:39:51 2000
Received: from postal.sdsc.edu (IDENT:X/Ap/dfcecMDe7X5qBpsXNz4szNnICYZ@postal.sdsc.edu [132.249.40.114])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id CAA18571
	for <Groff@ffii.org>; Tue, 13 Jun 2000 02:39:50 +0200
Received: from elmak (elmak.sdsc.edu [132.249.52.146])
	by postal.sdsc.edu (8.9.3/8.9.3/SDSCserver-16) with SMTP id RAA10017;
	Mon, 12 Jun 2000 17:51:50 -0700 (PDT)
From: Keith Thompson <kst@SDSC.EDU>
Received: by elmak (SMI-8.6/1.11-client)
	id RAA02571; Mon, 12 Jun 2000 17:51:50 -0700
Message-Id: <200006130051.RAA02571@elmak>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
To: wl@gnu.org
Date: Mon, 12 Jun 2000 17:51:49 -0700 (PDT)
Cc: kst@SDSC.EDU (Keith Thompson), nicb@axnet.it, Groff@ffii.org
In-Reply-To: <20000612.174953.77323284.sx0005@gnu.org> from "Werner LEMBERG" at Jun 12, 2000 05:49:53 PM
Organization: San Diego Supercomputer Center
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 772
Lines: 23

> > > May I ask you to test
> > > 
> > >   ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz
> > 
> > It compiles without error on both SunOS 4.1.3 and SunOS 2.5.1, using
> > gcc 2.95.2 in both cases.  The single test case I tried (formatting
> > a man page to PostScript) worked correctly on both systems.
> 
> Thanks a lot for testing -- do you have a change to try Sun's C++
> compiler also?
> 
>     Werner

I don't have Sun's C++ compiler for SunOS 4.1.3 (was there one?)
I'm trying a build now using Sun's C++ compiler under SunOS 5.5.1
(CC: WorkShop Compilers 4.2 30 Oct 1996 C++ 4.2).  I'll let you know
how it goes.

-- 
Keith Thompson, San Diego Supercomputer Center  kst@sdsc.edu
<http://www.sdsc.edu/~kst/>
Welcome to the last year of the 20th century.


From groff-admin  Tue Jun 13 02:48:04 2000
Received: from postal.sdsc.edu (IDENT:WunTPJYEuV4uh8WdxHuBhVYhp25Y0L/9@postal.sdsc.edu [132.249.40.114])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id CAA18651
	for <Groff@ffii.org>; Tue, 13 Jun 2000 02:48:03 +0200
Received: from perigee (IDENT:+JGGZ0VeA+NTNU8IORQrgnoCFDL3ovJ7@perigee.sdsc.edu [198.202.75.81])
	by postal.sdsc.edu (8.9.3/8.9.3/SDSCserver-16) with SMTP id SAA10523;
	Mon, 12 Jun 2000 18:00:04 -0700 (PDT)
From: Keith Thompson <kst@SDSC.EDU>
Received: by perigee (SMI-8.6/1.11-client)
	id SAA22093; Mon, 12 Jun 2000 18:00:03 -0700
Message-Id: <200006130100.SAA22093@perigee>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
To: wl@gnu.org
Date: Mon, 12 Jun 2000 18:00:03 -0700 (PDT)
Cc: kst@SDSC.EDU, nicb@axnet.it, Groff@ffii.org
In-Reply-To: <20000612.174953.77323284.sx0005@gnu.org> from "Werner LEMBERG" at Jun 12, 2000 05:49:53 PM
Organization: San Diego Supercomputer Center
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 353
Lines: 11

> Thanks a lot for testing -- do you have a change to try Sun's C++
> compiler also?

It builds without error and passes the same single trivial test as
the other builds.

-- 
Keith Thompson, San Diego Supercomputer Center  kst@sdsc.edu
<http://www.sdsc.edu/~kst/>  Office: 858-822-0853  Fax: 858-534-5077
Welcome to the last year of the 20th century.


From groff-admin  Tue Jun 13 14:43:13 2000
Received: from atlantis.erlm.siemens.de (atlantis.erlm.siemens.de [212.114.202.14])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id OAA04716
	for <Groff@ffii.org>; Tue, 13 Jun 2000 14:43:12 +0200
Received: from mail01.erlm.siemens.de (mail01.erlm.siemens.de [193.98.99.89])
	by atlantis.erlm.siemens.de (8.9.3/8.9.3) with ESMTP id MAA05743;
	Tue, 13 Jun 2000 12:14:10 +0200 (MET DST)
Received: from nbgv101a.nbg9.siemens.de (nbgv101a.nbg9.siemens.de [130.170.148.248])
	by mail01.erlm.siemens.de (8.9.3+Sun/8.9.3) with ESMTP id MAA03869;
	Tue, 13 Jun 2000 12:14:05 +0200 (MET DST)
Received: by nbgv101a.nbg9.siemens.de with Internet Mail Service (5.5.2650.21)
	id <L58SSTGA>; Tue, 13 Jun 2000 12:14:03 +0200
Message-ID: <11DD9734B036D311947400805F0DD607BD89D4@nbgv101a.nbg9.siemens.de>
From: Freudenberger Joerg <Joerg.Freudenberger@nbg9.siemens.de>
To: "'Werner LEMBERG'" <wl@gnu.org>, kst@SDSC.EDU
Cc: nicb@axnet.it, Groff@ffii.org
Subject: RE: [Groff] [PATCH] compiling error on grolbp with latest CVS
Date: Tue, 13 Jun 2000 12:14:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by genba.ffii.org id OAA04717
Status: O
Content-Length: 236
Lines: 10

> > (BTW, strncasecmp is not defined in ISO C; is it POSIX?)
> 
> BSD 4.3
Also defined in Single UNIX Specification Version 2 
which is online available after registration
  	http://www.opengroup.org/pubs/catalog/t912.htm

Yours
	Jörg


From groff-admin  Tue Jun 13 15:46:52 2000
Received: from baoule.ath.cx (daemon@ppp-44-61-17.wly.club-internet.fr [213.44.61.17])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA05392
	for <Groff@ffii.org>; Tue, 13 Jun 2000 15:46:50 +0200
Received: (from gael@localhost)
	by baoule.ath.cx (8.10.0/8.10.0) id e5DDwVk00327;
	Tue, 13 Jun 2000 15:58:31 +0200
Date: Tue, 13 Jun 2000 15:58:31 +0200
From: Gael Queri <gqueri@mail.dotcom.fr>
To: Groff@ffii.org
Cc: Andries Brouwer <aeb@cwi.nl>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
Message-ID: <20000613155831.A155@baoule.ath.cx>
References: <11DD9734B036D311947400805F0DD607BD89D4@nbgv101a.nbg9.siemens.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.11i
In-Reply-To: <11DD9734B036D311947400805F0DD607BD89D4@nbgv101a.nbg9.siemens.de>; from Joerg.Freudenberger@nbg9.siemens.de on Tue, Jun 13, 2000 at 12:13:40PM +0200
X-Operating-System: Linux 2.2.17-pre1
Status: O
Content-Length: 348
Lines: 12

On Tue, Jun 13, 2000 at 12:13:40PM +0200, Freudenberger Joerg wrote:
> > > (BTW, strncasecmp is not defined in ISO C; is it POSIX?)
> > BSD 4.3
Uh? FreeBSD's str?casecmp.3 says

HISTORY
     The strcasecmp() and strncasecmp() functions first appeared in 4.4BSD.

It seems that this is a typo in the linux man page...

[Andries, can you fix that?]


From groff-admin  Tue Jun 13 17:21:50 2000
Received: from baoule.ath.cx (daemon@ppp-44-82-36.wmar.club-internet.fr [213.44.82.36])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id RAA06295
	for <Groff@ffii.org>; Tue, 13 Jun 2000 17:21:49 +0200
Received: (from gael@localhost)
	by baoule.ath.cx (8.10.0/8.10.0) id e5DFXYC00848
	for Groff@ffii.org; Tue, 13 Jun 2000 17:33:34 +0200
Date: Tue, 13 Jun 2000 17:33:33 +0200
From: Gael Queri <gqueri@mail.dotcom.fr>
To: Groff@ffii.org
Subject: The mess of charsets (was Re: [Groff] [PATCH] compiling error on grolbp with latest CVS update)
Message-ID: <20000613173333.A425@baoule.ath.cx>
References: <20000610153945.A16079@baoule.ath.cx> <20000610.153235.64840345.sx0005@gnu.org> <20000610215234.A1581@baoule.ath.cx> <20000611.062135.105169863.sx0005@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.1.11i
In-Reply-To: <20000611.062135.105169863.sx0005@gnu.org>; from sx0005@sx2.HRZ.Uni-Dortmund.DE on Sun, Jun 11, 2000 at 06:21:13AM +0000
X-Operating-System: Linux 2.2.17-pre1
Status: O
Content-Length: 3374
Lines: 81

On Sun, Jun 11, 2000 at 06:21:13AM +0000, Werner LEMBERG wrote:
> 
> > PS: what do you think about my latin9 patch? is 8-bit char encoding
> > considered obsolete?
> 
> Your patch is OK, but I don't know how to proceed.  Creating more and
> more directories for the various encodings + devices isn't a valid
> solution, so I will postpone your changes.

Well, sure; We should really separate that...

> A guy is trying to make Unicode input possible (BTW, any results
> meanwhile?), and I will try to remove input encoding stuff from the
> font description files.

And did someone look at the way plan9's troff works? Maybe we
could find some ideas there as this system uses 16-bit chars everywhere.
It can be downloaded w/source at http://plan9.bell-labs.com/
If someone can easily afford a 50 Mo download...

> I'll probably introduce a kind of `fonts.dir' file to register the
> (font) encoding of the fonts for a particular device to have the
> following chain:
> 
>   groff glyph -> lookup the device's fonts.dir
>               -> search a font which covers the input encoding
>               -> check font shape, slant, etc.
>               -> if no results, check the special fonts
> 
> For example, having `devX100' and `latin2', let's assume that the font
> for shape `Roman bold italic' is called TBI2.  In fonts.dir, this
> would be mapped to `TBI', and everything works as expected.

Yes, it seems appropriate for X output because there the fonts
actually have their charset embedded in their LFD name.
And unicode fonts start to show, so we can
easily fall back to them. (But these are not the typical fonts
used by groff so the output may look ugly :( )

Also for PostScript I suppose the situation is similar.

For html utf8 is more and more recognized by browsers but we
should not rely on this added complexity. And it's almost impossible
to write a multi-encoding html file so we have to choose an encoding.

Also for the ttys the situation is similar: we simply can't
change the font; we have to say which charset we're using.
Sure, we could just use utf8 output but I don't know of any easy way
to recode it to any charset. libc's iconv/recode/etc don't know
what to do when one character is not in the current charset.

What we need is a way to convert utf8 to whatever charset
conserving as much as possible. Actually lynx has
something similar.

Also for dvi output the situation is a bit different because there
we are able of making our own chars, ie if I want a Y with a
dieresis I can simply ask for {\"Y} (or something like that...)
but I don't know how to deal with non-latin encodings.

> Such an approach of course assumes that a particular font covers a
> given input encoding, but anything else would be much more
> complicated.

Sure. i18n is certainly the point where unix sucks the most :(
UTF-8 is theoritically the best solution but almost no one is able
of processing it with most devices.

And there is also the problem that most input files
doesn't have any encoding specified, so we should really add
a way to specify the input encoding.
And the devices are also too heterogen: latin1 is the only device
to be usable for other charsets because it leaves most of the characters
alone, but all other devices suppose latin1 input (especially -Thtml
which converts it to sgml entities)  


Hope I'm not too unclear :(

	Regards, Gaël


From groff-admin  Tue Jun 13 17:33:01 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id RAA06391
	for <Groff@ffii.org>; Tue, 13 Jun 2000 17:33:00 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 13 Jun 2000 15:42:23 +0200
Received: from rigel.univie.ac.at (dial-143187.HRZ.Uni-Dortmund.DE [129.217.143.187])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id PAA29150;
	Tue, 13 Jun 2000 15:42:20 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id FAA18142;
	Tue, 13 Jun 2000 05:49:07 GMT
Date: Tue, 13 Jun 2000 05:49:07 +0000 (GMT)
Message-Id: <20000613.054907.51305042.sx0005@gnu.org>
To: kst@SDSC.EDU
Cc: nicb@axnet.it, Groff@ffii.org
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <200006130100.SAA22093@perigee>
References: <20000612.174953.77323284.sx0005@gnu.org>
	<200006130100.SAA22093@perigee>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 474
Lines: 18

> > Thanks a lot for testing -- do you have a change to try Sun's C++
> > compiler also?
> 
> It builds without error and passes the same single trivial test as
> the other builds.

Again, thanks a lot!  Usually, if old Sun compilers work without
problems this means that the program is quite portable :-)

Of course, IRIX is sometimes even more braindead...


[Anatomical question: Does it make sense to say `braindead', `more
 braindead', `most braindead'?]


    Werner


From groff-admin  Tue Jun 13 21:48:12 2000
Received: from hera.cwi.nl (hera.cwi.nl [192.16.191.1])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id VAA08299
	for <Groff@ffii.org>; Tue, 13 Jun 2000 21:48:11 +0200
Received: from arend.cwi.nl (arend.cwi.nl [192.16.184.162]) by hera.cwi.nl with ESMTP
	id WAA19373 for ; Tue, 13 Jun 2000 22:00:12 +0200 (MET DST)
Received: by arend.cwi.nl 
	id WAA19889; Tue, 13 Jun 2000 22:00:09 +0200 (MET DST)
Date: Tue, 13 Jun 2000 22:00:09 +0200 (MET DST)
From: Andries.Brouwer@cwi.nl
Message-Id: <UTC200006132000.WAA19889.aeb@arend.cwi.nl>
To: Groff@ffii.org, gqueri@mail.dotcom.fr
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
Cc: Andries.Brouwer@cwi.nl
Status: O
Content-Length: 37
Lines: 6

> BSD 4.3

Changed to 4.4.

Andries


From groff-admin  Tue Jun 13 21:52:46 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id VAA08365
	for <Groff@ffii.org>; Tue, 13 Jun 2000 21:52:46 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Tue, 13 Jun 2000 22:04:47 +0200
Received: from rigel.univie.ac.at (dial-143184.HRZ.Uni-Dortmund.DE [129.217.143.184])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id WAA11563;
	Tue, 13 Jun 2000 22:04:44 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id TAA19864;
	Tue, 13 Jun 2000 19:49:32 GMT
Date: Tue, 13 Jun 2000 19:49:32 +0000 (GMT)
Message-Id: <20000613.194932.131901800.sx0005@gnu.org>
To: gqueri@mail.dotcom.fr
Cc: Groff@ffii.org
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000613173333.A425@baoule.ath.cx>
References: <20000610215234.A1581@baoule.ath.cx>
	<20000611.062135.105169863.sx0005@gnu.org>
	<20000613173333.A425@baoule.ath.cx>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Groff] Re: The mess of charsets
Status: O
Content-Length: 5310
Lines: 134

> And did someone look at the way plan9's troff works?

Indeed, checking this would be a good thing.

> It can be downloaded w/source at http://plan9.bell-labs.com/
> If someone can easily afford a 50 Mo download...

Unfortunately, I can't :-(

> > I'll probably introduce a kind of `fonts.dir' file to register the
> > (font) encoding of the fonts for a particular device to have the
> > following chain:
> > 
> >   groff glyph -> lookup the device's fonts.dir
> >               -> search a font which covers the input encoding
> >               -> check font shape, slant, etc.
> >               -> if no results, check the special fonts
> > 
> > For example, having `devX100' and `latin2', let's assume that the
> > font for shape `Roman bold italic' is called TBI2.  In fonts.dir,
> > this would be mapped to `TBI', and everything works as expected.
> 
> Yes, it seems appropriate for X output because there the fonts
> actually have their charset embedded in their LFD name.

This is unimportant, I think, except for a script which adds fonts to
groff -- groff will see its own `fonts.dir'-like file and is not
dependent on any external representation.

> For html utf8 is more and more recognized by browsers but we should
> not rely on this added complexity.  And it's almost impossible to
> write a multi-encoding html file so we have to choose an encoding.

HTML files with multiple encodings are deprecated, AFAIK -- it is very
complicated to construct such a beast anyway.

But HTML is special since everything can be represented as an SGML
entity in HTML 4.0 -- theoretically, we can have a Unicode encoded
document completely written in ASCII...

> Also for the ttys the situation is similar: we simply can't
> change the font; we have to say which charset we're using.

Thus my idea to first try the input encoding specified during a groff
call -- something like

  groff --input-encoding=latin-2 --device=tty ...

> Sure, we could just use utf8 output but I don't know of any easy way
> to recode it to any charset.  libc's iconv/recode/etc don't know
> what to do when one character is not in the current charset.

I don't plan to support encoding conversions.  There are a lot of
filters which can be applied before calling groff (or in case of ttys,
after calling groff).

> What we need is a way to convert utf8 to whatever charset conserving
> as much as possible.  Actually lynx has something similar.

Why should we do this?  With the new version of X, xterm has built-in
utf8 support.  Converting utf8 to anything else is doomed to fail in
most cases.

And be careful to distinguish between `input encoding' and `font
encoding'.  Even with Unicode as the input encoding, groff will still
use *glyph names* for output if necessary.

> Also for dvi output the situation is a bit different because there
> we are able of making our own chars, ie if I want a Y with a
> dieresis I can simply ask for {\"Y} (or something like that...)  but
> I don't know how to deal with non-latin encodings.

I think this is beyond the scope of groff.  The only chance to get
support for non-latin encodings IMHO is to support the extended DVI
format of Omega.

Especially for DVI I will probably add another switch to groff which
makes it possible to specify the font encoding:

  groff --input-encoding=latin-2 --font-encoding=T1 --device=dvi ...

Then we have the following mappings;

  input encoding -> glyph names -> font encoding

I've already implemented such things for my ttf2pk converter, so I
know quite well how to handle it...

> > Such an approach of course assumes that a particular font covers a
> > given input encoding, but anything else would be much more
> > complicated.
> 
> Sure. i18n is certainly the point where unix sucks the most :(

Windows is not much better -- just now you can e.g. write Thai with
the German version of Windows 2000 without using special Thai
software.

> UTF-8 is theoretically the best solution but almost no one is able
> of processing it with most devices.

groff can already use 16bit fonts!  There is no 8bit limit with the
font encoding.

UTF-8 as input encoding will be finally mapped to output glyph names.
A possible algorithm may be

  . Check whether we have a glyph named `U+xxxx' (or something
    similar) -- since, say, more than 90% of the characters in Unicode
    have a direct mapping to a single glyph, I believe it is a valid
    shortcut to directly use Unicode character codes in font
    encodings.

  . If not, consult a (not yet existing) mapping table which maps
    Unicode to glyph names.

It will become a bit more complicated for composed characters -- I
think we shall then follow the Adobe Glyph List (and its algorithm)
for constructing glyph names in case no mapping value is found.  Even
here, glyphs not having an Adobe glyph name get its names constructed
with Unicode names, e.g. `uni01B703020300' (which is a composite glyph
consisting of the three Unicode characters U+01B7, U+0302, and
U+0300).

> And the devices are also too heterogen: latin1 is the only device to
> be usable for other charsets because it leaves most of the
> characters alone, but all other devices suppose latin1 input
> (especially -Thtml which converts it to sgml entities)

This will change in the not-too-far future, I hope.


    Werner


From groff-admin  Fri Jun 16 18:45:58 2000
Received: from mescaline.gnu.org (we-refuse-to-spy-on-our-users@mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA17474
	for <groff@ffii.org>; Fri, 16 Jun 2000 18:45:57 +0200
Received: from babs.bnv.baycix.de (babs.BNV.BayCIX.de [212.72.72.77])
	by mescaline.gnu.org (8.9.1a/8.9.1) with SMTP id MAA28517
	for <groff@gnu.org>; Fri, 16 Jun 2000 12:58:24 -0400
Received: (qmail 22030 invoked from network); 16 Jun 2000 16:58:23 -0000
Received: from airbus.mayn.de (HELO mayn.de) (qmailr@194.145.150.13)
  by babs.bnv.baycix.de with SMTP; 16 Jun 2000 16:58:23 -0000
Received: (qmail 2590 invoked from network); 15 Jun 2000 20:16:10 -0000
Received: from cottbus.mayn.de (194.145.150.15)
  by airbus.mayn.de with SMTP; 15 Jun 2000 20:16:10 -0000
Received: (from bwarken@localhost)
	by cottbus.mayn.de (8.8.8/8.8.8) id XAA16525;
	Tue, 13 Jun 2000 23:19:10 +0200
Message-ID: <20000613231910.A16423@mayn.de>
Date: Tue, 13 Jun 2000 23:19:10 +0200
From: Bernd Warken <bwarken@mayn.de>
To: Keith Thompson <kst@SDSC.EDU>
Cc: GNU troff discussion list <groff@gnu.org>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
References: <20000610.103303.78073704.sx0005@gnu.org> <200006110318.UAA21118@elmak>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <200006110318.UAA21118@elmak>; from Keith Thompson on Sat, Jun 10, 2000 at 08:18:31PM -0700
Status: O
Content-Length: 307
Lines: 11

On Sat, Jun 10, 2000 at 08:18:31PM -0700, Keith Thompson wrote:
> (BTW, strncasecmp is not defined in ISO C; is it POSIX?)

It seems to be POSIX.  The O'Reilly book "POSIX Programmer's Guide"
by D. Lewine states the prototype:

char *strncmp(char *s1, char *s2, size_t n);

Bernd Warken <bwarken@mayn.de>



From groff-admin  Fri Jun 16 20:08:30 2000
Received: from mescaline.gnu.org (mescaline.gnu.org [158.121.106.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id UAA18101
	for <groff@ffii.org>; Fri, 16 Jun 2000 20:08:29 +0200
Received: from postal.sdsc.edu (IDENT:zNBWjk7tSLCWYkQ5uiszLMEwFGp4NqyL@postal.sdsc.edu [132.249.40.114])
	by mescaline.gnu.org (8.9.1a/8.9.1) with ESMTP id OAA05651
	for <groff@gnu.org>; Fri, 16 Jun 2000 14:20:57 -0400
Received: from elmak (elmak.sdsc.edu [132.249.52.146])
	by postal.sdsc.edu (8.9.3/8.9.3/SDSCserver-16) with SMTP id LAA02509;
	Fri, 16 Jun 2000 11:20:51 -0700 (PDT)
From: Keith Thompson <kst@SDSC.EDU>
Received: by elmak (SMI-8.6/1.11-client)
	id LAA27093; Fri, 16 Jun 2000 11:20:14 -0700
Message-Id: <200006161820.LAA27093@elmak>
Subject: Re: [Groff] [PATCH] compiling error on grolbp with latest CVS
To: bwarken@mayn.de (Bernd Warken)
Date: Fri, 16 Jun 2000 11:20:14 -0700 (PDT)
Cc: kst@SDSC.EDU (Keith Thompson), groff@gnu.org (GNU troff discussion list)
In-Reply-To: <20000613231910.A16423@mayn.de> from "Bernd Warken" at Jun 13, 2000 11:19:10 PM
Organization: San Diego Supercomputer Center
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Status: O
Content-Length: 570
Lines: 16

> On Sat, Jun 10, 2000 at 08:18:31PM -0700, Keith Thompson wrote:
> > (BTW, strncasecmp is not defined in ISO C; is it POSIX?)
> 
> It seems to be POSIX.  The O'Reilly book "POSIX Programmer's Guide"
> by D. Lewine states the prototype:
> 
> char *strncmp(char *s1, char *s2, size_t n);

That's strncmp, which is defined in both ISO C and POSIX.  The function
in question is strncasecmp.

-- 
Keith Thompson, San Diego Supercomputer Center  kst@sdsc.edu
<http://www.sdsc.edu/~kst/>  Office: 858-822-0853  Fax: 858-534-5077
Welcome to the last year of the 20th century.


From groff-admin  Fri Jun 23 16:29:30 2000
Received: from jess.glam.ac.uk (jess.glam.ac.uk [193.63.147.97])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA22506
	for <groff@ffii.org>; Fri, 23 Jun 2000 16:29:29 +0200
Received: from ems2.glam.ac.uk ([193.63.150.65])
	by jess.glam.ac.uk with esmtp (Exim 3.12 #1)
	id 135Udt-0002LN-00; Fri, 23 Jun 2000 15:41:13 +0100
Received: from floppsie.comp.glam.ac.uk (gmulle.comp.glam.ac.uk [193.63.130.52]) by ems2.glam.ac.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LFY5B8JJ; Fri, 23 Jun 2000 15:41:43 +0100
Received: by floppsie.comp.glam.ac.uk (Linux Smail3.2.0.101 #1)
	id m12YDs5-000SLZC; Thu, 23 Mar 2000 20:06:21 +0000 (GMT)
Message-Id: <m12YDs5-000SLZC@floppsie.comp.glam.ac.uk>
Date: Thu, 23 Mar 2000 20:06:21 +0000 (GMT)
From: Gaius Mulley <gaius@glam.ac.uk>
To: eddie@mngovsci.com
CC: bwarken@mayn.de, groff@ffii.org
In-reply-to: <Pine.LNX.3.96.1000323125049.30863A-100000@ns1.greenbush.com>
	(message from Eddie Maddox on Thu, 23 Mar 2000 12:59:54 -0500 (EST))
Subject: Re: [Groff] tmac renaming
References:  <Pine.LNX.3.96.1000323125049.30863A-100000@ns1.greenbush.com>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 120
Lines: 4

Oops sorry Eddie, and thanks for the permission.
Over to you Werner and Ted to decide on the name change.

Thanks Gaius

From groff-admin  Sat Jun 24 17:07:56 2000
Received: from Hesperia (ppp129-global3.libertysurf.fr [213.36.122.129])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id RAA12165
	for <groff@ffii.org>; Sat, 24 Jun 2000 17:07:55 +0200
Received: from baruchel by Hesperia with local (Exim 2.05 #1 (Debian))
	id 1360C5-0003o6-00; Sat, 24 Jun 2000 17:22:37 -0700
Date: Sat, 24 Jun 2000 17:22:35 -0700
From: baruchel <baruchel@libertysurf.fr>
To: groff@ffii.org
Message-ID: <20000624172235.A14631@Hesperia>
References: <200006241425.QAA08881@genba.ffii.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <200006241425.QAA08881@genba.ffii.org>; from groff-request@ffii.org on Sat, Jun 24, 2000 at 04:25:43PM +0200
Machine: Hesperia sur Debian (Linux)
Subject: [Groff] Writing in gray with groff... possible?
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 298
Lines: 12

Brest, le samedi 24 juin

Is it possible to write in gray with groff?
Is it possible to use gray in the tbl preprocessor (eg. have the background of
a cell in gray and your letters in black)?

-- 
   .~.   Thomas Baruchel
   /V\   baruchel@libertysurf.fr
  // \\    Brest
 /(   )\   FRANCE
  ^`~'^

From groff-admin  Sat Jun 24 18:03:08 2000
Received: from picnic.mat.net (root@picnic.mat.net [206.246.122.133])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA16014
	for <groff@ffii.org>; Sat, 24 Jun 2000 18:03:07 +0200
Received: from localhost (chuckr@localhost [127.0.0.1])
	by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA24032;
	Sat, 24 Jun 2000 12:14:52 -0400 (EDT)
	(envelope-from chuckr@picnic.mat.net)
Date: Sat, 24 Jun 2000 12:14:51 -0400 (EDT)
From: Chuck Robey <chuckr@picnic.mat.net>
To: baruchel <baruchel@libertysurf.fr>
cc: groff@ffii.org
Subject: Re: [Groff] Writing in gray with groff... possible?
In-Reply-To: <20000624172235.A14631@Hesperia>
Message-ID: <Pine.BSF.4.21.0006241212340.318-100000@picnic.mat.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1012
Lines: 26

On Sat, 24 Jun 2000, baruchel wrote:

> Brest, le samedi 24 juin
> 
> Is it possible to write in gray with groff? Is it possible to use gray
> in the tbl preprocessor (eg. have the background of a cell in gray and
> your letters in black)?

I did that by making a gray postscript page, importing it with PSPIC,
moving back to the top of the page, and overprinting.  It would seem to be
something that would be a wonderful feature ... being able to specify a
background (either a percent fill level, or a postscript image directly).

Doing the way I did, well, it seemed a huge kluge.

> 
> 

----------------------------------------------------------------------------
Chuck Robey            | Interests include C & Java programming, FreeBSD,
chuckr@picnic.mat.net  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.
----------------------------------------------------------------------------


From groff-admin  Sat Jun 24 19:18:30 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id TAA20651
	for <groff@ffii.org>; Sat, 24 Jun 2000 19:18:30 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 135tmY-000FMv-00; Sat, 24 Jun 2000 18:31:50 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id RAA28300;
	Sat, 24 Jun 2000 17:38:44 +0100
Message-ID: <XFMail.000624173844.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000624172235.A14631@Hesperia>
Date: Sat, 24 Jun 2000 17:38:44 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: baruchel <baruchel@libertysurf.fr>
Subject: RE: [Groff] Writing in gray with groff... possible?
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1781
Lines: 53

On 25-Jun-00 baruchel wrote:
> Brest, le samedi 24 juin
> 
> Is it possible to write in gray with groff?
> Is it possible to use gray in the tbl preprocessor (eg. have the
> background of
> a cell in gray and your letters in black)?
> 
> -- 
>    .~.   Thomas Baruchel

Yes in principle, but not all easily.

There is no provision at present in tbl for cell-background-filling, so
you would have to fake it.

The only way I can think of would go as follows:

Knowing the size of the cell, define a string (say \*[bbg]) which
defines a fill-level (using \D'f ...'), and draws a filled box
(using \D'P ...') (see man groff_out). Then make your cell entries
like (using # for the tab character):

  ...#\*[bbg]<cell text contents>#...

How do you know the cell size?, you ask.

Well, if you inspect the output of tbl itself very carefull, you
will find that number registers are defined from which the
dimensions of a cell could be deduced.

This would be the hardest bit of all. I have from time to time
thought of trying it out, but hace never been sufficiently
motivated to really do it. So I can't say how well it could be
made to work.

Nevertheless, for what it's worth, that is my idea on the question!

Best wishes to all,
Ted.

PS if anyone does want to try doing it, don't forget that the
\D'f ...' command implements, as a side effect, a horizontal
motion equal to its argument in groff units. This has to be
undone with an extra \h'...' command so as to suppress the motion.



--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 24-Jun-00                                       Time: 17:38:44
------------------------------ XFMail ------------------------------

From groff-admin  Sat Jun 24 23:56:44 2000
Received: from Hesperia (ppp245-global3.libertysurf.fr [213.36.122.245])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id XAA04741
	for <groff@ffii.org>; Sat, 24 Jun 2000 23:56:43 +0200
Received: from baruchel by Hesperia with local (Exim 2.05 #1 (Debian))
	id 1363VN-00042Z-00; Sat, 24 Jun 2000 20:54:45 -0700
Date: Sat, 24 Jun 2000 20:54:44 -0700
From: baruchel <baruchel@libertysurf.fr>
To: groff@ffii.org
Subject: Re: [Groff] Writing in gray with groff... possible?
Message-ID: <20000624205444.A15525@Hesperia>
Mail-Followup-To: groff@ffii.org
References: <20000624172235.A14631@Hesperia> <XFMail.000624173844.Ted.Harding@nessie.mcc.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <XFMail.000624173844.Ted.Harding@nessie.mcc.ac.uk>; from Ted Harding on Sat, Jun 24, 2000 at 05:38:44PM +0100
Machine: Hesperia sur Debian (Linux)
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 437
Lines: 17

Brest, le samedi 24 juin
> 
> Yes in principle, but not all easily.
> 
> There is no provision at present in tbl for cell-background-filling, so
> you would have to fake it.
> 
Thank you for this. Is it possible to do the second thing I asked (write
with gray characters)? I am not afraid of doing some job in the troff output
;-)

-- 
   .~.   Thomas Baruchel
   /V\   baruchel@libertysurf.fr
  // \\    Brest
 /(   )\   FRANCE
  ^`~'^

From groff-admin  Sun Jun 25 01:54:01 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id BAA12741
	for <groff@ffii.org>; Sun, 25 Jun 2000 01:54:00 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 135zxK-000O0b-00; Sun, 25 Jun 2000 01:07:23 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id BAA09128;
	Sun, 25 Jun 2000 01:06:07 +0100
Message-ID: <XFMail.000625010607.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000624205444.A15525@Hesperia>
Date: Sun, 25 Jun 2000 01:06:07 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: baruchel <baruchel@libertysurf.fr>
Subject: Re: [Groff] Writing in gray with groff... possible?
Cc: groff@ffii.org
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 1837
Lines: 73

On 25-Jun-00 baruchel wrote:
> Brest, le samedi 24 juin
>> 
>> Yes in principle, but not all easily.
>> 
>> There is no provision at present in tbl for cell-background-filling,
>> so
>> you would have to fake it.
>> 
> Thank you for this. Is it possible to do the second thing I asked
> (write with gray characters)? I am not afraid of doing some job in the
> troff output
> ;-)
> 
> -- 
>    .~.   Thomas Baruchel

This one is easy (if the output device is PostScript). You don't need
to edit the output. The following is an entire input file:

  .ps 36
  .vs 36p
  .ce 3
  \X'ps: exec 0.7 setgray'GREY
  \X'ps: exec 0 setgray'BLACK
  \X'ps: exec 0.4 setgray'DARK GREY

(Note that in PostScript gray = 0 means "black", gray = 1 means "white").

You could define strings or macros for this, e.g.

  .de grch
  .ds ngr \\$1
  .shift
  \X'ps: exec \\*[ngr] setgray'\\$*
  ..
  .ps 36
  .vs 36p
  .ce 3
  .grch 0.7 GREY
  .grch 0 BLACK
  .grch 0.4 DARK GREY

This also works for coloured text, e.g.

  .ds RED "\X'ps: exec 1 0 0 setrgbcolor'
  .ds BLACK "\X'ps: exec 0 0 0 setrgbcolor'
  .ps 36
  .vs 36p
  .ce 3
  THIS IS BLACK
  \*[RED]THIS IS RED
  \*[BLACK]THIS IS BLACK AGAIN

  .nr bwd \w'\0WHITE ON GREY\0'u
  .ce
  \D'f 400u'\h'-400u'\
  \Z'\v'0.5m'\D'P 0 -1.7m \n[bwd]u 0 0 1.7m -\n[bwd]u 0'\v'-0.5m''\
  \X'ps: exec 1 1 1 setgray'\0WHITE ON GREY\0


If you view the output in a colour PostScript renderer such
as ghostscript or ghostview, you should see the colour changes.

The last item above shows how to print white on grey.

Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 25-Jun-00                                       Time: 01:06:07
------------------------------ XFMail ------------------------------

From groff-admin  Sun Jun 25 12:40:36 2000
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by genba.ffii.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id MAA03197
	for <groff@ffii.org>; Sun, 25 Jun 2000 12:40:36 +0200
Received: from tedistan.annex.umist.ac.uk
	([194.66.22.200] helo=eels.fort.knox.uk ident=root)
	by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4)
	id 136A36-0009rY-00; Sun, 25 Jun 2000 11:54:01 +0100
Received: (from efh@localhost)
	by eels.fort.knox.uk (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id LAA21151;
	Sun, 25 Jun 2000 11:46:06 +0100
Message-ID: <XFMail.000625114606.Ted.Harding@nessie.mcc.ac.uk>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.000625010607.Ted.Harding@nessie.mcc.ac.uk>
Date: Sun, 25 Jun 2000 11:46:06 +0100 (BST)
X-Face: [qQGB(tVuNmTW7d2IIW?}Q@o\5ylM)dMKj=^)[^u78SI^oF|,Bgx4.qr\~1$FU%GYMu+4U>
 OY}WP|MMo':O[#t;qquVe4?Wp)tW_tDEc#PbkUjmo,UX*`u)`|LAB}A?r.BsFqTs-Tf_&5NS$8foVz
 m@3`)E_hwiU$|h>{'yxV&}u<:bTv|4"bG|_kp.3U}Z$|p.WZ+YHYoiSAz&\Vj;K'H{$+_%^7Eg\FJw
 6Or=.@t38!:GOH#NPD*%=c%D{>x`1cf!t<D0cw2jzk,=aYrizabpqR-kK=RNHP+\{GY[]QKrb>Z_|f
 $Gnqe+;Z#tPqxW)r-k<.`v
Reply-To: Ted.Harding@nessie.mcc.ac.uk
From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
To: groff@ffii.org
Subject: Re: [Groff] Writing in gray with groff... possible?
Cc: baruchel <baruchel@libertysurf.fr>
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 779
Lines: 27

Sorry, there was a typo in my last example:

On 25-Jun-00 Ted Harding wrote:
> 
>   .ps 36
>   .vs 36p
> 
>   .nr bwd \w'\0WHITE ON GREY\0'u
>   .ce
>   \D'f 400u'\h'-400u'\
>   \Z'\v'0.5m'\D'P 0 -1.7m \n[bwd]u 0 0 1.7m -\n[bwd]u 0'\v'-0.5m''\
>   \X'ps: exec 1 setgray'\0WHITE ON GREY\0
> 
> The last item above shows how to print white on grey.
> 
> Ted.

(Last line corrected: the original works as far as it goes, but leaves
a couple of junk items on the POstScript stack).

Ted.

--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
Fax-to-email: +44 (0)870 284 7749
Date: 25-Jun-00                                       Time: 11:46:06
------------------------------ XFMail ------------------------------

From groff-admin  Tue Jun 27 23:10:12 2000
Received: from Hesperia (ppp56-brest.libertysurf.fr [213.36.44.56])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA17111
	for <groff@ffii.org>; Tue, 27 Jun 2000 23:10:11 +0200
X-Authentication-Warning: genba.ffii.org: Host ppp56-brest.libertysurf.fr [213.36.44.56] claimed to be Hesperia
Received: from baruchel by Hesperia with local (Exim 2.05 #1 (Debian))
	id 1372p0-0000CD-00; Tue, 27 Jun 2000 23:23:06 +0200
Date: Tue, 27 Jun 2000 23:23:06 +0200
From: baruchel <baruchel@libertysurf.fr>
To: groff@genba.ffii.org
Message-ID: <20000627232306.A746@Hesperia>
Mail-Followup-To: groff@ffii.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
Machine: Hesperia sur Debian (Linux)
Subject: [Groff] Is there an archive with macros contribution?
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 253
Lines: 13

Brest, le mardi 27 juin

Hi,

I was just wondering if there was on the net an archive with users macros
as contributions or something of the kind?

-- 
   .~.   Thomas Baruchel
   /V\   baruchel@libertysurf.fr
  // \\    Brest
 /(   )\   FRANCE
  ^`~'^

From groff-admin  Wed Jun 28 08:31:33 2000
Received: from nx5.HRZ.Uni-Dortmund.DE (nx5.HRZ.Uni-Dortmund.DE [129.217.131.21])
	by genba.ffii.org (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id IAA26199
	for <groff@genba.ffii.org>; Wed, 28 Jun 2000 08:31:32 +0200
Received: from sx2.hrz.uni-dortmund.de by nx5.HRZ.Uni-Dortmund.DE
          via smtp-local with ESMTP; Wed, 28 Jun 2000 08:45:05 +0200
Received: from rigel.univie.ac.at (dial-143198.HRZ.Uni-Dortmund.DE [129.217.143.198])
	by sx2.hrz.uni-dortmund.de (8.8.8+Sun/8.8.8) with ESMTP id IAA11382;
	Wed, 28 Jun 2000 08:44:56 +0200 (MET DST)
Received: from localhost (sx0005@localhost [127.0.0.1])
	by rigel.univie.ac.at (8.9.3/8.8.8) with ESMTP id IAA07148;
	Wed, 28 Jun 2000 08:08:35 +0200
Date: Wed, 28 Jun 2000 08:08:35 +0200 (CEST)
Message-Id: <20000628.080835.30179207.sx0005@gnu.org>
To: baruchel@libertysurf.fr
Cc: groff@genba.ffii.org
Subject: Re: [Groff] Is there an archive with macros contribution?
From: Werner LEMBERG <sx0005@sx2.HRZ.Uni-Dortmund.DE>
In-Reply-To: <20000627232306.A746@Hesperia>
References: <20000627232306.A746@Hesperia>
X-Mailer: Mew version 1.95b35 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Reply-To: Werner LEMBERG <wl@gnu.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: groff-admin@ffii.org
Errors-To: groff-admin@ffii.org
X-BeenThere: groff@ffii.org
X-Mailman-Version: 2.0beta2.local2
Precedence: bulk
List-Id: GNU troff discussion list <groff.ffii.org>
Status: O
Content-Length: 275
Lines: 8

> I was just wondering if there was on the net an archive with users
> macros as contributions or something of the kind?

AFAIK, no.  You are invited to build up such a thing :-) If you find
something essential, I can include it directly into the groff package.


    Werner

