KMeleonWiki > Resources
The available resources are grouped into different categories depending on what you want to do.
The best source for K-Meleon information is in the Documentation section. There is also the (dated) User's Guide and Reference Manual. Among the external K-Meleon resources you can find some links to other general K-Meleon pages?.
The skinning tutorial shows you how to install a new skin that you have downloaded from the KMeleonThemesWiki page. 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 resources page has links to skins and themes pages? located throughout the web. To customize your Windows desktop or personal web page there is 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 edit these files through the PreferencesDialog. Beginners should use caution when editing these files and it is helpful to create a test profile for extensive customization.
Much of K-Meleon's behaviour can be altered through the PreferencesDialog. 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 in the following documents.
The skinning tutorial shows you which files to edit to make K-Meleon look the way you want. Visit the GraphicalTools? page to see a some of the recommended applications that can be used to help create K-Meleon themes.
K-Meleon uses Gecko, the rendering engine from Mozilla.org, and should be detected as such. You should use K-Meleon to see how Gecko handles your pages, not how K-Meleon handles your pages. Gecko aims to be fully standards compliant. If K-Meleon fails to follow the standards due to limitations in Gecko (and thus is also visible in Mozilla and/or mfcEmbed) you should report your findings to bugzilla. If K-Meleon is the only browser that fails to follow the standards on a certain page, it should be reported to our bug database. Never ever try to get K-Meleon to "work around" bugs we have. Write standards complaint pages and let us know if we fail to handle them correctly. That's all.
Using the Neptune plug-in from Mead, one can have K-Meleon display some pages that require the use of ie for proper operation. I came here to find out how to do this better, so someone who knows will have to finish this description.