Closed Bug 192764 Opened 22 years ago Closed 7 years ago

Characters with accent are not visible in the new source code window of the debugger

Categories

(Other Applications Graveyard :: Venkman JS Debugger, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: xavier.loup, Assigned: rginda)

References

()

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3b) Gecko/20030210 Characters with accent are not visible in the source code window. They are replaced by question marks. Reproducible: Always Steps to Reproduce: 1. Go to http://www.sfr.fr 2. open the debugger window 3. In the debugger, open the source code for navh_fonction.js 4. Go to line 25 Actual Results: Character with accent is replaced by a question mark (// POPUP Visite guid�e) Expected Results: Character with accent should be dispayed. ( // POPUP Visite guidée) The problem appear one every line of the source code, not only on comments. When you use old source code window, characters with accent appear correctly.
Sounds to me like your monospace font doesn't support those characters.
I think that every font of windows NT supports characters with accent. If you tell me which font it is, i 'll verify the font in another application. (The font "Courrier New" which is my default monospace font in mozilla displays accent correctly). Moreover it used to work with the old source code window.
Same problem on linux
It's a regression between the old source code and the new source code. The problem is not in the font because : - the bug is present on windows and Linux - the old source code works
Steps to Reproduce: 1 - Open a html document containing the following code <html> <head> <script language=javascript> <!-- function test() { alert("Text with accents : יטא"); } --> </script> </head> <body onload="test()"> Test </body> </html> 2 - open the javascript debugger and show in the view menu : Source Code (new) and Source Code (old) Result: Accents are displayed correctly in the old source code. They are displayed as question marks in the new source code. - This is a regression - This bug can be reproduced on linux and windows I hope this is enough to change the status of this bug to new !
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attached file xml testcase
bare bones xml file showing the problem. I'm not sure if I have to specify some specific character set, or if this is a mozilla problem.
peterv: any idea what's going on here?
caillon pointed out that these charaters are not valid utf-8 characters, and utf-8 is the default character set. You can make venkman use a different character set with a comment like: // meta http-equiv content-type charset=ISO-8859-1 or, you could use utf-8 equivilant characters.
If I try with this code (meta added), the problem remains : <html> <head> <meta HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1"> <script language=javascript> <!-- function test() { alert("Text with accents : יטא"); } --> </script> </head> <body onload="test()"> Test </body> </html>
that's because your meta tag spans two lines. Venkman doesn't expect that. Perhaps it should.
If I create two files (HTML in the first one and javascript in the second), the bug remains : Note that the encoding of the external javascript is specified. 1 - HTML File (test.html) <html> <head> <meta HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1"> <script language="javascript" src="test.js" encoding="ISO-8859-1"></script> </head> <body onload="test()"> Test </body> </html> 2 - External js (test.js) function test() { alert("Text with accents : יטא"); }
The javascript engine provides no way for venkman to figure out what script tag a .js file came from, so specifying a character set on the script tag doesn't help venkman at all. If you want to set the charset on an external js file you have to add a comment, as shown in comment #8, and http://www.hacksrus.com/~ginda/venkman/faq/venkman-faq.html#2.21.
Product: Core → Other Applications
QA Contact: caillon → venkman
Component is obsolete so resolving bugs as INCOMPLETE
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: