ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: inclusion from image database broken (mkii+mkiv)
Date: Tue, 20 May 2008 20:20:58 +0200	[thread overview]
Message-ID: <4833168A.2000204@gmx.net> (raw)
In-Reply-To: <4832E22E.8040805@gmx.net>

Peter Rolf schrieb:
> luigi scarso schrieb:
>>> i can make a minimal example(<100kb), so you can look into it when you
>>> have time. there are still problems with clipping in mkiv, but my first
>>> try to create a breaking minimal failed. so far db problems and clipping
>>> in mkiv are the only issues left (rest looks pretty good!).
>> ok , plus your tex code
>> (offlist)
>>
> thanks luigi. no way to test it elsewhere :)

first of all: *thanks to luigi* for testing and for using the 'right' 
binary versions (which was the key) :)

now the news:
- pdftex 1.40.7 works fine with my test file. the only thing is, that it 
complains about the wrong pdf version of the included db file.
..
pdfTeX warning: pdftex (file ./lib/test-db.pdf): PDF inclusion: found 
PDF version <1.6>, but at most version <1.5> allowed

- luatex 0.25.3 doesn't break, but includes always the first image in 
the database. if i remember it right this was a filter problem.


- pdftex 1.50alpha and
   luatex trunk (17.05.2008) fail with the described error


the latest official released versions of luatex and pdftex generate a 
working pdf. both developement versions fail. i guess there is a bug in 
the pdf inclusion routines, as this is all that is done in my test file.
if someone can tell me how i can pass the pdfminorversion as runtime 
parameter, i can create a database in pdf1.4 and test it again with a 
more 'compatible' pdf version. anyhow, i quit for today...


best wishes, peter

> ___________________________________________________________________________________
> 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  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-05-20 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20  9:10 Peter Rolf
2008-05-20  9:18 ` Hans Hagen
2008-05-20 13:01   ` Peter Rolf
2008-05-20 14:26     ` luigi scarso
2008-05-20 14:37       ` Peter Rolf
2008-05-20 18:20         ` Peter Rolf [this message]
2008-05-20  9:25 ` Wolfgang Schuster
2008-05-20 10:18   ` Peter Rolf

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=4833168A.2000204@gmx.net \
    --to=indiego@gmx.net \
    --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).