default XML encoding (UTF-8) or XML encoding set in XML files is ignored: inputEncoding is used instead

here are 2 patches to add XML encoding detection for contents that are defined in XML: xdoc, xhtml, docbook, fml

see http://docs.codehaus.org/display/MAVENUSER/XML+encoding for the roadmap to XML encoding support in Maven2

re-did the patch with latest trunk revision

patch reworked after the big refactoring in revision 562838.

From an API point of view, I am not at ease with Doxia.isXmlSource( String parserId ). I propose you a better approach which sounds better for me:

...
    /**
     * @param parserId Identifier for the parser to use.
     * @return the parser defining for parserId.
     * @throws ParserNotFoundException if no parser could be found
     * for the given id.
     */
    Parser getParser( String parserId )
        throws ParserNotFoundException;
...

...
    /**
     * @return xml for xml parser, text for text parser
     */
    String getType();
...

...
             boolean isXml = doxia.getParser( renderingContext.getParserId() ).getType().equals("xml");
...

Thoughts?

+1 on Doxia.getParser(String): Parser

-0 on Parser.getType():String
At least, there should be constants for "text" and "xml".
I prefer Parser.isXml() because getType() seems too open for me

Constants was implicit for me

IMHO isXml() is too specific for an api.

why not, today this attribute is used only for encoding algorithm selection, but it could be used more later: such a choice is more extensible
then go for it

instead of String constants, why not use int constants, which would more clearly show that not any value can be used: each value has a precise meaning in the code
and the code could switch(parser.getType()) instead of a suite of if (parser.getType().equals(Parser.TYPE_XML)) {} else if...

Patch applied with modifications discussed there.
Thanks again Herve.