From: Jano Kula <jano.kula@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: names of cached images
Date: Fri, 2 Jul 2021 17:01:57 +0200 [thread overview]
Message-ID: <CAPefzZ1daitjhAr-aguY6tzX+0Z7XRWk6Rz02LK9XyfzbdwQ2A@mail.gmail.com> (raw)
In-Reply-To: <CAPefzZ3Cf9v5AbG2i9Ds=OAxr9WGCpm6ADMbrpq5pqL26QtO7w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1938 bytes --]
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?
Thank you,
Jano
On Wed, Jun 9, 2021 at 3:23 PM Jano Kula <jano.kula@gmail.com> wrote:
> Hello Hans,
>
> On Sun, Jun 6, 2021 at 4:56 PM Hans Hagen <j.hagen@xs4all.nl> wrote:
>
>> On 6/6/2021 1:16 PM, Jano Kula wrote:
>> > Hello list,
>> >
>> > usingconversion=gray.pdf in lmtx the cached images' names have some
>> > string in their name. I thought it's a name of random sequence of
>> luatex
>> > cache, but the string is the same on other machines and I don't know,
>> > where it comes from. mkiv used to have m_k_i_v_ string there.
>> >
>> > hacker.pdf = source image
>> > hacker_jpg_c60ccda70ef92e32d7a6334f31c23259.gray.pdf = cached linux
>> > hacker_jpg_c60ccda70ef92e32d7a6334f31c23259.gray.pdf = cached win
>> >
>> > MWE
>> > \starttext
>> > \externalfigure[hacker]
>> > [cache=./,
>> > conversion=gray.pdf]
>> > \stoptext
>> >
>> > Is it intended behavior?
>> sure, something like that is always intended; it's an md5 of a hash of
>> all relevant parameters so that when you change one (say the resolution)
>> we now that we need to update
>>
>
> Thank you, wiki updated.
> J.
>
[-- Attachment #1.2: Type: text/html, Size: 3016 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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-07-02 15:01 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 [this message]
2021-07-02 15:43 ` Aditya Mahajan
2021-07-02 17:00 ` Jano Kula
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=CAPefzZ1daitjhAr-aguY6tzX+0Z7XRWk6Rz02LK9XyfzbdwQ2A@mail.gmail.com \
--to=jano.kula@gmail.com \
--cc=j.hagen@xs4all.nl \
--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).