jkesselm commented on PR #167: URL: https://github.com/apache/xalan-java/pull/167#issuecomment-1912916533
We both have solutions (mine is at https://github.com/apache/xalan-java/tree/XALANJ-2618), I think I like my fix a bit better, since it resolves the problem without having to remove encoding names that, correct or not, someone might have been depending upon, and addresses the problem at a systemic level rather than just patching this one encoding set. Any suggestions on the best way to make sure you get credit for isolating the issue while we check in my fix? (I'm used to working in an environment where we cared more about the fix getting in than exactly who got credit for it, so my reflexes are not entirely right for public Git. I'm trying to retrain myself to be more sensitive about that, recognizing that contributor history is important for most folks.) -- 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: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
