ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Michal Vlasák" <lahcim8@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: QR Code
Date: Mon, 18 Dec 2023 22:06:40 +0100	[thread overview]
Message-ID: <CXRRKW1HYNRH.1SGYJKH47OHWO@gmail.com> (raw)
In-Reply-To: <89516307-3928-15b5-5154-d83720d58529@gmx.es>

On Mon Dec 18, 2023 at 9:35 PM CET, Pablo Rodriguez via ntg-context wrote:
> On 12/18/23 20:34, Henning Hraban Ramm wrote:
> > [...]
> > Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
>
> Many thanks for your reply, Hraban.
>
> I understood my issue with your reply (I known, your answer is intended
> to Uschi).
>
> It is also in the sent file:
>
>  Creator:
>    LuaMetaTeX 2.10.11 20230908 + ConTeXt LMTX 2023.09.26 18:19
>  PDF Producer:
>    LuaMetaTeX-2.10.11
>
> > I guess a missing EPS means you load the MkIV version of the module,
> > probably because "m-zint".
> >
> > I can’t help with Windows; since Hans developed it on Windows, it should
> > work (but don’t ask me how).
>
> I will try to explain what I understand from this (intended for Uschi).
>
> Given that there are two modules (m-zint and zint), there are two options:
>
> 1. Either you use the LMTX module (\usemodule[zint]) and you need the
> Zint library (as explained in
> https://wiki.contextgarden.net/Barcodes#Zint_module).
>
> 2. Or you use the MkIV module (\usemodule[m-zint]) and you need the Zint
> binary installed and CMD should be able to invoke it (already knowing
> its past).
>
> You may have the Zint binary installed, ConTeXt may be generating the
> required EPS files, but either Inkscape is not installed (or its path is
> unknown to the system), or ConTeXt cannot simply find where the
> converted PDF versions of the zint images are.
>
> If I have the following source in testing-barcodes.tex:
>
>   \usemodule[m-zint]
>   \starttext
>   \startTEXpage[offset=1dk]
>   \barcode[alternative=isbnx, text=9783865419026, width=4cm]
>   \stopTEXpage
>   \stoptext
>
> ConTeXt compiles it generating to extra files (when compared to the pure
> zint module for LMTX only):
>
>   zint-isbnx-fe90eda0e93cf020312eps
>   m_k_i_v_zint-isbnx-fe90eda0e93cf020312_eps_c60ccda70ef.pdf
>
> (Removed some characters in strings so file names fit in a single line.)
>
> The first file is generated by the Zint binary itself. The second one is
> the automatic conversion (through Inkscape) that ConTeXt needs to embed
> EPS (and SVG) files in the final PDF document.
>
> If m_k_i_v_zint-*.pdf files are missing, the problem might be that
> Inkscape isn’t installed (or its path is unknown to the system).
>
> If also zint-*.eps files are missing, you should find where Zint is
> generating them.

I will just add to the excellent answers above, that I very much
recommend LMTX and the LMTX way of using the zint _library_. I published
compiled versions of zint and couple of other libraries to the optional
libraries repository:

    https://github.com/contextgarden/luametatex-optional-libraries
    https://github.com/contextgarden/luametatex-optional-libraries/releases/tag/v20230902

I tested the steps on the wiki and libzint.dll works without problems:
i.e. install ConTeXt, create a few folders, move the dll and
mtxrun --generate.

My goto document for testing zint, that went without problems (even the
hexagons!):

    \starttext
    \usemodule[zint]
    \barcode[alternative=isbnx, text=9783865419026, width=4cm]
    \barcode[alternative=qrcode, text={https://wiki.contextgarden.net}, width=3cm]
    \barcode[alternative=maxicode, text={test}, width=3cm]
    \stoptext

Michal

PS: Coincidentally zint 2.13 has been released just today. Usually every
new zint release requires an update on the ConTeXt side, but older
releases still work well with ConTeXt (e.g. currently ConTeXt supports
2.10, 2.11 and 2.12). The version linked above works.
___________________________________________________________________________________
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:[~2023-12-18 21:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 12:00 [NTG-context] " Ursula Hermann
2023-12-18 12:26 ` [NTG-context] " Henning Hraban Ramm
2023-12-18 14:13   ` Ursula Hermann
2023-12-18 15:14     ` vm via ntg-context
2023-12-18 16:05       ` Ursula Hermann
2023-12-18 16:44         ` vm via ntg-context
2023-12-18 19:17         ` Pablo Rodriguez via ntg-context
2023-12-18 19:34         ` Henning Hraban Ramm
2023-12-18 20:35           ` Pablo Rodriguez via ntg-context
2023-12-18 21:06             ` Michal Vlasák [this message]
2023-12-19 11:37           ` Ursula Hermann
2023-12-21 13:29           ` Ursula Hermann
2023-12-18 14:19   ` Ursula Hermann
2024-04-29  3:03 Benjamin Buchmuller
2024-04-29  7:12 ` Henning Hraban Ramm

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=CXRRKW1HYNRH.1SGYJKH47OHWO@gmail.com \
    --to=lahcim8@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).