Do you have tapestry 4.0 dtd in .application? <!DOCTYPE application PUBLIC "-//Apache Software Foundation//Tapestry Specification 4.0//EN" "http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd">
2005/8/30, Ted Steen <[EMAIL PROTECTED]>: > Thank you Mind Bridge! I obviously didn't read the docs carefully enough. > > You are absolutely right, except that it should be > <meta key="org.apache.tapestry.messages-encoding" value="ISO-8859-1" /> > not > <meta key="org.apache.tapestry.template-encoding" value="ISO-8859-1" /> > > > But for some reason the xml parser won't accept the <meta> in my > .application file > I get this error: > "org.apache.tapestry.util.xml.DocumentParseException: Unable to read > context:/WEB-INF/Peng.application: Element type "meta" must be > declared. [context:/WEB-INF/Peng.application, line 10, column 76]" > > Is this a bug or am I doing something wrong? > > On 8/30/05, Mind Bridge <[EMAIL PROTECTED]> wrote: > > Just as a reference: > > > > In Tapestry 4 the property files no longer need to be ASCII -- Tapestry > > implements its own parsing that is backward compatible with the Java > > one, but allows it to be based on other encodings if needed. > > > > Please read this for details: > > http://jakarta.apache.org/tapestry/UsersGuide/localization.html > > > > (just to mention: nice description Howard :) > > > > I am actually guessing that the problem may not be in the property > > files, but in your template encodings. > > > > Please place something like this in your .application file: > > > > <meta key="org.apache.tapestry.template-encoding" value="ISO-8859-1"/> > > > > Replace the encoding above with the one you use for the templates. That > > would also resolve any property problems as well, actually, since the > > encoding of the propery files defaults to the template encoding, unless > > specified separately. > > > > I hope this helps, > > -mb > > > > P.S. Please note that in Tapestry 3 the above line is > > <property name="org.apache.tapestry.template-encoding" value="ISO-8859-1"/> > > and the property files still require native2ascii > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > /ted > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
