ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: zint module on LMTX
Date: Wed, 16 Mar 2022 18:05:13 +0100	[thread overview]
Message-ID: <8a009480-b4e2-2e26-32d8-f5a8d4a868fe@xs4all.nl> (raw)
In-Reply-To: <f16a88c5-e52f-950d-5d5a-71faac6f7820@gmx.es>

On 3/16/2022 5:37 PM, Pablo Rodriguez via ntg-context wrote:
> Dear list,
> 
> using latest LMTX and following the steps from
> https://wiki.contextgarden.net/Barcodes#Zint_module, I’m afraid I don’t
> get any barcode either in Linux or Windows.
> 
> Minimal sample:
> 
>    \starttext
>    \usemodule[zint]
>    \barcode[alternative=isbnx, text=9783865419026, width=4cm]
>    \stoptext
> 
> Error message is rather weird on Linux:
> 
>    optional        > using library '/home/ousia/context/tex/texmf-linux-
>      64/bin/lib/luametatex/zint/libzint.so'
>    zint            > unknown barcode alternative 'isbnx'
>    zint            >
>    zint            > valid barcode alternatives:
>    zint            >
>    [...]
>    zint            >   isbn
>    zint            >   isbnx
>    [...]
> 
> It seems that a valid barcode alternative ends up being unknown to the
> library.
> 
> What am I missing here?
> 
> Many thanks for your help,
Are you sure that you have the latest zint? (from sourceforge)


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2022-03-16 17:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 16:37 Pablo Rodriguez via ntg-context
2022-03-16 17:05 ` Hans Hagen via ntg-context [this message]
2022-03-16 18:11   ` Adam Reviczky via ntg-context
2022-03-16 21:32     ` Pablo Rodriguez via ntg-context
2022-03-16 23:04       ` Adam Reviczky via ntg-context
2022-03-17 15:26       ` Pablo Rodriguez via ntg-context
2022-03-25 10:43         ` Lutz Haseloff via ntg-context
2022-03-16 18:12   ` Pablo Rodriguez via ntg-context
     [not found] <mailman.2658.1647466369.1172.ntg-context@ntg.nl>
2022-09-03 23:36 ` Ivan Pešić via ntg-context
2022-09-04  8:51   ` Hans Hagen via ntg-context
     [not found] <mailman.272.1662280561.1198.ntg-context@ntg.nl>
2022-09-04  9:59 ` Ivan Pešić via ntg-context
2022-09-04 10:59   ` Michal Vlasák via ntg-context
2022-09-04 11:27     ` Hans Hagen via ntg-context
2022-09-04 11:43     ` Hans Hagen via ntg-context
2022-09-04 11:25   ` Hans Hagen via ntg-context
2022-09-04 12:23     ` Michal Vlasák via ntg-context
     [not found] <mailman.0.1662285601.13547.ntg-context@ntg.nl>
2022-09-04 12:53 ` Ivan Pešić via ntg-context

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=8a009480-b4e2-2e26-32d8-f5a8d4a868fe@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).