Closed Bug 30202 Opened 25 years ago Closed 25 years ago

Russian autodetection module corrupts data

Categories

(Core :: Internationalization, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 23920

People

(Reporter: mik, Assigned: ftang)

References

()

Details

If Russian characterset autodetection module detects windows-1251 encoding

it corrupts some characters



Detection itself is done correctly.



Linux M14 release and all previous releases.

 (by the way, it reports that is is M13, but it IS M14)
please prvide more detail. The information is not enouge for track down the 
problem. Please include url , and point out where gwt corrupt
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
url: http://www.chel.com.ru/~mik
there the files koi8.html and win1251.html do contain meta headers for
encodings, and *-noencoding do not contain them.
If autodetect is off, pages with metas are displayed properly, pages without
weta are displayed properly if I chouse encoding manually.

Now, if I turn on Autodetection (Russian), all the pages are being displayed
properly except for win2151-nometa, which is correctly autodetected,
but some characters are damaged.
I am really supprise that you claim "which is correctly autodetected," !!! I 
have not fix bug 23920 yet. There are no way it can detect as windows-1251 
untill that bug got fixed.
I think this is simply a dup of 23920.

Depends on: 23920
add the url to the URL field
I see everything correctly in my private build which have the fix of 23920 which 
I will check in soon. (sorry, not in beta1)
In my Mac which do not have that fix, I see the first two line convert 
incorrectly but the third line seems ok. I think what happen is the detector 
detect the page as x-mac-cyrillic and happen the third line are identical in 
windows-1251 and x-mac-cyrillic.

Mark this as dup of 23920

*** This bug has been marked as a duplicate of 23920 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verified as dup.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.