case 1:
db contains values not encoded (in html sense), but that can have possible "special" values not handled correctly by browsers if sent as they are.
The objective here is to make db unaware of the translation needed to accomplish the round-trip from web server to browser. So we have to encode special chars, feelings happy that browsers will unencode on sending them back.
In this way db data is preserved, and html format too.
case 2:
db contains "html" code, that has to be rendered "as it is" on the html page (using a label tag, I can't see any other dbforms's way).
Here we don't want to encode, as chunks of html is readed from db, but it seems to me that we don't have the problem of data returned from browser.
So, the idea to encode by default and an attribute to disable it, is feasible to me.
cheers, sergio
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
