I'm wondering which font packages are available in MikTeX and TeXLive containing real small caps and also work together with the "microtype" package? ... kpfonts
has real small caps but doesn't work with microtype
as it complains that it doesn't work with non-scalable fonts.
As others have pointed out, the fact that you're getting this error message is not because of some fundamental incompatibility between the two packages, but because your document's preamble instructions must, somewhere, be loading the font in OT1
encoding. Finding the offending instruction and replacing it with a command such as
\usepackage[T1]{fontenc}
should do the trick.
By the way, version 2.5 of microtype
, available in beta form from this site, coexists just fine with xelatex. The package's "official" version on the CTAN is still 2.4., which unfortunately doesn't work with xe(la)tex. I've been using version 2.5 for more than a month now without experiencing any problems when using xelatex.
I believe there are quite a few latex packages that provide fonts with "real" small caps and also come with matching math fonts. Among them are (with no claim whatsoever to completeness!)
- lmodern [yep!]
- kpfonts
- mathpazo (Palatino-type font); load as follows:
\usepackage[sc]{mathpazo}
- mathptmx (Times New Roman font)
There is also the fourier
package, which uses a font that's based on the Adobe Utopia
text font (generally classified as a "transitional" font a la Baskerville
). To get "real" rather than "faked" small caps with this package, you'll have to have access to Adobe's (non-free) Utopia
font; if your system already happens to have this font, you may want to consider it too.
Best Answer
First of all,
microtype
will never issue an error message when it encounters a font that it doesn't know about, so it is always "compatible" in your sense.With regards to "effective": For protrusion of unknown fonts (Calibri being one of them),
microtype
will use fallback settings and write an info about this in the log file. These fallback settings (inmicrotype.cfg
) are quite conservative and contain protrusion settings only for the characters which are most likely to require protrusion (but this is still more than what the settings fromluaotfload
contain, which actually only protrude the punctuation characters). This should give reasonable results in most cases. Of course, it is possible, and probably preferable, to create a proper configuration file for the font in question, but this requires some time and a good eye.With expansion the situation is even better, as it doesn't require dedicated font settings, and will just work, even for unknown fonts.