Closed Bug 297330 Opened 20 years ago Closed 18 years ago

The Greek symbols do not convert. They appear in the English alphabet. format

Categories

(Tech Evangelism Graveyard :: English Other, defect)

Other
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: paul.j.daniels, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 On a PC the symbols are the usual ones in Greek. In Mozilla, on my Linux workstation,, the same symbols appear in the English language alphabet. So, when I should be seeing Ohm-meters, I see W-m, which is Watt-meters (wrong units). Reproducible: Always Steps to Reproduce: 1. Go to http://www.webelements.com/ 2. Click on Fe (iron, the 26th element) 3. Click on the link that includes "electrical resistivity" 4. Scroll down until you find it -- I see 'W' where I should see the Greek symbol for Omega -- What do you see? Actual Results: English appears, rather than Greek. Expected Results: It should have displayed Greek symbols. I did communicate with the site owner, and he thinks the problem may be some issue with the revision of the Greek font he's using. What I want to know is what you folks at Mozilla Headquarters see when you bring it up and look at it. If it looks OK to you, then the issue is a problem with our server, or my workstation, etc.
<http://www.webelements.com/webelements/elements/text/Fe/phys.html> is in iso-8859-1 charset. I see Electrical resistivity [/10-8 W m; or mW cm]: 9.7 on the page and in the source <span style="font-family: symbol">W</span>. I think the use of fonts like this depends on issues he can not control on the users machine. Perhaps html entities? <http://bclary.com/2004/11/25/html-entities>
This website now uses Unicode and HTML entities.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.