If it is so, and I am pretty sure it is, than I must say it’s totally wrong solution. Even launching Clip to DT in the internal DT browser does not work! Your HTML to Markdown converter starts from scratch ignoring the existing session. And the app must go through the login process again because from the server point of view it is a new session.
IMO the DT clipper just sends the page URL to the DevonThink application and the real parsing/capturing of the page occurs later in the app. When I launched the Clip to DT action, instead of the page content (as I would expect) the login screen was captured! I think I understand, what’s the DT problem. I played a bit with the DT web clipper trying to capture content from sites that require login. That’s how the competitors work.Īn extension to my previous post. For example, Mercury parser extracts only essential HTML code from the page, and Turndown then converts it to markdown. You don’t need to think up the wheel again. Evernote can do it, and Quiver can do it, One Note can do it, many other programs can do it. the DOM existing in my browser) into the markdown code and to save the result in DT. All I need is to convert the content between the and tags (e.g. What does the browser content conversion have in common with the implementation of the login or paywall mechanism? When I am going to capture a page content, I am already logged in, and the login mechanism is therefore not relevant. and also note sites with logins or paywalls can be implemented in a way that makes them difficult to clip from. I do not understand the arguments of the DT team as. Leaving aside the quality of the clipped content, the DT users cannot clip pages behind the paywall/login. The fact that it is still active means that the topic is still current and the problem is not solved.
0 kommentar(er)
