I can't give you any specifics, but I set all my databases for UTF-8 character storage. Saves time later when a client says that they need to expand into Korea. :-)
Just remember that AJaX isn't anything new. At the risk of (slight) oversimplification, it's nothing more than a way to spawn a separate request via JavaScript. The request target can store data just like any page called through a "standard" URI call. I've /never/ had any charset trouble except for what I mentioned. And, to be clear, in that case I was returning an extended character (an accented "e") that I hadn't coded for. It wasn't the other way around. On 5/12/06, Rey Bango <[EMAIL PROTECTED]> wrote: > LOL. Thanks Rob. I'm trying to do my homework before I fall into a pit. > > I appreciate the feedback. Anything that I should consider in terms of > data storage in SQL Server or MySQL? > > Rey... > > Rob Wilkerson wrote: > > I'd first try it and see what happens. The only time I've ever had a > > problem was when I had to return XML from an AJaX call and it was > > pretty easy to get around by specifying the charset as you listed: > > > > > > <cfprocessingdirective suppresswhitespace="true"> > > > > <cfcontent type="text/xml; charset=UTF-8" reset="Yes" /> > > > > <cfoutput> > > #toString ( getProfileXML ( URL.profile, URL.version, URL.directory ) > > )# > > </cfoutput> > > > > </cfprocessingdirective> > > > > Took me longer than it should have to catch it, but once I realized > > the problem the fix was easy. And you've already realized the fix - > > even if you didn't quite know what it fixed. :-) > > > > > > On 5/12/06, Rey Bango <[EMAIL PROTECTED]> wrote: > > > >>Hi everyone. I'm doing my best to learn about Ajax and development of > >>web apps using this architecture. I recently read this: > >> > >>"Ajax uses UTF-8. Normal forms are sent using the encoding of the parent > >>page. Thus a SJIS encoded page will default to sending form content > >>encoded in SJIS. Ajax submitted forms on the other hand will be sent as > >>UTF-8. If for some strange reason, UTF-8 is not the character set of > >>choice for the server, this will require a solution such as the server > >>recognizing and translating UTF-8 responses to a desired character > >>encoding." > >> > >>The line that immediately jumped out at me was this one: > >> > >>"If for some strange reason, UTF-8 is not the character set of choice > >>for the server, this will require a solution such as the server > >>recognizing and translating UTF-8 responses to a desired character > >>encoding." > >> > >>Does this mean that IIS or Apache have to be explicitly setup to handle > >>UTF-8? If so, how? I've never had to deal with since I've not worked on > >>international sites so this is new to me. > >> > >>I know I can set the charset to UTF-8 for a specific page via the > >>following line: > >> > >><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > >> > >>as well as setting up CF pages to use UTF-8 as explained here: > >> > >>http://mxblogspace.journurl.com/users/admin/?mode=article&entry=7288 > >> > >>but again, I'm concerned about my web server not being configured to > >>handle that. > >> > >>Also, what about SQL Server? Does that have to be configured in some > >>special way if I'm receiving AJAX data in UTF-8? > >> > >>Thanks, > >> > >>Rey... > >> > >> > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240331 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
