This is the mail archive of the
cygwin
mailing list for the Cygwin project.
printf '\377\376h\000\r\000\n\000'|file - #wrong result?
- From: cygzx at trodman dot com (Tom Rodman)
- To: cygwin at cygwin dot com
- Date: Mon, 04 Dec 2006 14:47:43 -0600
- Subject: printf '\377\376h\000\r\000\n\000'|file - #wrong result?
- Reply-to: cygwin at cygwin dot com
Should this directed to the "file" package maintainer?:
~ $ date;uname -a
Mon Dec 4 14:31:38 CST 2006
CYGWIN_NT-5.0 OurServer121 1.5.22(0.156/4/2) 2006-11-13 17:01 i686 Cygwin
~ $ printf '\377\376h\000\r\000\n\000'|file -
/dev/stdin: MPEG ADTS, layer I, v1, 192 kBits, 32 kHz, Stereo
--snip
~ $ date;uname -a
Mon Dec 4 14:34:15 CST 2006
Linux localhost.localdomain 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux
~ $ printf '\377\376h\000\r\000\n\000'|file -
standard input: Little-endian UTF-16 Unicode character data, with CR line terminators
~ $
>From above you can see linux and cygwin "file" output differs. The printf
above was inspired recently when "file" mis-identified a unicode file.
I don't think this is a new problem.
--
thanks,
Tom
--
PS
above unicode contains one line with a single "h" char
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/