Encoding of the web page - encoding

I have used a free template and used it as a master page in the visual web developer.
Each time I close the master page file and reopen it it will ask me for the encoding of the web page. The title is "Choose an encoding", and body is "Visual web developer was unable to determine the encoding of this file. Please choose an encoding from the list box below".
How can I fix this? How can I save the file with UTF-8 encoding from the beginning.

Try putting a tag like this inside the <head> element:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
That's how you identify the encoding to browsers. Not sure about the editor you're using.

Related

Why are special characters displayed as question marks in Facebook posts?

When we share links to our magnolia website (running on Tomcat), umlaut characters are displayed as question marks.
The page head has <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> and the response header has content type text/html;charset=UTF-8 and content encoding gzip. What could be causing the wrong character encoding on Facebook?
In the end I found out, that my problem was not related to the character encoding, but rather the Facebook crawler request. The Facebook Sharing Debugger really got me on track. The core problem was that, the magnolia cache did not support partial requests.
Edit:
HTTP range requests from Facebook is a known issue, see https://documentation.magnolia-cms.com/display/DOCS62/_Known+issues#id-_Knownissues-HTTPrangerequestsfromFacebookdon%27twork

Russian Text in HTML Email (In Russia)

I pasted in my HTML code into Exact Target (email vendor), using this character set:
<meta http-equiv="content-type" content="text/html;charset=utf-8" />
The HTML body text was in Russian, and I tested it in several browsers and email clients - looked fine, until it got to Russia. See attached screenshot I was provided with. Screen shot
Lots of UNICODE replacement characters.
What happened, and what do I do to make sure my Russian text works in Russia?

Weebly header links encoding error for arabic site

My arabic website is created using weebly, today when i wanted to edited any page i found the page I am editing is with encoded page title! even after changing the title again to be arabic, nothing is happening and stil the title is encoded!
I checked my code and it is ok! :
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
And this is the website: www.elbosna.com
Is there any solution to this wired problem that appeared only today?
The strings that you send to the function initPublishedFlyoutMenus are encoded incorrectly. Instead of strings like "title":"&#1575;&#1604;.. your code should contain strings like "title":"ال.. without the & escape code.
Some of the titles in the navigation menu are encoded correctly, so check the configuration on your side, what is the difference between correct and incorrect menu items. It may be something with the tools you use to edit the site's configuration

using .php with .css or some thing better?

I have a log in page for my web site. The log in file is "index.php" this will be the first page you come to when comming to my site. The rest of my site is HTML with a style.css file providing the look for my site. Now my questions is how do I get my index.php file too look like the rest of my web site?
Right now when you come to mydomain.com/index.php it is just a white page with a log in and password box. I would like my log in page to look like the rest of my web site. Can some one please refer me as how to do this?
I have other .php files that would also need to be linked with the .css such as register.php and so forth. thanks guys.
If there is a different/better method of doing what I need please feel free to chime in, I'm all ears at this point I've been trying to do this for 2 days.
Like you would do in every other html page you will have to link the file the same way.
I guess that you have already seen that in every php file there is html code?
Just stay out of the php brackets
<!DOCTYPE html>
<html>
<head>
<link rel="stylesheet" type="text/css" href="styles.css">
</head>
<body
<?php
"php code in here"
?>
</body>
</html>
If you don't find the usual html markup somewhere search for a include function in the php file.
Maybe the html header is in other php file and it is being called from there.
They would be included like this
include '_header.php';
You can use the CSS file, similar to how you use it in your HTML files. You can either post the CSS tag below your PHP code, or you can use an echo "cssTagHere"; call within your PHP code.
If you're using a login page, though, are you maintaining that security with the rest of your site by using PHP on your other pages?

classic asp character encoding

I'm having a problem with Spanish characters in a classic asp site. A user is able to submit their name/address in a form on an aspx page. The aspx page then does an ajax post to a classic asp page which all it does is stored in our Sql 2008 DB. I can see in the database that the character is not stored correctly. For example the first name looks like Mª where it should be Mª.
When I then read that data and display it in a text box it is still displaying Mª.
things I've tried:
<%# Language=VBScript codepage=65001 %>
<% Response.Charset="UTF-8" %>
encoding file as UTF-8 (using notepad++)
any other ideas? Do I need to go back into the database and fix the characters first or can this be done when I read the characters and display them?
I had same problem when started using utf-8 on ASP, found that session.CodePage makes the difference. In classic ASP pages do always this first ASP declarations to ensure all page uses UTF-8 for data, forms, asp code, data received or sent.
<%#Language=VBScript CodePage = 65001%>
<%
Session.CodePage = 65001
Response.charset ="utf-8"
Session.LCID = 1033 'en-US
%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
What you are looking at is UTF-8. It's probably exactly as it should be, and the problem is that the tool you use for the looking is not handling the UTF-8 correctly, either because it cannot, or because it is not configured correctly.