Declaring Different Versions of One Font

Rand Brittain · 09-27-2020, 01:10 PM

I'm making an ePub using the Vollkorn font, and I wound up deciding to use the semi-bold version instead of the bold version for my <strong> text, so I made my @font-face declarations as usual.

Code:

@font-face {
  src: url(../Vollkorn-Regular.ttf);
  font-family: "Vollkorn";
  font-weight: normal;
  font-style: normal;
  font-stretch: normal;
}
@font-face {
  src: url(../Vollkorn-Italic.ttf);
  font-family: "Vollkorn";
  font-weight: normal;
  font-style: italic;
  font-stretch: normal;
}
@font-face {
  src: url(../Vollkorn-SemiBold.ttf);
  font-family: "Vollkorn";
  font-weight: bold;
  font-style: normal;
  font-stretch: normal;
}
@font-face {
  src: url(../Vollkorn-SemiBoldItalic.ttf);
  font-family: "Vollkorn";
  font-weight: bold;
  font-style: italic;
  font-stretch: normal;
}

However, Calibre is throwing up an error because the proper font-family name for the semi-bold fonts is "Vollkorn Semi-Bold".

This is probably a very minor problem but I do want to get it cleared up.

What's the best practices way to declare all these fonts and tell the <body> to use them to get rid of the error?

DNSB · 09-27-2020, 02:27 PM

Quote:

Originally Posted by Rand Brittain

I'm making an ePub using the Vollkorn font, and I wound up deciding to use the semi-bold version instead of the bold version for my <strong> text, so I made my @font-face declarations as usual.

However, Calibre is throwing up an error because the proper font-family name for the semi-bold fonts is "Vollkorn Semi-Bold".

This is probably a very minor problem but I do want to get it cleared up.

What's the best practices way to declare all these fonts and tell the <body> to use them to get rid of the error?

The error message is correct. If you look at the font, the font-family name is Volkorn SemiBold. To modify this, you can edit the font family name. I used FontForge but there are several other free options. See the attached epub which calibre seems to be happy with. Oddly, calibre internal check is the only one I've run into that complains about the internal font family not matching. EpubCheck does not seem to care.

JSWolf · 09-27-2020, 05:01 PM

Quote:

Originally Posted by DNSB

The error message is correct. If you look at the font, the font-family name is Volkorn SemiBold. To modify this, you can edit the font family name. I used FontForge but there are several other free options. See the attached epub which calibre seems to be happy with. Oddly, calibre internal check is the only one I've run into that complains about the internal font family not matching. EpubCheck does not seem to care.

It's not really an error. the way the fonts are embedded will work no problem. The fonts do not need the internal name changed.

Rand Brittain · 10-02-2020, 06:15 PM

Okay, I guess I'll leave it at that.

09-27-2020, 01:10 PM	#1
Rand Brittain Bookmaker Posts: 416 Karma: 2143650 Join Date: Sep 2010 Device: Cybook Opus	Declaring Different Versions of One Font I'm making an ePub using the Vollkorn font, and I wound up deciding to use the semi-bold version instead of the bold version for my <strong> text, so I made my @font-face declarations as usual. Code: @font-face { src: url(../Vollkorn-Regular.ttf); font-family: "Vollkorn"; font-weight: normal; font-style: normal; font-stretch: normal; } @font-face { src: url(../Vollkorn-Italic.ttf); font-family: "Vollkorn"; font-weight: normal; font-style: italic; font-stretch: normal; } @font-face { src: url(../Vollkorn-SemiBold.ttf); font-family: "Vollkorn"; font-weight: bold; font-style: normal; font-stretch: normal; } @font-face { src: url(../Vollkorn-SemiBoldItalic.ttf); font-family: "Vollkorn"; font-weight: bold; font-style: italic; font-stretch: normal; } However, Calibre is throwing up an error because the proper font-family name for the semi-bold fonts is "Vollkorn Semi-Bold". This is probably a very minor problem but I do want to get it cleared up. What's the best practices way to declare all these fonts and tell the <body> to use them to get rid of the error? Last edited by Rand Brittain; 09-27-2020 at 01:18 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Last try before declaring PW2 dead ?	Cmcm8319	Kindle Developer's Corner	18	08-03-2015 12:14 PM
Declaring default values for columns	Snow Sciles	Library Management	3	05-16-2014 07:33 AM
Newbie: Sigil versions vs. OS versions?	bmwill	Sigil	3	06-07-2013 09:40 PM
Free (Kindle) Declaring Spinsterhood by Jamie Lynn Braziel	arcadata	Deals and Resources (No Self-Promotion or Affiliate Links)	0	12-09-2011 06:07 PM
Sur Amazon, des versions électroniques plus chères que les versions papier	IreneDelse	Amazon Kindle	8	08-29-2008 08:35 AM

10-02-2020, 06:15 PM	#4
Rand Brittain Bookmaker Posts: 416 Karma: 2143650 Join Date: Sep 2010 Device: Cybook Opus	Okay, I guess I'll leave it at that.

Advert