Symbol appearing before £.

[Daverms]

Hi,

In one of our report we face this issue, like it is displaying the "Â" before £, Trademark and Registered symbols.

I tried setting the encoding as "UTF-8" using <cfprocessingdirective> , <cfcontent> and SetEncoding() functions.. But none of them were worked.

Can any one shed some light here?

[Dileep_NR]

Hi

Please use ASCII instead of   £

ASCII -   &#163;

[tooMuchTrouble]

first off, please don't use NCR. use the actual char.

most likely your encodings (cf page vs cf server) aren't matching.

what do you mean by "report"? cfreport?  where are these chars coming from? statict text? db?

[Daverms]

Hi Paul,

Thanks for the tip.

In server where can I set the encoding setting?. I saw one under the "CFMail settings" in Admin.

Ours is a simple html report served by VB Dll (which actually comes from Mainframes).

[tooMuchTrouble]

ah, so what role does cf play in this?

if the report's getting produced by VB, find out what encoding it uses (guessing windows-1252 or maybe less so, latin-1). since cf6, cf defaults to utf-8. i'm going to guess that you probably can't change the mainframe's encoding, so change cf's. stick a cfprocessingDirfective tag at the top of the cf page & set the pageEncoding option to whatever the html report is using (or just keep guessing until it looks ok).

[Daverms]

Hi Paul,

Thanks for the reply.

In VB6.0 we have the encoding set to "UTF-8" so as in ColdFusion end, I also tried having the <cfpreprocessingdirective> tag at the top of the page and the setencoding("form","UTF-8") functions before outputting the html.

But still that "Â" character appears before the pound and other html entities like ® and © symbols.

Let us know if we can try any other workaround(s).

Thanks again Paul!.

[tooMuchTrouble]

any chance i can see an example and/or the cf code?

i don't recall much, if anything, about VB. unless you've messed up the cf, i'd

have to call shenanigans on it for either messing up the output HTML encoding or

sticking in badly encoded symbols in the output.

[Daverms]

Hi Paul,

We figured it out. The issue was actually with the VB Code in parsing the quoted printable value.

Now it is resolved.

Appreciate your time and help!.