Peter Schaffter pe...@schaffter.ca wrote:
Thanks. Isobib gave me some ideas that let me come up with a clean
solution to the idem (multiple works by the same author) problem in
mom.
I'm glad of that.
I'm busy with mom right now, but I'd be happy to proofread and
correct your README and
Peter Schaffter pe...@schaffter.ca wrote:
Still not happy about refer not having a mechanism for dealing with
multiple works by the same author, but it's way beyond my expertise
to fix that.
Hello,
I've got a macro that take care of that: Isobib.tmac.
It has been made to respect the
On Sun, Sep 05, 2010, Werner Lemberg wrote:
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
On Sun, Sep 05, 2010, Werner Lemberg wrote:
\*[foo Blow2], with macro foo blank, as above, prints the entry
correctly but refer doesn't sort it (probably something to do with
the asterisk). It winds up at the top of the bibliography.
%A \C'Blow2'\[duplicate] works reliably, so it's
Hi Peter,
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?
Have you a little
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
Peter:
On Fri, Sep 03, 2010 at 08:38:45PM -0400, Peter Schaffter wrote:
Any refer experts out there? I'm overhauling mom's refer handling
to make it fully MLA compliant, and I've encountered two issues.
The first is that refer doesn't appear to recognize named glyphs in
a refer database,
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
On Sat, Sep 04, 2010, Ralph Corderoy wrote:
Hi Peter,
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
On Fri, Sep 03, 2010, Peter Schaffter 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
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
\*[foo Blow2], with macro foo blank, as above, prints the entry
correctly but refer doesn't sort it (probably something to do with
the asterisk). It winds up at the top of the bibliography.
%A \C'Blow2'\[duplicate] works reliably, so it's probably the best
solution. The 2 is abitrary.
Any refer experts out there? I'm overhauling mom's refer handling
to make it fully MLA compliant, and I've encountered two issues.
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
13 matches
Mail list logo
