From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Mothra and <style> tags
Date: Sat, 26 Aug 2006 22:08:19 -0500 [thread overview]
Message-ID: <81d9ff2e8bbbc339227934e9af41ccb6@quanstro.net> (raw)
In-Reply-To: <3ca3b662696954350b24db0c30e75551@hamnavoe.com>
styles are supposed to be parsed with the same rules as scripts.
i realize that mothra doesn't use libhtml, but there's a patch on
sources -- /n/sources/patch/libhtml-lexscript -- that fixes script
parsing for libhtml, which may be helpful.
- erik
On Wed Aug 23 10:57:19 CDT 2006, 9fans@hamnavoe.com wrote:
> > case Tag_style:
> > break;
>
> This will cause the tag itself to be ignored, but the text following the
> tag will still be treated as displayable unless you do something to stop
> it. That's why I suggested a loop calling pl_gettoken() until it returns
> an ENDTAG with g.tag==Tag_style.
prev parent reply other threads:[~2006-08-27 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 11:28 Gregory Pavelcak
2006-08-23 12:57 ` Richard Miller
2006-08-23 14:37 ` Gregory Pavelcak
2006-08-23 15:53 ` Richard Miller
2006-08-27 3:08 ` erik quanstrom [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81d9ff2e8bbbc339227934e9af41ccb6@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).