Results 1 to 9 of 9

Thread: feature request: view/convert .webarchives using 'print' stylesheets

  1. #1

    Default feature request: view/convert .webarchives using 'print' stylesheets

    Many websites are now offering built-in 'print-friendly' versions using specific stylesheets designed for printing. These versions are also nicer for archiving, because they tend to be easier to read thanks to the cutting of most of the website's cruft (superfluous headers, navigation, etc).

    Would it be possible to either add a 'capture print .webarchive when possible' preference, or a "convert to print format" option in the Record menu?

    Thanks

  2. #2

    Default

    I agree that it would be nice for EagleFiler to be able to use the print stylesheets. However, please note that this only applies to how the page is displayed. It’s not necessary to capture the Web page any differently or to convert it, just to display it using the print stylesheet instead of the screen stylesheet. So you can keep on importing Web archives as you have been doing, and when EagleFiler some day lets you choose which format you want to use for display, this will work retroactively.

  3. #3

    Default

    good point Michael, thanks.

    actually, this reminds me, the main reason I'm interested in this sort of functionality is that I'd like to exclude the non-printing material from searches. I'm guessing that kind of functionality is outside your capabilities however.
    Last edited by mattly; 02-21-2007 at 11:30 PM.

  4. #4

    Default

    Quote Originally Posted by mattly View Post
    I'd like to exclude the non-printing material from searches.
    I could do that, although it’s probably not what everyone would want. Maybe it could be a preference, but would be a pretty obscure one, I think.

  5. #5

    Default

    heh.

    well, if you look at your standard blog or web-zine page, there's a ton of cruft there. sidebar links, "related" articles, etc. in my experience that's just enough extra noise to screw searches up.

    I *would* just convert to rtf and remote the extra, unwanted crap, except that:
    1. the original link disappears without manual intervention
    2. rtf formatting cannot easily emulate a lot of what html does
    3. the built-in rtf editor cannot cleanup a lot of said html styling even if it will render it

    anyway, the way things are currently works. perhaps not as smoothly as I might like, but it works nevertheless.

  6. #6

    Default

    Quote Originally Posted by mattly View Post
    1. the original link disappears without manual intervention
    EagleFiler preserves the source URL when converting to RTF. But I agree with your other points.

  7. #7

    Default MyPage

    mattly:

    Why not use MyPage as discussed here? I use it almost daily before importing web pages into EagleFiler. And, thanks to Michael, the pages import perfectly now.

  8. #8

    Default

    Quote Originally Posted by TinyApps.Org View Post
    mattly:

    Why not use MyPage as discussed here?
    Because it takes me out of what I'm doing to focus on something else; Probably the biggest thing I like about EF is the no-brainer capturing.

  9. #9

Similar Threads

  1. Feature Request: Quick Note
    By efjedi in forum EagleFiler
    Replies: 11
    Last Post: 11-23-2010, 07:03 PM
  2. Feature request: 5-star rating
    By kc144 in forum EagleFiler
    Replies: 3
    Last Post: 03-04-2009, 11:11 AM
  3. Feature Request: Import from Preview
    By mtof in forum EagleFiler
    Replies: 8
    Last Post: 10-16-2008, 05:24 PM
  4. Replies: 4
    Last Post: 10-16-2008, 05:07 PM
  5. Feature request - export as plain text
    By afterhours in forum EagleFiler
    Replies: 9
    Last Post: 03-30-2007, 12:54 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •