Hi Paul,
PH> in theory, yes sure. but locale resource data/implementation varies version
to
PH> version & i suppose OS to OS--even something as simple as the terminology
PH> differs OS to OS (and sometimes version to version).
PH> any chance the host is setting the file encoding?
Hmm, I doubt so. But my hope is to find the source of the problem,
because theoretically it should be running fine the way I thought.
>> <cfscript>
>> dDate1 = CreateDate(now());
PH> that works? if it does it's redundant, now() should suffice.
>> dDate2 = CreateDate(DateAdd('yyyy', 1, now()));
PH> that works? just dateAdd should be ok.
Was to late for me write that last reply. For sure I just juse now()
and DateAdd() without CreateDate.
>> Even without using those vars as formfield-values the umlauts are
>> screwed up...
PH> ?? that script only produces numeric values for your day/month/year bits.
am i
PH> missing something?
No your missing nothing. It's absolutely correct. Those values are
just filled into corresponding formfields for start and end day,
month, year.
PH> btw are you using cfprocessingdirective & cfcontent both set to use
iso-8859-1?
For now I only used
<cfcontent type="text/html; charset=ISO-8859-1" />
<cfset setEncoding("URL", "ISO-8859-1") />
<cfset setEncoding("FORM", "ISO-8859-1") />
in Application.cfm.
I would imagine that the use of cfprocessingdirective is only useful
when you want to force the processing encoding on one special page. Or
does one have to use it always when not using utf-8?
Patric
--
Patric Stumpe
mailto:[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:231565
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
