ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Procházka Lukáš Ing." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Pdf info with Lua/Ctx API
Date: Tue, 15 Aug 2017 14:08:58 +0200	[thread overview]
Message-ID: <op.y40hc8zr62epfj@lprx> (raw)
In-Reply-To: <2b0ca8a5-f92a-234f-387a-8b99d7a2d5e8@wxs.nl>

Hello Hans,

that's exactly what I've been looking for!

(And yes, I've asked one or more times, with a solution that seemed to me a bit "forced" or "non-clear", so the latest solution looks perfectly!)

Best regards,

Lukas


On Mon, 14 Aug 2017 16:55:09 +0200, Hans Hagen <pragma@wxs.nl> wrote:

> On 8/14/2017 1:08 PM, Procházka Lukáš Ing. wrote:
>> Hello,
>>
>> is there a way how to get the following info from a PDF file via Lua/Ctx
>> API?:
>>
>> - first: number of pages of the PDF,
>>
>> - next: for each page: get width, height and orientation
>> (portrait/landscape) or rotation (+90,+ 180, +270 or so) of i-th page.
>
> this probably has come up several times now, anyway
>
>
> \getfiguredimensions[test.pdf]
> \dorecurse {\noffigurepages} {
>      \getfiguredimensions[test.pdf][page=#1]
>      \figurenaturalwidth
> ,\figurenaturalheight,\figureorientation,\figurerotation\par
> }
>
> in lua you can either use the img library (see luatex manual) or context
> helpers
>
>          local data = figures.push("foo.pdf")
>          figures.identify()
>          figures.check()
>          figures.pop()
> 	inspect(data)
>
> i'll add:
>
> function figures.getinfo(name,page)
>      if type(name) == "string" then
>          name = { name = name, page = page }
>      end
>      if name.name then
>          local data = figures.push(name)
>          figures.identify()
>          figures.check()
>          figures.pop()
>          return data
>      end
> end
>
> so that one can do
>
> local n = "ms.pdf"
> local d = figures.getinfo(n)
>
> if d then
>      for i=1,d.used.pages do
>          local p = figures.getinfo(n,i)
>          if p then
>              local u = p.used
>              print(u.width,u.height,u.orientation)
>          end
>      end
> end
>
> etc etc
>
>


-- 
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o.      | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn
Bezová 1658
147 14 Praha 4

Mob.: +420 702 033 396

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-08-15 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 11:08 Procházka Lukáš Ing.
2017-08-14 14:55 ` Hans Hagen
2017-08-15 12:08   ` Procházka Lukáš Ing. [this message]
2017-08-16 10:11   ` Procházka Lukáš Ing.
2017-08-16 11:57     ` Wolfgang Schuster

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=op.y40hc8zr62epfj@lprx \
    --to=lpr@pontex.cz \
    --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).