Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Odd Custom Tag Charset Behaviour
1 view
Skip to first unread message
McGarnagle
Feb 1, 2005, 12:38:56 PM2/1/05
to
Hello, I'm having some difficulties with a custom tag I'm working on. It
basically generates an english and french layout for applications, and uses
defaults for META elements such as <meta name='dc.title'>, etc. The problem is
as follows... when the tag is used in french, and the calling app overrides the
dc.title value, french characters appear OK. When no dc.title value is
specified and the tag uses the default value, the french chars appear garbled
in the processed page. Here is the code in the custom tag that sets the
default: <cfparam name='attributes.title' default='Secteur des services
int?gr?s'> Here is what is generated: <meta name='dc.title' content='Secteur
des services int??gr??s'> The default charset of CF server (6.1MX) has been
set to iso-8859-1, and I've used the <cfcontent> and <cfprocessingdirective>
tags to no avail. To sum this up, all french text appears ok EXCEPT when the
calling page uses one of the default values set in the tag using <cfparam>.
Help?
basically generates an english and french layout for applications, and uses
defaults for META elements such as <meta name='dc.title'>, etc. The problem is
as follows... when the tag is used in french, and the calling app overrides the
dc.title value, french characters appear OK. When no dc.title value is
specified and the tag uses the default value, the french chars appear garbled
in the processed page. Here is the code in the custom tag that sets the
default: <cfparam name='attributes.title' default='Secteur des services
int?gr?s'> Here is what is generated: <meta name='dc.title' content='Secteur
des services int??gr??s'> The default charset of CF server (6.1MX) has been
set to iso-8859-1, and I've used the <cfcontent> and <cfprocessingdirective>
tags to no avail. To sum this up, all french text appears ok EXCEPT when the
calling page uses one of the default values set in the tag using <cfparam>.
Help?
PaulH
Feb 1, 2005, 11:28:35 PM2/1/05
to
maybe you missed cfprocessing in the cftag itself?
0 new messages