ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lutz Haseloff <lutz.haseloff@toppkieker.info>
To: Context Mailing List <ntg-context@ntg.nl>
Subject: Re: degrade module
Date: Fri, 15 Feb 2019 11:48:51 +0100	[thread overview]
Message-ID: <5A20CD44-27E6-408A-8D89-DD4019F79B05@toppkieker.info> (raw)
In-Reply-To: <20190215110845.3a741c38@homerow>


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

Thanks Marco,
Your Module with wrapper finally works for me as expected.
Thank you very much.
Will it find its way into the distribution as an  enhanced degrade module?

Greetings ant thanks again

Lutz

Am 15. Februar 2019 11:08:45 MEZ schrieb Marco Patzer <lists@homerow.info>:
>On Fri, 15 Feb 2019 10:22:48 +0100
>Lutz Haseloff <lutz.haseloff@toppkieker.info> wrote:
>
>> but both scripts trow the same error on windows and linux-armhf:
>> 
>> grph-downsample.lua:32: bad argument #2 to 'format' (number has no
>> integer representation)
>
>It works here on linux-armhf. No Lua error. Maybe the file got
>mangled during transmission.
>
>I've uploaded a modified version to github, maybe try that one:
>
>  https://github.com/mpfusion/context-downsample
>
>It includes a wrapper so you can call it like any other module
>(\usemodule[downsample]). It's still Peter's code, but with small
>modifications, so it degrades jpg as well as png images at the same
>time. It's a quick hack, but works here, also on armhf.
>
>Marco

[-- Attachment #1.2: Type: text/html, Size: 1528 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
___________________________________________________________________________________

  reply	other threads:[~2019-02-15 10:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 19:49 Lutz Haseloff
2019-02-14 20:22 ` Marco Patzer
2019-02-14 20:37   ` Peter Münster
2019-02-14 20:32 ` Peter Münster
2019-02-14 20:41   ` Wolfgang Schuster
2019-02-14 21:00     ` Peter Münster
2019-02-14 20:44   ` Hans Hagen
2019-02-15  6:56     ` Lutz Haseloff
2019-02-15  7:24       ` Henning Hraban Ramm
2019-02-15  7:25       ` Marco Patzer
2019-02-15  9:22         ` Lutz Haseloff
2019-02-15 10:08           ` Marco Patzer
2019-02-15 10:48             ` Lutz Haseloff [this message]
2019-02-15 11:23               ` Marco Patzer
2019-02-17 11:14                 ` Peter Münster
2019-02-18  9:13                   ` Marco Patzer
2019-02-18 10:03                     ` Peter Münster
2019-02-18 15:25                     ` Alan Braslau
2019-02-18 21:09                       ` Peter Münster
2019-02-18 21:23                         ` Alan Braslau
2019-02-18 22:50                           ` Peter Münster
2019-02-18 23:21                             ` Alan Braslau
2019-02-19  9:42                               ` Peter Münster

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=5A20CD44-27E6-408A-8D89-DD4019F79B05@toppkieker.info \
    --to=lutz.haseloff@toppkieker.info \
    --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).