According to Matthew Nuzum:
> > I've encouraged them to instead use HDL<span
> > style="font-size:8pt">3</span> instead. It looks better because it
> > doesn't increase the line spacing. They now have several of each
> > throughout the site.
> >
> > I just tested a search and found that none of the above show up in the
> > results. Only HDL3 shows up as a result for a search "hdl3".
> > HDL<sub>3</sub> and HDL<span style="font-size:8pt">3</span> are
> > excluded.
> >
> > I'm glad someone caught this. Can we have spans treated the same way?
> > I often use <span> tags with stylesheet rules in place of some HTML
> > equivs.
>
> ; It's a pretty easy fix: just add "|span|/span" to the end of the
> string
> ;passed to nobreaktags.Pattern("...") on line 85 of HTML.cc (in 3.1.6).
> ;I had put font tags in the list for this very reason, but I didn't put
> in
> ;span.
>
> ;I'm really ignorant when it comes to CSS tags in HTML, but are span
> tags
> ;just used for font and style changes which shouldn't trigger a word
> break,
> ;or are there other uses of <span ...> which should cause word breaks?
>
> ;In any case, it would probably make sense to have this list settable by
> ;config attribute, to allow adapting to varying needs and evolving
> ;standards.
>
> <span> tags have been around for ever, but they don't do anything.
> They're just a container. They're related to a <div> tag which implies
> a break. <span> tags should not imply a break and really should just be
> invisible to robots (IMHO). I'll make the change you recommended.
OK, I'll keep this in mind for future releases. Sounds like it should
be added to the distributed source by default, even if we add a settable
attribute for this.
> Couldn't we just as easily add the <sub> and <sup> tags? Or is that a
> quick hack in comparison to some other solution?
Yes, and yes. If you find it preferable that htdig never treat the <sub>
and <sup> tags as causing a word break, then by all means add them to
the nobreaktags pattern list. However, that doesn't work for everyone,
as I said before, and for a lot of uses of superscripts and subscripts
the current behaviour of htdig is correct. What I'm proposing is that
htdig essentially do both, just as it does for compound words using
hyphens or other valid_punctuation characters.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
