Gabriele Tomassetti

It is a good idea, the problem is how to implement it. We do have some language-base statistics [to calculate time to read](https://github.com/Strumenta/SmartReader/blob/master/src/SmartReader/TimeToReadCalculator.cs) that we could use as a starting...

Thanks for your offer to help on this issue, too. Honestly, I was mostly looking at this issue as an excuse to work on a NLP library, but if your...

That's a really smart idea. I will work on it.

It already exists an alternative approach that could work for your problem. There is a feature in SmartReader [to perform custom operations either at the beginning or the end of...

Well, we are already creating an explicit dependency on AngleSharp, since we allow users of the library to define custom operations that depends on AngleSharp code. So it would not...

Hello, thanks for your feedback. The library does not manage encoding of the source directly, it delegates it to the AngleSharp library. This is widely used, so I do not...

I have taken a look at the source you provided. It is true that the source is not displayed correctly. However, the encoding/charset is correct, the issue seems to be...

The latest commit should fix the issue. The problem was not the unusual character references, but because for some reason AngleSharp ignored the encoding setting provided in the header. I...

@marhyno I published [version 0.9.0](https://www.nuget.org/packages/SmartReader) that should fix your issue. It took a while because we found other issues to fix.

Thanks for your feedback. It is a direct port of the main algorithm, but I can see some potential explanations: - it is possible that we make a mistake -...