Closed Bug 230660 Opened 21 years ago Closed 21 years ago

[FIX] XML prettyprint does not work on UTF16-LE encoded page

Categories

(Core :: XML, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla1.7alpha

People

(Reporter: sekundes, Assigned: bzbarsky)

References

()

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7a) Gecko/20040108
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7a) Gecko/20040108

Summary says it all

Reproducible: Always

Steps to Reproduce:
Tried to create a testcase, but every single editor on my system choked on the
file.  Even Vim.  Maybe for some odd-ball reason Mozilla has a problem with the
raw length of the line -- 154,000+ characters.

Maybe someone with the horsepower on their system to do it could break the file
up  over multiple lines and see how it works.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6b) Gecko/20031208
To sicking.   The problem is that the page is UTF-16 (not ascii-compatible,
therefore) and his prettyprinter CSS doesn't have @charset rules.  So we try to
decode it as UTF-16 and that fails badly.
Assignee: general → bugmail
Status: UNCONFIRMED → NEW
Component: Browser-General → XML
Ever confirmed: true
OS: Windows 2000 → All
QA Contact: general → ian
Hardware: PC → All
The CSSLoader stuff is a minor improvement to how we do charsets a tad, plus
converting logging to use PR_LOG instead of printf.
Comment on attachment 138852 [details] [diff] [review]
Fixes the problem

I call upon thee, CSSLoader not-fearers!  Review!  ;)
Attachment #138852 - Flags: superreview?(peterv)
Attachment #138852 - Flags: review?(bugmail)
Comment on attachment 138852 [details] [diff] [review]
Fixes the problem

* sicking fights off CSSLoader deamons with a keyboard
Attachment #138852 - Flags: review?(bugmail) → review+
Taking.
Assignee: bugmail → bz-vacation
Priority: -- → P2
Summary: pretty print XML does not work on specific page → [FIX]pretty print XML does not work on specific page
Target Milestone: --- → mozilla1.7alpha
Attachment #138852 - Flags: superreview?(peterv) → superreview+
Would it make sense to use "UTF-8" instead of "utf-8" in the @charset rule?
Doesn't matter, really.  I could change that, sure.
*** Bug 230811 has been marked as a duplicate of this bug. ***
Summary: [FIX]pretty print XML does not work on specific page → [FIX] XML prettyprint does not work on UTF16-LE encoded page
Checked in.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: