G'day tothestars,

Welcome to the Monastery.

[Please put code, data, program output, and similar text within <code>...</code> tags. This has a number of benefits: your posts will be easier to read; you won't need to escape special HTML characters (e.g. turn '<' into '&lt;'); it provides a download facility so we can get a verbatim copy of your code.]

You can find the Perl deltas in the Miscellaneous section of perldoc. Looking in perl5220delta: Selected Bug Fixes, there's a reference to '-T' that may be what you're looking for. There's another in the Performance Enhancements section but that doesn't look relevant to me. If those don't help, try other deltas in the version range you specified.

You might also want to try:

$ file spk_pre_180208_180715_180419_bpo12_p.bsp
[download]

How does the output from that compare with what '-T' is telling you?

I don't have any of those Perl versions handy so I can't do any direct testing for you.

I think you might be right about that entry in perl5220delta. Just for reference, I think that the corresponding commit is f13c8ddbf, which references this P5P thread.

Of course, we really need tothestars to show a SSCCE, then it'd even be possible to run a git blame to narrow it down to the exact commit. But using the above information, it might be something related to misdetection of UTF-8.

tothestars: Note that -T is a heuristic test only, for example, the documentation has always said (emphasis mine): "The first block or so of the file is examined". If you want any kind of certainty, you should use a more reliable method - what's best here depends on what you're trying to achieve with this test.

• -T File is an ASCII or UTF-8 text file (heuristic guess).

• -B File is a "binary" file (opposite of -T).

...

The -T and -B tests work as follows. The first block or so of the file is examined to see if it is valid UTF-8 that includes non-ASCII characters. If so, it's a -T file. Otherwise, that same portion of the file is examined for odd characters such as strange control codes or characters with the high bit set. If more than a third of the characters are strange, it's a -B file; otherwise it's a -T file. Also, any file containing a zero byte in the examined portion is considered a binary file. (If executed within the scope of a use locale which includesLC_CTYPE , odd characters are anything that isn't a printable nor space in the current locale. ) If -T or -B is used on a filehandle, the current IO buffer is examined rather than the first block. Both -T and -B return true on an empty file, or a file at EOF when testing a filehandle. Because you have to read a file to do the -T test, on most occasions you want to use a -f against the file first, as in next unless -f $file && -T $file .

Consequently I would check if the new Perl installation has another locale setting.

Like others said, give us an example input to reproduce the problem.