View Single Post
Old 03-25-2014, 05:39 AM   #23
bfollowell
Fanatic
bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.bfollowell ought to be getting tired of karma fortunes by now.
 
Posts: 541
Karma: 1152752
Join Date: Aug 2010
Location: Evansville, IN, USA
Device: Samsung Galaxy Tab 4 Nook & Samsung Galaxy Tab S 10.5
Quote:
Originally Posted by Hitch View Post
No. He's talking about, particularly, the Nook HD Color, which routinely and very annoyingly ignores perfectly solid CSS and embedded fonts, and simply does NOT display them, publisher-fonts or no publisher fonts. There was a very lengthy thread, when was it, Jellby, Tox, do you remember?--last year, sometime, and I thought the OP was crazy, too, until we had the same thing happen. A file with an embedded font could NOT display the font on the client's Nook HD Color. Subsequent experiments seem to indicate an override of some type. And, yes, we directly side-loaded the file to the devices, with no joy. And the fonts worked perfectly on a Nook Color, Nook readers and other Nook devices.

And it didn't matter how we embedded the fonts; by individual style; by class, by body. One of the fonts just would NOT display.

FWIW.
Hitch
That is really strange. I've never experienced anything like that with my Nook Tablet or Nook HD+. Neither have ever failed to display an embedded font, assuming it was setup correctly. I guess I've just been lucky.

- Byron
bfollowell is offline   Reply With Quote