<div>It appears that you're trying to convince Seaside to send UTF-8, right? I had the same problem during my time working with it. Then again, I didn't want complete texts but only the Euro currency sign. And and what I did was: I left my fingers off of WAListener and all those. Instead, I assembled the three bytes needed for a Euro sign myself by hand into a normal String and lo and behold, it looked right in the browser.
</div>
<div> </div>
<div>For Korean your approach is probably better, I guess. Mine was unsatisfying, too, because it assumed incoming text to be encoded in latin-15, but emitted texts in utf-8. Really not satisfying. I thought, the right approach might be to enhance the String class with an additional field for the encoding and give it some methods to transcode between them. By the way: the method asUtf8 (or something like that) does not work properly with the Euro sign.
</div>
<div> </div>
<div>For example, when you print this: </div>
<div> </div>
<div> 'Grüß Gott!' asUtf8</div>
<div> </div>
<div>it looks awful, because the new string doesn't know it's UTF-8.</div>
<div> </div>
<div>So, it appears that for Seaside to cope with Korean well, you might have to change more than Seaside only. </div>
<div> </div>
<div>niko<br><br> </div>
<div><span class="gmail_quote">2008/1/3, <a href="mailto:chunsj@embian.com">chunsj@embian.com</a> <<a href="mailto:chunsj@embian.com">chunsj@embian.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>I've managed to find and modify WAListenerEncoded so that it can process<br>multibyte language - I've only tested it with Korean as UTF-8. During testing
<br>I found following problem.<br><br>When I use WAListener/WAListenerEncoded I cannot get FileLibrary registered<br>image files correctly. I can get CSS file or script file correctly, but I cannot get<br>image files.<br>
<br>It seems that when I use WAListener, the server sent the image file of the size<br>of 16135 byte, but original file size is 10819 byte, and this might be the source<br>of the problem. I cannot open wrong sized file even though I cut the size of the
<br>file to the original one.<br><br>Can anyone help me? Thanks in advance.<br><br><br></blockquote></div><br>