-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sender: [EMAIL PROTECTED] Precedence: bulk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" Although Embperl supports both Raw and Non-Raw processing of input, that doesn't handle situations where designers use both WYSIWYG and non-WYSIWYG editors (e.g. DreamWeaver and BBEdit). That's how I typically do my work (or in vi/vim), and I'd rather not program in DreamWeaver-encoded Perl. To manage this, you can wrap some tags in something that causes the browser ignore the contents. The most obvious one is <% ... %>, which most editors will take as referring to ASP code. This works great in DreamWeaver. However you can really only wrap it around Embperl tags that don't do any output. To get around that problem I wrote an Embperl input method that strips all <% and %> tags from the input prior to sending it for processing by Embperl. This allows Embperl commands to be embedded within ASP-style tags so that WYSIWYG editors won't touch them. If you're interested, you can download it from http://www.somewhere.com/software/. It's pretty tiny, the docs are larger than the code. P.S. Also on that page, although perhaps someone has already done this, are the diffs for vim's html.vim module. This version will switch to Perl mode whenever it's in an Embperl tag. Kee Hinckley Somewhere Consulting Group - Consultants without the cubes(tm) I'm not sure which upsets me more: that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's. -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.2 for non-commercial use <http://www.pgp.com> iQA/AwUBOEa+qyZsPfdw+r2CEQJ6hACg1HmqCo6vwHHTUZ7Hpq56B8MoHBQAoLXz aRVIPmb+ggTK/p3CYQT7HbQY =RXkg -----END PGP SIGNATURE-----
