WordPress.org

1. Anonymous
   Unregistered
   Posted 8 years ago #

   Hi,
   I am trying to use WordPress as my blog tool.
   But WordPress has a problem in charset encoding, I guess.
   When I was Korean, the characters are displayed well on Web browser. However, when I view the source with NotePad, the characters are displayed as following:
   #44228;룡산 하면 그동안 동학
   Of course I had checked the related configuration in b2config.php :
   // IMPORTANT! set this to 0 if you are using Chinese, Japanese, Korean,
   // or other double-bytes languages
   $use_htmltrans = 0;
   Could you help me?

2. Anonymous
   Unregistered
   Posted 8 years ago #

   do you set charset in meta tag in html?
   like <meta http-equiv="Content-Type" content="text/html; charset=euc-kr" />

3. Anonymous
   Unregistered
   Posted 8 years ago #

   <meta http-equiv="Content-Type" content="text/html; charset=euc-kr" />

4. Anonymous
   Unregistered
   Posted 8 years ago #

   espacially when meta tag of b2edit.php is iso-8859-1,then
   your input multibyte characters are automatically converted entity references by browser.
   please please,developpers.
   don't hardcoding charset of metatag or header.
   please make changeable it in b2config.php
   like
   <meta http-equiv="Content-Type� content="text/html; charset=$charset" />

5. Anonymous
   Unregistered
   Posted 8 years ago #

   Yes, I tried to change all meta tags to assign encoding charset.
   However, I can't get a appropriate charset in view source mode. :(

6. Anonymous
   Unregistered
   Posted 8 years ago #

   first,I can see the korean text.
   but this page encoding is iso-8859-1,
   so the text is converted "Character entity references".
   so probably your input page is viwed in latin encoding.
   confirm your page encoding when posting.
   or
   maybe htmlentities() function is the origin.
   convert "htmlentities(" to "htmlspecialchars".
   http://jp.php.net/manual/kr/function.htmlentities.php
   sorry, I don't know when it used in source.
   please search.

7. Anonymous
   Unregistered
   Posted 8 years ago #

   when >>where
   mistake

Topic Closed

This topic has been closed to new replies.