GBP (£) sign

Chris Loftus wrote:
> The db driver is MySQL (3.x), I'm pretty sure the encoding is 'latin1'?

well latin1 should handle your currency symbol. what driver (jdbc or odbc)?

i forgot to ask if you've used the cfprocessingdirective to change cf's encoding
for the form & display pages?

bump

The db driver is MySQL (3.x), I'm pretty sure the encoding is 'latin1'?

Stressed_Simon wrote:
> Try changing it to £ instead that is the HTML entity for it!

depending on the application that's not a good solution. won't sort right, can't
be searched for properly (without some form of massaging), etc. and that still
leaves the underlying encoding issue which will almost certainly bite him again
somewhere down the line.

Thanks Simon, £ works :-)

Is there a function that will make this process more dynamic?

Try changing it to £ instead that is the HTML entity for it!

Chris Loftus wrote:
> I am currently working on an intranet system that uses ColdFusion and mySQL,

what version of mysql? what db driver?

> Simply put, when I insert a ? (GBP) sign into the database (processed with
> ColdFusion), and then output it using CF, it displays a small square box '?'

verdana does contain that glyph but you can also see empty boxes when the
encoding is just a bit off.

> (as if the font doesn't have that character, Verdana, 10px). I have checked the
> value in the database using phpMyAdmin, and it displays the GBP sign correctly.

doesn't count--if the db's mangling that data, it's un-mangling it as well.

> The page is using XHTML 1.0 Transitional doctype and 'iso-8859-1' charset.

if you mean via metaheaders, doesn't matter to cf.

> I have come across this
> http://www.experts-exchange.com/Software/Server_Software/Web_Servers/ColdFusion/
> Q_20983733.html using Google, however I have tried it twice without success.

ignore the metaheader bits, nonsense as far as cf goes (but always add them for
forensic reasons, screen readers, etc.).

> We are running ColdFusion 7 with Windows Server 2003.

ok, cf6 & above default to utf-8, so that's probably where the "minor" encoding
mismatch is happening (or the db driver). have you tried

<cfset setEncoding("form","iso-8859-1")>

to your application.cfm?