K-Meleon :: Extensions

Extensions : K-Meleon Forum

All about K-Meleon extensions.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=disrupted]
desga, i'm not sure if this will work because it will be a function setting a command for a different function so guictrlsetdata will not know what gui to modify..i'm doing a slight update for kem(it will be a surprise[img]http://necb.bizhat.com/kmeleon/icon_wicked.gif[/img]) and test adding the seperate function

actually matt after struggling with localising autoits for more than 3 months, i came to the conclusion that the best way is that for every language; the script is translated just as you've mentioned..it's not very hard..the text that will need translating in every script is very little..mainly labels and buttons. then the script is compiled and uploaded to a seperate folder..

for example german extensions:
kmext.sf.net/files_de/
etc

the slight problem which will need efforts form everyone is translating all pages to all languages supported by km..that is:
es, de, fr, pl, and ru

the translators will be responsible for:
1- maintaining the translated pages for their language
2- translating autoit scripts and compiling them

extensions which are chromes and macros only do not need to be localised and uploaded to the localised files folder(files_es, files_de etc) as many chrome(mozilla) have the locales and if not it's very easy to add a locale nside the jar and make a kml for the macro

translating and compiling autoit is very easy..just translating the few lines necessary in the script and compiling with autoit..for every extension, it won't take more than a minute ..this way better solution than messing up the scripts and rewriting everything so it can work from an external locale file.. using locales is alright for macros..in jars, it's no problem..the locale can be added inside and identified in the manifest.

just remember those guidelines for compiling autoit
1- the compiled file (exe) name must not be changed because it's called from the macro and sometimes it's called from other scripts
2- universal scripts(those that work on all windows version) must be compiled in ansi mode
3- scripts for nt must be compiled in unicode
4- scripts for windows 9x must be compiled in ansi

when you open the auoit compiler, just select ansi or unicode radio button before compiling..or a nice way i do it through the context menu of au3 scripts is adding 2 commands for au3 files in folder optons>file types
first command"compile in ansi": "I:\program files\autoIT\Aut2Exe\Aut2ExeA.exe" /in "%l" /icon "I:\program files\autoIT\Aut2Exe\Icons\main9x.ico"

second command "compile unicode": "I:\program files\autoIT\Aut2Exe\Aut2Exe.exe" /in "%l" /icon "I:\program files\autoIT\Aut2Exe\Icons\main.ico"

the problem is who is willing to participate in the project.
i can translate autoit scripts into german but that's about it..my crappy german is not good enough for translating a website.. maybe gunter can help :P

french will be for alain, desga and aniatziag can do spanish, and anyone from russian team will do the russian(watsonrus or alex) and ofcourse you will do polish :)

remeber kmext is an open project for anyone to join in just like kmeleon, and several people have all the site details(passwort/ftp etc)

the pages are not too many..maybe 12 or so with not that much text either..mainly focus on extension pages and help, kplugins, plugins and disclaimer and credits pages are not important/not much to translate

if you like to translate the scripts and compile+ translating kmext.sf.net, i'll send you site ftp so you can upload..my email is openbsd6 AT googlemail , or you can contact gunter who has all the details.

here's a preview of what i hope will become of kmext one day:
[url=http://kmext.sourceforge.net/int-preview2.htm]http://kmext.sourceforge.net/int-preview2.htm[/url][/quote]

K-Meleon forum is powered by Phorum.