pdf readers from browser

[notbob]

I'm still on 13.37, but gonna update as soon as a legal crisis is
past. Ain't got no time fer install/config nonsense, right now.
Until then, I'll ask this question for future ref: Why, when I access
a pdf doc from SM, does acroread only work once, but not twice? I'm
using adopey's acroread, so that's part of it. I don't think I'll do
that again. Regardless, the 2nd time I try to open a pdf, I get a blk
screen. I gotta close all iterations of SM and reboot it fresh, then
acroread will work ...again, only once! Anyone know why?

When I install 14 in a couple weeks, I'll not install acroread again.
Okular is good enough for me. Will if fire from SM? IOW, work for
viewing pdf's from inside SM w/o having to detach/save pdf file and
open separately?

nb

[Aragorn]

On Friday 03 May 2013 22:38, notbob conveyed the following to
alt.os.linux.slackware...

> I'm still on 13.37, but gonna update as soon as a legal crisis is
> past. Ain't got no time fer install/config nonsense, right now.
> Until then, I'll ask this question for future ref: Why, when I access
> a pdf doc from SM, does acroread only work once, but not twice? I'm
> using adopey's acroread, so that's part of it. I don't think I'll do
> that again. Regardless, the 2nd time I try to open a pdf, I get a blk
> screen. I gotta close all iterations of SM and reboot it fresh, then
> acroread will work ...again, only once! Anyone know why?

Can't say I know _why_ but I've never liked Acroread. It's crap.

> When I install 14 in a couple weeks, I'll not install acroread again.
> Okular is good enough for me. Will if fire from SM? IOW, work for
> viewing pdf's from inside SM w/o having to detach/save pdf file and
> open separately?

For what it's worth, I don't use Adobe's Acroread here. I use Firefox
as my browser and Okular for viewing PDFs, and that works just fine.

--
= Aragorn =
GNU/Linux user #223157 - http://www.linuxcounter.net

[Tralfaz]

What is "SM"?

Whatever browser you use, you can have it use whatever app you want for
any particular need. Since you don't like acroread (I haven't used it for
years myself now), I'd stick with Okular, like you said...it just works.
Simply go to the preferences and set it in the 'helper applications'
section to use Okular and that's it.

[Michael Black]

On Sun, 5 May 2013, Tralfaz wrote:

> On Fri, 03 May 2013 20:38:45 +0000, notbob wrote:
>
>> I'm still on 13.37, but gonna update as soon as a legal crisis is past.
>> Ain't got no time fer install/config nonsense, right now. Until then,
>> I'll ask this question for future ref: Why, when I access a pdf doc from
>> SM, does acroread only work once, but not twice? I'm using adopey's
>> acroread, so that's part of it. I don't think I'll do that again.
>> Regardless, the 2nd time I try to open a pdf, I get a blk screen. I
>> gotta close all iterations of SM and reboot it fresh, then acroread will
>> work ...again, only once! Anyone know why?
>>
>> When I install 14 in a couple weeks, I'll not install acroread again.
>> Okular is good enough for me. Will if fire from SM? IOW, work for
>> viewing pdf's from inside SM w/o having to detach/save pdf file and open
>> separately?
>>
>> nb
>
> What is "SM"?
>

Seamonkey.

> Whatever browser you use, you can have it use whatever app you want for
> any particular need. Since you don't like acroread (I haven't used it for
> years myself now), I'd stick with Okular, like you said...it just works.
> Simply go to the preferences and set it in the 'helper applications'
> section to use Okular and that's it.
>

But isn't the issue really configuration?

I remember at some point using a browser and it would invoke a PDF reader
to display the file. Yet today (with a pretty much still standard SLack
14) I noticed a box opened up to ask where to save it. Actually, I think
that box offered the ability to save the file, or to open a PDF reader.

I can't remember what happend with Slack 12, but I know at times I've
sometimes invoked a reader, sometimes just had to save the file and then
read it separately. Not too helpful, but I wasn't paying attention.

Michael

[notbob]

On 2013-05-05, Michael Black <et...@ncf.ca> wrote:

> I remember at some point using a browser and it would invoke a PDF reader
> to display the file. Yet today (with a pretty much still standard SLack
> 14) I noticed a box opened up to ask where to save it. Actually, I think
> that box offered the ability to save the file, or to open a PDF reader.

That's a different situation, like when there's a pdf dwnld file
linked within the website. I'm talking about when the website url IS
a pdf file, like.....

http://illustration ... yada.pdf

You see them in google as [PDF]-yada-yada in the listings. I don't
know if okular will opens the file automatically, but acroread does.
Unfortunately, only once, until I close all iterations of seamonkey
(SM) and restart it.


nb

[Chick Tower]

On 2013-05-03, notbob <not...@nothome.com> wrote:
> When I install 14 in a couple weeks, I'll not install acroread again.
> Okular is good enough for me. Will if fire from SM? IOW, work for
> viewing pdf's from inside SM w/o having to detach/save pdf file and
> open separately?

Your remark about detaching and saving files makes me wonder if you're
talking about viewing pdf files that are e-mail attachments rather than
ones that are linked to on a web page. However, if the latter, then
Firefox 20.0 (if not earlier versions) appears to have a built-in pdf
viewer, so maybe Seamonkey will inherit that in the near future. Before
that, it used to ask if you want to save the pdf or view it with an
external program. If you chose the latter, you could specify whatever
program you wanted to use. For that reason, I created a link to xpdf in
my home directory so that it would be easy to find in the file selector
window, and I didn't want to make using xpdf the default in Firefox.
--
Chick Tower

For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net

[Martin]

On 05/05/2013 03:15 AM, Michael Black wrote:

> I remember at some point using a browser and it would invoke a PDF
> reader to display the file. Yet today (with a pretty much still
> standard SLack 14) I noticed a box opened up to ask where to save it.
> Actually, I think that box offered the ability to save the file, or to
> open a PDF reader.

The reason for that is probably a misconfigured web server. Part of the
HTTP reply is the so-called MIME type which defines the nature of the
file. A standards compliant browser uses this mime type (not the file
extension, and not the output of /usr/bin/file) to decide what to do
with the file.

A PDF file should be sent as application/pdf. If it is sent as
application/octet-stream (the fallback for a generic binary file), the
browser will bring up the save dialog.

The reason why this type of misconfiguration is not noticed by the
content provider is perhaps that it doesn't show up in internet exploder.