On 17.10.24 01:39, Dave Kemper wrote:
On Wed, Oct 16, 2024 at 3:01 PM joerg van den hoff wrote:
I now double-checked: the manual seems to indicate that w/o preceding mk, rt
needs an argument
(distance from page top). if it _really_ does the line would have to read `.rt
0'. but doing
joerg van den hoff wrote:
At 2024-10-16T13:30:23+0200, joerg van den hoff wrote:
I ran into this problem several months ago but did never suspect
it would be related to a preceding update to 1.23 (which happened
as part of general package update run so I did not even take note
until recently tha
On 16.10.24 19:38, G. Branden Robinson wrote:
[CCing groff@gnu and directing Reply-To there]
Hi Joerg,
hi branden,
At 2024-10-16T13:30:23+0200, joerg van den hoff wrote:
I ran into this problem several months ago but did never suspect it
would be related to a preceding update to 1.23
On 13.10.24 15:31, G. Branden Robinson wrote:
[replying only to the lists since you're clearly subscribed, or
otherwise following them]
Hi Joerg,
hi branden,
At 2024-10-13T12:36:23+0200, joerg van den hoff wrote:
On 13.10.24 11:24, G. Branden Robinson wrote:
it seems it would pro
On 13.10.24 11:24, G. Branden Robinson wrote:
Hi Joerg,
hi branden,
it seems it would probably be best to just agree to disagree and move on, but
...
At 2024-10-13T11:03:52+0200, joerg van den hoff wrote:
but I really believe the line should never have been deleted in the
first place
sonally believe the same is true for the .IX
removal ;)).
best,
joerg
On 04.10.24 15:10, joerg van den hoff wrote:
correction regarding the "long entries that do line break do not honour indent": this probably is
technically not a bug since in the original context the entries do hav
3T23:06:18+0200, joerg van den hoff wrote:
table of content when using ms macros (wide entries failing to line
break and "pushing" the page number out of line to the right instead).
I cannot say, however, whether this is a 1.23-related issue or whether
it just has escaped my attention pr
On 03.10.24 23:21, G. Branden Robinson wrote:
At 2024-10-03T23:06:18+0200, joerg van den hoff wrote:
table of content when using ms macros (wide entries failing to line
break and "pushing" the page number out of line to the right instead).
I cannot say, however, whether this is a 1.
On 03.10.24 21:58, Deri wrote:
On Wednesday, 2 October 2024 19:29:26 BST G. Branden Robinson wrote:
To accept such a restriction is to surrender groff to stagnation. While
I am aware of at least one person for whom that situation is a
preference, I claim that the same can be achieved by neve
this trivial macro is ... trivial :)). you maintain it, you decide. if you would
reconsider that decision, I would welcome it, if not, so be it.
At 2024-10-02T18:12:06+0200, joerg van den hoff wrote:
I was not aware of this change (not following groff development
closely) and it took me quite
On 09.08.22 21:38, G. Branden Robinson wrote:
[looping in groff@ again due to a shift in discussion focus to
development]
At 2022-08-09T19:14:25+0200, joerg van den hoff wrote:
On 09.08.22 17:05, Deri wrote:
groff and grops can find the SS file, which gives the widths of the
SS glyphs, but
On 10.08.22 01:55, Deri wrote:
ok, in this case, yes. I would have expected the relative movement
being relative to the fraction bar itself, but that's obviously not
what eqn does.
This part I cannot speak to, as I have only barely begun coping with GNU
eqn's source code. If someone else kno
Robinson wrote:
[looping in main groff list since I went into didact mode]
Hi Joerg,
At 2022-08-08T21:32:24+0200, joerg van den hoff wrote:
I think I nearly get it now regarding font selection. but regarding
font metrics: my rudimentary understanding was/is that each glyph
essentially gets assigned a
On 27.07.22 14:29, Deri wrote:
On Wednesday, 27 July 2022 08:49:01 BST joerg van den hoff wrote:
hi deri,
thanks a lot for bothering. have read and understood everything. this is all
interesting and mostly was unknown to me so far. I also tried out your
manual slanting suggestion for grops
ich was truncated!!
On Tuesday, 26 July 2022 17:19:04 BST Deri wrote:
On Tuesday, 26 July 2022 09:00:25 BST joerg van den hoff wrote:
me again with an update/correction to the previous description of the
issue
(the described problem remains, though):
1.
regarding the symobl fonts used by
On Sat, 16 Jan 2010 04:22:27 +0100, Miklos Somogyi
wrote:
On 15/01/2010, at 09:21 PM, joerg van den hoff wrote:
On Thu, 14 Jan 2010 11:48:48 +0100, Miklos Somogyi
wrote:
On 14/01/2010, at 08:31 PM, Patrik Schindler wrote:
Hello Miklos,
Am 14.01.2010 um 07:57 schrieb Miklos
thank you, and just a short confirmation that, indeed, now it works
seemingly perfect for
me.
all the best
joerg
On Thu, 06 Aug 2009 13:11:50 +0200, Deri James
wrote:
On Wednesday 05 August 2009 11:30:50 joerg van den hoff wrote:
Warning: An error occurred while reading an
just a short feedback:
1.)
thanks!
2.)
in a first test with
groff 1.19.3
perl v5.8.8
macosX
this seems to work more or less correctly.
but with a small text sample the generated pdf was about a factor of
10 larger than that resulting from `ps2pdf' (i.e. gs). furthermore `gv'
complained when
On Mon, 20 Jul 2009 16:57:05 +0200, Matthias-Christian Ott
wrote:
On Mon, Jul 20, 2009 at 04:20:36PM +0200, Joerg van den Hoff wrote:
I'm using 'refer' (and the ms macros) for generation of auto-numbered
literature
references (using the refer 'bibliography' reque
I'm using 'refer' (and the ms macros) for generation of auto-numbered literature
references (using the refer 'bibliography' request).
problem: if numbers go beyond 99 there is not enough indentation space,
so I get something like
...
98. some reference
99. some reference
100.
some reference
..
On Jun 03 2009 (Wed, 23:53), Jan-Herbert Damm wrote:
> Hello,
>
> thank you everybody for this very interesting thread!!
>
> as someone who came to groff via it's makro-sets (mom in my case): may i ask
> for a short indication on how to accomplish this (or where to find it in TFM):
> > > last no
On Jun 03 2009 (Wed, 20:57), Tadziu Hoffmann wrote:
>
> One thing that hasn't been mentioned yet: creating
> nontrivial tables with tbl+roff is *much* easier than
> with LaTeX (in part thanks to tbl's "n" (numeric) format
> specifier).
>
>
> > groff is a single pass formatter, LaTeX is multi-pas
On Jun 03 2009 (Wed, 8:55), John¹ wrote:
> Many years ago, when type used to be set by hand, I was one of those who
> did the typesetting. I am now looking at the methodology of using either
> Groff or LaTex to produce print ready text. Can anyone briefly tell me if
> Groff does the same job as
thanks a lot (example and all). the `vpt' request is what I was looking
for, I think. in you example, though, the page footer is misaligned
relative to the text body (page offset is different). it seems that the
footer does not learn of the modified PO until page two. how come?
and I get an error
On May 13 2009 (Wed, 13:30), Ralph Corderoy wrote:
>
> Hi Joerg,
>
> > over all I therefore probably would prefer to fiddle with BT to get
> > the multiline footer in place...
>
> You're probably right that the trap is being triggered again, and
> again... A crufty solution might be to only mov
On May 12 2009 (Tue, 23:17), Larry Kollar wrote:
>
> Joerg van den Hoff wrote:
>
>> currently I try to get a multiline footer at the page bottom (in my
>> case only on page one but it could be a running footer, too). I'm
>> using
>> the `ms' mac
dear all,
currently I try to get a multiline footer at the page bottom (in my
case only on page one but it could be a running footer, too). I'm using
the `ms' macros. I tried to modify the BT macro as such:
.de BT
.if \\n%=1 \{\
. sp -2v
. so footer.tbl
. bp
\}
.ie o .tl \\*[pg*OF]
.el .tl \
On Mon, Feb 16, 2009 at 08:04:18AM +0100, Werner LEMBERG wrote:
>
> > I thought some of you might be interested to know that there's now a
> > rolling import of Groff's CVS repository into GNU Bazaar
> > (http://bazaar-vcs.org/), thanks to Michael Hudson and others at my
> > employer, Canonical.
>
On Tue, Jul 15, 2008 at 06:01:18PM +0200, Tadziu Hoffmann wrote:
>
> > but I still would appreciate to get some hint how to tune
> > the inter-column spacing.
>
> From "Tbl -- A Program to Format Tables":
>
> Space between columns -- A number may follow the key-letter.
> This indicate
On Wed, Jul 16, 2008 at 06:34:48AM +0200, Werner LEMBERG wrote:
> > I have not used `tbl' for some time and now see the following
> > behaviour, which was not present before, I'm quite sure: [...]
>
> Source code, please.
>
> > and it's still funny: the table is rendered completely (but
> > exten
On Tue, Jul 15, 2008 at 04:52:21PM +0200, Joerg van den Hoff wrote:
> hi,
>
> I have not used `tbl' for some time and now see the
> following behaviour, which was not present before, I'm quite
> sure:
>
> the inter-column space seems to be zero,
hi,
I have not used `tbl' for some time and now see the
following behaviour, which was not present before, I'm quite
sure:
the inter-column space seems to be zero, i.e. in a table
with all left centered columns the longest entry (max. width
entry, I mean) in each column "touches"
On Sun, Jul 13, 2008 at 08:59:30PM +0200, Werner LEMBERG wrote:
>
> > In addition to my new MAC laptop (with groff v 1.19.2). I have been
> > able to access a MAC desktop with groff v 1.19.1. I ran three
> > different files on the desktop using groff -ms -e filename >
> > filename.ps All three ra
On Mon, Feb 04, 2008 at 05:17:36PM -0500, Larry Kollar wrote:
>
> Robert Marks wrote:
>
> > Never seen anything like this -- suggestions?
> >
> > Input file testeq:
>
> [snip]
>
> My suggestion would be to compile groff from CVS and install over the shipped
> version. The magic incantation on
On Wed, Jan 30, 2008 at 11:49:50PM -0500, Luke Huang wrote:
> Who please teach me how to add the header (or footer) which is NOT shown
> in the first page of each section.
>
> P.S I am suing groff with -ms.
>
> Thanks a lot
> Luke
>
>
add
.P1
at the top of you document.
joerg
On Mon, Jan 21, 2008 at 01:33:19PM +0100, Dan H wrote:
> On Mon, 21 Jan 2008 12:35:05 +0100
> Joerg van den Hoff <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Jan 21, 2008 at 10:22:12AM +0100, Dan H wrote:
> > > I use groff
> > > with the mm package (because it i
On Mon, Jan 21, 2008 at 10:22:12AM +0100, Dan H wrote:
>Hello all,
>
>As my job frequently requires me to write highly structured,
>long emails, I???ve discovered groff to be the perfect tool for
>me. This email is an example of how I use groff with the mm
>
On Mon, Jan 21, 2008 at 10:37:42AM +0100, Dan H wrote:
> On Mon, 21 Jan 2008 10:22:12 +0100
> Dan H <[EMAIL PROTECTED]> wrote:
>
> > 2. Foreign languages: How can I load different
> > hyphenation patterns, if they exist?
>
> More specifically: I did find the .hpf command an
On Thu, Jan 10, 2008 at 09:57:18PM +0100, Gunnar Ritter wrote:
> Joerg van den Hoff <[EMAIL PROTECTED]> wrote:
>
> > shows that the "hat" is sort of right aligned above the K,
> > not centered as the dot is in the ps output. moreover the
> > vertical
On Wed, Jan 09, 2008 at 04:02:37PM +0100, Gunnar Ritter wrote:
> "Michael Kerpan" <[EMAIL PROTECTED]> wrote:
>
> > After joining this board (and being mostly a lurker), I've been clued
> > in to the awesome -mom macro package. I'd like to use it with my
> > extensive collection of OTF fonts, but i
attempting to generate the html version of the manual, but
with groff 1.19.3 I ran into the following problem: after
./configure
make
cd doc
make groff.html
I get
CUT--
makeinfo --enable-encoding -I. --html --no-split groff.texinfo \
On Fri, Jan 04, 2008 at 04:10:09PM -, Ted Harding wrote:
> On 04-Jan-08 15:24:31, Joerg van den Hoff wrote:
> > I thought I had this solved but cannot find it again (neither
> > in my stuff nor in the docs):
> >
> > `.po' requests (and PO register in `ms&#x
I thought I had this solved but cannot find it again (neither
in my stuff nor in the docs):
`.po' requests (and PO register in `ms' which I actually use)
do take effect only on the next page, i.e. after page break.
question: how to enforce some page offset on the very first
page without either ed
On Fri, Nov 02, 2007 at 05:37:15PM +0100, Werner LEMBERG wrote:
> > the `.fam' request works just fine but seemingly not in combination
> > with the -ms macropackage. [...]
> >
> > question: how to enforce palatino (or whatever) as the default
> > family for a complete document _inside_ the docume
hi,
back to the roots: I was always content using the default
font family (times roman -- after all troff is rumoured to
mean 'times roman roff'...) but finally, I've to switch
fonts sometimes.
the `.fam' request works just fine but seemingly not in
combination with the -ms macropa
hi,
in case somebody uses `vi': I played around with some short-
cuts which allow to substitute inplace groff source text
by its `groff -Tlatin1' formatted output.
this usually is _not_ what one wants but I think it's useful
for simple text files (such as READMEs and the like) where
you a
On Mon, Sep 03, 2007 at 08:01:39PM -0700, andlabs wrote:
>
> Hello. I'm getting ready to install Plan 9 from Bell Labs on an old computer
> I have, and I noticed that it has a wonderful macro set called "mpictures",
> which allows you to put a PostScript image within your document:
>
> .BP image.
On Tue, Aug 28, 2007 at 07:39:21PM +0200, Axel Kielhorn wrote:
>
> Am 27.08.2007 um 06:58 schrieb Werner LEMBERG:
>
> >
> >>Please take a look at this document (It is written in german), I
> >>would like to add it to the groff-wiki or maybe even the groff
> >>distribution, once it is finished.
>
On Sun, Aug 19, 2007 at 02:31:34PM +0200, Axel Kielhorn wrote:
> Hi!
>
> I'm writing a german document in ms and I'm wondering about the best
> way to enter quotation marks.
>
> Should I
> .ds Q \(Bq
> .ds U \(lq
> and use
> \*Q \*U?
>
> or can I simply use ,,and''?
>
> The later is much easie
On Thu, Aug 09, 2007 at 04:08:54PM -0700, Frank Jahnke wrote:
> I am writing a highly-technical review article with a colleague who
> knows only MS Word on the Mac (and so is not particularly
> computer-savvy). I've agreed to use Word, for which I don't much care,
> but it seems to be the only wa
On Wed, Mar 21, 2007 at 04:05:08PM +0100, Werner LEMBERG wrote:
>
> > what seems buggy is the following:
> >
> > I now get "numeric overflow" errors/warnings for each `.PSPIC' call
> > although the generated output looks alright.
>
> Example, please.
>
>
> Werner
in trying to boil it down
On Tue, Mar 20, 2007 at 10:19:11PM -0400, Larry Kollar wrote:
> >what seems buggy is the following:
> >
> >I now get "numeric overflow" errors/warnings for each `.PSPIC'
> >call although
> >the generated output looks alright.
>
> It has been that way for a long time. I have the Makefile redirec
On Mon, Mar 19, 2007 at 09:05:11AM +0100, Werner LEMBERG wrote:
>
> > Maybe the real issue is that AT&T troff and its derivatives do not
> > change to copy mode when reading names:
> >
> > .ds xx foo
> > .ds \\f bar
> > \*(\f2xx \n(.f
> >
> > prints "foo 2" with both 7th Edition troff and Heirlo
On Mon, Mar 19, 2007 at 06:01:18PM +0100, Gunnar Ritter wrote:
> Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>
> > > it seems not to have made it into the development snapshot dated
> > > 19-march-2007 13:08 (I downloaded that right and encounter the same
> > > problem as before). is this to be exp
On Mon, Mar 19, 2007 at 09:05:11AM +0100, Werner LEMBERG wrote:
>
> > Maybe the real issue is that AT&T troff and its derivatives do not
> > change to copy mode when reading names:
> >
> > .ds xx foo
> > .ds \\f bar
> > \*(\f2xx \n(.f
> >
> > prints "foo 2" with both 7th Edition troff and Heirlo
On Mon, Mar 19, 2007 at 11:27:02AM +0100, Tadziu Hoffmann wrote:
>
> > Can you file a bug report to the xterm people?
>
> I don't think it's a bug in xterm. Nroff emits [40m codes,
> which normally means "set background color to black", and this
> is exactly what xterm is doing.
>
> Pipe the ou
On Sun, Mar 18, 2007 at 09:35:52PM +0100, Werner LEMBERG wrote:
>
> > I get garbled output (text is eliminated by some "censor"). I'm
> > usually using MacOSX and the problem occurs
> >
> > -- with the native terminal app of Apple
> > -- with xterm
> > -- with rxvt
> >
> > I now checked it, too
On Sun, Mar 18, 2007 at 02:52:56PM +0100, Werner LEMBERG wrote:
> > I now encounter the situation where the `nroff' output starts to
> > switch the background colour to black (or whatever: there are black
> > rectangles instead of readable text) after it encounters some pic
> > code in the document
I seem to recall that once upon a time simple pic output was reasonably
approximated with nroff (i.e. groff -Tlatin1).
at least I'm rather sure that some 2 years ago it was always possible to look at
the actual text of larger documents containing interspersed `pic' code with
nroff without problems
On Fri, Mar 16, 2007 at 05:48:21PM +0100, Werner LEMBERG wrote:
> > 1.)
> > contrary to earlier versions, this one did initially _not_ compile
> > due to a probably simple problem: utilities such as `xpmtoppm' which
> > are used during documentation generation are not present under OSX
> > und not
On Fri, Mar 16, 2007 at 10:28:30AM -0400, Larry Kollar wrote:
>
> Joerg van den Hoff wrote:
>
> > I've tried to test the current snapshot (under OSX 10.4.8.). I encountered
> > the
> > following problems:
> >
> > 1.)
> > contrary to earlier ver
hi,
I've tried to test the current snapshot (under OSX 10.4.8.). I encountered the
following problems:
1.)
contrary to earlier versions, this one did initially _not_ compile due to a
probably
simple problem:
utilities such as `xpmtoppm' which are used during documentation
generation are not pr
On Wed, Mar 14, 2007 at 02:28:15PM -0700, Frank Jahnke wrote:
> I am trying to cast references from refer into the format requested by a
> particular journal. My old Bell Labs documentation on refer does not
> have much information on the topic, and sadly the man page is nearly
> incomprehensible
On Thu, Mar 15, 2007 at 11:39:16AM +0100, Tadziu Hoffmann wrote:
>
> > I can only track down this to the step where the `refer' ms-macros
> > are inserted (i.e. the `refer' output for my original document).
> > the relevant modified excerpt from the latter is:
> [snip]
>
> I think this has to do
On Wed, Mar 14, 2007 at 08:15:10PM +0100, Werner LEMBERG wrote:
>
> > I noticed that groff might format something like
> >
> >
> > " some_text(more_text) "
> >
> >
> > in such a way that it comes out as
> >
> > " some_text("
> > "more_text) "
>
> Example code, please. This s
I noticed that groff might format something like
" some_text(more_text) "
in such a way that it comes out as
" some_text("
"more_text) "
in other words, although there is no space after the opening parenthesis, the
latter is treated as the word ending.
question: is this inten
On Mon, Mar 12, 2007 at 12:43:59PM +0100, Werner LEMBERG wrote:
>
> > Groff can produce decent HTML, but you have to work with it.
>
> You might try Eric's DocLifter for that. Since it works on the
> high-level side (this is, parsing the input file and not the
> intermediate output) and can hand
On Mon, Mar 12, 2007 at 11:16:55AM -0400, Eric S. Raymond wrote:
> Frank Jahnke <[EMAIL PROTECTED]>:
> > I have a paper set in groff, and I wish to submit it to a journal for
> > publication. Their standard line is to submit in DOC or RTF formats;
> > needless to say, that is not helpful, particul
On Sun, Mar 11, 2007 at 12:26:37PM -0700, Frank Jahnke wrote:
> I have a paper set in groff, and I wish to submit it to a journal for
> publication. Their standard line is to submit in DOC or RTF formats;
> needless to say, that is not helpful, particularly since it is full of
> differential equat
On Wed, Feb 28, 2007 at 01:42:38PM +1100, Miklos Somogyi wrote:
> Dear Folks,
>
> I need some integral signs with circles/ellipses around them (e.g. for
> control volumes).
> I've experimented a lot but only got something that is just acceptable
> in print,
> but downright ughhly in Preview and
On Tue, Feb 20, 2007 at 07:04:41AM +0100, Werner LEMBERG wrote:
>
> > > 2. Make a copy of the block beginning with
> > > "GXditview.paned.viewport.dvi.translations",
> > > change "GXditview.paned.viewport.dvi.translations" to
> > > "GXditview.paned.translations", and edit the bindings
On Sat, Feb 17, 2007 at 12:09:12PM +0100, Tadziu Hoffmann wrote:
>
> > I small point: I've noted that `gxditview' (the same holds for
> > `xditview') does not recognize any user input (keyboard or
> > mouse) as long as the mouse cursor is in the 'decoration
> > frame' provided by the window manage
On Thu, Feb 15, 2007 at 04:16:06PM +, Keith MARSHALL wrote:
> Joerg van den Hoff wrote, quoting Tadziu Hoffmann:
> >>> another question: wouldn't it be wiser to emit a warning in
> >>> s.tmac a la
> >>>
> >>> "warning: register `SN&
On Wed, Feb 14, 2007 at 09:26:50PM +0100, Tadziu Hoffmann wrote:
>
> > > Also, had you called ".NHH n xxx" with n>0 first, everything
> > > would have been okay.
> >
> > not quite: the interspersed `.SH' section would have got an
> > erroneous section number (the last one) in the TOC.
>
> You're
(Ted Harding) wrote:
On 12-Feb-07 Joerg van den Hoff wrote:
hi, second try (something went wrong the first time...):
I stumbled over the following:
I have some ms-macros to collect .NH section headings automatically in
a table of content
(TOC) with the correct section number. a stripped down
hi, second try (something went wrong the first time...):
I stumbled over the following:
I have some ms-macros to collect .NH section headings automatically in a table
of content
(TOC) with the correct section number. a stripped down variant is attached. in
order to
account for .SH sections as
hi everybody,
I small point: I've noted that `gxditview' (the same holds for `xditview')
does not recognize any user input (keyboard or mouse) as long
as the mouse cursor is in the 'decoration frame' provided by the window manager or in the
bottom line (where the page number is displayed) of the
Eric S. Raymond wrote:
Werner LEMBERG <[EMAIL PROTECTED]>:
Werner, I have a couple of minor improvements to the MathML patch;
notably, I've fixed a minor bug in the handling of inline equations
and another that attached an incorrect attribute to . Would
you prefer to receive an incremental patc
Eric S. Raymond wrote:
doclifter has reached a point in its evolution at which the single
new feature that would add the most value is probably the ability
to translate eqn markup to MathML. I have looked for programs that do
this, and I have found no evidence that any exist.
Having looked at t
Eric S. Raymond wrote:
Jon Snader <[EMAIL PROTECTED]>:
As a Vim user, I use the K command to pop up a man page in an
editor window when I need to check the exact usage or parameters.
I know that emacs users can do similar things with the M-x man
command. Most serious developers use either emacs
Werner LEMBERG wrote:
I've added German support for groff, both traditional (`-mde') and new
(`-mden') ortography. Please test and enjoy!
`ortography' being an example of the english equivalent of 'neue deutsche
rechtschreibung', I presume? :-)
but seriously: thank's for this change.
joerg
Werner LEMBERG wrote:
just an idea: the problem would go away if the `.so' request could
be told (by a second argument to the request) to rerun all necessary
preprocessors on the sourced file before inserting it (the
preprocessors could be those specified in the groff call or
explicitely specifie
(Ted Harding) wrote:
On 18-Aug-06 Joerg van den Hoff wrote:
hi,
looking at the docs and the archives I did'nt find this:
if there are preprocessor directives in a sourced file and
the file name is specified in a string register in the
document errors result.
say I have to files `t2
hi,
looking at the docs and the archives I did'nt find this:
if there are preprocessor directives in a sourced file and the file name
is specified in a string register in the document errors result.
say I have to files `t2' and `t3' which are to be sourced from within
this document `t1':
M Bianchi wrote:
On Wed, Jul 12, 2006 at 02:52:02PM +0200, Joerg van den Hoff wrote:
:
and while I'm writing anyway: does anybody know how to handle the
following situation:
source:
Miller et al.
.[
miller01
.]
did it wrong and John Doe, too.
.[
Doe02
.]
r
Werner LEMBERG wrote:
(and to be fair, it _is_ in the manpage of refer and one can
understand that passage without making it a project of it's own --
which is not the case with other parts of the manpage, I'm afraid
:-)
Friends, since I don't use refer, I have no real chance by myself to
improv
Frank Jahnke wrote:
I use refer a lot to process references in [gt]roff. I have been unable
to figure out how to handle the groupings of references. An example
would be:
The flux capacitor has been studied widely [7-23] after the pioneering
work of Smith [11-15]...
where those references are
Werner LEMBERG wrote:
Such a warning can only be emitted by PSPIC itself. You might extend
it with
pspic.tmac: No image support for output device `foo'. Using an
empty rectangle instead.
Then the file pspic.tmac can be always loaded at start-up.
Patches welcome.
BTW, I've j
a minor issue:
when formatting a document including .PSPIC directives
with -Tlatin1 (i.e. for the terminal) one gets the warning:
macro `PSPIC' not defined (probably missing space after `PS')
while notification that the macro does not exist is OK, the guess that
this might be due to a missing
Werner LEMBERG wrote:
refer:./test:4: nothing to reference (probably `bibliography'
before `sort')
I've fixed that now in the CVS. Please test.
Werner
perfect. refer warnings are gone (for good). thank you.
question:
> groff --version
yields
GNU groff version 1.19.3
Copyright (C) 2
Larry Kollar wrote:
I stumbled across this today, and didn't see anything about it in the
archives.
http://heirloom.sourceforge.net/doctools.html
"The Heirloom Documentation Tools package provides troff, nroff, and
related utilities They are portable and enhanced versions of the
utilitie
Werner LEMBERG wrote:
I asked this some 6 weeks ago but got no answers. hoping that the mail
maybe reaches some other list members this time I dare to repeat my
question:
I haven't forgotten your email, but I wasn't able to immediately
response, and it moved deeper and deeper into my cueue of
hi,
I asked this some 6 weeks ago but got no answers. hoping that the mail
maybe reaches some other list members this time I dare to repeat my
question:
after upgrading to 1.19.2 I get new warnings from refer which were'nt
there previously:
refer:./test:4: nothing to reference (probably `
hi,
after upgrading to 1.19.2 I get new warnings from refer:
refer:./tt:4: nothing to reference (probably `bibliography' before `sort')
if the document `tt' contains the directive
.R1
accumulate
.R2
but does _not_ include references. (the situation arises, because I
always use a standard head
hi,
there is a typo (sort of) in the manpage. concerning the '-Z' option it
reads:
-Z Do not postprocess the output of troff that is normally called
automatically by groff. This will print the intermediate output
to standard output; see groff_out(5).
the first sentence is b
Werner LEMBERG wrote:
The simplest way is to say
make groff.pdf
I forgot to add that this passes option `-e' to texi2dvi to let
makeinfo expand the macros.
Werner
OK, the omitted '-e' explains my problem with the direct texi2dvi call.
thanks again
joerg
__
hi,
I tried to recreate a new pdf-version of the manual with
texi2pdf groff.texinfo
for the 1.19.2 release. I get (sorry for this...):
===CUT===
sed: 2: "s/\(^\|.* \)@documenten ...": whitespace after branch
sed: 4: "s/\(^\|.* \)@document
Larry Kollar wrote:
Joerg van den Hoff wrote:
well, MacOS is commercial and they seem to be reluctant to update
things like, e.g., rsync or groff as fast as they could [...]
Apple updates it when there's a security-related issue. I install groff
in /usr/bin, wiping the Apple-sup
Keith Marshall wrote:
On Wednesday 03 May 2006 5:25 pm, Louis Guillaume wrote:
Joerg van den Hoff wrote:
sorry to interfere, but \*[SN-DOT], \*[SN-NO-DOT] seem not be there
in groff 1.19.1 (which is what I'm running on my Mac), at least they
don't work and are not present in s.tmac
Keith Marshall wrote:
On Tuesday 02 May 2006 5:47 pm, Louis Guillaume wrote:
Thank you for the explanation. This is great. "\*[SN]" works.
Note that \*[SN_DOT] does not appear to work!
Sorry, my mistake. That should have been \*[SN-DOT], and \*[SN-NO-DOT]
for the case without the terminal d
1 - 100 of 110 matches
Mail list logo
