PDA

View Full Version : Guests & Users writing public feedback in Korean


yowsupjj
18th of November 2003 (Tue), 19:14
Hi,
This is my website: Http://WWW.JJPIX.COM

I have mainly Korean visitors to my site. the problem is not them having to read English from my site.

the problem is, most of the visitors that I get, WRITE COMMENTS in Korean into my message boards... or the PUBLIC FEEDBACK sections.

When they write on the field box, it shows the Korean fonts being typed, but as soon as you click 'CLICK HERE TO SEND YOUR FEEDBACK' the words get all scrambled and there are only unknown characters shown.

Is there a way to enable the messages to be shown in Korean?

I thought the languages depended on the users PC. If they had the languages installed on their system or not. Also if they had the correct encoding set for their browsers. Does EE just not allow other languages?

I would appreciate some feedback please.

Thank you

JJ

JJ@JJPIX.COM

TomKa
19th of November 2003 (Wed), 01:54
Changing the character set of the html page into UTF should perhaps solve your problem. But I don't know if there are problems with EE - A question for Pekka.

Actually there is the following tag in the header of the EEpages:


it should be:

yowsupjj
19th of November 2003 (Wed), 03:33
Hi,
thanx for the quick reply.

I tried to find that in my feedback.php or header.php but it doesn't seem to be there.

I found something similar in a file called, feedback_editor.php in the INPUT folder.

">

looks like its a php statement. So, I'm not sure if I'm just supposed to overwrite this statement with the text you have given me.

I don't really know much about php.

So... would you be able to tell me exactly which file I'm supposed to open and make those changes in?

There are so many files in different directories, I don't know which one I'm supposed to be looking at.

Sorry, for the trouble...

TomKa
19th of November 2003 (Wed), 05:01
You have to wait for Pekka's response, I don't want to mess up your EE.
The character set tells the browser which characers to use to form the html page.

In the file global.php (directory languages/eng) on line three you have:

$s_charset = "iso-8859-1";

You can try to change the character set here, I don't know if this will work (make a backup of the old global.php).

Pekka
19th of November 2003 (Wed), 05:19
Open file gallery/languages/eng/global.php into text editor (not Word!) and

replace line

$s_charset = "iso-8859-1";

with

$s_charset = "UTF-8";

Actually it may be a good idea to change all languages (language/xxx/global.php) like this so you can view mixed character sets no matter which UI language you have selected.

This may not affect existing feedbacks but will affect all new ones.

Other option (if you expect only Korean or English feedback) is to use Korean character set definition

KSC 5601

instead of UTF-8, which makes the pages korean by default but AFAIK all browsers display western ASCII, too.

UTF coding needs support from operating system and browser used, a good test page is http://www.columbia.edu/kermit/utf8.html

For example, on Windows XP Firebird displays it much better than IE.

yowsupjj
19th of November 2003 (Wed), 16:29
TomKa & Pekka!
Thanx so much!!! Everything worked out PERFECTLY!!!
I love it!! I really love EE.

The one thing I wouldn't mind adding to the function would be
'Groups - Exhibitions - Sub Exhibitions?' which [dunhill] already posted.

Anywayz, I just wanted say thank you!~

P.S. One quick question. I see beta updates on the site. Is it always neccessary to have the latest update for EE? I have till the 1.5 beta 4 update 2.

Pekka
20th of November 2003 (Thu), 10:23
yowsupjj wrote:

The one thing I wouldn't mind adding to the function would be
'Groups - Exhibitions - Sub Exhibitions?' which [dunhill] already posted.


I'll think of something in following versions.

Anywayz, I just wanted say thank you!~

:)

P.S. One quick question. I see beta updates on the site. Is it always neccessary to have the latest update for EE? I have till the 1.5 beta 4 update 2.

There are some important fixes in newer betas and fix packs. I recommend updating up to beta 1.5 fix pack 2.