On 2009-12-10, Uwe Stöhr wrote:
> > Yes. First since MiKTeX 2.8 (about 2 months old) it is by default
> > included. So I would wait for at least one year until using this as
> > default.
> >
> > OK. Could the WindowsInstaller recommend to install Latin Modern?

> lmodern is automatically installed to MiKTeX or TeXLive when installing
> LyX. This is done by configure.py that calls chkconfig.ltx that in turn
> asks LaTeX if the package lmodern is installed.  If not, MiKTeX and
> TeXLive will automatically install it.

Fine.

> >> Currently we default to LaTeX's default which is the best solution.
> >
> > LyX uses the default font but *not* the default font encoding. These
> > two must be seen in context and therefore the current situation is not
> > the best!

> What do you mean? The default font encoding is T1. 

The *LyX* default font encoding is T1 (Cork encoding, 8 bit).

The *TeX* default font encoding is OT1 (Old TeX encoding, 7 bit).

With OT1 font encoding you will get outline (vector, type1) fonts for
CM with a basic LaTeX installation since several years.

Howver, the TeX FAQs states the problem we face:

  answers to these FAQs recommend that you use an ‘8-bit’ font to permit
  accentuation of inflected languages, and also recommend the use of Type
  1 fonts to ensure that you get good quality PDF. These recommendations
  used to be contradictory: one could not just “switch” from the free CM
  fonts to free Cork- (or similarly) encoded Type 1 fonts. 

  -- http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1

> When you set the document language to e.g.  Russian, T2A is used as
> encoding. The font default for T2A is not CM and thus you get another
> font (I don't know its name right now). 

The same with the T1 (Cork) font encoding. Both, the original Kuthian
bitmap CM and the Blue Sky/AMS vectorized version of CM is not available
in T1 encoding. Therefore TeX selects a replacement which in the default
installations results in the bitmap EC fonts. (If CM-Super is installed,
you will get it instead of CM)

  The only Metafont-fonts that conform to the Cork encoding are the EC
  fonts. They look CM-like, though their metrics differ from CM-font
  metrics in several areas. The fonts are now regarded as ‘stable’ (in
  the same sense that the CM fonts are stable: their metrics are unlikely
  ever to change). Their serious disadvantages for the casual user are
  their size (each EC font is roughly twice the size of the corresponding
  CM font), and there are far more of them than there are CM fonts. The
  simple number of fonts proved problematic in the production of Type 1
  versions of the fonts, but EC or EC-equivalent fonts in Type 1 or
  TrueType form (the latter only from commercial suppliers). Free
  auto-traced versions — the CM-super and the LGC fonts, and the Latin
  Modern series (rather directly generated from Metafont sources), are
  available. 
  
  -- http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts

.... off topic

> By setting the font encoding to T1 this does not
> always mean that really T1 is used. 

More precisely: the setting in 
"Tools>Preferences>Output>LaTeX>TeX encoding"
(misnamed, because it is a *font* encoding) is just the default.

Babel and LyX care for you to select a different font encoding if
required.

However, with "Tools>Preferences>Output>LaTeX>TeX encoding" == T1
you will always get a line
  \usepackage[<optional,other,encdings,>T1]{fontenc}
in the *.tex file.

> Thanks to LaTeX efforts like XeTeX, this setting can be ignored for
> most fonts. 

We actually had a bug report in the users list because XeTeX does not
ignore the \usepackage[T1]{fontenc} call. (This is solved with the
dedicated XeTeX export in trunk which omits this line.)

.....

The problem remains that LyX by default uses EC bitmap fonts (*not* CM).
They not only look bad on screen but also the first compilation takes
more time when the bitmaps are generated and afterwards these bitmaps use
up your disk-space.

Günter

Reply via email to