본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Appears to ignore charset in http-equiv meta directive

  • 3 답장
  • 2 이 문제를 만남
  • 27 보기
  • 최종 답변자: cor-el

more options

<head> section contains <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

but the "micro" symbol is displayed as the white question mark on a black diamond background. In the datastream received this symbol is correctly encoded for iso-8859-1 as hex b5.

The browser reports page text encoding as UFT8 when queried by clicking on favicon on address bar, selecting "more info", then "general". However, page (as transmitted from host) does not contain the text "UTF".

This behaviour was observed on page http://www.8052.com/store/index.phtml?PRODUCTID=9.

Why is this? It appears to me that 1) the browser is ignoring the charset directive, or 2) I have created an override somewhere

<head> section contains <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> but the "micro" symbol is displayed as the white question mark on a black diamond background. In the datastream received this symbol is correctly encoded for iso-8859-1 as hex b5. The browser reports page text encoding as UFT8 when queried by clicking on favicon on address bar, selecting "more info", then "general". However, page (as transmitted from host) does not contain the text "UTF". This behaviour was observed on page http://www.8052.com/store/index.phtml?PRODUCTID=9. Why is this? It appears to me that 1) the browser is ignoring the charset directive, or 2) I have created an override somewhere

선택된 해결법

The server sends the file as "Content-Type: text/html; charset=UTF-8" and that prevails over what is specified in the main HTML file.

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

Visitors would have to change the encoding manually from Unicode to Western. Best would be to save the HTML file as Unicode (UTF-8) and re-upload the file.

The characters are in the same position in Unicode.

Only 20-µA current
Intel® BASIC-52
Power down mode reduces current requirements to 20 µA.
Some ±8V power
문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (3)

more options

선택된 해결법

The server sends the file as "Content-Type: text/html; charset=UTF-8" and that prevails over what is specified in the main HTML file.

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

Visitors would have to change the encoding manually from Unicode to Western. Best would be to save the HTML file as Unicode (UTF-8) and re-upload the file.

The characters are in the same position in Unicode.

Only 20-µA current
Intel® BASIC-52
Power down mode reduces current requirements to 20 µA.
Some ±8V power
more options

Thank you. Very silly of me to have ignored the HTTP headers. They were there, in front of me in the tcpdump I'd done. So, we have a mis-configured server or a user of said server who doesn't understand what he's doing.

This is frightening. I'm increasingly seeing examples of technology being used without any understanding of what it's doing.

글쓴이 catsmum 수정일시

more options

It is best to keep the server set to Unicode and advice users to make sure that all files are saved as Unicode as well. Unicode should cover all possible characters and shouldn't cause issues with visitors from various countries.