Perhaps it is the include for the ui templates that uses the wrong character encoding and therefore your ui tags are messed up? I don't know WW2, but I assume now that it is working the same way as in WW1.3: The UI tags call a static include method that resides in the IncludeTag class in order to include the JSP template for the ui tag. This method in the IncludeTag looks for the property webwork.i18n.encoding which it uses when writing the result to the servlet response. If the encoding is not set correctly then perhaps you could get the problems you are describing?
Best regards, Dick Zetterberg [EMAIL PROTECTED] ----- Original Message ----- From: "James Pan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 30, 2003 3:48 PM Subject: RE: Spam:[OS-webwork] Again: internationalization problems > I don't think so, though I'm not 100% sure. > > I changed the encoding of the JSPs and template JSPs to UTF-8 (manually saving the > files in UTF-8 format), which is why the Japanese show up directly in my JSPs. > However, I'm inclined to think that the taglib is what's messing with the encoding, > because after all, only the <ui:xxx /> tags mess up (and this is from adding a line > <webwork:text name="'main.title'" /> in both controlheader.jsp *and* text.jsp in > /template/xhtml... > > Help please!! The end of the project is so close I can smell it, I just need to > solve this last problem! Thank you!! > > James > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
