🚀 go-pugleaf

Andrue Cope wrote:
> Jim Dodd,
> 
> 
>>In this way, we don't use Andrue's "times 3" fudge factor. We just say 
>>that if ANY character falls out side the range [8,9,10,13,26,32-127], 
>>the file is probably a binary file.
>>
> 
> 
> 'Fudge factor'? How dare you sir. It's a kludge :)
> 
> In truth our routine is son-of-son-of-something-written-many-years-ago 
> and hence my disclaimer about statistics. It's a definite example of code 
> that has evolved to meet requirements. We don't claim to know why it's so 
> good we just accept that it is <g,d&r>.
> 
> Another reason why I've never tried to rationalise it is that it counts 
> lines and generates an index for fast seeking. It handles various methods 
> of EOL marking (CR/LF, LF/CR, CR, LF) and I don't want to touch that code 
> with a bargepole :)
> 
> Andrue Cope
> [Bicester, UK]
> 
Very good :-)

Actually, I employ my own "factor" which I was reminded of when reading 
Gambit's later reply - I don't usually read the entire file. I pick a 
percentage of the file size and read that (usually 10-20%) and if I 
haven't found any non-text characters by that time, I declare it text.

Jim Dodd
Onset Computer Corp.