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

[Phil Race]

On Thu, 15 May 2025 12:33:06 GMT, Raffaello Giulietti <rgiulietti at openjdk.org> wrote:

>>> 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.
>
> FYI, the style guide for France [recommends](https://fr.wikipedia.org/wiki/Espace_ins%C3%A9cable#En_France):
> 
> - U+202F (Narrow No-Break Space NNBSP) preceding semicolon, question mark, and exclamation mark.
> - U+00A0 (No-Break Space NBSP) preceding colon.
> 
> Similar conventions are used in other French speaking countries.

> 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.


I didn't say it reversed that entire changeset. I am saying that the previous changeset for L10N changed

the Java unicode escape to UTF-8 for the localised message string.

You propose restoring it to Java escape.


I wouldn't be surprised if the next message drop reverses what you reversed.

I don't know what tools the L10N team use but there's a chance it doesn't handle Java escapes

since that is very much a Java thing. So you are probably making the translation job harder.


So I am suggesting you leave all of the translation files as is.
Which might mean withdrawing this PR.

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

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