> Le 31 oct. 2016 à 16:52, Bill Weale <[email protected]> a écrit : > > [...] > It’s 2016 and we’re now all unicode; is there any reason to use a text filter > at all if I’m not particularly concerned about controlling input? Has anyone > else seen different behaviors between using no input filter and using a > blank/null input filter?
The "danger" comes from user that copy/paste or drag'n drop (from browser, word processor, etc). You may then encounter "unwanted" characters in alpha or text fields - unwanted meaning they are allowed but can result in strange behavior after (display, export, print…) For my own, I don't use filters because I don't understand how they work (except simplest ones: date, time, numbers…) and code seems to me more easy to use widely and adapt. I use something like this: //method form on data change if(self is alpha or text) clean(self) //clean delete all char under code 31, except 9, 10, 13 replace LF with CR replace decimal 8232 (U+2028 - line separator) with CR trim -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
