From: dorayme on
In article
<edc8ce19-5265-4eaa-9f2d-9e9586ee21bb(a)k41g2000yqm.googlegroups.co
m>,
Karsten Wutzke <kwutzke(a)web.de> wrote:

> On 4 Feb., 23:37, dorayme <doraymeRidT...(a)optusnet.com.au> wrote:
> > In article
> > <ef01ebd2-06c5-43ff-9b4c-18e7cdef3...(a)u41g2000yqe.googlegroups.co
> > m>,
> >  Karsten Wutzke <kwut...(a)web.de> wrote:
> >
> > > does CSS have a selector that allows the selection of content? I want
> > > to syntax highlight specific keywords in my pre and code tags, ideally
> > > operators, numerics, strings, and comments, too.
> >
> > No.
> >
> > --
> > dorayme
>
> :-) I love concise answers.
>
> So using spans is the only pure HTML/CSS way to go?
>

Or perhaps em, depends on what you want to be saying, as it were.

You know, it is not so hard to stick these element tags in if you
know in advance what they are for, using Find and Replace, maybe
even a bit of GREP.

And as for the markup being being hard to read, well, mark-up
does not have to be very beautiful. And, it might be that its
beauty is enhanced in fact and that you need to reassess the
aesthetics in this matter. Form married to function is an
intoxicating and exciting cocktail...

Go forth young man and think sideways and <b>ly. <g>

--
dorayme
From: rf on

"dorayme" <doraymeRidThis(a)optusnet.com.au> wrote in message
news:doraymeRidThis-F526EF.21021605022010(a)news.albasani.net...

> Go forth young man and think sideways and <b>ly. <g>

dorayme of here you are in gravely danger to be splitting an
<i>nf<i>n<i>t<i>ve.


From: Karsten Wutzke on
On 5 Feb., 11:19, "rf" <r...(a)z.invalid> wrote:
> "dorayme" <doraymeRidT...(a)optusnet.com.au> wrote in message
>
> news:doraymeRidThis-F526EF.21021605022010(a)news.albasani.net...
>
> > Go forth young man and think sideways and <b>ly. <g>
>

Hehe I'm not THAT young anymore, but thanks for the technical info :o)

Karsten
From: Harlan Messinger on
Karsten Wutzke wrote:
> On 5 Feb., 11:19, "rf" <r...(a)z.invalid> wrote:
>> "dorayme" <doraymeRidT...(a)optusnet.com.au> wrote in message
>>
>> news:doraymeRidThis-F526EF.21021605022010(a)news.albasani.net...
>>
>>> Go forth young man and think sideways and <b>ly. <g>
>
> Hehe I'm not THAT young anymore, but thanks for the technical info :o)
>

It's just as well. Suppose you could use CSS to specify boldface for the
keyword "int", and you found it bolding the "int" in "print", "tint",
and "intention".
From: dorayme on
In article <7t435dFhjpU1(a)mid.individual.net>,
Harlan Messinger <hm.usenetremoverthis(a)gavelcade.com> wrote:

> Karsten Wutzke wrote:
> > On 5 Feb., 11:19, "rf" <r...(a)z.invalid> wrote:
> >> "dorayme" <doraymeRidT...(a)optusnet.com.au> wrote in message
> >>
> >> news:doraymeRidThis-F526EF.21021605022010(a)news.albasani.net...
> >>
> >>> Go forth young man and think sideways and <b>ly. <g>
> >
> > Hehe I'm not THAT young anymore, but thanks for the technical info :o)
> >
>
> It's just as well. Suppose you could use CSS to specify boldface for the
> keyword "int", and you found it bolding the "int" in "print", "tint",
> and "intention".

Well, just as that would be something to watch out for when
making your F&R/GREP pattern, it would presumably be something
you would be able to watch out for and cope in the possible world
where one could style for keywords. Possible worlds are many and
some of them would be very sophisticated.

--
dorayme