Michiel Meeuwissen <[EMAIL PROTECTED]> wrote: > I do not yet quite understand. But mm:formatter has actually 2 modes, it > takes it's body as a String or it constructs a DOM tree internally. > > In both cases I think the information is received as String instead of as > byte-arrays (what XML's are). Being a Java String, the encoding gets > irrelevant, and I can imaging that specifying it again could give problems. > > Can you cite how excactly you used mm:formatter, or can you send a JSP which > reproduces the bug? > The jsp:
<%@ page session="false" language="java" contentType="text/html; charset=ISO-8859-1" %> <%@ taglib uri="http://www.mmbase.org/mmbase-taglib-1.0"; prefix="mm" %> <mm:formatter xslt="test.xsl"> <?xml version="1.0" encoding="ISO-8859-1"?> <p>Caf� twee�ntwintig</p> </mm:formatter> and test.xsl: <?xml version="1.0" encoding="ISO-8859-1" ?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform";> <xsl:output method="html" encoding="ISO-8859-1" /> <xsl:template match="/"> <xsl:apply-templates /> </xsl:template> </xsl:stylesheet> Using <?xml version="1.0" encoding="ISO-8859-1"?> returns a wrong encoding, but with <?xml version="1.0"?> everything is ok. Martijn Houtman
