On Tuesday, September 4, 2018 at 10:45:11 AM UTC-5, [email protected] wrote: > > I'm shocked, shocked that an MS App writes a naughty character in UTF-16. > (Pleasantly surprised you didn't get bad surrogate pair warnings.) > > Guessing they've not UTF-16LE encoded the trailing Ctrl-Z EOF ? > (Confusingly in UTF-16LE, EOF should be ^Z \000 . Any app not doing UTF > should treat as Binary and ignore ^Z !) > > > If you *2>/dev/null*, to mask the noise, and search for a word that > appears in the files, do you get sensible results ? > > Sorry, I was being foolish: There were other files ack was searching and croaking on. Against just one file of the right encoding your trick works perfectly.
-- You received this message because you are subscribed to the Google Groups "ack users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/ack-users. For more options, visit https://groups.google.com/d/optout.
