Relatively new LaTeX user going mad here.

All I want to do is use the Day Ramon S font, but it seems nigh on impossible to do so.


What is the secret to using fonts in (La)TeX? Is there any rhyme, reason, or rules of thumb to follow? Or do I need to just keep trying random combinations of the patterns I have found until something works?


Although all I really want to do is use Day Roman S, I have intentionally kept the question focused on fonts in general as there doesn't seem to be any bullet-proof advice on working with fonts. I see a lot of solutions for specific problems, and even fonts in general, but as can be seen in the next section, it's all a jumble.

note 2

Yes, I have RTFM for the Day Roman S font in question, it is installed, and has been reinstalled several times. It's still a pain to figure out a consistent and reliable way to use different fonts in a document.

Previous research

In trying to figure this out, I have looked at many of the samples from FontCatalogue archive that did compile and found that there seem to be a wide variety of ways of specifying fonts. I'm not sure which to use when.

Sometimes you need to just load a package with the same name as the font and add \normalfont\normalfont twice (why?) before the text:


Other times you need to add \normalfont\<font-name> before the text:


Still other times you need to remove ic from the font name and add family, creating \normalfont\<font-name-minus-ic>family before the text:


And sometimes the second command after \normalfont doesn't appear to be related to the package name at all:


Sometimes you also need to use \renewcommand* after loading the font package and before loading fontenc:

\renewcommand*\familydefault{\sfdefault} %% Only if the base font of the document is to be sans serif

And sometimes you can do that without loading the font package first and after loading fontenc (all other examples are before):

\renewcommand*\familydefault{\ttdefault} %% Only if the base font of the document is to be typewriter style

Sometimes you use \renewcommand* to set other defaults such as \rmdefault (previous two examples were \familydefault:


And sometimes you have to set various defaults:

\renewcommand*\familydefault{\ttdefault} %% Only if the base font of the document is to be typewriter style

Finally, some appear to require loading an .fd file (font definition?) directly rather than through the \usepackage command, set up a \newcommand* (rather than \renewcommand*), skip loading fontenc, and change the duplicated \normalfont\normalfont before the text to something more complex:

\input Carrickc.fd
  • 1
    Welcome to TeX.SX! You can have a look at our starter guide to familiarize yourself further with our format. – Speravir Mar 19 '14 at 3:26
  • 1
    Do you plan to change your name for every question? Then think of one: In my eyes you should ask the part “Previous research” as new question. This would also make this question here shorter and a bit more readable. – Speravir Mar 19 '14 at 3:29
  • 1
    edit it if you don't like it. nothing's stopping you. – Want to use Day Roman S Mar 19 '14 at 3:33
  • 2
    First: You misunderstood me (maybe because English is not my natural language), I wanted to say, I cannot say anything about some possible special behahiour of TL in Ubuntu. Second: In TeX.SX the manners are different (also the frequent use of SX instead of SE), see Why do people answer in comments?, but I even didn’t intend to give an answer. – Speravir Mar 19 '14 at 3:52
  • 3
    By the way, I cannot think of any purpose which would be served by \normalfont\normalfont which would not be equally well served by \normalfont. Resetting the default font series, shape and family twice is no better than doing so once. Sometimes, however, \normalfont\normalsize can be helpful. (But that is not your problem here.) – cfr Mar 19 '14 at 4:16

Here is a working (almost) MWE:


\section*{Dayrom S}
For mange Aar siden levede en Keiser, som holdt saa uhyre meget af
smukke nye Kl\ae der, at han gav alle sine Penge ud for ret at blive
pyntet. Han br\o d sig ikke om sine Soldater, br\o d sig ei om Comedie
eller om at kj\o re i Skoven, uden alene for at vise sine nye Kl\ae
der. Han havde en Kjole for hver Time paa Dagen, og ligesom man siger
om en Konge, han er i Raadet, saa sagde man altid her: >>Keiseren er i


Dayrom S

I am almost certain this example will fail for you because I am almost certain you do not have the font installed. The font is not part of TeX Live. Three possibilities:

  • Ubuntu provides a package which you can install.
  • You install the package from CTAN manually, perhaps following the instructions in the link Speravir provided in the comments on your original question.
  • You install the font using the getnonfreefonts script which will automate the process for you. This is part of TeX Live but probably not packaged by Ubuntu. Two possibilities:
    • It is packaged by Ubuntu (despite my pessimism).
    • You install TeX Live from upstream using the instructions in the link Speravir provided in the comments. In this case it would be best to remove the installation you currently have to avoid future confusion.
  • As additional information: The example works fine in TeX Live for Windows, as well. – Speravir Mar 19 '14 at 4:14
  • @Speravir Are you sure? It ought not do so unless you have installed the font either manually or using getnonfreefonts. – cfr Mar 19 '14 at 4:17
  • Oh, yes, you are right, I once have executed getnonfreefonts! – Speravir Mar 19 '14 at 4:20
  • @cfr I tried that approach and still get a warning: Font shape T1/dayroms/bx/n undefined using T1/dayroms/m/n instead on input line 8. Judging from your screen-shot, which looks the same to me, you probably have the same warning. Could you comment on that? – Martin - マーチン Mar 19 '14 at 5:18
  • 1
    @Martin That's because in the \section Latex looks for a bold series, which seems not to exist (dayroms is only available in one weight, and shape). – Manuel Mar 19 '14 at 7:40

There’s no “secret”; fonts in TeX systems started simple, with no choice for the user -- everyone used computer modern, and as a result, the tools for handling fonts, written using Metafont, reached a stable state in the 90s, and haven't needed much extra support.

When it became possible to use Adobe Type 1 fonts, with TeX, the complications hit us, pretty hard. No longer could we just make the font sources available, and let TeX deal with compiling the fonts (and so on) behind the scenes. Which is why you have found it so hard: even if someone has created the files, you need to get them into their rightful places and to conduct some magic to make sure the system notices them. It's not exactly difficult, but finding documentation might not be simple.

It seems we’re getting back to where we started, with TrueType and OpenType fonts. You need an alternative TeX engine (XeTeX or LuaTeX), but those engines are set up to find your system fonts, without much soul-searching by you.

Note that I'm not solving your problems, merely showing how they arose. Your best bet is to ask about individual fonts, as and when you want to use them.


  • It isn't true that everyone used Computer Modern before type1 was a possibility. Other fonts were created using Metafont - some by Knuth, many by others. These still needed to be installed, selected etc. Of course, it was simpler because there was at least only one type of font and obviously this limited user choice. But to suggest that there was no choice at all is just wrong. fonts/source/public/ alone contains 128 sub-directories in my installation of TeX Live, and there are some under jknappen etc., too. Obviously some are newer but not all are. – cfr Mar 19 '14 at 22:51
  • @cfr i said “started ... with no choice”, which wording i chose specifically to avoid your misinterpretation. however, i've only been using tex since the 1980s, so i don't actually know (at first hand) what it was all like for users of tex-in-sail (for example). – wasteofspace Apr 30 '14 at 12:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.