Parsing rules

[Matt Neuburg]

On Sat, 3 Nov 2001 10:48:52 -0600, TQ White II <tq at justkidding.com> said:

>I do a lot of PHP and Javascript stuff with mySQL implications. That means
>that I do a lot of string processing, especially in PHP. As a result, I
>have a lot of strings that will become html tags later. That is, they have
>>  and <, as well as \ in them.
>I have had many situations where I rendered a page of code (a PHP class)
>with a minor change and spent a couple of hours debugging php language
>errors.
>I have found that sometimes a macro won't render until I stick an extra
>angle brace in a comment in the line before the macro. I have millions of
>'\r\n' strings that have their \'s stripped out by Frontier and I haven't
>been able to figure out what to do about them. Sometimes the extra angle
>brace trick works, other times, no

Not sure if this will help, but in general I've found it's not worth 
wrestling with Frontier's behavior when stretches of JavaScript are 
introduced. Frontier doesn't understand that the curly braces, 
quotes, and less-than signs inside a stretch of JavaScript need to be 
ignored. It's easier if you introduce the JavaScript during macro 
processing; that way it isn't evaluated again for macros and glossary 
items. See:

    http://drmatt.userland.com/webAdvancedStuff/javascript.html

m.

-- 

matt neuburg, phd = matt at tidbits.com, http://www.tidbits.com/matt
pantes gar anthropoi tou eidenai oregontai phusei