On Sun, Mar 4, 2018 at 2:08 PM, Lars Schneider wrote:
>> On 25 Feb 2018, at 20:50, Eric Sunshine wrote:
>> On Sat, Feb 24, 2018 at 11:28 AM, wrote:
>>> + if (!re_src || src_len != re_src_len ||
>>> + memcmp(src, re_src, src_len)) {
>>> + con
> On 25 Feb 2018, at 20:50, Eric Sunshine wrote:
>
> On Sat, Feb 24, 2018 at 11:28 AM, wrote:
>> UTF supports lossless conversion round tripping and conversions between
>> UTF and other encodings are mostly round trip safe as Unicode aims to be
>> a superset of all other character encodings. H
On Sat, Feb 24, 2018 at 11:28 AM, wrote:
> UTF supports lossless conversion round tripping and conversions between
> UTF and other encodings are mostly round trip safe as Unicode aims to be
> a superset of all other character encodings. However, certain encodings
> (e.g. SHIFT-JIS) are known to h
From: Lars Schneider
UTF supports lossless conversion round tripping and conversions between
UTF and other encodings are mostly round trip safe as Unicode aims to be
a superset of all other character encodings. However, certain encodings
(e.g. SHIFT-JIS) are known to have round trip issues [1].
4 matches
Mail list logo