LyX should not embed type 3 fonts in PDFs.

Bug #145445 reported by Russell Sears on 2007-09-27
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lyx (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: lyx

The pdf files that lyx produces (pdflatex, ps2pdf and dvipdfm) have type 3 (bitmap) fonts embedded in them. They should have type 1 (vector) fonts instead.

I'm not sure if this is a lyx or a tetex / texlive bug. lyx 1.4.3 and 1.5 exhibit the same behavior with both sets of latex packages. I'm filing it here because I don't see any way to change lyx's behavior to work with ubuntu's latex.

The line in the exported latex that seems to be causing the problem is:

\usepackage[T1]{fontenc}

This command typically causes latex to use type 1 fonts.

I see the problem with the feisty and current gutsy latex and lyx packages. Here's a set of packages that exhibits the problem:

tex-common 1.9
texlive-base texlive-common texlive-fonts-recommended texlive-latex-base texlive-latex-recommended 2007-10
texlive-doc-base 2007-3
texlive-base-bin 2007-12ubuntu3
lyx 1.5.0-0ubuntu2
lyx-common 1.5.0-0ubuntu2

Vincenzo Ciancia (vincenzo-ml) wrote :

I don't perfectly understand:

"The line in the exported latex that seems to be causing the problem is:

\usepackage[T1]{fontenc}

This command typically causes latex to use type 1 fonts."

So, in exported latex files, you _have_ "\usepackage[T1]..."? Is the bug that such commands at the beginning of the file should make latex use type1 fonts and it uses type3 fonts instead?

On Thu, 2007-09-27 at 21:02 +0000, Vincenzo Ciancia wrote:
> I don't perfectly understand:
>
> "The line in the exported latex that seems to be causing the problem is:
>
> \usepackage[T1]{fontenc}
>
> This command typically causes latex to use type 1 fonts."
>
> So, in exported latex files, you _have_ "\usepackage[T1]..."? Is the bug
> that such commands at the beginning of the file should make latex use
> type1 fonts and it uses type3 fonts instead?
>

Yes. It uses type 3 fonts if "\usepackage[T1]{fontenc}" is present in
the output file. Removing the line causes type 1 fonts to be used.

I'm not sure if the tetex and texlive people intentionally broke
compatibility (and lyx needs to change), if this is a bug on their end,
or if something funny has happened to my machine.

This copy of ubuntu is only a week or so old. I've tried removing and
reinstalling a few different sets of latex packages. All of them have
had the same behavior.

Thanks!

Artem Baguinski (femistofel) wrote :

adding

    \usepackage{times}

to the latex file causes pdflatex it to use vector font.

Artem Baguinski (femistofel) wrote :

To make LyX insert

    \usepackage{mathptmx}

(which has similar result) go to Document > Settings > Fonts and select in Roman: "Times Roman"

Which suggests that default font isn't available in vector format, or isn't selected for one reason or another. I think default font is computer modern - if i select that I get the ugly bitmap font again.

Swistak (swistakers) wrote :

I confirm that on hardy. With \usepackage[T1]{fontenc} I get Type 3 fonts and Type 1 without.

Swistak (swistakers) wrote :

Installing cm-super fonts fixes this issue.

Dara Adib (daradib) on 2008-05-15
Changed in lyx:
status: New → Confirmed
Stefan Kottwitz (stefan.k) wrote :

I can confirm it (texlive 2007-13 on Ubuntu 8.04) and also that the installation of cm-super by synaptic or apt-get will solve it, without changes to the latex document. cm-super is not installed by default, perhaps because there are good alternative T1 fonts. I just want to mention Latin Modern, it's derived from the default Computer Modern fonts and provides very high quality. For information see the homepage: http://www.gust.org.pl/projects/e-foundry/latin-modern or look at the lmodern package on CTAN.

Dara Adib (daradib) wrote :

The LyX package should suggest cm-super, see Bug 261312.

Changed in lyx:
importance: Undecided → Low
Dara Adib (daradib) wrote :

This particular bug is being marked as a duplicate of bug 261312, because this bug will be fixed with that bug. Please look at the other bug report to see if there is any missing information that you can provide. Additionally, any further discussion regarding the bug should occur in the other report.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers