boldfontstypewriter
This question was asked and answered 20 years ago but I wonder if there is a more modern solution today that does not involve quite so much hackery with overriding settings in font files.
I want my font to look exactly like the result of \texttt but in bold face.
How might I achieve this?
I don't think it is reasonable to expect a full list to be created and maintained here. I think it is better to explain how to figure out whether fonts have this support so that users can determine the current answer for a specific font for themselves. If nothing else, this will enable people to check whether an answer here is still correct.
Thérèse is right that $(kpsewhich -var TEXMFDIST)/tex/latex/microtype/ contains configuration files for microtype. But this provides only a limited amount of information because:
I illustrate these points by examples.
$(kpsewhich -var TEXMFDIST)/tex/latex/ebgaramond/mt-EBGaramond.cfg. $(kpsewhich -var TEXMFDIST)/tex/latex/junicode/mt-Junicode.cfgA file may be present without supporting a font in a particular encoding with a particular engine.
microtype just are not supported by some engines regardless of configuration files. All features are supported by pdfTeX, many are now supported by LuaTeX, some are supported by XeTeX and none are supported by TeX.mt-LatinModernRoman.cfg does not support Latin Modern if you compile with pdfTeX because this file concerns encodings only used by XeTeX and LuaTeX. So the presence of a file for a font does not establish that customised settings will be used in your document, even if your engine supports all microtype features and you use that font. [Latin Modern is supported - see below - but this file proves nothing if you are using pdfTeX.]mt-cmr.cfg includes this code:
\SetProtrusion
[ name = lmr-T1,
load = cmr-T1 ]
{ encoding = {T1,LY1},
family = lmr }
{
\textquotedblleft = {300,400}, \textquotedblright = {300,400}
}
This means that Latin Modern Roman will largely use the protrusion settings for Computer Modern Roman when loaded in encodings T1 or LY1, with a couple of additions or adjustments.
But the crucial work is done in microtype.cfg. There a good number of aliases are defined, including:
\ifMT@fontspec
\DeclareMicrotypeAlias{lmr} {Latin Modern Roman}
\else
\DeclareMicrotypeAlias{lmr} {cmr} % lmodern
\fi
This means that if fontspec is in use, the settings from mt-LatinModernRoman.cfg will be used. Otherwise, the settings for Computer Modern Roman will be used.
However, this is not necessarily true merely because you are using Latin Modern Roman. You must be using it as lmr. If you are using the lmodern package, all will be well. But if you are using cfr-lm, then you are using Latin Modern Roman but you are not using lmr:
\renewcommand{\rmdefault}{clm\cfrlm@rmpt\cfrlm@rmol}
Which family this is depends on the options used, but whatever options are active, the result will not be lmr. It will be clm.... So the alias configured in microtype.cfg will have no effect.
To figure out whether microtype will use custom settings, we need to look to another section of cfr-lm.sty (with some comments removed):
\newcommand{\cfr@ffs}{% alias to cmr
clm,clm2,clm2j,clmj,% roman
clms,clm2js,clm2s,clmjs,% sans
clmqs,clm2jqs,clm2qs,clmjqs%
}
\gdef\cfrlm@MicroType@Aliases{%
\@for \xx:=\cfr@ffs \do {%
\DeclareMicrotypeAlias{\xx}{cmr}}%
}
\def\cfrlm@MT@Hook{\cfrlm@MicroType@Aliases}
\@ifpackageloaded{microtype}{%
\cfrlm@MT@Hook}{%
\@ifundefined{Microtype@Hook}{%
\let\Microtype@Hook\cfrlm@MT@Hook}{%
\g@addto@macro\Microtype@Hook{\cfrlm@MT@Hook}}}
This sets up aliases for the various families to Computer Modern Roman if, and only if, microtype is loaded by the user.
[To be honest, I'm not certain these are right now. Every time I look into this, it seems different. However, my code is apparently based on discussion on this site, so it must be good ;), mustn't it?]
If all of that seems really complicated, that's because it is. Fortunately, there is a very simple way to determine whether a font has customised microtype settings or not. Simply use the font in a document, compile with microtype and examine the log file.
\documentclass{article}
\usepackage{cfr-lm}
\usepackage{microtype,kantlipsum}
\begin{document}
\kant[1]
\end{document}
Compiling this test with pdfLaTeX, the following lines appear in the log file:
(/usr/local/texlive/2014/texmf-dist/tex/latex/microtype/mt-cmr.cfg
File: mt-cmr.cfg 2013/05/19 v2.2 microtype config. file: Computer Modern Roman
This shows that the alias has resulted in the relevant settings being loaded.
Now replace cfr-lm by kpfonts and examine the log:
Package microtype Info: Loading generic settings for font family
(microtype) `jkp' (encoding: OT1).
(microtype) For optimal results, create family-specific settings.
(microtype) For optimal results, create family-specific settings.
(microtype) See the microtype manual for details.
This tells us that no custom settings for jkp with encoding OT1 were found and that microtype is therefore relying on generic settings in this case.
Of course, whether font-specific settings are an improvement depends entirely on the quality of those settings. If I've messed up the aliases in cfr-lm or the person who created the settings for Computer Modern Roman lacked an eye for detail, you might be better off with the generics!
Here are the results replacing cfr-lm in the above with newcent and compiling with pdfLaTeX:
Package microtype Info: Loading generic settings for font family
(microtype) `pnc' (encoding: OT1).
(microtype) For optimal results, create family-specific settings.
(microtype) See the microtype manual for details.
So microtype uses generic settings in this case.
There’s a free version of the EB Garamond family on GitHub that comes in different weights. It’s based on EB Garamond 12, though, not 8. You can download regular, bold, italic and bold italic into your project directory or a subdirectory. Just Loading EB Garamond with the Path option to this subdirectory should work.
Then, create your font family using the Path, Scale, BoldFont, and BoldItalicFont options to \newfontfamily. For example, [Scale = MatchUppercase, Ligatures = {Common, TeX}, BoldFont = EBGaramond08-bold.otf, BoldItalicFont = EBGaramond08-BoldItalic.otf] (If you have such fonts.) Use Scale=MatchUppercase to make the heights match, then whatever Ligatures, Numbers and other options you want. You might also need BoldFeatures and BoldItalicFeatures. If you’re loading the specific font files you downloaded into a directory yourself, you probably want to load them by filename with Extension = .otf.
If your copy of the bold font is recent, it should contain small caps already, and they should just work. If you need to load a separate font, you might need to set the BoldFeatures = { SmallCapsFont = ... } option as well.
There is a free version of a Garamond No8 with small caps at Arkandis.
Best Answer
Use Bera Mono: