ansaurus

Question

django + mysql + UTF-8 - Chars are not displayed

Answer 1

+3 A:

That source code, when placed into an otherwise empty HTML document, looks like this for me in Google Chrome, IE and Firefox:

まいにちいっしょ

Which appears to be what you want.

My only thought is that that is not really the source code, and you've in fact got source code that looks like this:

&amp;#12414;&amp;#12356;&amp;#12395;&amp;#12385;&amp;#12356;&amp;#12387;&amp;#12375;&amp;#12423;

in which case you're HTML-encoding something that's already HTML-encoded.

If that's not the case, then I've no idea.

The source I used to test this is:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt; 
<html xmlns="http://www.w3.org/1999/xhtml"&gt; 
  <head> 
    <title>Foo</title> 
  </head> 
  <body> 
   <p>&#12414;&#12356;&#12395;&#12385;&#12356;&#12387;&#12375;&#12423;</p>
  </body> 
</html>

Dominic Rodger 2009-12-18 13:21:23

Answer 2

A:

As Dominic has said, the generated HTML source code is correct (these are your Japanese characters translated into HTML entities), but we're not sure, if you see the same code rendered in the page (in this case, you have probably set content-type to "text/plain" instead of "text/html" - do you use render_to_response() or HttpResponse() in the corresponding view.py method?), or your Japanese is rendered correctly but you just don't like the entities in the source code.

Since we don't know your Django settings and how do you render and return the page, it's difficult to provide you the solution.

mykhal 2009-12-18 22:30:47

Answer 3

A:

the problem is the auto escape django function ... my source code is like the one that Dominic pasted :

&#12414;&#12356;&#12395;&#12385;&#12356;&#12387;&#12375;&#12423;

i simple put the tag in places there i known that may be some diff chars:

{% autoescape off %}
xxxxx
{% endautoescape %}

and everything works like a charm... :D

than you all

http://docs.djangoproject.com/en/dev/ref/templates/builtins/#autoescape

fabriciols 2009-12-21 09:43:23

Actually, use the `safe` template filter, e.g. `{{ var|safe }}`. (Documentation on the page linked to by this answer.)

Michał Marczyk 2009-12-21 09:51:53

"safe" is the better way ?

fabriciols 2009-12-21 10:51:25

Well, not always, in fact sometimes `{% autoescape off %}` / `{% endautoescape %}` is really the only way to go, but with just one problematic variable's contents being unnecessarily escaped, I'd say it's best to be explicit about the intent to turn autoescaping off for that particular variable so as to decrease the probability of catching something which actually *should* be escaped in the `autoescape off` block. Obviously that would very likely be a bigger problem than overzealously escaping something where it's not desired could ever be.

Michał Marczyk 2009-12-25 05:32:26

ansaurus

tags:

views:

answers:

django + mysql + UTF-8 - Chars are not displayed

related questions