I am using in project German alphabet, so I need to use ü, ä, ö. But instead of this, when I run the server, I got �. How can I fix it?
I thought that I need to add to my static index.html meta data charset utf-8, but it was already there and it didn't work.
Related
I want my xdime page to be displayed in Hindi. However I am getting ???? in place of Hindi characters. I have taken care that my Hindi character properties file is in UTF-8 and has unicode characters. Also I've set Charset to UTF-8 in view.jsp. Hindi locale support has been added to portal and its working fine.
You can set the default character set to UTF-8 of the XDIME markup for each local on the Supported Markups section on Administration page.
I tried to post characters such as "āēīū" from a form in a PDF viewer to a web server, but on the server side those characters look like this: "????". What can I do to pass these characters as UTF-8?
Use xml or xfdf posts.
Encoding doesn't work for html, fdf posts.
My codeIgniter application serves all html pages with a header of Content type: text/html; charset=iso-8859-1. I would like it to serve utf-8 by default. I checked the config file and the database config file.
$config['charset'] = 'UTF-8';
It just keeps encoding iso-8859-1..
If you are using Apache, add this in .htaccess
AddDefaultCharset UTF-8
Make sure your HTML templates aren't setting a different charset. Check whatever templates have the opening <html> and/or <head> tags.
Edit Since your templates are encoded properly, it will probably be worthwhile to do a quick "find in files" search for iso-8859-1 and see where it's getting overridden. If it's anywhere in the core CodeIgniter instance, and you're using the most recent version (and haven't edited the core), then it might be a bug, and you'll need to report it to the CodeIgniter people.
Keep in mind, though, that it's not necessarily a bug, but a different setting overriding that one. Make sure you look at the context of any instances you find it, before you jump to the bug report form.
I have a multi language website that is hosted on a server that appears to have character encoding set to default to iso-8859-1.
I thought I would be best having the pages utf-8 and included a meta tag to declare this. Unfortunately this meta tag seems to get overridden and the page defaults to iso-8859.
Many special characters in the German and Dutch pages are not showing correctly.
Do I need to try and change the server default to utf-8 or something? Maybe I could remove the server default completly? Hmm... really not sure what's best to do here.
Any advice would be great!
The HTML meta tags for the content type are not used when the HTML page is served over HTTP. Instead, the content type header in the HTTP response will be used. You can determine the content type header with for example Firebug, in the Net panel.
How to change this depends on the programming language and/or the webserver which you are using, which is unclear from your current question. As per you question history, you seem to be using PHP. In that case, you need to add the following line to the PHP file, before you emit any character to the response.
header('Content-Type: text/html; charset=UTF-8');
See also:
PHP UTF-8 cheatsheet
If you're unable to change the HTTP response header, you have to give more detail about the programming language and webserver which you're using. This way we can give you better suited answers.
If you want to stick to ISO-8859-1, then you need to ensure that your pages are saved as ISO-8859-1 as well instead of as UTF-8. Otherwise some characters may indeed go mojibake when you display a UTF-8 saved resource as ISO-8859-1.
There are several possible solutions, but the cleanest solution would be to properly declare your character encoding.
When serving web pages from an HTTP server, the encoding is normally not given by the meta-tags of the HTML file, but by the Content-type HTTP header.
The webserver is probably sending something like Content-type: text/html; charset=ISO-8859-1, and you need to change that.
How to do this depends on the webserver.
As an addition: Yes, iso-8859-1 is fine for German; it will work for all western European languages. It is missing a few characters, however, notably the Euro sign (that is in iso-8859-15). But using UTF-8 is better, as it covers just about every language.
You can see the characters supported and the languages that should cover in this Wikipedia article. According to that, German is fully supported and Dutch is almost.
It's not just a matter of selecting the correct character encoding, you also have to save the pages using that encoding. If you save a page as ISO-8859-1 and use a content type that says that it's UTF-8, then it will be decoded incorrectly by the browser. Both ISO-8859-1 and Unicode support the characters you need, but you have to make sure that the content type corresponds to how the pages are actually saved.
I'm treating all *.jpg files as static, but I need to serve a few dynamically. Can I simply omit the extension so I don't have to get fancy with my url rules? Is it enough to just set the file type in the header?
I've never had a problem serving dynamic images with a strange extension or no extension at all. Querystrings are also fine.
It will be enough for the headers to be correct and the binary file correctly formed. When you do this make sure you also set the Content-Disposition to a reasonable file name so people don't try to download your files with crazy querystring names. (Which windows users will be unable to save since they will most likely have a "?" in them.)
Instead of omitting the extension (on your server), activate content negotiation (i.e. +MultiViews if you're using Apache) and omit the extensions in your URIs. That way, Apache will decide what file to serve; you could have an image in both png and svg format, and serve the one accepted by the browser.
Generally, a correct Content-type header is enough.