Can anyone see a more efficient use of cfprocessingdirective than what I
describe here?  This is my first try at implementation.  I'm developing
strictly for MX 6.1, if that matters.

I'm using <cfprocessingdirective pageEncoding="utf-8">

Its my understanding this is technically redundant but making the
statement explicit is a best practice.  Is that incorrect?

Presently I'm planning on plugging in the code in all files that either
a)output to the screen, b)interact with the db, c)interact with a file
stored on disk in utf-8 format or d)if form or url vars are being
processed.

The statement is to go in individually, one at a time, on every template
including includes and called modules.  Am I overdoing it?  

I am also doing <cfcontent type="text/html; charset=utf-8"> and using
setencoding on form and url vars, but will do these once in the app in
an include and application.cfm, respectively.

Any advice pro/con the above would be appreciated.

--------------------------------------------
Matt Robertson       [EMAIL PROTECTED]
MSB Designs, Inc.  http://mysecretbase.com
--------------------------------------------

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to