On Thu, 22 May 2025 21:26:08 GMT, Phil Race wrote:
>> 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
On Thu, 15 May 2025 12:33:06 GMT, Raffaello Giulietti
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
On Thu, 15 May 2025 09:17:42 GMT, Magnus Ihse Bursie wrote:
>>> 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
On Thu, 15 May 2025 03:18:30 GMT, Naoto Sato 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?
>
> Maybe, but sometimes it is intentional. CLDR has once switched normal spaces
> to NBSP/NNBSP for certain
On Thu, 15 May 2025 09:16:10 GMT, Magnus Ihse Bursie 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,
On Thu, 15 May 2025 02:25:30 GMT, Sergey Bylokhov wrote:
>> I believe it is OK to leave these as UTF-8 native characters, as these files
>> are l10n resource bundles. If we wanted to replace those look-alike spaces
>> to unicode escapes, other characters may also need the same treatment, such
On Wed, 14 May 2025 17:34:45 GMT, Naoto Sato wrote:
>> For the l10n files, they are synced by the translation team and we don't
>> edit them. IMO, I think it's fine leaving those ones as is. Especially
>> because language rules can cause different spacing and punctuation
>> characters, so gene
On Wed, 14 May 2025 17:18:35 GMT, Justin Lu wrote:
>> src/java.desktop/share/classes/com/sun/java/swing/plaf/gtk/resources/gtk_fr.properties
>> line 39:
>>
>>> 37: GTKColorChooserPanel.hue.textAndMnemonic=&Teinte :
>>> 38:
>>> 39: GTKColorChooserPanel.red.textAndMnemonic=Roug&e\u00a0:
>>
>> S
On Wed, 14 May 2025 16:59:23 GMT, Phil Race wrote:
>> Non-breaking space characters are problematic. They look identical to the
>> normal space character, but is not. For that reason, it should never be
>> typed as an UTF-8 literal, but only by using unicode sequences.
>>
>> I have checked:
>>
On Wed, 14 May 2025 15:11:24 GMT, Magnus Ihse Bursie wrote:
> Non-breaking space characters are problematic. They look identical to the
> normal space character, but is not. For that reason, it should never be typed
> as an UTF-8 literal, but only by using unicode sequences.
>
> I have checked
10 matches
Mail list logo
