On Mon, 9 Jun 2025 15:52:24 GMT, Magnus Ihse Bursie wrote:
>> After we converted the source base to be fully UTF-8, we do not need to use
>> unicode sequences (like \u0123) in string literals. Sometimes, that might
>> still make sense, as for control characters, non-breaking space, etc. But
>>
On Mon, 9 Jun 2025 13:41:10 GMT, Magnus Ihse Bursie wrote:
>> After we converted the source base to be fully UTF-8, we do not need to use
>> unicode sequences (like \u0123) in string literals. Sometimes, that might
>> still make sense, as for control characters, non-breaking space, etc. But
>>
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
> strings that is supposed to be a coherent text in a language
On Mon, 9 Jun 2025 13:41:10 GMT, Magnus Ihse Bursie wrote:
>> After we converted the source base to be fully UTF-8, we do not need to use
>> unicode sequences (like \u0123) in string literals. Sometimes, that might
>> still make sense, as for control characters, non-breaking space, etc. But
>>
On Tue, 27 May 2025 17:01:13 GMT, Naoto Sato wrote:
>> After we converted the source base to be fully UTF-8, we do not need to use
>> unicode sequences (like \u0123) in string literals. Sometimes, that might
>> still make sense, as for control characters, non-breaking space, etc. But
>> for st
On Tue, 27 May 2025 16:31:47 GMT, Justin Lu wrote:
>> @justin-curtis-lu Are these files handled by the translation team?
>
> @magicus The ones under java.xml and jdk.jdi are updated by the translation
> team, I think it'd be best to remove those files from this change.
I have now reverted the c
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
> strings that is supposed to be a coherent text in a language
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
> strings that is supposed to be a coherent text in a language
On Wed, 14 May 2025 14:29:23 GMT, Magnus Ihse Bursie wrote:
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
On Mon, 26 May 2025 08:25:30 GMT, Magnus Ihse Bursie wrote:
>> After we converted the source base to be fully UTF-8, we do not need to use
>> unicode sequences (like \u0123) in string literals. Sometimes, that might
>> still make sense, as for control characters, non-breaking space, etc. But
>
On Wed, 14 May 2025 14:29:23 GMT, Magnus Ihse Bursie wrote:
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
On Wed, 14 May 2025 14:29:23 GMT, Magnus Ihse Bursie wrote:
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
On Wed, 14 May 2025 14:29:23 GMT, Magnus Ihse Bursie wrote:
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
On Wed, 14 May 2025 14:29:23 GMT, Magnus Ihse Bursie wrote:
> After we converted the source base to be fully UTF-8, we do not need to use
> unicode sequences (like \u0123) in string literals. Sometimes, that might
> still make sense, as for control characters, non-breaking space, etc. But for
14 matches
Mail list logo
