![]() |
#1 |
Junior Member
![]() Posts: 6
Karma: 10
Join Date: Oct 2013
Device: Kindle Fire HD Kindle Paperwhite
|
Certain font characters not rendering in the correct font
Hello All,
I'm new to the forum so forgive me if this is posted in the wrong location. I'm working on converting an epub to mobi/kf8 with embedded fonts. Everything has been going smoothly except for one issue. Certain characters in my fonts do not show up properly when viewing the file on the Kindle and Kindle Previewer. For example... In the words "Jane Collins & Bob Smitz" the J, & and Z render in the default Kindle font. I've dug through the font and the characters/glyphs do exist. They view properly in InDesign as well. I've moved out of the InDesign file completely and am fully coding html and css. This problem has me pulling my hair out. Here is some sample code. This is happening for more than 1 font so I'm not convinced it has to do with the font itself. Any help would be greatly appreciated! <span class="ch_backcover_author">Jane Collins & Bob Smitz</span> span.ch_backcover_author { color:#ffffff; font-family:"Gibson Light", sans-serif; font-size:1.2em; font-style:normal; font-weight:200; } |
![]() |
![]() |
![]() |
#2 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 5,631
Karma: 23190435
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
If the problem persists, please answer the following questions:
|
|
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Junior Member
![]() Posts: 6
Karma: 10
Join Date: Oct 2013
Device: Kindle Fire HD Kindle Paperwhite
|
I purchased the entire Gibson family ( including light ) for commercial use on this book. Here are the answers to your questions!
1. On the Kindle Fire HD the characters ( J, &, Z and a few numbers ) are rendered in whatever font I have selected as default. Currently in my case Georgia 2. Yes all characters do scale when I adjust the font size on the device. 3. I ran the validator and got the following results. It says that each individual font is not included in the "package". Aside from the obvious of what its saying...the fonts are in the Sigil project when I open the epub there. I see them getting recognized in kindlegen as well. Quite strange... ERROR OEBPS/content.opf 18 86 attribute "http-equiv" not allowed here; expected attribute "id", "name", "scheme" or "xml:lang" ERROR OEBPS/content.opf 18 86 element "meta" missing required attribute "name" ERROR OEBPS/toc.ncx 27 42 assertion failed: identical playOrder values for navPoint/navTarget/pageTarget that do not refer to same target ERROR OEBPS/toc.ncx 33 42 assertion failed: identical playOrder values for navPoint/navTarget/pageTarget that do not refer to same target ERROR OEBPS/Styles/style.css 5 2 'OEBPS/fonts/arezzodemi.ttf': referenced resource missing in the package. ERROR OEBPS/Styles/style.css 11 2 'OEBPS/fonts/gibson-bold.otf': referenced resource missing in the package. ERROR OEBPS/Styles/style.css 17 2 'OEBPS/fonts/gibson-light.otf': referenced resource missing in the package. ERROR OEBPS/Styles/style.css 23 2 'OEBPS/fonts/gibson-lightit.otf': referenced resource missing in the package. ERROR OEBPS/Styles/style.css 29 2 'OEBPS/fonts/gibson-regular.otf': referenced resource missing in the package. ERROR OEBPS/Styles/style.css 35 2 'OEBPS/fonts/gibson-semibold.otf': referenced resource missing in the package. ERROR OEBPS/Styles/style.css 41 2 'OEBPS/fonts/louisiana.otf': referenced resource missing in the package. ERROR OEBPS/Styles/style.css 47 2 'OEBPS/fonts/minionpro-regular.otf': referenced resource missing in the package. |
![]() |
![]() |
![]() |
#4 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,540
Karma: 134254544
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
The problem is that you did not reference the fonts in the CSS. Here is a sample from one of my stylesheets from an ePub edited in Sigil.
Code:
@font-face { font-family: Charis; font-style: normal; font-weight: normal; src: url(../Fonts/CharisSILR.ttf); } @font-face { font-family: Charis; font-style: normal; font-weight: bold; src: url(../Fonts/CharisSILB.ttf); } @font-face { font-family: Charis; font-style: italic; font-weight: normal; src: url(../Fonts/CharisSILI.ttf); } @font-face { font-family: smallcaps; font-weight: normal; font-style: normal; src: url(../Fonts/CharisSILSmCp-R.ttf); } body { font-family: Charis; widows: 0; orphans: 0; margin-top: 0; margin-bottom: 0; margin-left: 0; margin-right: 0; text-align: justify; font-size: 92.5% } |
![]() |
![]() |
![]() |
#5 |
Junior Member
![]() Posts: 6
Karma: 10
Join Date: Oct 2013
Device: Kindle Fire HD Kindle Paperwhite
|
I do indeed have them referenced.
Code:
@font-face { font-family:Arezzo; font-style:normal; font-weight:bold; src : url("../fonts/arezzodemi.ttf"); } @font-face { font-family:"Gibson Bold"; font-style:normal; font-weight:bold; src : url("../fonts/gibson-bold.otf"); } @font-face { font-family:"Gibson Light"; font-style:normal; font-weight:200; src : url("../fonts/gibson-light.otf"); } @font-face { font-family:"Gibson Light Italic"; font-style:italic; font-weight:300; src : url("../fonts/gibson-lightit.otf"); } @font-face { font-family:Gibson; font-style:normal; font-weight:normal; src : url("../fonts/gibson-regular.otf"); } @font-face { font-family:"Gibson SemiBold"; font-style:normal; font-weight:600; src : url("../fonts/gibson-semibold.otf"); } @font-face { font-family:Louisiana; font-style:normal; font-weight:normal; src : url("../fonts/louisiana.otf"); } @font-face { font-family:"Minion Pro"; font-style:normal; font-weight:normal; src : url("../fonts/minionpro-regular.otf"); } |
![]() |
![]() |
Advert | |
|
![]() |
#6 |
frumious Bandersnatch
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,526
Karma: 19000001
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Is the directory called "font" or "Fonts"? File and directory names are case-sensitive.
|
![]() |
![]() |
![]() |
#7 | |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,540
Karma: 134254544
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
Another problem I see is that two of the fonts are incorrect because they have a number and not a style. ADE doesn't support numeric font weights. It's either normal or bold. 300 or 600 do not work. Last edited by JSWolf; 11-06-2013 at 05:04 PM. |
|
![]() |
![]() |
![]() |
#8 |
Junior Member
![]() Posts: 6
Karma: 10
Join Date: Oct 2013
Device: Kindle Fire HD Kindle Paperwhite
|
Thanks all for your responses! I've resolved all epub check errors. The font names were not respecting the correct case for folder/file name. However my character issue still remains. I've added some screen shots to help illustrate the problem...
One is the Sigil view. You can already see a rendering problem... The second is the view in the Kindle previewer. You can see that those eff'd characters are rendering in a default font... The third is a cap of the font characters/glyphs in the font manager. The characters do appear to exist in the font. Thanks again for everyone's help! EDIT: Removed attachments as they contained names of real people. ![]() Last edited by omskillet; 10-31-2013 at 12:51 PM. |
![]() |
![]() |
![]() |
#9 |
Junior Member
![]() Posts: 6
Karma: 10
Join Date: Oct 2013
Device: Kindle Fire HD Kindle Paperwhite
|
RESOLVED! I did not know that the InDesign export embeds a subset of the font based on what characters are being used in the file. I deleted the fonts from the epub and re-added the full clean fonts. All characters rendering properly!
|
![]() |
![]() |
![]() |
#10 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,471
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
One last note--when you license a font for "commercial use," it frequently does not include redistribution, which, if you have not subsequently subsetted the font, is what is required for licensing without any issues for ePUBs, where the entire font goes forth merrily with each sale. When you license fonts, for ebooks, make sure that redistribution rights are included in the license. Otherwise, you may find that when foundries say 'commercial rights,' they only mean for print, not for distributing the entire font file over and over. Adobe in particular is downright cranky about this. ;-) I recommend you try subsetting the font in your ePUBs, which is then again subset in Kindle via KindleGen--it's the safest route, particularly with commercially-licensed fonts. Hope that helps. Hitch |
|
![]() |
![]() |
![]() |
#11 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,540
Karma: 134254544
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
kindlegen subsets the embedded fonts?
Calibre does subset and I know it works well as I've used it many times. |
![]() |
![]() |
![]() |
#12 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,471
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Amazon says it does, somewhere--the KP manual, perhaps? (Wait...maybe I'm lying...maybe I meant to say, "encrypted." I'll go look it up.) Hitch Last edited by Hitch; 11-06-2013 at 08:15 PM. Reason: Brain-fart? |
|
![]() |
![]() |
![]() |
#13 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,471
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Wolfie:
Here's what I meant; from Section 3.11 of the Kindle Formatting Guidelines, v.2013.3. Quote:
Hitch |
|
![]() |
![]() |
![]() |
#14 |
Junior Member
![]() Posts: 6
Karma: 10
Join Date: Oct 2013
Device: Kindle Fire HD Kindle Paperwhite
|
Hey Hitch...that's interesting that KindleGen does its own obfuscation. I was able to run the python script I found on one of the mobileread threads on my epub and almost all fonts came through correctly except for that gosh dang Gibson Light! My client only plans to do mobi release via Amazon so would it be foolish to assume that I can leave that one font "un-obfusicated" and Kindlegen will provide at least some support in protecting the font?
|
![]() |
![]() |
![]() |
#15 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,471
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Um...that's a complicated question. Here are my responses:
P.S.: Deja Vu Sans or Nobile might work for you where you used the Gibson Light. As far as I remember, they aren't quite as "soft," as Gibson...and the ascenders might be slightly different, but there are much "font-ier" guys on here than I who can likely suggest others. But the DVS will definitely do in a pinch, if you need a sans serif fill-in. And you can redistribute those to your heart's content. Hitch |
|
![]() |
![]() |
![]() |
Tags |
kindle font issue |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
903 ugly font rendering ('not enough ink') | jbaach | PocketBook | 9 | 10-18-2011 07:08 AM |
ADE Font Rendering Engine? | totanus | General Discussions | 7 | 02-18-2011 01:23 PM |
Bug in MobiPocket font rendering? | jpt | Astak EZReader | 2 | 05-26-2010 08:22 PM |
Font rendering with FW 2.0 | Jellby | Bookeen | 1 | 01-03-2010 12:47 PM |
Embolden font when rendering PDF | caritas | 0 | 10-25-2009 07:30 AM |