Detected encoding as iso-8859-16 but null Encoding

CharsetDetector / UTF-unknown

Character set detector build in C# - .NET 5+, .NET Core 2+, .NET standard 1+ & .NET 4+

303 stars 46 forks source link

Detected encoding as iso-8859-16 but null Encoding #114

Closed AdamJurga closed 3 years ago

AdamJurga commented 3 years ago

Please see screenshot below.

From my tests I see that it works fine for many other types of encodings. Only this one is problematic.

rstm-sf commented 3 years ago

Hello!

This is ok: there is no object in the dotnet that is iso-8859-16 encoding. The remarks that this library can detect, but not represent in dotnet format, are specified in the Docs

AdamJurga commented 3 years ago

Sorry, my bad, I ended reading after "Usage" section 🤦‍♂️.

Is this full list of not available aliases?

cp949,
iso-2022-cn,
euc-tw,
iso-8859-10,
iso-8859-16,
viscii,
X-ISO-10646-UCS-4-34121/X-ISO-10646-UCS-4-21431

Thanks.

rstm-sf commented 3 years ago

Is this full list of not available aliases?

Yes, these are the encodings that this library can define, but for which there are no implementations. Also, two were replaced with similar ones, at least no one has yet reported that this is incorrect

AdamJurga commented 3 years ago

Thank you very much for help!