Why not just allow visitors to download it?

Or use the Print module to dynamically generate a pdf from the node content. If you need help, I've just finished wrestling with that module and know a few tips.

Well, the actual content is a pdf version of a church newsletter which is emailed to anyone that has registered to receive it and then posted to the website. The content of the newsletter is, as you would expect, a collection of articles which would be tough to build into a single node.

But those issues aside, right now I've got my hands full just getting all the function needed in the initial launch in place, so for the sanity of both myself and the church staff, I'm trying to be sensitive to not changing too much. I realize I sound kind of inflexible here but, for the sake of actually getting some traction on this website migration, restructuring the entire church newsletter format and process is a project for after the inital site is launched.

Check out the iPaper Module. I'm going to start using this to directly embed sheet music and chord charts onto my website. Should work great for a newsletter as well. Also, it's still a node, so you future-proof your site and can still have people "Subscribe" to it by setting up an rss feed of the content type.

Blessings,
Tony

You can also use the IMCE module. You can configure IMCE to handle files as well as images. That way, when you are creating your content, you just upload your file via IMCE (same way as you would for an image) and then you get an inline link which will download the pdf when your users click on it.

I've got several places where I need to provide site visitors with a PDF document. It's pretty easy to specify a 'target="_blank"' in your link to the file, but if you use this consistently you may open a lot of windows on your visitor's machine which is considered pretty poor form.

So, I name my targets and only use a couple of names. For example, let's assume that the site is MySite.com. If I'm linking to a PDF document, usually hosted on this site, I specify a target as "ms-pdf". Then I'll open, at maximum, only one additional window to display any PDF from my site. If I'm linking to an external site, then I specify the target as "ms-ext".

Admittedly, this is a compromise between the "never open another window" and "always open another window" crowds, but I think it's reasonable.

IMO forcing a user to "download and open" a PDF file is a bad idea, I agree with Bob here. Unfortunately in the "real world" working with "real people" we may have to realize that we doing as good as we can expect if we get them to post a PDF and we'll never win the battle to get them to actually put content in nodes.

It's not too difficult to create a custom content type to simplify the uploading of a PDF file (attached to a node) and handle the actual display of pertinent files via a view or some custom PHP in another node (oops, I may have started another religious war 8=) ).

Just my 2¢ worth,
Curt

iPaper looks great to me for some of the sites I want to build, but it has had bugs that have sprung up repeatedly in various of the rc versions (same bug). I would keep an eye on it before committing to it. I hope it all gets worked out.