Closed Bug 273212 Opened 21 years ago Closed 17 years ago

The text files (windows format) are not interpretting as (7 bit ?) text, and instead show garbled characters

Categories

(Firefox :: File Handling, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: darkpeace, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 There is no need to expand on the error. when viewing (non Unix) TXT files via the URL directly, they show as garbled characters, Unix TXT files MIGHT work fine, note the files are not HTML or HTM files, if they are renamed it works fine. Reproducible: Always Steps to Reproduce: 1. Click the link I provided above 2. 3. Actual Results: ਍湉汣摵⁥⁡敳瑣潩湯删䵁琠獥楴杮਍਍睷⹷敭瑭獥⹴牯൧眊睷洮浥整瑳㘸挮浯਍਍ is displayed, instead of the actual contents of the (Windows) TEXT file when veiwed via the URL directly Expected Results: Displayed this: "Include a section on RAM testing www.memtest.org www.memtest86.com " The text file in question
WFM I can only get such characters if I force utf-16 encoding. Server respose is text/plain, no character encoding in HTTP header - perhaps your default is funny? Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Well that is weird, I changed it, then change it back (char encoding settings) and now I can't even recreate the problem. Most strange, I wonder if any devs can recreate it with a fresh install on a Windows XP Pro, SP2, English machine ? Still leaving as unconfirmed for now, but there is a work around, so it is far lower priority now. Tabris.DarkPeace
URL no longer works/exists
QA Contact: ali → file.handling
Assignee: bugs → nobody
wfm per inability to reproduce, if problems occurs again, feel free to reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.