dankito

I had a similar issue on a Wiko Sunny as it return wrong values for surfaceView.getLeft(). I solved it by adding this one more check for the Status.Close case in...

Then i don't think there will be a workaround as this library is based on the code of Firefox's reader mode. So what in Firefox's reader mode doesn't work, will...

I don't think it's a Readability4J issue but that you have to wrap the output in a structure like this to set encoding to UTF-8 (see https://github.com/dankito/Readability4J/issues/2): ``` ``` This...

You're right, `article.getContentWithUtf8Encoding()` didn't take into account document's charset. Created now the method `article.getContentWithDocumentsCharsetOrUtf8()` which exactly just does that. But i don't think that will resolve @jamal2362's issue as above...

The issue is the whole article is wrapped in a element and in a clean up step all elements get removed from document. It's difficult to solve that for me...

Hi Erdem, really curious as i'd say you did everything right. What error message did you get? Did a Gradle sync help? Did importing other libraries from Maven Central in...

Thanks for reporting that bug to me! Figured out the issue. Version 1.0.5 should fix that (should be visible at Maven Central in maximum two hours).

Hi @ManuelaJL, sorry, i didn't implement this method. Are you interested in implementing it and giving me a pull request?

It now came to my mind why i didn't implement this method: As Readability4J is really fast! So you have the already the result and know if it's actually readable,...

Do you have an example project, anything so that I can reproduce the issue? Sorry for answering that late, but was really a tough week for me.