1)
Korean(KR) language file (UTF-8 text file) / About 15% are translated.
Google Docs, work in progress
https://docs.google.com/spreadsheets/d/ ... p=sharing
2)
If I set to use SQL language (MYSQL utf8_general_ci charset), The lastest SVN does not show non-ASCII letters , only show "??". It works correct if I set to use Text language file (KR, UTF-8 text file). I think there may be a problem to process the UTF-8 SQL query results. DE language also does not show non-ASCII letters(umlaut , Ä, Ö, Ü) when I use SQL language DB.
ps)
I added one screenshot.
Environment:
SVN 3375 Dolserver (Use Text Language File ; use_dblanguage=FALSE )
(language TXT(UTF-8) file : GamePlayer.Sit.YouSitDown: DE(äü) 앉았습니다. 일어나려면 '/stand' 치거나 움직이세요.)
Client 1.109 , chat font 굴림(korean font) , main.dat ([international], mbcs=1, codepage=949)
1) It shows "Do you want to be teleported to [CLASHED LETTER].
Actually [CRASHED LETTER] is "돌토피아", UTF-8 encoded in script folder.
It crashed but it's because client does not support Korean font. It's a client-side problem.
I will work OK, if I change the client font which can support Korean.
2) It shows "DE(au) 앉았습니다. 일어나려면 '/stand' 치거나... ".
Dolserver can read UTF-8 language text database (/release/language folder) . All Korean correct.
In this time, because I set chatting font to 굴림-font(Korean font), it show correctly.
"DE(au)" is not correct. actually it is DE(äü) . The reason it show false , is the korean font does not support German umlaut.
ps) I added one more screenshot. in some case, UTF-8 SQL DB works.
SQL (edited by phpmyadmin)
column dolcharacters.name --> "피부미인" (UTF8)
In screenshot (chracter selection), you can see correct Korean character name.