On Friday, July 18, 2003, at 10:50 AM, Robert Ernens wrote:
Problem with email has been fixed. The default options in IC for body and
header encoding of SMTP messages were conflicting with the conversion made
by A4D in creating the output message. Works fine now.
Bravo.
Regarding the issue with javascript:
1. no encoding problem with extended characters when using A4D to output
database information to browser except for the Euros sign that never
displays correctly.
Please enter that as an issue at http://www.aparajitaworld.com/mantis so I can take care of it.
2. problems still exists when going through javascript :
The A4D method is in a library. The method creates inline javascript in the
html output file which is sent to the browser. When looking to the source of
the page, extended characters are encoded :
"12 résidence du Golf"
When the javascript function populates the form fields with these value, the
address field displays "12 résidence du Golf"
You need to do this in your Javascript function:
$encoding := get output encoding set output enconding(A4D Encoding None)
// body of Javascript code here
set output encoding($encoding)
This will prevent Active4D from converting special characters to HTML character entities.
Regards,
Aparajita Victory-Heart Productions [EMAIL PROTECTED] www.aparajitaworld.com
"If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoylibrary.com
