View Single Post
Old 08-28-2008, 07:20 PM   #187
porkupan
Fanatic
porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.
 
porkupan's Avatar
 
Posts: 556
Karma: 1057213
Join Date: Sep 2006
Location: North Eastern U.S.
Device: Sony Reader
Quote:
Originally Posted by Valloric View Post
That's it, from what I can see. You can only mess up one (or more) of those steps, I can't see where else you could go wrong. I got everything working on my first try, in a whole 15 minutes. No bricking, nothing.
I agree that it's not difficult at all. But there is a couple of issues. First, you have to get a hold of FontCreator. Preferably a licensed copy so no one gets in trouble. Second, how do you propose to automate this process through the PRSCustomizer tool? You would need to know the structure of the TTF file, where does the Font Family Name fit, what name to use for the file, which font you are replacing. All sorts of complications for a tool that was not intended for this sort of task.

You can easily make a separate set of fonts manually, and stick it into the FONT directory on the card. But automating this seems like an overkill.
porkupan is offline   Reply With Quote