ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: <josephcanedo@gmail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Detecting content out of print/page area ?
Date: Thu, 18 Aug 2016 23:46:00 +0200	[thread overview]
Message-ID: <57b62c98.81a2c20a.9de76.6734@mx.google.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 944 bytes --]

Dear all,

I was wondering if there were any sort of tool (beyond manual eye inspection) in general sense, either printing some warning in log file, or visually in output document, or even reading pdf file, that would help determining if for a some page there is content that is typeset outside (partially or even worse totally) the print/page area. 

If not, could the approach of using a lua function to inspect nodes after shipouts task could possibly work (although not very easy to implement maybe) :

local report_check = logs.reporter("user", "check")

function userdata.page_check(head)
   local realpage = tex.getcount('realpageno')
   report_check('Page ' .. realpage)
   -- TODO: code to check stuff is inside print area
   return head, false
end

tasks.appendaction("shipouts", "after", "userdata.page_check")
tasks.enableaction("shipouts", "userdata.page_check")

Many thanks

Best regards

Joseph Canedo


[-- Attachment #1.2: Type: text/html, Size: 3023 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

                 reply	other threads:[~2016-08-18 21:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=57b62c98.81a2c20a.9de76.6734@mx.google.com \
    --to=josephcanedo@gmail.com \
    --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).