Re: Invisible character treated as word?

2015-02-05 Thread Bob Sneidar
he means non-printing character. Bob S On Jan 30, 2015, at 21:01 , Thierry Douez th.do...@gmail.commailto:th.do...@gmail.com wrote: Umm, as invisible char has no-standard meaning, ___ use-livecode mailing list use-livecode@lists.runrev.com Please

Re: Invisible character treated as word?

2015-02-05 Thread Bob Sneidar
[ -~] http://www.catonmat.net/blog/my-favorite-regex/ bob s On Jan 31, 2015, at 13:03 , J. Landman Gay jac...@hyperactivesw.com wrote: On 1/30/2015 11:01 PM, Thierry Douez wrote: if looking at regular expressions it's like a goat staring at a new fence, Wonderful imagery. :) I knew

Re: Invisible character treated as word?

2015-01-31 Thread J. Landman Gay
On 1/30/2015 11:01 PM, Thierry Douez wrote: if looking at regular expressions it's like a goat staring at a new fence, Wonderful imagery. :) I knew you'd show up to solve the regex problem, I didn't even have to say your name. I suppose when your wife wants you to come to dinner, she only

Re: Invisible character treated as word?

2015-01-30 Thread J. Landman Gay
On 1/30/2015 6:50 AM, David Epstein wrote: But since it seems that fonts and systems will differ as to which characters are actually invisible, I will need to purge even harmless visible characters. So my current plan is to use this function: function scrubbedText txt -- For tab-delimited

Re: Invisible character treated as word?

2015-01-30 Thread Thierry Douez
function scrubbedText txt repeat for each char k in txt if charToNum(k) 31 or charToNum(k) 127 then put k after hold else put space after hold end repea set itemDelimiter to tab repeat for each line k in hold repeat for each item i in k put word 1 to -1 of i

Re: Invisible character treated as word?

2015-01-30 Thread David Epstein
Thanks for the helpful responses on this question. A complication is that while I want to get rid of invisible characters that cause seeming-numbers not to be numbers, I don't want to exclude all non-numbers from my table. But since it seems that fonts and systems will differ as to which

RE: Invisible character treated as word?

2015-01-27 Thread Ralph DiMola
A non-breaking space(160) is respected in LC as a word delimiter. But the 202 is just another character. In the standard extended ascii table this is a │ character In other character sets is might be displayed as a space or just invisible. This would be part of the word it's adjacent to. GIGO. If

Re: Invisible character treated as word?

2015-01-27 Thread Kay C Lan
On Wed, Jan 28, 2015 at 9:11 AM, David Epstein dfepst...@comcast.net wrote: Are there other characters that are always or sometimes invisible that cause the same problem? And what is a remedy? Many thanks. In the multi-line msg box: put empty into msg repeat with x = 0 to 255 put x =

Re: Invisible character treated as word?

2015-01-27 Thread JB
On Jan 27, 2015, at 6:46 PM, Kay C Lan lan.kc.macm...@gmail.com wrote: My suggested solution is where ever the data originally came from, prior to inputting into your fields, variables or custom properties, it should be tested to confirm that the data only contains ASCII chars 48 to 57

Re: Invisible character treated as word?

2015-01-27 Thread JB
That should have been put after tCleanText repeat with x = 1 to number of chars in pText if char x of pText is in tList then put char x of pText in tCleanText end repeat On Jan 27, 2015, at 7:28 PM, JB sund...@pacifier.com wrote: On Jan 27, 2015, at 6:46 PM, Kay C Lan