I am currently working on a site which has some pages displaying Chinese characters. These display fine on Firefox however on IE I receive a simple box where the character should be.
I thought this was simply because I did not have the language pack installed onto Windows, but then I was provided some samples of it working.
Can someone please explain why this page displays properly for me in IE
http://www.ifc.org/chinese
But this does not?:
http://www.jjl.cn/
(Google.cn does not display correctly either)
I have tried
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
But have had no luck.
Thanks
It has nothing to do with the encoding, both sites work fine on my browser. It is because you do not have the proper language fonts installed on your computer.
I typically install these fonts upon install, so don't recall that exact installation process. But you can likely find out how by going to Control Panel -> Regional and Language Options. If you still can't figure it out check out this wiki link.
http://en.wikipedia.org/wiki/Help:Multilingual_support_(East_Asian)
note Keep in mind that input methods(used for typing the languages) are different than character fonts(used for displaying the languages).
note 2I typically use UTF-8 as the charset for all my pages, especially if I know I will be dealing with multilingual content.
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Here is how I tell what my problem is when dealing with characters not displaying correctly:
If you see a bunch of squares, it is your computer, and you need to install the appropriate font files.
If you see a bunch of random ASCII characters, then it is likely that the page encoding is incorrect. In which you can change which encoding to render the page in via browser settings as a temp fix
Very Unlikely Somebody is playing a mean joke and wrote a page using random ASCII characters/squares just to annoy users. :)
Related
I just spend the last few hours debugging a huge problem, the problem being,
My external css style sheet were not loading when I used Firefox.
Using Firefoxes debugging tools I was able to conclude that the file was not been found, it had nothing to do with the MIME type or encoding as I checked.
I was using relative URL's to reference my style sheets to I decided to use absolute and it worked! after hours of nearly losing my mind.
However using absolute URL's on every page is just a pain and not practical if I am debugging on localhost all the time.
Could anyone tell me why I need to proved the absolute URL's? The CSS file is there and Firefox states the relative URL and when I go to it manually, it works, however Firefox will just not find it. Every other browser including Chrome and Safari Works with the relative URL's.
I could use php and define all these relative URL's and then reference these within my HTML making it easier to switch domains for debugging but still its a pain and I don't know why I have to do this.
My site here
Thanks in advance,
Jack.
Note : For testing reasons I am giving the link to my site which I am having problems with, nothing to do with advertising.
For your stylesheet problem: change the backslash to a forward slash in your <link> element.
<link rel="stylesheet" href="css/main.css">
There are a couple of images with a similar problem.
You have a number of other errors: <script> tags between <head> and <body>, and some loose </article> tags as well
If you're using Firefox, take a look at the page source and fix anything you see highlighted in red. Then try again.
So I have almost no iphone programming experience, yet I have found some basic rss reader code and playing around with it.
The thing is, when I visit the link in my Chrome browser, it works fine in terms of character encoding, but when I visit it through the built-in browser in the iphone app code I have (in iphone simulator), the characters are not displayed properly.
Why it could be?
Edit:
So what I was trying to access over the web browser was a simple UTF-8 text file (I was too lazy to put into an HTML), and I could not see the non-English characters.
You must tell the client that the file is in UTF-8 format. If you are running apache, you can add this to your .htaccess file:
AddDefaultCharset UTF-8
Or you can put the text into a HTML file and add a meta tag for the charset encoding:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
We are having some annoying issues with BlackBerry phones. For some odd reason, our webpages aren't downloaded fully by some BB phones and I don't have clue what it could be.
If you have a BB, please try www.safarinow.com.
We are currently mainly experiencing this issue on the BB Curve 8520, but we don't have a lot of BB's around here to properly test. I have used the BB simulator for this BB and also for different models, but of course, on the simulators everything works fine. In order to browse the Internet on the BB simulator, it requires you to have the MDS service installed and I assume this works differently than the live server.
Something strange is that when you change the character encoding (BlackBerry browser menu -> Set encoding), it usually does load the full page...
Any clues? Please help :-)
Some articles I read
http://www.builtfromsource.com/2008/08/27/major-bug-with-blackberry-browser-and-multiple-cookies/
-> This doesn't seem to be the issue
http://www.blackberryforums.com.au/forums/general-bes-discussion/284-request-entity-too-large.html -> We are not getting an error, although page request size might be an issue
Maybe you should add an Encoding tag on your page's header.
Something like <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
This could be an issue specifically related to the browser rending engine. It's a long shot but make sure your HTML validates. The browser on certain Blackberries may be choking on improperly validated HTML.
Validate markup for your site: The W3C Markup Validation Service
The service found 41 errors and 9 warnings. It's worth eliminating as many errors as possible and re-testing.
Alison has some very good advice.
One other thing to look into is the amount of, and specifics of, javascript on the page. Before OS 6 and the Web Kit based browser, support for javascript on BlackBerry devices was intentionally limited.
It turns out that a lot of BlackBerries have Javascript turned off. And even if it's turned on, there is a checkbox for "Terminate slow running scripts" (something like that). We use jQuery Mobile, which is pretty heavy, so that was causing the issues. Ticking both checkboxes solved the issue.
We display a piece of signed XML in a TEXTAREA. The signing takes into account the whitespace, so it is critical that this is maintained.
The user then copies and pastes this into an application that validates the XML... we've not had a problem with this until now... IE9 is rending the text slightly differently.
When I copy it into a HEX editor, I can see that IE9 is rendering newlines as 0xA... put it into compatibility mode (or use IE6,7,8, Chrome, Firefox etc.) and it gets rendered as 0xD,0xA
I guess this won't effect most people, as it looks ok... but for us it is a royal PITA!!!
Anyone come across this, and better have a fix :)
Thanks!!!
Not sure if this is really a fix (and I do wonder if this is a bug in IE9?)
Anyhow, I ended up putting IE9 into IE7 emulation mode for the page in question:
http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx
<!-- Mimic Internet Explorer 7 -->
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" >
It works, but now, of course I don't have the IE9 features on this page.
Does anyone know of a best practice print document for printing a website in IE6? I have a specific page that needs to be printed and it comes out well in other browsers except IE6 where it is being chopped off by a huge amount on the right side of my page.
Thanks
I have found the most fool-proof method of making something printable is by providing a print button that links to a PDF version of the document.
Generating the PDF is the major task there but that can be quite simple with the right tool.
I use http://www.xhtml2pdf.com/ which is a Python app to take a page and generate a PDF version. It might need some tweaking so you might need a special stylesheet to fix some things.
Other than that, you're left fixing IE. It might help to add a print stylesheet:
<link rel="stylesheet" href="print.css" type="text/css" media="print" />
And overriding some of your more extravagant positioning methods. If you're centring, pull it back to the left, cut out extraneous margins and padding (remember background-images won't render with standard print settings so you can cut out a lot of padding).
You might find there's some crossover (ie you use some of the print styles in your PDF version) so you might be able to generate a hybrid solution to allow people to grab PDF versions and print straight from HTML.