the conversion is complete and it works exactly like in firefox, i never convert an extension without testing it first on firefox and check how it works. if the conversion has limitations compared to firefox i'd mention that but there are no limitations and the only difference is that in firefox it opens a toolbarless window and in kmeleon it opens a new tab. that can be changed easily using kiosk mode but i thought people preferred tabs, you can see in the macro i tried with kiosk but it was annoying..why imitate when you can do better?
#exec($k_path."\\k-meleon.exe " .$kioskcomm. "". $imtransexec);
select text and select imtranslate and your text is translated instantly, you don't copy and paste and that's how it works exactly in firefox
compare in kmeleon
text selected:
text translated:
same with TTS. text selected and read out
same in firefox:
selected
and translated
the other thing missing from the extension is the chrome xul options dialog, i was begininng to make it work..see in macro
#$initlang=getpref( STRING, "imtranslator.dirParentFrom" );
#$tolang=getpref( STRING, "imtranslator.dirParentTo" );
#$localang=getpref( STRING, "imtranslator.locParent" );
those are meant to fetch the settings for from and to languages and then i found out the options dialogue is pointless because their api will always open in english to spanish and ignores language strings, so i'm not going to add extra meaningless code and a non-functioning xul just to make it identical to firefox without thinking
this is a test:
http://translation.imtranslator.net/widget2/?dir=fr/de&loc=en&text=merde%20merde
the above tells their api to choose translation from french to german, it doesn't matter and still opens using default english>spanish
so the only thing you are complaining about 'the conversion isn't complete' is that it doesn't open in kiosk and opens a new tab? if that's what you like i'll change it in the macro-np