I have several .APT documents hat were created for a site processed by the
maven-site-plugin. Everything works fine even with special characters (like
like Ä, etc...) in the generated HTML.

The maven-site-plugin is configured for ISO-8859-1.
<plugin>
        <artifactId>maven-site-plugin</artifactId>
        <configuration>
                <locales>en</locales>
                <outputEncoding>ISO-8859-1</outputEncoding>
        </configuration>
</plugin>
All .APT documents are using the ISO-8859-1 encoding (my eclipse IDE is
configured with -Dfile.encoding=ISO-8859-1).

Now I have added the doxia-maven-plugin for creating a  PDF book from all
.APT documents that were written for the site.
The doxia-maven-plugin throws a ExceptionConverter:
org.xml.sax.SAXParseException: Invalid byte 2 of 2-byte UTF-8 sequence
 exception when processing any .APT document that contains a special
character (like &Auml;).

With some experiments I have figured out when converting the .APT documents
from  ISO-8859-1 to UTF-8 the doxia-maven-plugin creates a perfectly fine
(with correct special characters) PDF !

BUT now the the site HTML does not show special characters properly.

I have extended these tests for the XDOC doxia module. All of the .APT files
that are using the UTF-8 encoding do not produce proper HTML whereas all
.APT files with ISO-8859-1 encoding produce correct HTML.

Now I hope somebody can give me a clou on how to get both the
maven-site-plugin and the doxia-maven-plugin working with special
characters!

To me it looks like the maven-site-plugin and doxia-maven-plugin do not work
the same way regarding file encoding!

Thanks
  Martin


-- 
View this message in context: 
http://www.nabble.com/doxia-maven-plugin---special-characters-%28German-Umlaut%2C-etc...%29-tf2540610s177.html#a7078235
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to