On Fri, 2 Dec 2022 17:12:55 GMT, Andy Goryachev <ango...@openjdk.org> wrote:
>> This turned out to be much more complicated than anticipated. I am going to >> close this PR (and bug), and instead I have split up this work in five >> different bugs: >> >> [JDK-8298047](https://bugs.openjdk.org/browse/JDK-8298047) is about removing >> all non-significant whitespace from all properties files, basically >> corresponding to how this PR looked after the second commit. >> >> [JDK-8298042](https://bugs.openjdk.org/browse/JDK-8298042), >> [JDK-8298044](https://bugs.openjdk.org/browse/JDK-8298044), >> [JDK-8298045](https://bugs.openjdk.org/browse/JDK-8298045) and >> [JDK-8298046](https://bugs.openjdk.org/browse/JDK-8298046) is about fixing >> the significant whitespace, by turning it to unicode sequences or removing >> it, if it turns out there should not have been a space there. This work is >> split into four parts to be able to have one bug per component team. > >> and instead I have split up this work in five different bugs > > would you consider also adding a unit test to check whether the localized > resources also contain leading/trailing whitespace, and possibly special > characters (like {, }, , etc.) that are present in the main resource? @andy-goryachev-oracle No. Any such test is up to the component owners to write, if they deem it fitting. ------------- PR: https://git.openjdk.org/jdk/pull/10792
