Re: First stupid post of the year. [SOLVED]

All of these look the same for me in Opera under Linux. Character sets are not a browser war issue, they're a character set/font issue. Just because a character set supports a character, doesn't mean the character font exists. Cheers, Rob. On Mon, 2008-01-07 at 10:29 -0500, tedd wrote: > At 12:03 PM +0100 1/7/08, Nisse Engström wrote: > >How does the following pages compare? The display > >should be identical: > > > ><http://luden.se/test/t-1252.html> > ><http://luden.se/test/t-utf8.html> > > Nisse: > > No, there is quite a difference depending upon > the text encoding used in my browser (Safari). > > For example, using UTF-8 > > <http://luden.se/test/t-1252.html> > > produces nothing but repeating <?> (black diamond with question mark). > > Where as: > > <http://luden.se/test/t-utf8.html> > > Shows all the code-points correctly. > > --- > > Using Western (ISO Latin 1) > > http://luden.se/test/t-1252.html > > is correct, but > > <http://luden.se/test/t-utf8.html> > > is gibberish. > > > --- > Using Western (Mac OS Roman) > > http://luden.se/test/t-1252.html > > is almost correct (it has an Apple logo). > > and > > <http://luden.se/test/t-utf8.html> > > is gibberish. > > -- > > So, the browser wars move on to text encoding. > > Cheers, > > tedd > > -- > ------- > http://sperling.com > http://ancientstones.com > http://earthstones.com > -- ........................................................... SwarmBuy.com - http://www.swarmbuy.com Leveraging the buying power of the masses! ...........................................................