RE: HELP I'm drowning in a sea of encoding.
Can't think of any... you could be extra safe and be sure your database is set to the same encoding. I'll try and remember that. In this case there is no database involved; the app uses simple xml files. -- Ian Skinner Web Programmer BloodSource www.BloodSource.org Sacramento, CA - | 1 | | - Binary Soduko | | | - "C code. C code run. Run code run. Please!" - Cynthia Dunning Confidentiality Notice: This message including any attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and delete any copies of this message. ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241140 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: HELP I'm drowning in a sea of encoding.
> > Any advanced warnings of potential 'gotchas' would be most appreciated. Can't think of any... you could be extra safe and be sure your database is set to the same encoding. Then it's just a matter of remembering to set the type everywhere. You can put the setEncoding() in the Application.cfm, and set "url" var encoding there too... there was a wonderful post on internationalizing CF apps some time back but I can't remember where, or if was actually on this list, even. Peace, :Denny ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241096 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: HELP I'm drowning in a sea of encoding.
Ok, I've made my first attempt and it seems to be working well. I've added a cfprocessingdirective and cfcontent tags to the beginning of my file. http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> As well as the Content-Type meta tag in the html head section. Then in the form processing section of the page I have added a setEncoding function. Next I added an encoding line to where the xml is built. And finally, I have added charset parameters to my cffile tags. This all seems to be working, but is there anything I can added that would help in the stability of all this. This was just a single page test case. I am now off to apply these elements to all the pages of the full blown (albeit small) CMS tool. Any advanced warnings of potential 'gotchas' would be most appreciated. TIA -- Ian Skinner Web Programmer BloodSource www.BloodSource.org Sacramento, CA - | 1 | | - Binary Soduko | | | - "C code. C code run. Run code run. Please!" - Cynthia Dunning Confidentiality Notice: This message including any attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and delete any copies of this message. ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240990 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
RE: HELP I'm drowning in a sea of encoding.
I am finally back to working on this task. Ok 1st off tinyMCE isn't the most i18n friendly editor, it's a soup of different encodings. What encoding are you using? Are these chars making it out of tinyMCE ok? I believe they are, when I dump the form on the action page, the characters are there. I have played with a couple of encodings, windows-1252 and ISO-8859-1. I am trying to allow for MS-Word special characters such as curly quotes and em-dashes as well as foreign characters such as accented or umlauted vowels. - liberally use the usual encoding hints (cfprocessingdirective, cfcontent, setEncoding, etc.) - whenever you handle the form's content make sure the charset option of whatever tag you're using is utf-8. - make sure the xml is tagged as utf-8 Can anybody expand on these hints? Where one put cfprocessingdirective, cfcontent, setEncoding tags would, how does one use charset in a tag, and how does one fully tag an xml file to an encoding. - make sure tinyMCE is using utf-8 & the chars are surviving it, if changing editors is an option i'd go w/that wonderfully named FCK one This may be an option, but we have been using tinyMCE, mostly successfully, for some time. -- Ian Skinner Web Programmer BloodSource www.BloodSource.org Sacramento, CA - | 1 | | - Binary Soduko | | | - "C code. C code run. Run code run. Please!" - Cynthia Dunning Confidentiality Notice: This message including any attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and delete any copies of this message. ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240986 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: HELP I'm drowning in a sea of encoding.
Ian Skinner wrote: > I have a small CMS type form. I have used the tinyMCE wysiwyg widget to allow ok 1st off tinyMCE isn't the most i18n friendly editor, it's a soup of different encodings. what encoding are you using? are these chars making it out of tinyMCE ok? > I can not seem to get these characters to survive the http post, xml parsing, > file writing and xslt transformations my home grown CMS puts the data > through. safest bet is to use utf-8 encoding front-to-back. - make sure tinyMCE is using utf-8 & the chars are surviving it, if changing editors is an option i'd go w/that wonderfully named FCK one - liberally use the usual encoding hints (cfprocessingdirective, cfcontent, setEncoding, etc.) - whenever you handle the form's content make sure the charset option of whatever tag you're using is utf-8. - make sure the xml is tagged as utf-8 ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240447 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
