From: Michail Vidiassov <master@iaas.msu.ru>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lpdf.checkedkey has problem with false values
Date: Tue, 16 Sep 2014 07:33:00 +0400 [thread overview]
Message-ID: <CALDha9Pb0aicsGxgDDmH9gLa2UkvrAW8feYAsUEj12KMUg2ZMQ@mail.gmail.com> (raw)
In-Reply-To: <54173B60.4050606@wxs.nl>
Dear Hans,
> more like
>
> function lpdf.checkedkey(t,key,variant)
thank you. That works. Please, commit.
Michail
PS.
lpdf.checkedkey issue was raised while I reviewed 3D PDF support.
But there are greater problems:
It seems that u3d inclusion stopped to work in the current (2014.09.06
20:59) ConTeXt.
Texlive 2014 works.
As far as I can track, the problem is caused by the change in
function register(askedname,specification) from grph-inc.lua:
if "format %a supported by output file format" (and u3d falls under
this category)
specification.found is set to false in the current ConTeXt.
If I set it to true in this case (as in TeXLive 2014 version of
ConTeXt) things start to work again.
May be by doing so I am reversing some unfinished change, but "it works for me".
The relevant patch:
@@ -725,7 +725,7 @@
report_inclusion("format %a natively supported by
backend",format)
end
else
- specification.found = false
+ specification.found = true -- was false
if trace_figures then
report_inclusion("format %a supported by output
file format",format)
end
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-09-16 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 14:14 Michail Vidiassov
2014-09-15 14:59 ` Peter Rolf
2014-09-15 15:34 ` Michail Vidiassov
2014-09-15 15:56 ` Aditya Mahajan
2014-09-15 16:12 ` Michail Vidiassov
2014-09-15 17:12 ` Hans Hagen
2014-09-15 18:25 ` Michail Vidiassov
2014-09-15 19:17 ` Hans Hagen
2014-09-16 3:33 ` Michail Vidiassov [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=CALDha9Pb0aicsGxgDDmH9gLa2UkvrAW8feYAsUEj12KMUg2ZMQ@mail.gmail.com \
--to=master@iaas.msu.ru \
--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).