Ubuntu
file package

file detects utf32-be wrongly

Bug #285309 reported by Michael Tsang on 2008-10-18

Affects		Status	Importance	Assigned to	Milestone
	file (Debian)	Fix Released	Unknown	debbugs #513526
	file (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

michael@ubuntu:~/src/unicode$ file utf32-be.txt
utf32-be.txt: data

Revision history for this message

Michael Tsang (michaeldadmum-deactivatedaccount) wrote on 2008-10-18:

utf32-be.txt Edit (40 bytes, text/plain)

Revision history for this message

Adam Buchbinder (adam-buchbinder) wrote on 2009-01-29:

Confirmed in file 4.24-4. According to the Unicode FAQ[1], the Byte Order Mark is serialized as 00 00 FE FF in UTF-32. The magic in file 4.24-4 is looking for FE FF 00 00, which is why it's not detecting this file. A patch will be forthcoming.

[1] http://unicode.org/faq/utf_bom.html#bom4

Changed in file:
status:	New → Confirmed

Revision history for this message

Adam Buchbinder (adam-buchbinder) wrote on 2009-01-29:

Debdiff against 4.24-4. Edit (2.0 KiB, text/plain)

The attached debdiff adds a patch to debian/patches which fixes UTF-32BE detection. There's still a problem in Debian; I'll be opening a bug report upstream.

Bug Watch Updater (bug-watch-updater) on 2009-03-10

Changed in file:
status:	Unknown → New

Revision history for this message

Adam Buchbinder (adam-buchbinder) wrote on 2010-07-22:

This has been fixed since the release of 5.01-1 by Debian. I'm not sure why the Debian task is still showing as open; I'll try to get that to refresh.