> Von: "James Cloos"
>
> Certain versions of fontconfig (upstream) included the TeX GYRE fonts as
> suitable options for (some of) the base postscript font names.
>
> The GYRE fonts use names like /f_i for the ligs, not like /fi. They do
> so better to ensure than the text can be un-ligated whe
> Groff, of course, expects the glyph names used by the original
> Adobe fonts. And it is right to do so.
Yes, but you can of course change that by editing the font
description file used by gtroff, and the text.enc file used
by grops to generate the encoding vector. (Better yet, make
a copy and
> "BW" == Bernd Warken writes:
BW> You are right. The error come from my OS.
Certain versions of fontconfig (upstream) included the TeX GYRE fonts as
suitable options for (some of) the base postscript font names.
The GYRE fonts use names like /f_i for the ligs, not like /fi. They do
so be
> "RC" == Ralph Corderoy writes:
RC> How do you recommend `disassembling' a PDF to inspect its contents?
I like mupdfclean from mupdf best. Call it with the -d option.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
On Mon 02 Jun 2014 14:22:48 Tadziu Hoffmann wrote:
> > How do you recommend `disassembling' a PDF to inspect
> > its contents? I'm happy grokking PostScript but want to
> > see the PDF's structure so pdf2ps's output, for example,
> > isn't suitable.
>
> There is a wonderful program called "qpdf"
> Von: "Tadziu Hoffmann"
>
> > How do you recommend `disassembling' a PDF to inspect
> > its contents? I'm happy grokking PostScript but want to
> > see the PDF's structure so pdf2ps's output, for example,
> > isn't suitable.
>
> There is a wonderful program called "qpdf" that converts a
> PDF
On Mon 02 Jun 2014 11:55:32 Ralph Corderoy wrote:
> Hi Tadziu,
>
> > However, it does not embed the font (it contains an encoding vector
> > and only a reference to "Times-Roman") so it is up to the viewer to
> > provide the requested font.
>
> How do you recommend `disassembling' a PDF to inspec
> How do you recommend `disassembling' a PDF to inspect
> its contents? I'm happy grokking PostScript but want to
> see the PDF's structure so pdf2ps's output, for example,
> isn't suitable.
There is a wonderful program called "qpdf" that converts a
PDF file into an equivalent PDF file optionall
On Sun 01 Jun 2014 18:40:58 Bernd Warken wrote:
> `ttf-mscore-install' did not work for me.
>
> Von: "Deri James"
>
> > I've tested on okular 0.17.4 and 0.19.0, both seem Ok.>
> > If you'd like to send me the pdf which won't display on your ubuntu, I
> > might be able to see what is wrong.
> lig
Hi Tadziu,
> However, it does not embed the font (it contains an encoding vector
> and only a reference to "Times-Roman") so it is up to the viewer to
> provide the requested font.
How do you recommend `disassembling' a PDF to inspect its contents? I'm
happy grokking PostScript but want to see t
> ligature-error_$ echo filefile | groff -Tpdf > file.pdf # see appendix
The attached file displays correctly on my machine, both with
ghostscript and acroread.
However, it does not embed the font (it contains an encoding
vector and only a reference to "Times-Roman") so it is up to
the viewer
`ttf-mscore-install' did not work for me.
Von: "Deri James"
> I've tested on okular 0.17.4 and 0.19.0, both seem Ok.>
> If you'd like to send me the pdf which won't display on your ubuntu, I might
> be able to see what is wrong.
ligature-error_$ echo filefile | groff -Tpdf > file.pdf # see ap
On Sat 31 May 2014 19:29:32 Bernd Warken wrote:
> You are right. The error come from my OS. The viewers okular and evince in
> Kubuntu 14.04 (actual) and 14.10 (instable) produce the lacking ligature
> `fi', but 13.04 (old long-term LTS) is fine. That is independent from
> `groff'.
>
> Bernd Wa
Hi there,
try installing the ttf-mscorefonts-installer package on (K)Ubuntu 14.X. On my
system, that fixed the problem. Looks like the Times Roman font is replaced
with another one that lacks the ligature; installing the MS Times font fixes
this.
Leif Bruder
Am 31.05.2014 um 19:29 schrieb Be
> Von: "Peter Schaffter"
> On Sat, May 31, 2014, Bernd Warken wrote:
> > The command
> >
> > $ echo file | groff -Tpdf > /tmp/g.pdf
> > $ okular g.pdf
> >
> > will only print `le', the `fi' has vanished. That is because the ligature
> > `fi'
> > is not available in pdf mode.
>
> Not seeing th
> Von: "Peter Schaffter"
> On Sat, May 31, 2014, Bernd Warken wrote:
>
> > The command
> >
> > $ echo file | groff -Tpdf > /tmp/g.pdf
> > $ okular g.pdf
> >
> > will only print `le', the `fi' has vanished. That is because the ligature
> > `fi'
> > is not available in pdf mode.
>
> Not seeing t
On Sat, May 31, 2014, Bernd Warken wrote:
> # -Tpdf
>
> The command
>
> $ echo file | groff -Tpdf > /tmp/g.pdf
> $ okular g.pdf
>
> will only print `le', the `fi' has vanished. That is because the ligature `fi'
> is not available in pdf mode.
Not seeing this on my system. The 'fi' lig prin
17 matches
Mail list logo
