ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Willi Egger <w.egger@boede.nl>
Subject: Re: header entries semi-wrong
Date: Thu, 10 Mar 2011 15:55:44 +0100	[thread overview]
Message-ID: <7FAD7009-5193-49C2-98D6-E91FB9BF2C63@st.estfiles.de> (raw)
In-Reply-To: <BC53218F-CF4A-4F88-A8F4-52E3E5D78C40@boede.nl>


Of course, manually tweaking helps. 
Only, one needs to see that here is a page where tweaking is needed!

And this is the problem:
The head says "1.2 one", but it should be "1.1 one"!

First I trusted the automated head entries, then I realized it can be wrong and now I skim typeset books before sending them to printer.
But when skimming a book it is quite likely to not-see the wrong "1" when seeing the correct "one"!

Is there no way to automatically get the correct number information "1.1" that is corresponding to the correct text entry "one"??


"\getmarking[section]" provides the right information,
"\headnumber[section]" is too far in border cases ... 

Isn't there a command that gets the number that belongs to the text of "\getmarking[section]"


Steffen




Am 10.03.2011 um 15:16 schrieb Willi Egger:

> I agree with Luigi, after using different length and \page I was able to produce correct output.
> According to me your example is probably a border case.
> 
> Willi
> 
> On 10 Mar 2011, at 14:59, luigi scarso wrote:
> 
>> On Thu, Mar 10, 2011 at 2:38 PM, Steffen Wolfrum <context@st.estfiles.de> wrote:
>>> 
>>> Am 06.03.2011 um 11:56 schrieb Steffen Wolfrum:
>>> 
>>>> --on page 1 there is
>>>> section "1.1 one" and you get the header entry "1.1 one"
>>>> - on page 3 there is still
>>>> section "1.1 one" and you get the header entry "1.2 one" (<- ?!)
>>>> - on page 5 there is
>>>> section "1.2 two" and you get the header entry "1.2 two"
>>>> 
>>>> you see the problem? the "getmarking" behaves correctly (one/one/two)
>>>> while the "headnumber" is confused (1.1/1.2/1.2))!
>>> 
>>> 
>>> 
>>> Could some maybe please have look at my test file (see original post):
>>> Is this "asynchronous"head  a bug or am I simply doing something wrong??
>> I don't know, but with
>> 
>> \dorecurse{2}{\input tufte \par}
>> \page
>> \section{Two}
>> 
>> things go better.
>> 
>> -- 
>> luigi
> 
> \showframe
> \setupbodyfont[postscript, 10pt]\setupinterlinespace[line=12pt]
> 
> \definepapersize[Pape][width=14.7cm,height=22.3cm]
> \setuppapersize[Pape][Pape]
> \setuplayout
>    [width=113mm,height=572pt\relax,
>    backspace=17mm,topspace=17mm,
>    header=12pt,headerdistance=6pt,
>    footer=36pt,footerdistance=0pt,
>    location=middle,marking=off]
> \setupwhitespace[halfline]
> \setuppagenumbering [alternative=doublesided,location=]
> \setupheader[align=middle]
> 
> \mainlanguage[de]
> 
> \def\HeadL{Part {\convertnumber{Numbers}{\namedheadnumber{chapter}}}\enskip\getmarking[EbeneEins]}
> \def\HeadR{\headnumber[section]\enskip\getmarking[section][current]}
> 
> \setupheadertexts
>    [\vtop{\startalignment[center]\HeadR\stopalignment}] [pagenumber]
>    [pagenumber] [\vtop{\startalignment[center]\HeadL\stopalignment}]
> 
> 
> \starttext
> \chapter{X}
> \section{One}
> \dorecurse{9}{\input ward \par}
> % \dorecurse{5}{\input ward \par}
> %\dorecurse{2}{\input tufte \par}
> \page
> \strut\page
> \dorecurse{2}{\input tufte \par}
> \section{Two}
> \dorecurse{11}{\input ward \par}
> 
> \page 
> 
> \section{Three}
> \dorecurse{11}{\input ward \par}
> 
> \stoptext
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2011-03-10 14:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 10:56 Steffen Wolfrum
2011-03-10 13:38 ` Steffen Wolfrum
2011-03-10 13:59   ` luigi scarso
2011-03-10 14:16     ` Willi Egger
2011-03-10 14:55       ` Steffen Wolfrum [this message]
2011-03-10 14:59         ` Wolfgang Schuster
2011-03-10 15:02           ` luigi scarso
2011-03-10 15:17           ` Steffen Wolfrum
2011-03-10 14:26 ` Wolfgang Schuster
2011-03-10 14:48   ` Steffen Wolfrum
2011-03-10 14:57     ` Wolfgang Schuster

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=7FAD7009-5193-49C2-98D6-E91FB9BF2C63@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=w.egger@boede.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).