KMeleonWiki > Resources
The available resource are grouped into different categories depending of what you want to do.
The best source for K-Meleon information is the Documentation section in our KMeleonWiki. There is also the (dated) User's Guide and Reference Manual. Among the external K-Meleon resource you can find some links to other general K-Meleon pages?.
The skinning tutorial shows you have to install a new skin that you have downloaded from the KMeleonThemesWiki. You can also download (older) Skins? and help update them to full themes. Extra Throbbers? can be downloaded and used together with any skin or theme. The external K-Meleon resource page have some more links to skins and themes pages?. To customize your Windows desktop or personal web page there are also a list of Icons, Buttons, and Banners for K-Meleon.
You can download translated versions of the K-Meleon menus from our Localization resource section. That is also the place where you should find links and pointers to help you localize the Mozilla part of K-Meleon.
This information is kept in the ConfigFiles. You can easily edit these files through the PreferenceDialog?, but you must really know what you are doing or things can be badly messed up.. Detailed information on how each of these files can be altered.. is not available?
A lot of K-Meleon's behaviour can be altered through the PreferenceDialog?. Even more can be altered by editing the PrefsJS?, UserJS, UserChromeCSS? or UserContentCSS? files directly. These files are read by the Mozilla/Gecko rendering engine, further information is available by reading Mozilla documents.
K-Meleon uses Gecko, the rendering engine from Mozilla.org, and should be detected as such. Never ever try to detect K-Meleon to "work around" bugs we have. You could use K-Meleon to see how Gecko handles your pages (not how K-Meleon handles your pages; that's not important) Gecko aims to be fully standards compliant. If K-Meleon fails to follow the standards due to limitations in Gecko (on thus also visible in Mozilla and/or mfcEmbed) you should report your findings to bugzilla. When K-Meleon is the only browser with problems it should be reported to our bug database. Write standards complaint pages and let us know if we fail to handle them correctly. That's all.