开云体育

"?" can also be a 2 byte character, and that was one of the things that alerted me. As it happens, LTspice ignored the entire first line, when I wrote out what I thought was was Chris's 1st line in a separate file. When it encounters more than two increments with the same amplitude, it ignores the middle one. When it encounters a whole lone of the same amplitude, the whole line gets ignored. There's a message to that effect in the ErrorLog. Whereas with Chris's string, it threw an error message because there were the wrong number of sub-strings - the parser bombed out when it encountered an "illegal" character. The two files looked the same, but I noticed they differed in length by one byte, so the "?" was a double byte character, not extended ASCII. It might depend what keyboard and character set Chris is using, and how the "?" got there. They still looked the same to me, until I compared them in Meld (a file comparison tool). Then the difference was highlighted. It was a "duh!" moment.

So I then did a global search and replace of "u" for "?" on Chris's whole text and it worked straight away.