quotes in text field are not diplaying properly on the generated asp

Hi All,

I am running into this issue wherein any special characters \ quotes etc. are not displaying properly on the generated asp. They basically display in their friendly names as ‘ etc.

As of now, what I have done is to use VFE instead in such fields and made them display properly however using text fields is highly desirable. I am sure there is another better solution to the issue.

Please advice.

Find more posts tagged with

Comments

Adam Stoller

Hi All,

I am running into this issue wherein any special characters \ quotes etc. are not displaying properly on the generated asp. They basically display in their friendly names as ‘ etc.

As of now, what I have done is to use VFE instead in such fields and made them display properly however using text fields is highly desirable. I am sure there is another better solution to the issue.

Please advice.

For clarity if nothing else - you're talking about something that was a non-VFE textarea or a text-field? and the actual typed in contents had entities manually typed into them?

And you're processing these fields with a PT that gets the value of the field and does what with it?

It's possible your PT was doing an extra level of encoding the contents of the field such that something like ‘ became &lsquo; and thus the resulting presentation in the browser was the entity instead of what it was meant to represent... just a thought.

moonkhanna

Hi Adam,

Thanks for looking into the issue. Basically, the user is either typing manually or copying from word into these fields.

I checked for the encoding part. It seem both the PT and DCT use UTF -8 encoding. My browser also seems to be using Unicode. What else can I check for?

In my PT, I am just getting the value of these fields and displaying as it is. No changes there.. I can filter out some of these using regex but that does not seem to be an optimal solution for the end user as the end user wants to just use any possible character.

ISCBorisB

Hi Adam,

Thanks for looking into the issue. Basically, the user is either typing manually or copying from word into these fields.

I checked for the encoding part. It seem both the PT and DCT use UTF -8 encoding. My browser also seems to be using Unicode. What else can I check for?

In my PT, I am just getting the value of these fields and displaying as it is. No changes there.. I can filter out some of these using regex but that does not seem to be an optimal solution for the end user as the end user wants to just use any possible character.

Microsoft and it's moronic "smart quotes" is your problem. Take a look at this [thread=21410]thread[/thread] for discussion and proposals

moonkhanna

Hi ISCBorisB,

Thanks for your response. Yes, I saw your post on this. I am going to try the Demoroniser however I really feel, there is something we are missing here. Some quick and easy solution like the Microsoft compatible font kind of thing.. I will be researching this further..I will post back if I find something simpler

Best Regards,

Munish Khanna

ISCBorisB

Hi ISCBorisB,

Thanks for your response. Yes, I saw your post on this. I am going to try the Demoroniser however I really feel, there is something we are missing here. Some quick and easy solution like the Microsoft compatible font kind of thing.. I will be researching this further..I will post back if I find something simpler

Best Regards,

Munish Khanna

Here is "quick and easy" if you want it...In Perl context (PT for example)

$s =~ s/\x91/'/g;
$s =~ s/\x92/'/g;
$s =~ s/\x93/"/g;
$s =~ s/\x94/"/g;

As far as I know outside of MS Office there is no software that supports MS "smart quotes". That includes IE as well, go figure

moonkhanna

Hi ISCBorisb,

Thanks for your post. I feel, my issue is not just with the Smart Quotes but other characters as well. For eg. the below text -
"w'o'ot!" uh huh!Ê®~}~YA,!!

many of these chracters are not being interpreted fine by the PT but I am not sure right now as I do not have the version of the DCT and PT in place which was throwing these characters badly. I will get them in place and get back on whats actually happening.

Best Regards,

Munish Khanna

moonkhanna

Hi ISCBorisB,

Just so you know, I was able to resolve my issue with use of UTF-8 encoding at all possible places and your provided workarround.

Thanks very much for your help on the issue.

Best Regards,

Munish Khanna