Can replicate that encoding thing on KM1.6
=> it's the file itself. UTF-8 exists with or without "BOM", as notepad++ calls it. That is some sort of hidden special character in the very beginning of the file. When I save the cyrillic text as utf8 "without", then KM shows gibberish, and if saved "with", it displays fine. Had the same prob with another text editor some time ago :-)
Some editors are just more intelligent than others...
James, unlike rodocop, guenter, dorian, adodupan, naruman and a few others I have no clue about installing addons yet, that's exactly the prob!
My only few bits of knowledge are so far:
" is necessary that NEW xpi-FF-addons think KM were a Firefox, otherwise they claim in about:addons to be "incompatible with KM75". Sounded like sort of faking the KM UA to fool the addon-install-process, provided I read that right...
And they said this pref also makes changes in install.rdf unnecessary.
On the other hand there are (very few) genuine "KM-addons", adodupan had created one awhile ago, and THOSE need that same pref to be FALSE!
Guess each addon-macro should include a little check if it's in first run or not, and depending on that should change this pref itself at first run. And afterwards perhaps reset it back how it was before.
Assuming that it's only necessary for installation, but haven't tested yet.
Another addon-pref is native Mozilla: "xpinstall.enabled"
That doesn't seem to mean much, only to prevent accidental xpi-installations when unknowingly clicking on an xpi-link, but then again, have read that would pop up a confirmation anyway? Would need some testing in KM itself. The web says local installs would work regardless of that setting, and once an addon is installed it doesn't matter anymore. There exists a whitelist for sites like mozilla-archive that work even if that pref is False.
Installed addons seem to be stored as list in one of the "extensions" prefs in about:config, otherwise the browser probably wouldn't know if it's first run or not... but haven't tested that stuff yet either...
Hmm... what else...
The xpi (and jar?) doesn't seem to work if a dll is included in a zipped "plugin" folder. But that folder can simply be placed outside, either in browser/extensions/plugins or in browser/plugins... but this is all more half-knowledge as certain from me at this point yet.
To change page encoding in a new tab:
Try if $OnLoadOnce helps? After the opentab-line insert:
You said you tried already with a separate macro to change charset, so that would be it.
The little catch is: this will be fired at the NEXT page load, which could just as well be another tab if several tabs are currently loading...
(sig) K-Meleon FAQ
(link missing in forum sidebar)
New to K-Meleon? What do you like? What not?
Edited 3 time(s). Last edit at 10/09/2015 12:47AM by siria.