ja, tokenizing works like this:

C:\> kix32 /t myscript.kix

this produces a file called "myscript.kx" (note the new extention .KX) ... this file contains byte code, looks like this:


Õ�Ö•ÀœÏ ƲŤֳï¢Ë¨ÚµÆ©Ï»ç°Ù·Ó¼Ë¸ä§Ò Ò·Ù­ûžìŸö™÷«ùŒââú÷÷8Д_ƒË€
Ì�ÝŽá‡ó„å—ò®ì‰å‰Õ–ù”ù–øø2î£Â¡É Ϋç†è�ú›ü™ÚµÛ½Ô³Æ´Õ¡È§ÉÉï÷Ó;´h;
T2F1P"GV?\.A2];OD-C'H?LS&T&C-Yjkm_b~ct({vvVw`ÙA$W<H'WW›qh�‚‚M

your standard unreadable blob, then you can run this tokenized file back through kix32 like this:

C:\> kix32 myscript.kx

Depending on the script, and what its doing, you can get anywhere from 0 to 50% "compression" in size ... plus its already mostly "pre-parsed", so it should be faster ...

-Shawn