lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] non-html start URL


From: Thomas Dickey
Subject: Re: [Lynx-dev] non-html start URL
Date: Sun, 11 Mar 2012 16:30:33 -0400
User-agent: Mutt/1.5.18 (2008-05-17)

On Sun, Mar 11, 2012 at 08:38:08PM +0100, Klaus-Peter Wegge wrote:
> But why is the behaviour of lynx different
> 1- when the url to the pdf is given on command line
> 2- when the url to the pdf is given in a html-file?
>
> In the first case it tries to use xpdf
> in the second case it shows the download menu.
> If the problem is with the mailcap file, lynx should at least behave
> in the same manner.

When it reads the data via an html file, it's getting some input from
the server to tell what type of data the pdf file is.  That feeds into
lynx's morass of presentation-logic, which isn't necessarily identical
to what you'd get with just the url of the file.

I'd use the -trace option to see what's different between the two cases...

>
> Thanks
>
> Klaus
>
> On Sun, 11 Mar 2012, Thomas Dickey wrote:
>
>> On Sun, Mar 11, 2012 at 06:51:12PM +0000, Thorsten Glaser wrote:
>>> Klaus-Peter Wegge dixit:
>>>
>>>> I'm using lynx as URL viewer in the alpine mailer on debian linux
>>>                                                     ^^^^^^^^^^^
>>>
>>>> xpdf and how to come over it. I'd prefer that lynx simply comes up with
>>>> the download menu for the pdf file.
>>>> This effect is not specific to a certain lynx version.
>>>
>>> MIME types. They are broken in all GNU/Linux distributions I
>>> encountered to date ? in MirBSD, lynx behaves the way you want.
>>>
>>> What you can try to do is:
>>>
>>>   Preferred media type             : [33][(1)__Accept lynx' internal types_]
>>>
>>> in (O)ptions. Maybe that helps, or I?m misreading what this
>>> option should do.
>>
>> This option was used to solve a couple of problems - one is that if lynx
>> tells the server about all of the mime types that its system can deal with,
>> then the server chokes on the list.
>>
>> Actually it's the mailcap file which tells lynx what to do with a file.
>>
>>> At work, I couldn?t manage to get lynx to use xloadimage
>>> (which I?ve specified as XLOADIMAGE_COMMAND) for images,
>>> it always uses the system?s apparently-default imagemagick
>>> which is a PITA. So, ideas welcome too ;)
>>
>> perhaps this as well
>>
>> --
>> Thomas E. Dickey <address@hidden>
>> http://invisible-island.net
>> ftp://invisible-island.net
>>
>
> ---
> Dipl.-Inform. Klaus-Peter Wegge
> Siemens AG
> Corporate Technology, CT T DE ACC
> Accessibility Competence Center
> Fürstenallee 11
> 33102 Paderborn, Germany
> Tel:  +49 5251 60-6144
> Fax:  +49 5251 60-6139
> Mob:  +49 173 7019577
> Mail: address@hidden, address@hidden
>
> Siemens Aktiengesellschaft:
> Vorsitzender des Aufsichtsrats: Gerhard Cromme;
> Vorstand: Peter Löscher, Vorsitzender; Roland Busch, Brigitte Ederer,
>   Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt,
>   Siegfried Russwurm, Peter Y. Solmssen, Michael Süß;
> Sitz der Gesellschaft: Berlin und München, Deutschland;
> Registergericht: Berlin Charlottenburg, HRB 12300,
>   München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
> ---


-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]