ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: pdfstartview
Date: Thu, 02 Feb 2006 10:16:21 +0100	[thread overview]
Message-ID: <43E1CDE5.5030304@wxs.nl> (raw)
In-Reply-To: <6faad9f00602011716j724d709dv49796d3c1fe32b7b@mail.gmail.com>

Mojca Miklavec wrote:
> On 2/1/06, Hans Hagen wrote:
>   
>> Mojca Miklavec wrote:
>>     
>>> I vote for this as well (for enchanced possibilities of opening PDF
>>> documents: FitWidth, FitHeight, whole page, XX % of actual size). This
>>> might not be the same as request above, but a very similar one.
>>>
>>>       
>> hey, since when don't you read the source any more ...
>>
>> \setupinteraction[focus=fit|width|height|minwidth|minheight|standard|<empty>
>>     
>
> Till yesterday my acrobat was broken for quite some months and I
> couldn't experiment much (I hated to reinstall windows).
>
> I looked into ConTeXt source for PDF and into PDF Reference manual a
> while ago I don't remember any changes mentioned since that time.
>
> I realized that opening a document on 100% (75%) for example needs
> some special handling like /GoTo /D [page /XYZ left top zoom] (I'm
> guessing now, I don't have to proper resources available to check it)
> which has to be triggered right after the document opens. A bit dirty
> in comparison to "fit width", I agree.
>
> I would guess that 99% of the code needed to do that already exists,
> it's just that the "zoom to XX %" needs to be triggered at document
> opening time. This might have to do something with Taco's remarks. I
> might be wrong, so please excuse me in that case.
>   
the number of actions that can be done at doc open time using /Key 
/Values is limited (and sometimes contradictionary); that leave the 
openaction, which then may conflict with other open actions (just grep 
for openaction in the base path)
> (I find PDF way too complicated for experimenting in comparison to PS.)
>   
hm, it depends, the more complex pdf features are just taken from 
postscript -)

Hans

      parent reply	other threads:[~2006-02-02  9:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 15:33 pdfstartview Peter Münster
2006-02-01 16:17 ` pdfstartview Mojca Miklavec
2006-02-01 20:45   ` pdfstartview Hans Hagen
2006-02-01 21:10     ` pdfstartview Peter Münster
2006-02-01 22:28       ` pdfstartview Hans Hagen
2006-02-03 18:02         ` pdfstartview Peter Münster
2006-02-03 20:20           ` pdfstartview Hans Hagen
2006-02-16 17:55             ` pdfstartview Peter Münster
2006-02-16 21:24               ` pdfstartview Hans Hagen
2006-02-17  6:10                 ` pdfstartview Peter Münster
2006-02-01 22:32       ` pdfstartview Taco Hoekwater
2006-02-02  9:13         ` pdfstartview Hans Hagen
2006-02-02  1:16     ` pdfstartview Mojca Miklavec
2006-02-02  9:01       ` pdfstartview Taco Hoekwater
2006-02-03 17:56         ` pdfstartview Peter Münster
2006-02-03 18:29           ` pdfstartview Taco Hoekwater
2006-02-03 19:43             ` pdfstartview Hans Hagen
2006-02-03 19:58             ` pdfstartview Peter Münster
2006-02-03 20:07             ` pdfstartview Hans Hagen
2006-02-02  9:16       ` Hans Hagen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E1CDE5.5030304@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).