problemm with pound £ sign

D

diablo

Hi

I have this html/script

<td width="100" valign="top" class="sb_text">Price:
<b>£<%=mid(formatcurrency(rs.fields("pcost"),2),2)%></b><br /></td>

Now on some pages the pound £ is displayed but on others it comes out as a
'?'

Any ideas?

Kal
 
T

Toby Inkster

diablo said:
Now on some pages the pound £ is displayed but on others it comes out as a
'?'

Check the charset parameter on your Content-Type HTTP header.
 
D

diablo

diablo said:
Hi

I have this html/script

<td width="100" valign="top" class="sb_text">Price:
<b>£<%=mid(formatcurrency(rs.fields("pcost"),2),2)%></b><br /></td>

Now on some pages the pound £ is displayed but on others it comes out as a
'?'

Any ideas?

Kal

By the way this only happens in Firefox - it is ok in IE
 
A

Alan J. Flavell

Deciding to do something for the good of humanity, diablo


&pound;

Well, yes, that rates to solve the immediate problem; but the
immediate problem looks to me to be a symptom of a failure to properly
specify the character encoding (charset= attribute) of the page in
question. Unless and until that fault is addressed, the original
poster must expect to get analogous problems in other places too, into
the future.

I note that the original poster said elsewhere that:
This is always a Big Red Warning Sign. IE has a dirty habit of doing
what it guesses the author intended, instead of doing what the author
actually asked for. As such, IE should NEVER, repeat *NEVER*, be used
as any kind of test for correctness. Mozilla (or firefox if that be
your preference), on the other hand, does what it is told, rather than
what it guesses it ought to have been told instead. Bottom line:
design it for the WWW, make it work with Mozilla first, and then
verify that MSIE also gets it right. Never vice versa. This cannot
be stressed too strongly, IMHO.

I think it's fair to say that MSIE is the only browser(-like object)
that feels it can ride roughshod over the interworking rules in this
way. Some other browsers do have various kinds of error fixup behind
the scenes, but, if you don't make any errors, those fixups should
never be provoked. To put it in different words: design first for
the WWW (with the limitations of MSIE in mind), as part of your basic
structural design. Verify with actual browsers (and particularly with
MSIE) afterwards, as part of your quality control measures. Muddling
these two aspects of web design, i.e fiddling around until the page
merely looks right on a browser or two, is no substitute for knowing
what you're doing.

YMMV, IMHO and bar. hth.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,482
Members
44,901
Latest member
Noble71S45

Latest Threads

Top