I have this code in an .js file, if it is downloaded via ftp
texto=texto.replace(/á/g,"Waacute;");
texto=texto.replace(/é/g,"Weacute;");
texto=texto.replace(/í/g,"Wiacute;");
texto=texto.replace(/ó/g,"Woacute;");
texto=texto.replace(/ú/g,"Wuacute;");
but when the web browser downloads it with the webpage, that is what it gets.
texto=texto.replace(/á/g,"Waacute;");
texto=texto.replace(/é/g,"Weacute;");
texto=texto.replace(/Ã/g,"Wiacute;");
texto=texto.replace(/ó/g,"Woacute;");
texto=texto.replace(/ú/g,"Wuacute;");
I don't know what's wrong with the code. I hope some body can guide me.
Thanks in advance.
ernesto
You've a UTF-8 file that's being parsed as if it was some 8-bit fixed Latin format.
Ideally, send the correct headers from the server (just how to do that depends on server and/or server-side scripting language). As a back up add <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> though it's sucky to have it disagree with the server.
Alternatively, use unicode escapes in the javascript, and you become immune to all of this.
Your file is encoded in UTF8, so the á character is encoded as 195 161.
The browser is interpreting the file as CP-1252, so those bytes are interpreted as two different characters
You need to add a Content-Type header to tell that browser that it's really UTF8:
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
(Or configure your server to send that header)
Related
Hello, Folks!
All my script files are utf8, the server responses are utf8, the db collation.. quite everything.
I have a JSON data that populates the options of a select box. When I fix ISO I get in trouble in UTF8, or vice versa.
The point is: How can select option display both ISO-8859-1 and UTF-8 special chars?
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<select id="values" name="values">
<option>VALÊNCIA 18</option>
<option>BAHRAIN ‫البØرين‬‎ 40</option>
</select>
</body>
</html>
I think it is not possible. But as in http://www.w3schools.com/tags/att_a_charset.asp this is possible but not supported by any popular browser, and it is obsolete in HTML5, so you should not use it.
As an alternate, you can convert non-Unicode text to UTF-8 using server-side script (PHP, ASP.net,...).
PHP ----> UTFString= utf8_encode ( ISO_String)
ASP.NET ----> utf8_encode= Encoding.GetEncoding(28591).GetBytes(ISO_String);
https://msdn.microsoft.com/en-us/library/zs0350fy%28v=vs.90%29.aspx
Hopefully you will find this helpful
[SOLVED] If any one had the same problem as me and the charset was already correct, simply do this:
Copy all the code inside the .html file.
Open notepad (or any basic text editor) and paste the code.
Go "File -> Save As"
Enter you file name "example.html" (Select "Save as type: All Files (.)")
Select Encoding as UTF-8
Hit Save and you can now delete your old .html file and the encoding should be fixed
I tried charset UTF-8 to display the ä, it displayed some square box.
Also i tried with charset ISO-8859-1 to display the ä, it diplayed as ä. (which is correct)
But When combine the above both charset within javascript condition, its not working properly. Refer below code,
<html>
<head>
<script type="text/javascript">
var lang = 'German';
function f(){
if(lang != 'SomeOtherLanguage'){
//here code will execute. And page should display square box. Instead of square box, ä is displayed. Which is wrong. I cant able to find reason.
metaTag = '<meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/>';
}
else
metaTag = '<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>';
document.getElementsByTagName('head')[0].innerHTML += metaTag;
}
</script>
</head>
<body onload="f()">
<h1>Latin letter : ä </h1> <br />
</body>
</html>
You can't, the character set is established by the parser, which needs to parse Javascript in order to generate that meta DOM.
You still can use only one character set and convert the data.
What you are attempting to do will never work.
If the raw bytes of your HTML are not encoded as UTF-8 to begin with, you can't claim UTF-8, in a <meta> tag, or an HTTP Content-Type header. You would be lying to the browser/client, and is why you get bad results.
Your code will "work" only when your <meta> tag claims ISO-8859-1 (and there is no Content-Type header to override that) if your HTML is actually encoded in ISO-8859-1. In several (but not all) of the ISO-8859-X charsets, including ISO-8859-1, ä is encoded as byte 0xE4, so your code "works" when claiming ISO-8859-1 if byte 0x34 is present in the HTML's raw data.
In UTF-8, ä is encoded as bytes 0xC3 0xA4 instead. If your HTML contains byte 0xE4, but you claim UTF-8, you get bad results (0xE4 is not a valid byte in UTF-8).
So, your <meta> tag (and HTTP Content-Type header) needs to claim a charset that actually matches the real encoding of the HTML's raw bytes.
If your HTTP server is serving a static HTML file, the file is encoded in a specific charset when the HTML is saved to file. That same charset needs to be specified statically in the <meta> tag (and preferably also in the HTTP Content-Type header). If your HTTP server is generating the HTML dynamically, it needs to encode the HTML in a specific charset for transmission, so it needs to specify that same charset in the generated <meta> tag (and Content-Type header).
In other words, stop trying to lie to the browser/client. Tell the truth, then you won't run into this problem anymore.
I have this code but it only works using english characters
$( "input[name*='Name']" ).attr("placeholder","姓名");
My web page displays other chinese characters just fine and if I change the chinese characters to "Name", it starts working again just fine. Is there something special I have to do here?
In the header, I do see this as the encoding...
<meta http-equiv="content-type" content="text/html; charset=utf-8">
If the script is inline (in the HTML file), then it's using the encoding of the HTML file and you won't have an issue.
If the script is loaded from another file:
Your text editor must save the file in an appropriate encoding such as utf-8 (it's probably doing this already if you're able to save it, close it, and reopen it with the characters still displaying correctly)
Your web server must serve the file with the right http header specifying that it's utf-8 (or whatever the enocding happens to be, as determined by your text editor settings). Here's an example for how to do this with php: Set HTTP header to UTF-8 using PHP
If you can't have your webserver do this, try to set the charset attribute on your script tag (e.g. <script type="text/javascript" charset="utf-8" src="..."></script> > I tried to see what the spec said should happen in the case of mismatching charsets defined by the tag and the http headers, but couldn't find anything concrete, so just test and see if it helps.
If that doesn't work, place your script inline
So this is the code:
<script type="text/javascript" charset="UTF-8">
function loadScript("http://www.qppstudio.net/individualdays/noscroll/2012-08-15.js") {
document.write('<script type="text/javascript" charset="UTF-8" src="', url, '">', '<', '/', 'script>');
}
</script>
Included in page header:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Page displays unicode characters without any problems expect for the part where posted javascript writes to page. Is the script changed somehow while being downloaded between different domains?
Probably. This is the first time that I've seen the charset attribute. I'm not sure what you try to achieve with it. If the server sends you file with iso-latin-1 encoding but you tell the browser the file has UTF-8 encoding, what should happen? The browser won't convert the file from one encoding to the other; the best that you could hope for is that the browser tries to interpret the byte stream as UTF-8 which will not work.
The correct solution is to configure the server to send the files with the correct encoding in the HTTP response header. The browser will look for this information and read the byte stream with the encoding specified there.
Don't forget to actually send the bytes in the correct encoding! This means: File reading, copying to the output stream + setting the encoding headers, everything must work perfectly or you will have odd bugs.
I want to read a file from my server with javascript and display it's content in a html page.
The file is in ANSI charset, and it has romanian characters.. I want to display those characters in the way they are :D not in different black symbols..
So I think my problem is the charset.. I have a get request that takes the content of the file, like this:
function IO(U, V) {//LA MOD String Version. A tiny ajax library. by, DanDavis
var X = !window.XMLHttpRequest ? new ActiveXObject('Microsoft.XMLHTTP') : new XMLHttpRequest();
X.open(V ? 'PUT' : 'GET', U, false );
X.setRequestHeader('Content-Type', 'Charset=UTF-8');
X.send(V ? V : '');return X.responseText;}
As far as I know the romanian characters are included in UTF-8 charset so I set the charset of the request header to utf-8.. the file is in utf-8 format and I have the meta tag that tells the browser that the page has utf-8 content..
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
So if I query the server the direct file, the browser shows me the romanian characters but if I display the content of the page through this script, I see only symbols instead of characters..
So what I am doing wrong?
Thank you!
PS: I want this to work on Firefox at least not necessarily in all browsers..
While my initial assumption was the same as T.J. Crowder's, a quick chat established that the OP uses some hosting service and cannot easily change the Content-Type headers.
The files were sent as text/plain or text/html without any Charset paramter, hence the browser interprets them as UTF-8 (which is the default).
So saving the files in UTF-8 (instead of ANSI/Windows-1252) did the trick.
You need to ensure that the HTTP response returning the file data has the correct charset identified on it. You have to do that server-side, I don't think you can force it from the client. (When you set the content type in the request header, you're setting the content type of the request, not the response.) So for instance, the response header from the server would be along the lines of:
Content-Type: text/plain; charset=windows-1252
...if by "ANSI" you mean the Windows-1252 charset. That should tell the browser what it needs to do to decode the response text correctly before handing it to the JavaScript layer.
One problem, though: As far as I can tell, Windows-1252 doesn't have the full Romanian alphabet. So if you're seeing characters like Ș, ș, Ţ, ţ, etc., that suggests the source text is not in Windows-1252. Now, perhaps it's okay to drop the diacriticals on those in Romanian (I wouldn't know) and so if your source text just uses S and T instead of Ș and Ţ, etc., it could still be in Windows-1252. Or it may be ISO-8859 or ISO-8859-2 (both of which drop some diacriticals) or possibly ISO-8859-16 (which has full Romanian support). Details here.
So the first thing to do is determine what character set the source text is actually in.