From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: hard clipping in ConTeXt?
Date: Sat, 11 Nov 2023 11:02:15 +0100 [thread overview]
Message-ID: <b8197501-f6f5-46c4-bcc9-cc649fa84072@freedom.nl> (raw)
In-Reply-To: <460e8894-2796-2abe-20ea-fc3afef2069a@gmx.es>
On 11/10/2023 6:17 PM, Pablo Rodriguez via ntg-context wrote:
> Dear list,
>
> I have the following sample:
>
> \setuplayout[page]
> \starttext
> \clip[hoffset=5mm, voffset=5mm, width=15mm, height=15mm]
> {\externalfigure[xml-mkiv.pdf]}
> \stopnotmode
> \stoptext
>
> Using PDF.js (from current Firefox), xpdf, Evince, mupdf-gl, the viewer
> is able to find "dealing", altough it cannot be displayed.
>
> Okular and Sumatra (with Wine in Linux) are not able to find "dealing".
>
> Is there any way to have a hard clipping in ConTeXt?
>
> I mean, that only the contents of the clipped section is added to the
> resulting PDF document?
one has to render a document (page stream) in order to wee what end up
where .. a viewer has that info so it can decide to act upon it (apart
from some gambling with words clipped in the middle of a character)
this is not something for context to provide (it would mean keeping
track of what gets clipped, and then compensating for it because it can
still contribute to placement of following stuff, and then how about
half clipped stuff)
if i had a lifespan of 1000 years or were on a boring trip to another
planet it might make a nice (although pointless) challenge to keep me
occupied
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-11-11 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 17:17 [NTG-context] " Pablo Rodriguez via ntg-context
2023-11-11 10:02 ` Hans Hagen via ntg-context [this message]
2023-11-13 16:20 ` [NTG-context] " Pablo Rodriguez via ntg-context
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=b8197501-f6f5-46c4-bcc9-cc649fa84072@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).