Closed
Bug 137239
Opened 22 years ago
Closed 7 years ago
</title> is lost if no charset is specified
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
WORKSFORME
mozilla1.2beta
People
(Reporter: kazhik, Assigned: jshin1987)
References
Details
(Keywords: intl)
</title> is lost if no charset is specified, and the page is displayed as blank. Testcases: http://kazhik.net/mozilla/test/2052-1.html http://kazhik.net/mozilla/test/2052-2.html See these pages with character coding = Shift_JIS. The first page is displayed as blank. In the second file I put a blank between the title string and </title>. But the left frame is displayed as blank. The right frame has charset information and is displayed correctly. Original report in Bugzilla-jp: http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=2052
Comment 1•22 years ago
|
||
Hum, I don't see the difference between the 2 test pages on both 04-12 trunk and branch build. However, when I set charset to shift-jis, the page does display as blank, and when set charset to correct one - EUC-JP, the page (both frames) will display fine. With other wrong charset, e.g iso-8859-1, big5...etc. will get a display garbled page but not blank page.
Comment 2•22 years ago
|
||
In our charset converter, if the leading byte indicate that it is a 2-byte character, even if the 2nd byte is not in valid range, it will be eaten. In this case, the '<' character of "</title> was eaten inside SJIS to unicode converter. This caused failure in parsing and lead to blank page. reassign to frank, he may have similar bugs. I remember somebody suggested in some bug that we should only eat one char in such scenario.
Assignee: yokoyama → ftang
Comment 3•22 years ago
|
||
I think the reporter miss one step- you need to set your default encoding to "Shift-JIS" first in the language pref. If your default encoding is "ISO-8859-1" then there are no problem. Maybe we should do the following In DBCS if we hit an illegal sequence, if the next char is '<' EAT one bytes, if the next char is not a "<" eat two bytes if the lead bytes indicate it is a two byte sequence. Take this bug moz1.1beta
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1beta
Updated•22 years ago
|
Target Milestone: mozilla1.1beta → ---
Comment 5•19 years ago
|
||
what a hack. I have not touch mozilla code for 2 years. I didn't read these bugs for 2 years. And they are still there. Just close them as won't fix to clean up.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Comment 7•19 years ago
|
||
Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all the spam is his fault feel free to tar and feather him
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 8•19 years ago
|
||
Reassigning Franks old bugs to Jungshik Shin for triage - Sorry for spam
Assignee: nobody → jshin1987
Status: REOPENED → NEW
Comment 9•19 years ago
|
||
The bug can occur with a xml/rss/rdf file, and makes the file not available. http://big5.xinhuanet.com/gate/big5/rss.xinhuanet.com/rss/mil.xml Erreur d'analyse XML : balise ne correspondant pas. Attendu : </title>. Emplacement : http://big5.xinhuanet.com/gate/big5/rss.xinhuanet.com/rss/mil.xml Numéro de ligne 81, Colonne 132 : <comments>http://comments.xinhuanet.com/comment?url=http://news.xinhuanet.com/mil/2005-08/12/content_3343121.htm</comments> </item> -----------------------------------------------------------------------------------------------------------------------------------^ :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: <item> <title>緹����絀哄啗搴嗙U-2楂樼��渚﹀療鏈洪椋��0鍛ㄥ勾(緇勫浘)</title> <link>http://news.xinhuanet.com/mil/2005-08/12/content_3344604.htm</link> <description><![CDATA[ 緹����絀哄啗U-2楂樼��渚﹀療鏈�� 緹����絀哄啗U-2楂樼��渚﹀療鏈����卞��銆婇槻鍔℃柊��匯��2005騫��鏈��鏃ユ姤閬 撱��2005騫��鏈��鏃ワ紝涓��灦U-2"榫欏コ"(Dragon Lady)楂樼��渚﹀療鏈虹 ��緙����鍏ヤ��娌諱簹宸炵綏鈥︹��]]></description> <category>鍐涗簨鏂伴椈</category> <author>xinhuanet@xinhua.org</author> <pubDate>Fri, 12 Aug 2005 08:02:41 GMT</pubDate> <comments>http://comments.xinhuanet.com/comment?url=http://news.xinhuanet.com/mil/2005-08/12/content_3344604.htm</comments> </item> <item>
Updated•15 years ago
|
QA Contact: amyy → i18n
Updated•8 years ago
|
Depends on: encoding_rs
Comment 10•7 years ago
|
||
This has been fixed at some point. Probably as part of security fixes.
Status: NEW → RESOLVED
Closed: 19 years ago → 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•