Re: [Groff] refer help

2010-09-05 Thread Peter Schaffter
On Sun, Sep 05, 2010, Pierre-Jean wrote: > Peter Schaffter 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

Re: [Groff] opentype and postscript fonts

2010-09-05 Thread Pierre-Jean
Werner LEMBERG wrote: > > The standart AR macro > > Macro? You mean groff font file, right? Yes, of course. > BUT: You can use FontForge to load any font, then converting it to a > Type1 font and an AFM file. I just tried it for `Linux Biolinum' > (from the Libertine family): The AFM file ha

Re: [Groff] opentype and postscript fonts

2010-09-05 Thread Werner LEMBERG
> The standart AR macro Macro? You mean groff font file, right? > contain information about kerning. Should these informations be > manually added after conversion from .otf to groff font, or are they > part of the .pfa font? What you actually need is a cff2afm program, however, this doesn't

Re: [Groff] refer help

2010-09-05 Thread Peter Schaffter
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 reliabl

Re: [Groff] refer help

2010-09-05 Thread Peter Schaffter
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: unex

Re: [Groff] refer help

2010-09-05 Thread Pierre-Jean
Peter Schaffter 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 iso-690-2 bibliography

Re: [Groff] Omission in mom ?

2010-09-05 Thread Peter Schaffter
On Sun, Sep 05, 2010, Jacek Sobczak wrote: > Hello, > > I've noticed that setting DOC_FAMILY does not change the font for > author name that appears directly after the title at the beginning of > a document. Inspecting om.tmac version 1.5e I found in the definition > for the _FAMILY macro: > > --

Re: [Groff] opentype and postscript fonts

2010-09-05 Thread Pierre-Jean
Werner LEMBERG wrote: > > 1) OpenType font format is just an encapsulation of TrueType fonts > > or PostScript fonts. > > This is a exaggerating simplification, but I think you are aware of > that fact. I'm not aware about font formats... And so, I've got a last question: The standart AR macro

[Groff] Omission in mom ?

2010-09-05 Thread Jacek Sobczak
Hello, I've noticed that setting DOC_FAMILY does not change the font for author name that appears directly after the title at the beginning of a document. Inspecting om.tmac version 1.5e I found in the definition for the _FAMILY macro: -- cut -- .MAC _FAMILY END .    if '\\$0'AUTHOR_FAMILY' .