Re: WordML encoding problem

sc wrote: Just curious why I don't need to do setCharacterEncoding when I do response.setContentType("text/xml; charset=UTF-8"); You *do* need to call it, if you want to be sure things will work everywhere. There are various reasons it might work OK without doing that, most likely being that

Re: WordML encoding problem

character encoding it should assume is in use; setCharacterEncoding() > ensures that a particular encoding *is* used. The 'encoding' attribute > in your XML declaration must then match that encoding. > > HTH, > > L. &g

Re: WordML encoding problem

sc wrote: There is an earlier post http://mail-archives.apache.org/mod_mbox/struts-user/200603.mbox/[EMAIL PROTECTED] My problem is pretty much the same as described. But there is no soluton to it. My application is Tomcat + Struts. In the struts action class, I generates a WordML xml and th

WordML encoding problem

he code to: response.setContentType("text/xml; charset=UTF-8"); regardless of where I run the application, it can correctly display chinese characters, though in a text version. Any help is appreciated. SC -- View this message in context: http://www.nabble.com/WordML-encoding-pr