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: beta (12.05.2009, 22:36): footnote marker and overprinting
Date: Thu, 14 May 2009 19:08:11 +0200	[thread overview]
Message-ID: <4A0C4FFB.4080109@gmx.net> (raw)
In-Reply-To: <4A0C358F.4020109@wxs.nl>

Hans Hagen schrieb:
> Peter Rolf wrote:
>> Hi,
>>
>> just in case this slipped someone's mind :)
>>
>> I still get an error about an undefined control sequence 
>> (\PDFobjectreferenceB) and the footnote marker (star) is not moved 
>> with the footnote (\moveright).
>>
>> The attached example code (with overprinting) breaks with the 
>> mentioned error. The attached picture shows the problem with the 
>> separated footnote marker. It can be created with the other versions 
>> (without overprinting) of the \NoteNumber and \MyFootnote macros.
>
> it's
>
> \def\MyFootnote#1{\footnote
>   {\hskip3em \startproperty[overprint]#1\stopproperty}}
>
sorry, i couldn't resist. \dostartoverprint was the more 'sexy' 
alternative ;)

to tell the truth i can't quite remember why i chose this one. but i'm 
sure that i have tested everthing related to overprint.

>
> (i'll make \startoverprint which is actually kind of low level 
> unexpandable but not \dostartproperty which is not intended as user 
> command)
>
ah, perfect.... a nice and melodic user command without any expansion 
problems :)
many thanks!

>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
>                                              | 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://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:[~2009-05-14 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 10:46 Peter Rolf
2009-05-14 15:15 ` Hans Hagen
2009-05-14 17:08   ` Peter Rolf [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=4A0C4FFB.4080109@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).