Hi,
By default, groff uses Times Roman, as I'd expect.
$ groff <<<'hello world!' | grep Times
%%DocumentNeededResources: font Times-Roman
%%IncludeResource: font Times-Roman
/Times-Roman@0 ENC0/Times-Roman RE
/F0 10/Times-Roman@0 SF(hello w)72 12 Q(orld!)-.1 E 0 Cg EP
$
B
On 03-May-2016 08:51:32 Ralph Corderoy wrote:
> Hi,
>
> By default, groff uses Times Roman, as I'd expect.
>
> $ groff <<<'hello world!' | grep Times
> %%DocumentNeededResources: font Times-Roman
> %%IncludeResource: font Times-Roman
> /Times-Roman@0 ENC0/Times-Roman RE
> /F0
> Should I be telling groff that I want to use those Nimbus fonts so it
> uses their metrics rather than the "almost identical" Times' ones?
If you use the gropdf output device, try groff's `-P -y -P U' option
to use the URW fonts.
Werner
Hi Werner,
> > Should I be telling groff that I want to use those Nimbus fonts so
> > it uses their metrics rather than the "almost identical" Times'
> > ones?
>
> If you use the gropdf output device, try groff's `-P -y -P U' option
> to use the URW fonts.
Using -Tpdf gives a PDF that refers to T
Hi Werner,
> Hmm. It seems that Arch Linux doesn't set up the URW fonts. Bad.
They deliberately try to alter upstream as little as possible, AIUI.
https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/groff
shows the PKGBUILD file that defines how to build the upstream source.
I
On Tue 03 May 2016 10:53:45 Ralph Corderoy wrote:
> Hi Werner,
>
> > > Should I be telling groff that I want to use those Nimbus fonts so
> > > it uses their metrics rather than the "almost identical" Times'
> > > ones?
> >
> > If you use the gropdf output device, try groff's `-P -y -P U' option
>> groff -P -y -P U -Tpdf z.tr > z.pdf
>
> Ah, no mention of Times, and Nimbus embedded. It's a big file though,
> ~120,000 bytes compared with ~4,000 if -Tps and ps2pdf is used to also
> embed Nimbus. I guess the latter picks just certain runes?
gropdf is very simple; it doesn't subset font
I’ve looked through this thread and Ingo’s presentation, and several things
stand out:
* I guess one of the primary issues here is that Groff is GPL, and a BSD
distribution wants BSD licenses. That’s valid, if you’re willing to live with
the corner-cases. Then again, using something like XHTML
On Sun 01 May 2016 17:39:59 James K. Lowden wrote:
> As far as I can tell, you're defining "best" in terms of the goal of
> delivering a base OS without a troff dependency for manual display. I
> really don't understand why you consider that desirable. I would like
> to see groff used more, not l
