file --mime returns mimetype and charset separated by space only

Bug #413302 reported by Kim Alvefur
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by TJ

Bug Description

Binary package hint: file

file --mime output does not follow RFC 2045, where content-type should be something lite type/subtype; param=value, but instead of "; " it's only a space

Steps to Reproduce:
1) Write some text and save it onto a file.
2) run file --mime --brief the_file

Expected Results: (and also the result on hardy)
text/plain; charset=utf-8 (or other charset)

Actual Results:
text/plain charset=utf-8 (or other charset)

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: wl
Package: file 4.26-2ubuntu4
ProcEnviron:
 LC_TIME=en_DK.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: file
Uname: Linux 2.6.28-15-generic i686

Revision history for this message
Kim Alvefur (zash) wrote :
Revision history for this message
Kim Alvefur (zash) wrote :

This appears to be fixed in both hardy and karmic, but not jaunty.

Revision history for this message
TJ (tj) wrote :

Nominated for Jaunty based on Zash's assertion.

Changed in file (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.