> Let's think from the start. > In current code if you write ç it will be written to > database field as ç but when you go to edit this field > the entry field will show 'ç' wich is visually the same, but > not correctly because the real value in database is 'ç'. > > The escape make correctly the edit part of the system, but > must be optional to the developer in the labels, where the > developer can select to escape or not depending of the data.
+1 > > We can create an attribute in DbBaseHandlertag to control > this selection, the default must be to escape this make > transparent for applications the conversions, and only when > the developer really know that the value in field is HTML he > can show the data without escaping. We should add this attribute to textFields too. And default should be not to escape - this would be backward compatible. But we should always escape the " in textField because of the resulting parsing errors. ------------------------------------------------------- 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_id70&alloc_id638&op=click _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
