> I use me (the macro package, I mean) to produce these things and
> more.
I can't comment on -me since I've never used it.
> The program also draws text at .sp |19.7c, that is 10 cm from the
> bot of page, and the text's top is really at 10 cm height. A
> smaller font at the same .sp |19.7c he
[about the PDF output of groff.texinfo]
> - I find something interesting somewhere, I try it out and it does
> not work. Yeah, this thing does not belong to groff, it does
> belong to a macro package.
>
> The header says: "The GNU Troff Manual"
> The header on the next page says: "M
First of all, which groff version?
> I have started to use groff some time ago. I use it to generate
> document in Polish language. I have installed Polish font Quasi
> Times and I use to generate documents macro latin2. But as you can
> see in attached document that there is a problem with jus
> I'm trying to make some macros that will build up the SEE ALSO list
> [...]
>
> The approach I took was to try and rename the .SH macro to something else
> and stick my code in there. That flopped, what am I doing wrong?
You have first to call .TH within the man page (.TH defines .SH), then
> With Miklos's and Werner's messages of
>
> Feb 22 07:24 GMT distributed to me 18:24 GMT
> Feb 22 07:28 GMT distributed to me 18:41 GMT
>
> the delays at lists.gnu.org are now at least 11 hours.
Today it's significantly better!
> Looking at the list archives at
>
> http://lists.gnu.org
On 22-Feb-06 Ted Harding wrote:
> It seems, looking at the headers of recent mails to
> the list, that postings to the groff list are being
> delayed at lists.gnu.org by 6-12 hours, typically
> over 9 hours.
>
> Is this (as I hope) a temporary phenomenon?
>
> Best wishes to all,
> Ted.
With Mikl
Werner Lemberg wrote:
> Please be careful! Unicode gets extended from time to time, and there
> are high chances that new non-spacing diacritics are added.
> Consequently, a solution within groff must be based on
> user-controllable data.
>
> I suggest to (re)use
>
> .composite foo
>
> (just a s
> > When an input file contains the character , preconv
> > transforms it to \[u1EBF], and troff transforms it to a single
> > glyph u0065_0302_0301. Fine.
> >
> > But when an input file contains the characters
> > , preconv transforms it to
> > x\[u0302]\[u0301], and troff produces three distinct
http://lists.gnu.org/pipermail/groff/
which is spam-free (almost).
Nevertheless, I continue to wonder if the incidence of spam
is causing problems at lists.gnu.org; and I continue (a
In the last few days I received 3 or 4 e-mails 'bout sex movies and the
like.
I deleted them on the spo
