Hi Lukas, Lukas Theussl wrote:
> Anders Hammar wrote: >> On Mon, Jan 17, 2011 at 08:48, Lukas Theussl<[email protected]> wrote: >> >>> >>> Ok, I get it. The xdoc should be written with the same encoding that is >>> used when it is read to generate the final report, which is >>> project.build.sourceEncoding (by default). >>> >>> >> No, it shouldn't. The xdoc xml file should be written with the encoding >> specified in the xml prolog. > > Well, the xdoc is generated, so there is no xml prolog yet. Which implies UTF-8 by XML specification ;-) > But the xml > encoding declaration should of course match the actual file encoding. It has to, otherwise the XML is simply invalid. >> I tried the latest snapshot and the prolog defines UTF-8 but the text is >> written with the encoding specified by project.build.sourceEncoding. If >> project.build.sourceEncoding is something other than UTF-8, non-ascii >> chars are garbled if properly reading the XML (i.e. honoring the encoding >> specified in the xml prolog). The XML parser will throw an exception in worst case (if the read garbage does no longer result in a defined UTF-8 character). > Then my guess is that PluginXdocGenerator writes the wrong prolog. Can > you construct a test case? I hate encoding issues, but since I was > stupid enough to try to fix it... ;) - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
