|
From: Jesse V. <je...@6t...> - 2003-08-05 17:26:22
|
OK, I'll take a look at it when I get a sec. I got a new machine, and don't have Linux on it yet, so it might take a few days before I can test that part of it. As for the missing semi-colons, I went through a bunch of the files and fixed them up, but missed some. I'll fix up the functions.image.js one. What we really need (and has been talked about before) is a good way to find missing semi-colons on the fly and fix them at compression time. I'd love to add that, but I'm not sure of a good routine to determine when a semi-colon is missing. Jesse Kevin wrote: >Hi, > >I tried the Java compressor on Linux and had some problems. The >config xml wouldn't work if it had Dos line terminations '\r\n'. So >I had to convert to '\n'. I would have thought since a browser can >parse HTML or XML no matter what file type is stored on the server >then the Java compiler should take a xml of either Dos or Unix origin. > >Once compressed for a full ie/dom/ns4 api and a functions.image.js >include, more problems. I detected a semicolon is required on line >121 of functions.image.js and ns4 doesn't work at all. Sorry no >time to investigate the ns4 else statement in the compressed file. >I've attached an example and compressor components. > >- >Kevin > > |