in reply to Re^3: Encoding/decoding for korean strings
in thread Encoding/decoding for korean strings
I gather from your other reply below that you've confirmed there is valid utf8 data stored in the database, so the problem would seem to be limited to the output process, and probably involves the discipline setting on the output file handle. But I'm just guessing here.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: Encoding/decoding for korean strings
by siva_pm (Novice) on Jun 15, 2016 at 23:00 UTC |