Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider removing using non-unicode Encoding in the library, leaving the use of FallbackEncoding

See original GitHub issue

Hello!

Consider removing using non-unicode Encoding in the library, leaving the use of FallbackEncoding.

Or add use CodePagesEncodingProvider.Instance.GetEncoding(...)~~, or register CodePagesEncodingProvider.Instance~~ (adding target netcoreapp3_0?)

The background can be read here #445

Issue Analytics

State:
Created 4 years ago
Comments:14

Top GitHub Comments

1reaction

andersnmcommented, Jan 8, 2020

@rstm-sf Thanks, but alas the tests depend on run order. The tests run alphabetically and fail if you rename them to f.ex TestA and TestB

1reaction

rstm-sfcommented, Jan 6, 2020

I only suggest simplifying the use of the library to users of the .NET Core platform (in fact, this is the main central audience)

Top Results From Across the Web

Add target .NET Core 3.0 · Issue #445 · ExcelDataReader ...

Gets or sets the encoding to use when the input XLS lacks a CodePage ... Consider removing using non-unicode Encoding in the library, ......

How can I remove non-ASCII characters but leave periods ...

An easy way to change to a different codec, is by using encode() or ... You may use the following code to remove...

Powershell base64 encode utf8. UTF8Encoding encoding ...

Base64_Encoding (CLIENT_ID:CLIENT_SECRET) Most of the usage perform this Base64 encoding with encoding type as "UTF-8". GitHub Gist: instantly share code, ...

Support non-Unicode character encoding in Azure Logic ...

Handle non-Unicode characters in Azure Logic Apps by converting text payloads to UTF-8 with base64 encoding and Azure Functions.

Localizations and character encodings - Developer guides

Firefox needs a fallback encoding that it uses for non-conforming legacy content that doesn't declare its encoding. For most locales, the fallback encoding...