UTF-16LE character encoding not autodetected

RESOLVED INVALID

Status

()

Core
General
--
minor
RESOLVED INVALID
8 years ago
8 years ago

People

(Reporter: Erik Hahn, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:2.0b2pre) Gecko/20100629 Minefield/4.0b2pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:2.0b2pre) Gecko/20100629 Minefield/4.0b2pre

When attaching an export of the Windows registry (.reg) to bug 575941, I noticed Firefox did not automatically detect the character encoding, guessing UTF-8. The correct one is UTF-16LE

Reproducible: Always

Steps to Reproduce:
1.Visit the URL
Actual Results:  
After every character, a "non-printable" question mark is displayed. The character encoding has been detected as UTF-8

Expected Results:  
The detected character encoding is UTF16LE, the file is displayed correctly.

Bugzilla did not even recognize the file as text/plain in the first place, setting the MIME type as application/octet-stream instead.
The server sends:

  Content-Type: text/plain; name="HKEY_CURRENT_USER--FileExts.reg"; charset=UTF-8

so the browser shows it as UTF-8.  Bugzilla will default to sending all text/plain as UTF-8 unless you tell it otherwise by putting an explicit charset= in the type of the attachment.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.