| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 63416 | 2005-11-09 01:49:00 | Two different servers, differing text on same page? | John W (523) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 402830 | 2005-11-09 01:49:00 | Hi there Ive created a website that is hosted on the Domainz server, www.flyfishingguide.co.nz , the problem being that unique French text characters show up in strange text blocks. While the same page on my DiscountDomains server ourpage.co.nz has no problems displaying the correct text. I created the page using Frontpage 2003, and until loaded on to the Domianz site, had no problems with it. Ive checked the source code which displays the characters correctly, but faults on the Display page. So, where do you think the fault lies? Thanks..................John in Mosgiel. |
John W (523) | ||
| 402831 | 2005-11-09 04:37:00 | At the risk of stating the obvious, it appears the problematic page resides on a server that has one of 3 possible issues : it is either missing a character set or the upper ASCII characters are not of the standard Windows variety or the server is incorrectly interpreting the upper ASCII characters. For example, the problem page appears differently between IE and Firefox - in place of the French characters, my FF has question marks whereas my IE is displaying some sort of Asian characters. I suspect it is an issue with a character set on the server. Character sets aren't my forte but I am aware that the French characters are in the upper ASCII range (i.e. ASCII codes 128 through 255) as would the Asian characters being displayed in IE (unless they are question mark in an Asian language which is normally ASCII character 63 on PCs) . So the first thing to do would be to look at the OS on the server because I don't believe it is an issue with FP or your PC. Just my thoughts Andrew |
andrew93 (249) | ||
| 402832 | 2005-11-10 01:33:00 | ASCII is the "American Standard Code for Information Interchange". Like all good standards every man and his dog have "improved" on it, especially with all the permutations of 7/8/9 bits, parity bits, etc. I used to have a fair idea of how it all worked (and had a 1" thick manila folder of documentation, including a sreies of articles by Bemer, the main perpetrator of the ASCII standard). Now there is the new improved wonderful user friendly and intuitive Unicode, which uses 16 bits per character, and includes the variious modifications of ASCII as subsets. I don't know how it works. :D Perhaps one server uses Unicode, and the other doesn't. |
Graham L (2) | ||
| 402833 | 2005-11-11 11:57:00 | Wouldn't this depend on the server's encoding and the browsers encoding. Usually the web designer must tell what the document is encoded with so the browser understands it, you can force your browser to use UTF-8 also. I usually use UTF-8 for all my sites but UTF-16 is for most Chinese/Japanese characters (in which I don't use). Default should be UTF-8 but some servers are still setup to use the Latin-base encoding of ISO-8859-1, however FrontPage might use the Windows encoding (that would be bad). FrontPage doesn't write well-formed and standard compliant sites, a lot of browsers disregard <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> so the only other option is if using a dynamic web language, is to send the header yourself, in PHP you would do header('Content-Type: text/html; charset=utf-8'); otherwise you'll need to alter your server's default encoding to utf-8. If using xhtml then you'll need the processing line <?xml version="1.0" encoding="utf-8"?> as well as sending the mime-type application/xhtml+xml; charset=utf-8, yet IE does not support this mime-type or fully understands XHTML due to their lack of keeping up with standards. If I maybe so bold, I would recommend xstandard as a WYSIWYG editor, I've never used it, but they claim to write standard compliant websites, which is a good thing to hear. You can grab that from http://xstandard.com/ I should also add, HTML entities, if you're using them like © etc, it's best to use their numeric value, , ©, (change these commas with semi-colons ; as they were rendered in this thread) etc as I believe it's more compatible internationally. Cheers, KK |
Kame (312) | ||
| 1 | |||||