31054 - 'TEXT' file which contains non ASCII does not open correctly.

Status: VERIFIED FIXED

(Core :: Internationalization, defect, P3)

Description

[Teruko Kobayashi]

When you open the local Japanese text and html file from Browesr, the error dialog displays. 
Then, you cannot see the html and text file from Brower.

Steps of reproduce
1. Create Japanese text file from other applications, such as simpletext editor
   or create Japanese html file from Communicator 4.x
2. Launch Netscape
3. Select menu File|Open File...
   specify the file name which you created in step #1

Actual Result
The error dialog "Unknown File Type" shows up.  You cannot see the Japanese file 
from Browser.

Expected result
You should see the Japanese text file from Browser.

Bug 23744 is fixed.  Now Browser can open the local file, English content and English file name. 
I tested the following.
    English html and text file name but content is Japanese.  Browser does not open
    Japanese html and text file name and content is Japanese.  Browser does not open.

Tested 2000030809 Mac build.

Comment 1

[Teruko Kobayashi]

Because of this bug, I cannot verify the bug 23749 (PDT+).  I put the beta1.

Comment 2

[Frank Tang]

teruko's file name do not have file extension in it. All the file name do not 
have '.txt' or '.html' in it. If we add .txt and .html, then it work ok. It 
looks like Mac only listen to the file extension to decide the content-type but 
didn't listen to the Mac FILE type to decide the content-type . However, there 
are some code after it try to sniff the data and decide to use text type if 
there are only 7-bit data. That is way the ASCII only file work. 

The real problem is we should fix the content type mapper to listen to Mac File 
type 'TEXT' 

Comment 3

[Frank Tang]

reassign to warren
I chat with valenski, we think we probably should put some code in the file 
transport protocol handler to read those info just as how we read last modified 
date for Mac...

Comment 4

[davidm]

I have had this discussion with different people several times. We should not 
have code that does content typing based on extensions except perhaps as a 
method of last resort. That is a platform specific method of typing files and 
has no place in xp code.  The file should be asked for it's type so that 
different platforms can do the right thing. 

Comment 5

[Frank Tang]

Change the name to "'TEXT' file which contains non ASCII does not open 
correctly."

Comment 6

[leger]

Putting on PDT- radar for beta1.  Will relnote

Comment 7

[Warren Harris]

David, Can you deal with this one? Jud wrote the initial mime-type mapping 
stuff, but he's not a mac guy, so I think it would be better if you handled it.

Comment 8

[Warren Harris]

Marking beta2.

Comment 9

[davidm]

*** Bug 31090 has been marked as a duplicate of this bug. ***

Comment 10

[davidm]

fix checked in.

Comment 11

[Teruko Kobayashi]

I verified this in 2000041109 Mac build.