Re: [tlug] Today's discovery: ugrep

[Darren Cook <darren@example.com>]

> > grep was giving me no hits on a kanji string I knew was in my directory
> > tree at least once. Then it dawned: my terminal is in UTF8, but the
> > files I'm searching are in UTF-16.
> Good catch! But I'll definitely fix that fs naming (rather that switching
> to UTF-16, LE or BE?), before some other weirdness happens.

You are thinking of `find` not `grep`, Kalin!

But I do actually get these UTF-16 files in a zip file with Shift-JIS 
filename encoding. Yes, I suspect they are not using Linux ;-)

`unzip -O shift-jis ...` fixes that.

But for contents, I'd rather keep files in the original encoding where 
possible. For instance, troubleshooting has discovered a UTF-8 BOM at 
the start of a UTF-16 file before.

Darren