Quote:
Originally Posted by Hitch
for the font you've chosen to display, and on the newer NookHD's, you have a better than 90% chance that it won't display anyway--the NookHD Operating System seems to override embedded fonts. We've had several books we've had to remake that, for whatever reason, simply would not display correct embedded, proper type fonts. Absolutely infuriating.
|
I'm not sure what to make of that -- so as a professional at this, do you folks just not embed fonts at all? Is there not any way to embed fonts so that "everyone" will see them okay? If not, then geez... I might as well go back to my original design where I didn't use any embedded fonts.
If this is indeed the case -- that it's best to just not embed fonts at all -- then I know this is probably a stretch, but are there certain fonts that are common to ALL ereaders?
Quote:
Originally Posted by Hitch
You probably embedded the images at 100%, in your CSS, for height. That'll create an extra blank page every time.
|
No, as I mentioned I set both the height/width at 99%. Here, for example, this is my code for my "frontispiece" page (the first page after the cover, and before the title page), which is basically how I did up all my full-page images (all as single files, like this), and I did it this way based on what I've picked up here in these forums as well as elsewhere on the 'net...
Code:
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>A Letter To My Imaginary Friend</title>
<meta content="Copyright Ron Koster/Psymon" http-equiv="copyright" />
<link href="../Styles/letter.css" rel="stylesheet" type="text/css" />
<style type="text/css">
@page { margin: 0.000000pt; padding: 0.000000pt; }
</style>
</head>
<body>
<div class="svg_outer">
<div class="svg_inner">
<svg xmlns="http://www.w3.org/2000/svg" height="99%" preserveAspectRatio="xMidYMid meet" version="1.1" viewBox="0 0 592 900" width="99%" xmlns:xlink="http://www.w3.org/1999/xlink">
<image height="900" width="592" xlink:href="../Images/Frontispiece.jpg"></image>
</svg>
</div>
</div>
</body>
</html>
...and the relevant classes in my CSS file are...
Code:
.svg_outer {
display: block;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
margin-top: 0;
padding-bottom: 0;
padding-left: 0;
padding-right: 0;
padding-top: 0;
text-align: left;
}
.svg_inner {
display: block;
text-align: center;
}
If it matters, the "Frontispiece.jpg" image is, in fact, 1200x1800 in size, but as far as I know the above is how the code should be done up???
Quote:
Originally Posted by Hitch
I'd guess that Marvin, like many other reading apps, allows the user to override the fonts at will, OR, simply does not display your blackletter font.
|
No, the example that I loaded up earlier today is totally different from that "olde"-style version -- it's modern English, with regular text (i.e. Georgia as my specified base font, plus an embedded font for the headings only), so it SHOULD display just fine... at least as far as the text goes.
I'm so frustrated...
Ron
