[NiLuJe]

@meem: Check the docs/packages provided. You pretty much don't have to do anything except extract an archive and rename a file or reboot your Kindle.

If you're trying custom fonts not already packaged, then it's easier and less error-prone to just rename them following the usual scheme (because there's a bunch of safety checks in the hack preventing you from running with missing fonts, which would potentially be bad). But if you prefer tinkering with the fonts config, you can do it too. I'm pretty sure we don't have to touch the encoding options, and at least I never heard anyone having to do it to fix something. I'm not even sure anything user-visible in the Kindle fwk rely on that. (Maybe the browser?)