From: Jano Kula <jano.kula@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: names of cached images
Date: Fri, 2 Jul 2021 19:00:54 +0200 [thread overview]
Message-ID: <CAPefzZ1g_bTUk-ELJjH=sEH4JshXejCeyqHaO5eC+tXH+ZHxBA@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2107021140330.7291@nqv-guvaxcnq>
[-- Attachment #1.1: Type: text/plain, Size: 2110 bytes --]
Hi Aditya!
On Fri, Jul 2, 2021, 17:43 Aditya Mahajan <adityam@umich.edu> wrote:
>
> On Fri, 2 Jul 2021, Jano Kula wrote:
>
> > Hello again,
> >
> > likely a bug and one question. Using this code with lmtx:
> >
> > \starttext
> > \externalfigure[mill][width=40mm,cache=./first,conversion=gray.pdf] %
> > mill...
> > \externalfigure[mill][width=40mm,cache=.,conversion=gray.pdf] %
> > m_k_i_v_mill...
> > \externalfigure[mill][width=40mm,cache=./second] % no
> > visible caching
> > \stoptext
> >
> > *First two figures*
> > Chached image in the ./cache subdirectory has a lmtx name without prefix,
> > the cached image in the current directory has mkiv syntax with m_k_i_v_
> > prefix.
> >
> > *Third figure*
> > The images are cached to a specified directory, only when some conversion
> > is used. I'd like to cache images without any transformation. Is there
> any
> > conversion which doesn't alter the figure, just caches it? Is new
> > conversion type needed? Or is there other way to force caching without
> > conversion?
>
> Conversion is costly and that is why caching makes sense there. What is
> the benefit of caching (i.e., simply copying the file to a different
> directory) when there is no conversion?
>
Images are on the remote sever and I don't want to download them with every
run. Images don't change, changed ones have different ID. Encapsualating
jpgs into pdfs might be the right conversion, because pdf inclusion is
fast, right? So I probably answered myself: write a conversion jpg -> pdf
without any changes to the image.
J.
> Aditya
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3560 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2021-07-02 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 11:16 Jano Kula
2021-06-06 14:56 ` Hans Hagen
2021-06-09 13:23 ` Jano Kula
2021-07-02 15:01 ` Jano Kula
2021-07-02 15:43 ` Aditya Mahajan
2021-07-02 17:00 ` Jano Kula [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='CAPefzZ1g_bTUk-ELJjH=sEH4JshXejCeyqHaO5eC+tXH+ZHxBA@mail.gmail.com' \
--to=jano.kula@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).