Try putting on the
template that is giving you the problem. It may be that each template is
compiled using utf-8 on lucee unless a cfprocessingdirective on that
template indicates otherwise.
–
Get 10% off of the regular price for this years CFCamp in Munich, Germany
(Oct. 20th & 21st) with the Lucee discount code Lucee@cfcamp. 189€
instead of 210€. Visit https://ti.to/cfcamp/cfcamp-
2016/discount/Lucee@cfcamp
No, I tried it : no change.
It did work Under Coldfusion.
It seems that URLEncodedFormat always render under UTF8 with Lucee ?
(even if ISO-8859 is required)
Only that function URLEncodedFormat does that.
Rest of page is correct ISO-8859.Le jeudi 22 septembre 2016 13:58:40 UTC+2, Pierre Larde a écrit :
After migration from Coldfusion to Luccee,
I have a problem in the rendered value of URLEncodedFormat
Under Coldfusion I had an ISO url code (%E9 )
Under Lucee I have a UTF8 url code. (becomes : %A9 )
Files code have not been modified, just a copy.
Why this change ?
How to fix this ?
I added the iso-8859-1 in the Lucee admin server charset. (as default)
Same result
And, from the database, the field value render correctly if it is displayed
in the page (iso-8859-1)
and get an utf-8 value if it is rendered Inside the URLencodedFormat
Then this does not come from the database or the datasource.
ville=#URLEncodedFormat(p_ville)#’ is displayed in UTF-8
and
#p_ville# is displayed in iso-8859-1
It seems, there is a problem with the URLEncodeFormat function.
It always render in UTF-8
Thanks for any help, this is a point where I will have to go back to
Coldfusion if no solution.
Thanks to all.
Pierre.Le jeudi 22 septembre 2016 13:58:40 UTC+2, Pierre Larde a écrit :
After migration from Coldfusion to Luccee,
I have a problem in the rendered value of URLEncodedFormat
Under Coldfusion I had an ISO url code (%E9 )
Under Lucee I have a UTF8 url code. (becomes : %A9 )
Files code have not been modified, just a copy.
Why this change ?
How to fix this ?