Hello,
FireFox for some reason does not display international characters (for ex. german) on FC5
I have it working on WIN XP with no problems.
Why?
Thanks

First, does this apply for all web pages, or just for distinct ones?

Second, we would make sure the pages encoding is what it pretends to be:
- In the menu "View" (or German "Ansicht"), which Character Encoding is selected?
Are the special characters displayed correctly when you change the Character Encoding there?
- If you look at the page source (context menu "View Page Source" or "This Frame" --> "View Page Source"), is there an HTML "meta" tag in the "head" section (something like "<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>") - and if yes, does it correspond to the charset selected in Firefox' menu?
- Using Linux, when you save any text document, it gets saved in UTF-8 by default. Using Windows, you could save the page to disk, then open it with NotePad. When you say "Save as" in NotePad, the actual character set is pre-selected.

Web pages often are not encoded correctly, and some Quirks mode will sometimes display them right.

(BTW, when posting, you should always supply environment information like Firefox version, Linux distribution, URLs of those web pages in doubt, etc)

OK, got it working.
Thanks!

You haven't posted too many serious support requests yet, have you?

yeah, sorry for posting so much. Trying to figure out how to make FC work with my app that I built...

How To Ask Questions The Smart Way

The link does not work

Sorry for that. - It's really an important link.

How To Ask Questions The Smart Way

There's one thing I'm still missing with this link: The fact other people might get to this thread when they happen to have the same problem like yours. I bet they get frustrated when just seeing "OK got it" but not finding anything about a possible solution...

Again, any support request should be reproducable (that means, the environment data were mentioned, error messages - if possible - wordly mentioned, etc.). Secondly, it should be closed at some point of time (that's what you did), and with its closing, it should provide the (if possible) solution. Even if you gave up that's fine (for the thread). Just come back and let others know how you dealed with that issue so that they can decide what to do theirselves.

Thanks

And good luck with your issues!

ok thanks,

well the solution was simple - to set the correct encoding in the browser ( for somer reason I thought i did that before I post the message)

There should be no need to correct the encoding in the browser - the browser should automatically recognize it.

There are two main factors for enabling automatic character encoding recognition:
1. There should be a HTML "meta" tag: "<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>"
2. The HTML text file at disk should be saved with the correct encoding. (Under Windows, the default encoding is "Windows-something", which is in fact Latin-1. Using Notepad or Visual Studio, there are additional options to specify the encoding when saving a text file. - Under Linux, the default encoding is UTF-8, and ususally, there are no additional options when saving a file.)

I've got this tag but it does not recongize it automatically...

I'd say, that's typically Java - Java's default encoding for code files is still ISO-8859-1. Either change that in the HTML meta tag appropriately or in the file properties within your Java Editor. In Eclipse, you can set the default encoding globally, in Netbeans I didn't find such an option.

those are actually html and jsp pages what does Java have to do with html pages?

Thanks.

Popular Java editors (I think you mentioned NetBeans) encode JSP and HTML pages in ISO-8859-1.

(That's fine with Windows as this is Windows' default encoding but not with Linux as Linux' default encoding is UTF-8.
In part, you can edit the encoding in property pages but mostly (with NetBeans 4 & 5 and Eclipse 2 & 3) not. That's very disgraceful.)

Therefore, the tag you inserted into the HTML header,
might be invalid (and would confuse the web browser) as the actual encoding is *wondering* ISO-8859-1.
Try
If this doesn't help, we'd need much more elaborated information on your environment, the steps you processed to come to *which exactly?* results, and such.