[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Groff] refer help

From: Peter Schaffter
Subject: Re: [Groff] refer help
Date: Sat, 4 Sep 2010 16:01:29 -0400
User-agent: Mutt/1.5.20 (2009-06-14)

On Sat, Sep 04, 2010, Werner Lemberg wrote:
> > The first is that refer doesn't appear to recognize named glyphs in
> > a refer database, eg "Encyclop\[ae]dia Britannica" comes out as
> > "Encyclop dia Britannica" and "Antoine de St-Exup\['e]ry" as
> > "Antoine de St-Exup ry".  Is there a solution to this, or a known
> > workaround?
> There might be bugs in refer, but to test that we need an example, as
> Ralph has already said.

As I mentioned, I'm overhauling mom's refer support, consequently
I'm testing with an unstable om.tmac file.  I just noticed (not
enough sleep?) that refs gathered for output as endnotes do not
exhibit the missing glyph behaviour, only refs accumulated and
sorted for output as a bibliography with $LIST$.

I tested against om.tmac in the cvs, and there's no missing glyph
behaviour in either scenario, so the problem would appear to be
mine.  Stumped for now, but that's to be expected.

Another question/oddity.  Although it isn't likely one would need
two .R1 / .R2 blocks in the same document, in the case that one
does, the second causes groff (or refer? I'm not sure which) to emit
to stderr

  test: 12: .R1: unexpected operator

unless the .R1 is followed by a blank argument, like this

  .R1 ""

Any ideas why?

Peter Schaffter

Author of The Binbrook Caucus

reply via email to

[Prev in Thread] Current Thread [Next in Thread]