Given the following two files created by the following commands:
$ printf "foo\nbar\nbaz\n" | iconv -t UTF-8 > utf-8.txt
$ printf "foo\nbar\nbaz\n" | iconv -t UTF-16 > utf-16.txt
$ file utf-8.txt utf-16.txt
utf-8.txt: ASCII text
utf-16.txt: Little-endian UTF-16 Unicode text
I'd like to find the matching pattern in UTF-16 formatted file, the same way as in UTF-8 using Ruby.
Here is the working example for UTF-8 file:
$ ruby -e 'puts File.open("utf-8.txt").readlines.grep(/foo/)'
foo
However, it doesn't work for UTF-16LE formatted file:
$ ruby -e 'puts File.open("utf-16.txt").readlines.grep(/foo/)'
Traceback (most recent call last):
3: from -e:1:in `<main>'
2: from -e:1:in `grep'
1: from -e:1:in `each'
-e:1:in `===': invalid byte sequence in US-ASCII (ArgumentError)
I've tried to convert the file based on this post by:
$ ruby -e 'puts File.open("utf-16.txt", "r").read.force_encoding("ISO-8859-1").encode("utf-8", replace: nil)'
ÿþfoo
bar
baz
but it prints some invalid characters (ÿþ
) before foo
, secondly I don't know how to use grep
method after conversion (it reports as undefined method).
How I can use readlines.grep()
method for UTF-16 file? Or some other simple way, where my goal is to print the lines with the specific regex pattern.
Ideally in one line, so the command can be used for CI tests.
Here is some real world scenario:
ruby -e 'if File.readlines("utf-16.log").grep(/[1-9] error/) {exit 1}; end'
but the command doesn't work due to UTF-16 formatting of the log file.
Short answer:
You almost have it, just need to say which characters you want to replace (I would guess the invalid and the undefined):
Also I don't think you need
force_encoding
.If you want to ignore the
BOM
convert on open and usereadlines
you can use:More details:
The reason why you get invalid characters when you do:
is that in the beginning of each file which is in Unicode you can have the Byte Order Mark which shows the byte order and the encoding form. In your case it is
FE FF
(meaning Little-endian UTF-16), which are invalid UTF-8 characters.You can verify that by invoking
encode
withoutforce_encoding
:Question marks in black box are used to replace an unknown, unrecognized or unrepresentable character.
You can check more on BOM here.
While the answer by Viktor is technically correct, recoding of the whole file from
UTF-16LE
intoUTF-8
is unnecessary and might hit the performance. All you actually need is to build the regexp in the same encoding: