From: Michail Vidiassov <master@iaas.msu.ru>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: attachment attaches twice - the fix was minimal (?)
Date: Mon, 28 Feb 2011 12:24:57 +0300 (MSK) [thread overview]
Message-ID: <alpine.OSX.2.00.1102281150570.72222@macbook.local> (raw)
In-Reply-To: <4D6B60EB.1020402@wxs.nl>
Dear Hans,
On Mon, 28 Feb 2011, Hans Hagen wrote:
>>>>> to be precise, the attachment is attached once
>>>>> but is listed twice by Adobe Reader.
>>> i'll patch lpdf-wid
>> on one hand your patch fixes the bug that is in the Subj. of the thread,
>
> this is a bit of a weird comment given that i haven't uploaded anything that
> you can comment on; as far as i can see there were a couple of issues:
> attachments without associated annotation, and labeling and both are covered,
> but using the same command and extra keys/values ...
sorry for being so dumb,
but on one hand you "haven't uploaded anything",
on the other "there were a couple of issues" that "are covered" by now,
and on the third one first-setup.sh brought me this morning lpdf-wid.lua
that now has
---
local ignorereferenced = true -- fuzzy pdf spec .. twice in attachment list, can become an option
---
etc. - that change caused my comment.
On the positive side - ConTeXt internals are your internal affairs,
you are more sovereign than some kings and revolution leaders ;)
Just tell us what that user-level "extra keys/values" are and we'll sing,
dance and rejoice, being innocent of knowing what only the ConTeXt creator is to know.
Sincerely, Michail
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-02-28 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 7:54 attachment attaches twice Reviczky, Adam
2011-02-20 9:40 ` Michail Vidiassov
2011-02-20 22:21 ` attachment attaches twice - more research Michail Vidiassov
2011-02-21 0:11 ` Hans Hagen
2011-02-21 5:49 ` attachment attaches twice - please, do not fix by trimming Michail Vidiassov
2011-02-22 5:25 ` \useattachment: Embedding files in PDFs - was "attachment attaches twice - more research" Michail Vidiassov
2011-02-23 10:21 ` attachment attaches twice - more research Michail Vidiassov
2011-02-23 10:46 ` Hans Hagen
2011-02-23 11:35 ` Michail Vidiassov
2011-02-26 23:22 ` Hans Hagen
2011-02-28 7:52 ` attachment attaches twice - the fix was minimal Michail Vidiassov
2011-02-28 8:46 ` Hans Hagen
2011-02-28 9:24 ` Michail Vidiassov [this message]
2011-02-28 9:57 ` attachment attaches twice - the fix was minimal (?) Hans Hagen
2011-04-29 7:24 ` attachment attaches twice - the fix was minimal Michail Vidiassov
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=alpine.OSX.2.00.1102281150570.72222@macbook.local \
--to=master@iaas.msu.ru \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).