ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jim <zlists+context@jdvb.ca>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: \framed{\externalfigure} vs \externalfigure[frame=on]
Date: Sat, 27 Jan 2024 15:01:20 -0400	[thread overview]
Message-ID: <ZbVTAHKmvVUDWkQT@x360.localdomain> (raw)
In-Reply-To: <632c8f9f-8983-ca0c-241e-6ff0d96679e9@gmx.es>

On Sat, Jan 27, 2024 at 19:12 (+0100), Pablo Rodriguez via ntg-context wrote:

> On 1/27/24 17:44, Jim wrote:
>> The wiki page for \setupexternalfigure says
>>      "Show frame around image. Most(?) options of \setupframed are usable!"

Hi Pablo,

> I’m afraid that this is a too generous statement.

I can't disagree with you!  ;-)

> https://www.pragma-ade.com/general/qrcs/setup-en.pdf#page=218 shows
> which keys and values \setupexternalfigure allows.

Thanks for that pointer.

>> I tried to put a frame around a picture (using \externalfigure with
>> frame=on) but I didn't get the frame to play nicely (see example below).  I
>> can get the frame where I want it if instead I do
>>      \framed[frame=on,...]{\externalfigure...}
>> but this leaves me wondering whether
>> (1) I am misinterpreting the wiki pages,
>> (2) The wiki pages are misleading/wrong, or

> I would say, that the offset and frameoffset don’t seem to be available
> in \setupexternalfigure.

And yet, experiments suggest that frameoffset does indeed do something (in,
specifically, \externalfigure, I didn't yet try \setupexternalfigure).

Given that frameoffset does something and is not mentioned in setup-en.pdf,
I will add to my wonderment

(2') the summary in setup-en.pdf is incomplete.

>> (3) There is a bug in some code.


>> If anyone would care to enlighten me, I would appreciate it.

>> In particular, the offset=... option of \externalfigure does not seem to be
>> consistent with the offset=... option of \framed.

> I hope it is clear now.

Well, given that (at least on my computer, with context updated a couple of
days ago) frameoffset does do something.  So I still see an inconsistency.

I would be happy to help out by editing the wiki to accurately describe
reality.  The problem is, I'm not sure what reality is supposed to be on
this point.  For example, if I edited the wiki to say that offset has no
effect in \setupexternalfigure, and it turns out that some (recent?) change
to something else broke 'offset=', then I wouldn't want to add
misinformation.

>> Here is the example... one and all should be able to directly run it, but
>> the text above and below each picture may make the issues clear without
>> having to run the code.  (The result I was looking for is the second figure
>> in this example.)

> To get offset in the frame of the image, you need a different frame from
> the external figure itself (or so it seems).

As I mentioned, on my system I can get a frame offset from the image
without using \frame, but unfortunately it is the type of frame which is
"invisible" to the layout of the page.

> I hope it helps,

It does (a bit), thanks again for your time.

                                Jim
___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2024-01-27 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27 16:44 [NTG-context] " Jim
2024-01-27 18:12 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-01-27 19:01   ` Jim [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=ZbVTAHKmvVUDWkQT@x360.localdomain \
    --to=zlists+context@jdvb.ca \
    --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).