fridrich commented on PR #1274: URL: https://github.com/apache/maven-javadoc-plugin/pull/1274#issuecomment-3415000337
> I think the problem is that javadoc does expect a certain encoding, so we have no choice but to actually use that one. If we always write in UTF-8, I don't see how that would work. So, maybe it would be better to cross-check where the original problem lies then. I was having a thought, that if while reading in the try catch block we actually set the charset we used for reading and we write using that one, it could eventually work. But then, I am not sure, because the exception does not necessarily need to be thrown if the path is a valid utf-8, but it is actually in other encoding. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
