<i18n dev> RFR: 8356980: Better handling of non-breaking space

Magnus Ihse Bursie ihse at openjdk.org
Thu May 15 09:19:53 UTC 2025


On Thu, 15 May 2025 09:16:10 GMT, Magnus Ihse Bursie <ihse at openjdk.org> wrote:

>> Maybe, but sometimes it is intentional. CLDR has once switched normal spaces to NBSP/NNBSP for certain locales (https://unicode-org.atlassian.net/browse/CLDR-14032). And we cannot tell if it is intentional or not.
>
>> So, this exactly reverses what was done in the fix for JDK-8301991
> 
> No, it doesn't. I still agree with that fix -- the overwhelming majority of characters should indeed be UTF-8 instead of unicode sequences.
> 
> This is about a very specific character, that is impossible to visually tell the difference on screen from ordinary space.
> 
> Technically, it might be that some of these lines in the properties files are reversals of JDK-8301991, but that's just basically coincidence.

> maybe this is just a translation error and a simple space can be used instead, like in all the other properties in these files?

That seems unlikely. The pattern is used consistently in the French translations, where `Foo:` in the original is replaced with `Foo :` with a non-breaking space. I guess it is a French orthographic rule to have a space before the colon, and I understand why it really must be non-breaking in that case.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/25234#discussion_r2090695445


More information about the i18n-dev mailing list