Macros attached.
On Wed, 23 Jun 2021 21:26:23 +0100
"Denis M. Wilson" wrote:
> I have macros corresponding to Cs strchr and strrchr functions.
> Do you want me to pass them on?
>
> Denis
>
> On Wed, 23 Jun 2021 21:48:48 +0200
> Wim Stockman wrote:
>
> &
I have macros corresponding to Cs strchr and strrchr functions.
Do you want me to pass them on?
Denis
On Wed, 23 Jun 2021 21:48:48 +0200
Wim Stockman wrote:
> Is there a function in groff to find the position of a char in a
> string. So I can split a string into more than one.
> I found the sub
Hello all,
I suggest that this does not upset the Linux man pages project; that
conversion tools should be able to generate standard man format, in
view of the number of tools that assume this, eg RosettaMan and tkman.
Denis
On Wed, 21 Apr 2021 05:46:58 +0200
JM Marcastel wrote:
> Dear all,
>
The perl version of grog has a bug (I've sent a bug report).
I have previously sent bug fixes for the shell version.
If the the bug has been fixed since 1.22.3 ignore this email
( could not get 1.22.4 to compile)
Denis
--
rfc1345 does not have a base-line ellipsis, a character frequently used
in English writing. I've also found it surprising that it is not in
groff either considering groff was originally written by a British
person.
It is available as \N'188' in the symbol font or as \[u2026].
Denis
On Mon, 4 Jan
Hello all,
I have a module for address labels, look in
http://www.oxytropis.plus.com/groff/markup-1.0.7a.tar.gz
It attempts to adjust the typesetting to centre the text within
the label. There is provision for different makes of label and different
printers and how near the edge they print.
Hope
On Fri, 31 Jul 2020 15:11:15 +0200
Tadziu Hoffmann wrote:
> > If it DOES get implemented in Groff, please name it `.indexof`.
> > The name `.index` is so horribly misleading I'm almost tempted
> > to submit a PR just to rename it.
>
> Why not ".strpos"?
>
or ".strstr" as in the C library?
Sorry, the macros I've written are .strchr and .strrchr.
.index should not be too hard using direct method (KMP is too
complicated). I may have time to try, no promises...
On Sat, 25 Jul 2020 17:42:17 -0700strrchr
B 9 wrote:
> "Denis M. Wilson" wrote:
>
> > To impl
goal of groff to support the Heirloom Troff
> extensions?
>
>
> Nope, more like the other way around. Groff is the dominant Troff
> implementation these days, so it behoves Heirloom Troff to support
> the more commonly-used extensions.
>
>
>
> On Sun, 26 Jul 2020 at 10:
To implement .index as a macro one could consider using .substring
together with the Knuth-Morris-Pratt algorithm. I've done simpler
things eg the equivalent of The C library substr().
Denis
On Thu, 23 Jul 2020 16:13:41 -0700
B 9 wrote:
> Heirloom Troff has a handy string search function calle
I have an indexing package which uses 'makeindex', and the results are
good. Indexing is quite complicated. If you care to look at the source
it is in Index,pkg part of
http://www.oxytropis.plus.com/groff/markup-1.0.7a.tar.gz
Denis
On Thu, 23 Jul 2020 16:13:41 -0700
B 9 wrote:
> Heirloom Troff h
On Sat, 4 Apr 2020 18:49:11 -0700
Larry McVoy wrote:
> On Sat, Apr 04, 2020 at 06:42:37PM -0700, Larry McVoy wrote:
> > Could we please just converge on this spec? I'm old and tired but
> > if we can get agreement on this and noone wants to do the code I'll
> > take a swing at it.
>
> I co
The man page for 'grops' mentions "ttftot42" but this
program is now obsolete and won't compile out of the box.
(it is not in my Linux distribution). I did find
"ttftotype42" in the distribution, part of package lcdf-typetools.
It does not generate AFM, but there is a program "ttf2afm" which
does.
My -markup package has has fully parametrized lists (enumerated and
itemised) and a stack. The stack means that lists, fonts, displays etc
are nestable. Lists were the hardest, and it took me long time before I
could devise a good way of doing them. The package (not quite the
latest version) is in
Going back to shortened words, New Hart's Rules (OUP), states that an
abbreviation (trailing letters removed) is followed by a period, eg
Prof. whereas a contraction (other letters removed) is not, eg Mrs
Maybe UK English only...
Denis
On Tue, 21 Nov 2017 13:55:05 +1100 (AEDT)
Damian McGuckin w
soelim does not process .INCLUDE
Denis
On Fri, 21 Jul 2017 07:54:13 +0200
"E. Hoffmann" wrote:
> Am Thu, 20 Jul 2017 16:44:49 -0400
> schrieb Peter Schaffter :
>
> > On Thu, Jul 20, 2017, E. Hoffmann wrote:
> [...]
> > > When I enter unicode, like:
> > >
> > > ÄÖÜ SS ÒÓ
Thanks Ralph!
Denis
On Tue, 21 Mar 2017 16:48:29 +
Ralph Corderoy wrote:
> Hi Denis,
>
> > The following is line 344 of eqn.man (v 1.22.3)
> >
> > a punctuation character such as \[oq],\[cl];
> >
> > What should cl be?
>
> `\(cq'; they're a pair of quotes wrapping the comma. Werner
The following is line 344 of eqn.man (v 1.22.3)
a punctuation character such as \[oq],\[cl];
What should cl be?
Denis
--
An old quote:
If you cannot make it clear with white chalk, you cannot make it
clear with coloured chalk either.
I have a set of macros for doing what I think you mean. I enclose a
sample (with permission) of some pages of a newsletter I was once
involved with. Is this of interest?
Denis
On Mon, 18 Apr 2016 14:46:05 -0400
"James K. Lowden" wrote:
> While I'm in the groff neighborhood, I'd like to ask for
My -markup groff macro package has TOC, indexing and
cross-referencing. If interested look at the source to see how it is
done. I use makeindex, and supply a style file. You need to use gnu
make, it apparently does not work under BSD.
http://www.oxytropis.plus.com/groff/markup-1.0.7a.tar.gz
er, I
xpdf also works, but produces several occurrences of
Error: Illegal entry in bfrange block in ToUnicode CMap
On Wed, 8 Jul 2015 14:30:42 -0400
Peter Schaffter wrote:
> Hi, all.
>
> > > Are you aware that somenthing has happened to the mission
> > > statement PDF and that it is totally undreada
Try correcting line 7 to .vs 14.4
Does that improve what you want?
Denis
On Mon, 20 Apr 2015 17:06:41 +0200
Radek wrote:
> Hello, it's me Radek again.
> It's hard to describe my problems so I will try to isolate them and
> create small demonstration cases. And this is one of them.
> I do not
Rather than shrinking, squash the fake small caps, eg:
S\H'\n[.s]*5/7'MALL\H'0' C\H'\n[.s]*5/7'APS\H'0'
(the 5/7 should approximate to the x-height of the font).
This works better because more of the heavy strokes in a western font
are upright, and this keeps the weight of those.
As Matthew
I did text round a circle using a .eps file, adapted from the
PostScript Cookbook.
In case it's any help I enclose it.
Denis
On Fri, 16 Jan 2015 20:09:06 +1100
Robert Thorsby wrote:
> On 16/01/15 19:56:33, Ted Harding wrote:
> > On 16-Jan-2015 01:48:52 Robert Thorsby wrote:
> > > I need to set
On Mon, 08 Dec 2014 18:08:28 +
Ralph Corderoy wrote:
> Hi Ingo,
>
> > You are confusing character escape sequences \[...]
> > and user-defined strings \*[...].
>
See groff_char(7)
--
The following method works ( give an example):
.sp 1i
.ie n .nr w1 2i
.el .nr w1 .5i
.TS
tab(@);
lw(\n[w1]u) l l.
Hello@World@Nice
Day@Today
.TE
Denis
On Thu, 04 Dec 2014 07:57:50 -0800 (PST)
Anton Shterenlikht wrote:
> I want to make a document that can give good
> ascii and Postscript result
For the sake of othogonality and convenience it would be good to have
extended expressions usable anywhere an expression is required.
What about a new read/write number register ext to indicate how
expressions are to be interpreted?
DEnis
On Mon, 17 Nov 2014 09:22:54 +0100 (CET)
Werner LEMBERG w
On Fri, 14 Nov 2014 15:16:47 +0100
Steffen Nurpmeso wrote:
> |
> |Since the evaluation is done at runtime I can't see a problem \
> |with variables,
> |although it would enable some very obfuscated code...
>
> I don't understand this, actually.
A string variable could expand to a subexpre
Here is another idea. Use the existing (;) notation eg as follows
(Ex; expr )
Where x is the existing unit indicator, E indicates an extended
expression and expr differs from current expressions in having
(a) operator priority;
(b) new string, matching and regular expression operators (Posix
On Wed, 05 Nov 2014 09:15:54 +0100 (CET)
Werner LEMBERG wrote:
>
> groff 1.22.3 has been released.
Great that it has been released after all that's been going on in the
past few months.
Appears to be working perfectly, except for grog :-(
The command line
grog -ww -fN -P-pa5 -ra5=0 fge
It's really off topic, but in the UK in the 1980s, the printers strike
meant the the end of expert typography. The hot metal traditional
expert typography was replaced by crumbly computer software and 500
years of the art and craft of it was lost --- well it was still there
but unknown to the perso
On Wed, 30 Jul 2014 13:40:55 +0100 (BST)
(Ted Harding) wrote:
> On 30-Jul-2014 09:23:54 Anton Shterenlikht wrote:
> > To me
> > .char \[-+] \f[S]\v'.05v'\z+\v'-.3v'\-\v'.3v'\v'-.05v'\f[]
> >
> > looks better vertically aligned, but it's just a bikeshed.
> >
> > Many thanks for all replies.
> >
Try something like
.char \[-+] \f[S]\v'.1v'\z+\v'-.25v'\-\v'.25v'\v'-.1v'\f[]
The spacing needs more fine-tuning, I don't have time at the moment.
Denis
On Tue, 29 Jul 2014 16:21:01 +0100 (BST)
(Ted Harding) wrote:
> On 29-Jul-2014 15:14:27 Anton Shterenlikht wrote:
> >>From ra...@inputplus.c
It looks like -mm but the misalignment doesn't happen when I try it.
Denis
"if you can't see the bug where you're looking, it's somewhere else"
On Fri, 20 Jun 2014 11:09:10 +0200
Tadziu Hoffmann wrote:
>
> > Why the ".sp -0.7v" is needed to achieve alignment, is mystery
> > to me. Could someb
= 188[decimal], but it has no name.
> So define
>
> .char \[el] \f[S]\N'188'\fP
>
> and then you have it!
>
> Best wishes too all,
> Ted.
> (About to follow up with comments on the double up-down arrow).
>
> On 29-May-2014 19:48:31 Denis M. Wilson wrot
Another glyph that is in most text PostScript fonts, is widely used in
English, but is not in groff, is the ellipsis (three dots).
Denis
On Thu, 29 May 2014 20:13:49 +0200
"Bernd Warken" wrote:
> > Von: "Werner LEMBERG"
> >
> > > The following line is from groff_char.man:
> > >
> > > \[vA]
The method used in TeX is the shortest path in a directed acyclic graph.
This is a well-understood problem. There seems unfortunately to be
nothing useful in the STL. The DAG would need to be a new data type.
The real problem is assigning the values in the DAG. Something of the
sort must already b
I've found this with attachments to archive entries, so I downloaded
them and found they're plain text.
Denis
On Wed, 23 Apr 2014 19:37:15 -0400
Peter Schaffter wrote:
> Denis --
>
> On Thu, Apr 24, 2014, Denis M. Wilson wrote:
> > 7. I posted previously in thi
Writing index stuff was quite a lot of work, but worth the effort as
I've used it quite frequently.
Here's my remarks.
1. I used makeindex, which comes with the TeXLive package.
2. It uses a style file, and there are examples in the man page.
3. My macros use .write so troff cannot be used in s
There is a fully functional indexing facility in my -markup macro system
(http://www.oxytropis.plus.com/groff). It uses makeindex. It could be
adapted for format control by using a different syle file. Thus the
feasibilty of indexing is demonstrated. I never got round to finding
how to use xindy fo
Brave statement -- good luck!
Unlike TeX, troff has no modes, so a method of delimiting a paragraph has to
be introduced. Text outside would be treated as currently, text inside would
be subject to whatever algorithm is selected. Some care to get this right
should be taken, as for macro sets to t
On Tue, 18 Mar 2014 10:29:50 -0400
Peter Schaffter wrote:
> On Tue, Mar 18, 2014, Joachim Walsdorff wrote:
> > it would be fine if you could provide an example text, formatted
> > both with groff and Heirloom troff, to demonstrate us the
> > typographic gain by `paragraph-at-once formatting´ aga
... and my tuppenceworth
On Sun, 9 Feb 2014 11:59:18 -0500
Mike Bianchi wrote:
> My 2 cents.
>
> I learned nroff/troff in the mid 1970s, and have used it, almost
> exclusively, ever since. It is what I know in my spine.
I'm exactly the same.
> The MM
> macros are my presentation format of c
Hello all,
On Sun, 17 Nov 2013 21:03:45 +0100
Pierre-Jean wrote:
>
> Dear troffers,
>
> I wish we could simply cross the street to offer to Werner
> some champagne for the long time spent working on groff, and
> for the success of his next projects...
It will be très difficile to find a maint
t
> Peter Schaffter writes:
>
> > I've been dreading the day Werner stepped down as lead developer.
> > Werner, you have fulfilled the role perfectly, and I know I speak
> > for everyone on the list when I say you have earned not only our
> > respect, but our admiration. Being a lead developer
On Fri, 15 Nov 2013 15:53:28 +
Gaius Mulley wrote:
> Peter Schaffter writes:
>
> > I've been dreading the day Werner stepped down as lead developer.
> > Werner, you have fulfilled the role perfectly, and I know I speak
> > for everyone on the list when I say you have earned not only our
>
On Mon, 11 Nov 2013 12:57:31 -0600
Dave Kemper wrote:
> > There is no conflict to groff's `inability' to apply it
> > automatically. What you really want is a *macro package* which does
> > the job.
>
> Well, having a macro package which does the job is certainly better
> than not having it. A
It all works for me, except for ps2eps. I used
ImageMagick to trim and convert (getting rid of
the "Engraved by Lilypond" banner at the foot of the
page). I'm using Lilypond 2.12.3.
Denis
On Sat, 9 Feb 2013 02:20:29 +0100 (CET)
"Bernd Warken" wrote:
> .PSPIC is documented in groff_tmac(5). It
It looks fine to me (using gv as a viewer), although rough round the
edges, as I use the URW not Adobe fonts. The document structure is
incomplete, so gv does not display page numbers.
Denis
On Tue, 5 Feb 2013 11:55:18 +0100 (CET)
"Bernd Warken" wrote:
> From troff.org:
>
> IDEAL User's Manual
I'll be very interested to see how you do this, as I would like to
use some extended maths fonts I have available.
Denis
On Thu, 31 Jan 2013 20:24:20 +0530
Shiv Shankar Dayal wrote:
> On Thu, Jan 31, 2013 at 12:56 PM, Werner LEMBERG wrote:
>
> >
> > > I have initial success in doing this and
Hello Ralph,
The basic problem is to split the lines into a lot of segments
of different lengths -- pasting the segments into place
would then be possible. The solution to the centred picture is to
make the line length equal to the left/right margin, and paste
each with one-line traps (or the dive
Hello all,
On Fri, 25 Jan 2013 09:02:58 +0100
Patrik Schindler wrote:
> Hi Frank,
>
> Am 23.01.2013 um 22:53 schrieb Frank Jahnke:
>
> > I would like to revisit a topic that has come up from time to time
> > over the years but really has not been solved. That is wrapping
> > text around figur
case], and move .rm lowercase
to the end.
Denis
On Wed, 16 Jan 2013 15:02:53 - (GMT)
(Ted Harding) wrote:
> On 16-Jan-2013 14:49:04 Denis M. Wilson wrote:
> > If I run the following shell script
> >
> > troff -ww -dpaper=A4 -dcA5 <<'END'
> > .tm PAP
If I run the following shell script
troff -ww -dpaper=A4 -dcA5 <<'END'
.tm PAPER = \*[paper] c = \*[c]
.ex
END
The output is
PAPER = a4 c = A5
What is going on?
(groff v1.22.1)
Denis
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachme
In this situation I would use a a pair of macros to enclose text to be
rendered verbatim. For example
.BeginVerbatim
text
.EndVerbatim
The following version of these macros may be instructive (the code
cannot be commented for obvious reasons...):
\# From -markup
.de BeginVerbatim
.eo
.de verb-m
Yes, you can use a double quote in a macro argument (it is documented
and has been there forever).
But it gives you the ASCII quote mark, not the typographical open and
close quotes which are use in typesetting English (\[lq] and \[rq]).
What special symbols you use would depend on the language,
Please ignore my last message, sent in error.
Denis
Hello all,
You might want to
On Mon, 10 Dec 2012 13:56:54 +0100
Tadziu Hoffmann wrote:
>
> > image1 image2image3
> >(a) (b) (c)
> >
> > Caption: a common caption for all (a), (b) and (c)
>
> Use mark and return.
> Here's how I would do it if the pictures all
On Wed, 24 Oct 2012 13:00:10 -0400
"James K. Lowden" wrote:
> http://lists.gnu.org/archive/html/groff/2010-01/msg7.html
> http://www.schemamania.org/sailing/bh/
>
> In looking for a way to rotate pic figures, I found Ted Harding's
> message, which offers a nifty trick. But it seems it does
On Mon, 8 Oct 2012 20:26:47 -0400
"James K. Lowden" wrote:
> My world premier macro pair is below! What would you do to improve
> them? In particular, what should I do to make them work across page
> boundaries?
>
> The intention is to number a -ms DS display, a la eqn. Input
>
> .Ds (5)
On Fri, 05 Oct 2012 13:10:48 +0200
Johann Höchtl wrote:
> Is there a way to specifify different paper sizes but A4 and A5? If
> not, I suggest adding at least letter and legal
> (I am not US, but afaik those formats are widely used there)
>
There could be, I suggest, a separate package for US
Hello James,
Thanks for trying it.
Yes, 'supersede' -- I must have had cedere in mind.
I don't really know about writing portable makefiles.
I don't have any 'if' statements in mine -- are you referring
to the 'include' statements? The other places for problems are
special variables like $< etc
Having made many changes in the last three years, I've put up
version 1.0.7 of my -markup package. The changes are mostly cosmetic
and bug fixes, but I have added more real-life examples. It is at
http://www.oxytropis.plus.com/groff/
Denis
--
() ascii ribbon campaign - against html e-mail
/\
Hello all,
Pierre-Jean, you ask for experiences of users. My own is
that I used troff for all academic documentation, once Unix
was obtained, but once groff appeared (in the early 1990s)
writing troff macros became easier (well, less difficult).
I did a great number of newsletters and handbooks,
Hello All,
The line .B "\\n" turns into \n which looks like a number register
without an argument: if you try
groff -ww -man example.1 > /dev/null
you will see the error message
example.1:4: a newline character is not allowed in an escape
name
It's not a man bug, it's troff expected behaviou
Hello all,
explanation below
Denis
On Fri, 28 Sep 2012 16:21:05 -0500
Dave Kemper wrote:
> Hi,
>
> I'm having trouble understanding why the values of \n[rst] and
> \n[rsb], when used inside a string after a \w, are different
> depending on where the string is called from.
>
> In the first case
When designing my index package I found the trickiest part was the
style file. In case it is useful I attach it and the indexing macros
(which would have to be tailored for what package you use).
Denis
index.tmac
Description: Binary data
markup.ist
Description: Binary data
> ... I have just found a printout of the groff
> 'tbl' man page in an old ring-binder. The footer states:
>
> Groff Version 1.10 26 June 1995
>
> This is the old very terse (à la James Clarke) man-page, in which
> "Only the differences between GNU tbl and Unix tbl are described
> here". The
Hello all,
I have indexing in my -markup macros (which do the same sort of job as
-mom but differently). It uses the conventions of makeindex, and creates
several intermediate files (so has to be used with groff -U). The
process is automatic using the .Index macro. You can find the source and
docu
Hello all
On Tue, 24 Jul 2012 16:50:09 +0200
walter harms wrote:
> hi list,
> i run into a problem that may be solved by others already.
>
> I show a groff file as latin1, that worked fine. i had some ^H but
> that where filtered by "tr" no problem. But i added some boldface to
> the text and i
Date: Sat, 26 May 2012 17:47:26 +0100
From: "Denis M. Wilson"
To: Deri James
Subject: Re: [Groff] make fails creating U-
On Sat, 26 May 2012 12:25:43 +0100
Deri James wrote:
> On Saturday 26 May 2012 10:02:22 Denis M. Wilson wrote:
> > On Fri, 25 May 2012 23:41:32 -
On Fri, 25 May 2012 23:41:32 -0400
Peter Schaffter wrote:
> Building groff from the latest sources, 'make' terminates with
> Error 2 after multiple warnings of the sort
>
> Warning: line 78: Failed to create groff font 'U-AB' by running
> afmtodit
>
> I don't recall seeing this before. Wha
I regard the following behaviour of grog, which has been there
from the beginning, to be wrong:
On the input files
a.n:
.EQ
.so /dev/null
.EN
b.n:
.so a.n
the following commands give the indicated results:
grog a.n: groff a.n [missing -se]
grog b.n: groff b.n [missing -se]
With the shel
On Wed, 25 Apr 2012 13:30:38 -0400
Peter Schaffter wrote:
> On Wed, Apr 25, 2012, Denis M. Wilson wrote:
> > Does anyone have experience of installing OpenType fonts for use
> > with groff?
>
> This works for me:
>
> - use fontforge to convert the .otf to .t42 and .
Hello all,
Has anyone installed the Lucida maths fonts in place of the
usual Symbol font? There are lots of useful symbols there
I would like to use.
Denis
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Hello all,
Does anyone have experience of installing OpenType fonts for use
with groff?
Denis
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Ralph, I cannot solve your problem, but observe that there are two
warnings (I always use -ww):
warning: number register `3bot' not defined
warning: macro `T&' not defined
You need a .nr 3bot 0 and .if !d T& .ds T&
before .TS
The best I could do was replace your 3bot line by the two
lines
Hello all,
On Tue, 6 Mar 2012 14:33:04 +0100
Cedric Sodhi wrote:
> Hello everyone,
>
> how do you usually achieve Blackboard Bold ("R" for real numbers, "N"
> for natural, and so forth)?
>
> regards,
> Cedric
>
I don't know the answer! -- but I would presume you need one or more
fonts with
On Tue, 6 Dec 2011 12:50:50 -0600 (CST)
lxnf9...@gmail.com wrote:
> On Tue, 6 Dec 2011, Ralph Corderoy wrote:
>
> > Werner Lemberg wrote:
> >> Simply say `info groff' on the command line.
> >
> > And if you're not fond of info's interface, one that only its mother
> > could love ;-) then
> >
>
On Tuesday 06 Sep 2011 14:48 Deri James wrote:
> On Friday 02 Sep 2011 12:22:46 Denis M. Wilson wrote:
> > Hello all,
> >
> > There have been various postings on this list about the wrong
> > positioning of the radical extender. I found that it depended on
> >
Hello all,
There have been various postings on this list about the wrong
positioning of the radical extender. I found that it depended on which
font family was being used. It turned out that some text faces have a
square root sign which was therefore being used in place of that from
the symbol fo
I was using -ms due to the .TH, and .vs does not
work directly (what were you using?). It all
worked when I used
.nr VS 5m
.LP
This is my command line:
groff -ww -t -ms infile
Denis
On Sun, 31 Jul 2011 15:19:36 +0100 (BST)
(Ted Harding) wrote:
> On 31-Jul-11 13:10:36, Deni
Hello Ted,
On Fri, 29 Jul 2011 22:25:59 +0100 (BST)
(Ted Harding) wrote:
> Greetings All!
> I'm writing to flag up a little trap that one might
> fall into when using 'tbl'.
>
> Background: I'm setting up a table and I want each
> row to have a row number to the left of the table.
> (etc)
Even
This would be feature bloat, as there are ways to do all this
already.
On Tue, 3
May 2011 13:17:27 -0700 (PDT) Dorai Sitaram wrote:
> Wouldn't it be useful to have parameters like \$[m-n] that pick out
> the parameters \$m through \$n ?
Try writing a simple macro (eg)
.params m n $@
where m o
The YaDCM macros work very well standalone; I haven't yet tried
them with a package. They are fairly flexible, for example you can type
.dropcap "B\h'2n'right is the ring" 4 darkblue B P 0 2n 0
of words
When the right man rings them,
Fair the fall of songs
When the singer sings them.
If filling i
> > Is there any reason why changing the font should not
> > change the baseline also ?
>
> Yes. Simple example: assume you want to set just a few words in
> a smaller size, but this short sequence of words happens to wrap
> at the end of the line. With which baseline spacing should
> the lin
In rfloat.tmac need to take environment attributes into account.
For example line length (this works for raw troff without a
macro package):
> >
> > .\" rfloat.tmac
> > .\"
> > .
> > .
> > .\" rfloat
> > .\"
> > .\" Position an image to the right so that text is floating around
> > the image.
It works as documented with groff 1.20.1:
ua = \f[S]\[ua]\f[] uA = \f[S]\[uA]\f[]
I am using the URW version of Symbol
Denis
It's a reminder never to use BSD... On a cursory reading,
it wasn't clear how mdocml produces printable output.
I've found -man excellent, and also very simple to use,
and if the page is written properly produces very good
printed copy. In conjunction with viewers such as TkMan,
very quick for sc
I have tried Makefile.urw, and it works fine for text fonts, but not
for the special fonts. Two typos: udzrrev.afm should be uzdrrev.afm, and
PHONY should be .PHONY
The results are identical to using my devps-alt package, except symbol
fonts, and the latin2 example works.
US: I changed the
I reported this in February, below is what Werner said:
Denis
Remove the `inline' keyword as described in the last entry of the
PROBLEMS file. I haven't had time yet to fix this.
Werner
warning: around line 35: table wider than line width
warning: around line 35: table squeezed horizontally to fit line length
warning: around line 367: table wider than line width
warning: around line 367: column separation set to zero
I've included a patch to include the file name in the warnin
I would support making tbl warnings optional,
to be in line with troff, and other reasons,
for example if a table is deliberately wider
than the line width. A new flag -w to enable
warnings?
Denis
I've got macros to do this in my -markup
package. I'm currently checking that they
still work as it's a while since I used them.
As I recall, the solution was not trivial.
Haven't time at the moment.
Denis
As another retired gentleman, I have considered making
contributions to groff; eg when it was orphaned I thought
of offering to maintain TBL, which I use extensively (even
for purposes for which it was never intended -- such a
versatile tool!). Then the thought of relearning C++ was too
much...
R
I have put a new version of my -markup package
in http://www.oxytropis.plus.com/groff
I have added support for eqn, and included the
documentation preformatted as pdf.
The main features missing are now footnotes and
bibliographies.
I have added equations because I am still worried
about the mys
Dear Michail,
it seems reasonable to include ready groff font description files in the
distribution of your program. Valek Filippov, who extended URW fonts, made
some future versions available after ghostscript picked up his work, but
what distributions adopted them?
I had thought of including
I've put new versions of two packages on the web,
my programs for installing the URW fonts for use
with groff, and my -markup troff macros. Thanks
to all who tried these and found places for
improvement. Futher suggestions are welcome. Look in:
http://www.oxytropis.plus.com/groff
Denis
My point was not "compatibility over all" but "do not break
existing scripts". The .em case is just an example, but as
until recently the only doc of non-groff requests was the AT&T
Bell Labs published Unix books (my troff "bible"), I believed
that unless stated otherwise (or discovered by experim
1 - 100 of 115 matches
Mail list logo
