Title:
Bug 77177:(Watson Migration Closure)this comes up every so often over the year & just popped up again today: cf can't find files (cf, image, etc
| View in TrackerStatus/Resolution/Reason: Closed/Won't Fix/LowImpact
Reporter/Name(from Bugbase): Paul Hastings / PaulH (PaulH)
Created: 05/12/2009
Components: Localization
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Some users will encounter
Locale/System: English / Platforms All
Vote Count: 1
Problem:
this comes up every so often over the year & just popped up again today: cf can't find files (cf, image, etc.) that are named using languages that use a non-ANSI charset (like unicode). on windows the file names get garbaged (ie the thai named ???.cfm becomes ???.cfm) & cf can't find them. this is a cf issue as IIS can serve similarly named HTML files.
i have a vague recollection that if the server's default locale corresponds to the language used to name the file (ie the example above might work if server OS's locale was th_TH) but this won't do for apps that have to support many locales.
i know that the workaround is not to use non-english to name files but sometimes that simply won't work. i especially foresee problems as cf starts to handle more Office type documents that can be named pretty wildly by clerical staff.
Method:
create a cf file named in any non-ANSI language on an en_US server. try loading that file.
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3038529
External Customer Info:
External Company:
External Customer Name: PaulH
External Customer Email: 00EE238442D680B29920157F
External Test Config: 05/12/2009Attachments:
Comments: