Code page & ActiveVFP internal configuration

Topics: Developer Forum, User Forum
Feb 4, 2012 at 11:34 AM

On regular VFoxpro if I do

? ASC('ç')
? ASC('Ç')
I get

231
199

but on activeVFP if i do

Code Page <%= CPCURRENT() %><br>
Cedilha up <%= ASC('Ç') %><br>
Cedilha low <%= ASC('ç') %><br>

The result on page is

Code Page 1252
Cedilha up 195
Cedilha low 195


That is the wrong char number, and on foxpro it's ok, but on activeVFP the asc returned isn't correct, I guess need some codepage configuration on ACVFP

Coordinator
Feb 4, 2012 at 6:30 PM
Edited Feb 4, 2012 at 6:31 PM

You'll have to figure this out - all the source code is there.  This is all regular foxpro, just being served over the web.  I think it's good to keep this in mind...

Feb 4, 2012 at 7:48 PM

I will go further in source code, could you please give some tips, on how the active page is parsed ?, I guess something is missing on the parser, that ignore some special characters like ç á ã and they aren't parsed correctly.

Where is the main parser ?

Feb 4, 2012 at 8:28 PM

I'm working on active source and I already discovered

Mergetext function, where the fox pro code is evaluate and tested with this

#

DEFINE crlf CHR(13)+CHR

(10)

texto = "<%= ASC('ç') %>"

mergetext(texto)

The result is correct the problem is before arrive here, somewhere between the file.avfp and here the character is changed, I really don't know where ? But this is one issue that turn this toll english only, Some help will be welcome to help other idiom users

 

Feb 4, 2012 at 9:02 PM

A good or bad news ?

 

The same happens with standard asp

Response.Write(Asc("Ç"))

 Return also the wrong code, this means that is something related to IIS or asp net configuration, Now the problem goes to other beaches....