搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

html 5 charset issue

  • 1 回覆
  • 6 有這個問題
  • 1 次檢視
  • 最近回覆由 gnittala

more options

We have an application using html5. The server returns an accepted charset of utf-8. On the page is the following meta-tag: <meta charset="utf-8">.

When inputting "special"characters (é, è, à, etc) and submitting the form, firefox translates this to these characters: éÃ. Further examination tells us that these are utf-8 representations of the iso-8859-1 values for the given characters. (we are using firefox on windows)

When putting the accept-charset on the html-form, the issue is solved. However when reading the html5 spec, it seems to me that firefox should interpret either the server response or the meta-tag and submit the content as utf-8.

We have the same issue in chrome, however in IE it seems to work.

We have an application using html5. The server returns an accepted charset of utf-8. On the page is the following meta-tag: <meta charset="utf-8">. When inputting "special"characters (é, è, à, etc) and submitting the form, firefox translates this to these characters: éÃ. Further examination tells us that these are utf-8 representations of the iso-8859-1 values for the given characters. (we are using firefox on windows) When putting the accept-charset on the html-form, the issue is solved. However when reading the html5 spec, it seems to me that firefox should interpret either the server response or the meta-tag and submit the content as utf-8. We have the same issue in chrome, however in IE it seems to work.

所有回覆 (1)

more options

Hello,

Can you please confirm the following

  1. The file is saved with UTF-8 encoding
  2. Are the pages getting served by server side scripting (PHP etc) or is it a HTML+JS single page application
  3. Is it possible for you to provide a sample of the <meta> tag you are using

Like you mentioned, if you did provide the charset in the meta tag, it is not required to set the charset for the form (provided the charset is the same), but the browser should be able to identify the charset properly.

Can you please check these links to see if having the charset within the first 512/1024 bytes of the page is causing this issue

  1. Setting default encoding of a page to UTF-8
  2. Charset identified wrongly as Western-8859-1 for a UTF-8 page
  3. Details on MetaCharSetAttribute
  4. Meta on MDN

Thank you