View Single Post
Old 10-29-2011, 10:04 AM   #16
jackie_w
Wizard
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 2,579
Karma: 3784091
Join Date: Sep 2009
Location: UK
Device: Sony PRS-350/650/T1, PB360, Kobo Glo/AuraHD/Aura6"
I have been using embedded fonts on my PRST1 and I have been using the generic font-family name rather than the specific for the labels, i.e.
Code:
@font-face {font-family: serif; ... etc}
body {font-family: serif; ... etc}
rather than
Code:
@font-face {font-family: "Charis"; ... etc}
body {font-family: "Charis"; ... etc}
I have noticed that the PRST1's font override feature DOES work if you do it this way.

Given that the PRST1's font override feature is less than satisfactory (unpredictable loss of italics/bold) I am rather glad that embedded fonts do work correctly.

Last edited by jackie_w; 10-29-2011 at 10:07 AM.
jackie_w is online now   Reply With Quote