|Subject:||No UTF8 Support obvious|
The Spec and the code itself seem to be reasonably ignorant of UTF8 issues.
I just discovered this in the process of munging my own CPAN::Changes files, as an extension I have in progress ( CPAN::Changes::Markdown ) was sensitive to specific things in The Changes file.
Specifically, in my changes file, I regularly use 0xA0 ( Non-breaking space character ) and → ( 0x2192 ), which if not read in utf8 mode, become a chatoic mess of bytes that don't match regular expressions , like you're matching vs "\xC2\xA0\xE2\x86\x92\xC2\xA0" instead of " → "
The easiest approach here is to either have a load_utf8 method, or a load_filehandle() method that takes a Path::Tiny::path('foo')->openr_utf8 or something.
Alternatively, you could try to have unicode by default, but not sure how good an idea that is.