Title:
Source code file should not need special charset encoding instructions for them to compile properly
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/CannotReproduce
Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)
Created: 10/07/2012
Components: General Server
Versions: 10.0
Failure Type: Data Corruption
Found In Build/Fixed In Build: Final /
Priority/Frequency: Critical / Most users will encounter
Locale/System: English / Win All
Vote Count: 2
Problem Description:
If a source code file uses - for example - UTF-8 encoding, then one needs to TELL the CF compiler this, with s <cfprocessingdirective> tag.
Steps to Reproduce:
Put some non-ASCII-equivalent UTF-8 text into a CFM file and compile it, inspect results. EG, something like this:
<!---<cfprocessingdirective pageencoding="UTF-8">--->
<cfset message = "???? ??????">
<cfoutput>#message#</cfoutput>
Actual Result:
हैलो द�निया
Expected Result:
???? ??????
Any Workarounds:
Don't care. Should just work. Any text processor worth its salt (even NOTEPAD) can just work it out for itself. CF should be able to as well.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3342141
External Customer Info:
External Company:
External Customer Name: Adam Cameron.
External Customer Email:
External Test Config: My Hardware and Environment details:
Attachments:
Comments: