Thread: PRS-950 PRS+ Font Help
View Single Post
Old 06-08-2011, 10:31 AM   #40
anamardoll
Chasing Butterflies
anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.anamardoll ought to be getting tired of karma fortunes by now.
 
anamardoll's Avatar
 
Posts: 3,132
Karma: 5074169
Join Date: Mar 2011
Location: American Southwest
Device: Uses batteries.
Quote:
Originally Posted by jackie_w View Post
This is all very odd. I've just checked all my PRS+ css files. All 20 of them have ANSI encoding, not UTF-8 without BOM. I've never had a problem with any of them on my PRS650 (or PRS505 for that matter).

Still, if your solution works for anamardoll, all well and good
I can explain this, maybe?

When I went through Notepad++, I noticed that the ONE css of mine that had ANSI encoding worked fine -- that was Fontina in this case. Since EVERYTHING ELSE I had was broken and bolded, I thought that the Fontina one was a fluke of the font style. (Like, maybe the bold Fontina was identical to the regular Fontina.)

So it's probable, based on these data points, that ANSI encoding works and UTF-8 without BOM works, but UTF-8 be itself does not.

Thank you ALL for all your help in this.
anamardoll is offline   Reply With Quote