搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

UTF-8 problem

more options

Depending on the way I call a page, utf-8 does not show properly. The best way is to provide an example. Please, try this:

http://www.logicamix.fm.usp.br/cgi-bin/smst_testeeutf8.cgi

It is a test page in Portuguese. At the bottom part of this page there is a textarea that repeats the last entry. Just type anything that requires utf-8, send it (click [Enviar esta nota]) to store it in my database (correctly configured to utf-8) and return to the previous page by clicking [Clique aqui para voltar à tela anterior].

All characters that were displaying nicely are now messed up. Even without the source code of my cgi, You can save the page html (CTRL+U) before and after. I did so and applied Kompare to check for differences. Except for the additional entry, they are both identical !

Is ThIs a bug? I am using Ubuntu 14.04 and 16.04, but this behavior reproduces in Windows and MacOS, too. Chrome shows everything correctly.

Depending on the way I call a page, utf-8 does not show properly. The best way is to provide an example. Please, try this: http://www.logicamix.fm.usp.br/cgi-bin/smst_testeeutf8.cgi It is a test page in Portuguese. At the bottom part of this page there is a textarea that repeats the last entry. Just type anything that requires utf-8, send it (click [Enviar esta nota]) to store it in my database (correctly configured to utf-8) and return to the previous page by clicking [Clique aqui para voltar à tela anterior]. All characters that were displaying nicely are now messed up. Even without the source code of my cgi, You can save the page html (CTRL+U) before and after. I did so and applied Kompare to check for differences. Except for the additional entry, they are both identical ! Is ThIs a bug? I am using Ubuntu 14.04 and 16.04, but this behavior reproduces in Windows and MacOS, too. Chrome shows everything correctly.

被采纳的解决方案

Never mind... I just figured out the problem. There was a line break in

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

For some reason, Chrome displays correctly if it is

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

but Firefox has the behavior I've described above.

定位到答案原位置 👍 0

所有回复 (1)

more options

选择的解决方案

Never mind... I just figured out the problem. There was a line break in

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

For some reason, Chrome displays correctly if it is

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

but Firefox has the behavior I've described above.