Closed Bug 227402 Opened 21 years ago Closed 21 years ago

chatzilla displays blank page with hebrew language pack

Categories

(Other Applications :: ChatZilla, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: tsahi_75, Assigned: rginda)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; he-IL; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; he-IL; rv:1.5) Gecko/20031007 using the hebrew language pack (i produce), when you open a new profile, chatzilla displays a blank screen in the *client* tab. Reproducible: Always Steps to Reproduce: 1.apply the hebrew language pack from http://www.mozilla.org/projects/l10n/mlp_status.html#moz_1.5 to mozilla 1.5. 2.open a new profile 3.while in the new profile, open chatzilla Actual Results: the client tab content is all white, and empty. Expected Results: shoult display the usual content by adding utf-8 charset meta tag <meta http-equiv="content-type" content="text/html; charset=utf-8"> to /content/chatzilla/output-window.html in chatzilla.jar <head> section, the problem is solved. i released a modified chatzilla at http://prdownloads.sourceforge.net/hebmoz/CHATZILLA_0.9.35.XPI?download that implements this fix.
So adding the <meta> tag is all that was needed to fix it? (and why?) Does it depend in any way on the browser's default charset/auto-detect settings?
adding that meta tag is all what i did. the fix was found by milupo @ sorbzilla.de. i don't know why that helps. the default character set for the browser is set in the language pack to iso-8859-8-i (logical hebrew), which should be able to display english, even in unicode, since english in unicode has the same numeral code as in ascii. however, i didn't check yet what happenes if i change the default charset. i didn't translate the chatzilla component, so it should be in english, and it is, once you add the fix.
Depends on: 229545
Chatzilla 0.9.54 is now available and has landed on the trunk (cvs). This should have resolved this bug; if it has not, please reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Product: Core → Other Applications
You need to log in before you can comment on or make changes to this bug.