On Thu, 10 Apr 2025 14:28:02 GMT, Magnus Ihse Bursie <i...@openjdk.org> wrote:
> Most of the JDK code base has been transitioned to UTF-8, but not all. This > has recently become an acute problem, since our mixing of iso-8859-1 and > utf-8 in properties files confused the version of `sed` that is shipped with > the new macOS 15.4. > > The fix is basically simple, and includes the following steps: > * Look through the code base for text files containing non-ASCII characters, > and convert them to UTF-8, if they are not already > * Update tooling used in building to recognize the fact that files are now in > UTF-8 and treat them accordingly (basically, updating compiler flags, git > attributes, etc). I would like to run proper tests to verify the changes in libjava, but I don't know what tests that would be. If anyone can enlighten me, please do. (I suspect that the code did not really work properly before, and that the specially encoded characters where not thoroughly tested, but I can be wrong.) ------------- PR Comment: https://git.openjdk.org/jdk/pull/24574#issuecomment-2800165519
