On Fri, October 6, 2006 12:29 pm, tedd wrote: > No, that's not what I meant. I know how to convert DEC <-> HEX. > > What I was talking about is called a NCRs, or Numeric Character > References > > One could use the Unicode DEC value directly, such as: > > • > > or the Unicode HEX value directly, such as: > >   I think you meant x2022 a.k.a. (dec)8226 :-) 8226 or x2022 is the same number, so whatever it is, it should work the same. And maybe those will work the same as • on all modern browser now. But that was not my experience in the past. Perhaps you would care to extend your browsercam test to some regression testing of more ancient browsers -- on Mac OS. > Note, either will produce a bullet in most browsers. > >>But • is almost-for-sure *ONLY* going to "look right" on MS IE. > > Not true, for most (and all most current) browsers do render that > glyph correctly (other glyphs may vary), please review: > > http://www.browsercam.com/public.aspx?proj_id=289683 > > The first bullet is &149; (same as ALT 0149 on the windoze keyboard). > > The second is • and third is   > > Note all three produce a bullet -- oh and don't forget •, which > will produce the same result. > > tedd > > -- > ------- > http://sperling.com http://ancientstones.com http://earthstones.com > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
