At 3:29 PM -0800 12/4/99, Mike Schienle wrote: >At 4:32 PM -0500 12/4/99, Paul Schinder wrote: >>At 2:11 PM -0700 12/4/99, Dick Applebaum wrote: >>>Mike >>> >>>Not a Perl problem, but an HTML feature... >>> >>>HTML considers <......> as Tags. >>> >>>Any tag that it doesn't understand it ignores. >>> >>>You can circumvent this by changing >>> >>> from....... < >>> >>> to......... < >> >> >>Wouldn't it be better just to fix the server so that it served Perl >>scripts with the right MIME type? > >Unless I'm missing something, wouldn't that interfere with handling >CGI's with the same extension? .pl files are set to "CGI-script" on >my server. Currently, I'm removing the extensions from the perl >files and serving them up with a <PRE> before including the file. >I'd like to not hassle with the encoding. I'm running my own server >using Tenon's WebTen. If you need to, either change the extension for CGI or change the extension for the scripts themselves. But won't WebTen key off type/creator instead of extension, or is it so much just Apache that they haven't given it that capability? > >>Having to encode all of the forbidden (there are more than just < >>and >) HTML characters in each Perl script you put on a web site >>would be a real pain, and anyone who downloads the thing in raw >>(Netscape calls it "source") mode won't be able to use the script >>as intended. The MIME types should be set so that Perl scripts are >>text/plain. > > >Mike Schienle Interactive Visuals, Inc. >mgs@ivsoftware.com Remote Sensing and Image Processing >http://www.ivsoftware.com/ Analysis and Application Development -- Paul Schinder schinder@pobox.com # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org