ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \doifemptyelse
Date: Thu, 20 Feb 2014 23:23:24 +0100	[thread overview]
Message-ID: <F5E6E32E-278E-4C5F-AF7C-46FC9276520F@gmail.com> (raw)
In-Reply-To: <53067D34.4020903@gmx.es>


Am 20.02.2014 um 23:09 schrieb Pablo Rodriguez <oinos@gmx.es>:

> On 02/20/2014 09:39 PM, Wolfgang Schuster wrote:
>> Am 20.02.2014 um 21:12 schrieb Pablo Rodriguez:
>>> [...]
>>> How can I make the first conditional work?
>> 
>> You can’t, markings are only reliable when you use them in the
>> header of footer of the page.
>> 
>> To access the values of a heading you can use the \structurevariable
>> and \namedstructurevariable commands.
> 
> Many thanks for your reply, Wolfgang.
> 
> My question was about headers, but I didn’t mention it to make a shorter sample.

In this case this was a important part for the solution because it makes a difference
when you use \getmarking in \setupheadertexts or in the text.

> The code now is the following:
> 
> \setupheadertexts[\hfill\namedstructurevariable{chapter}{title}\hfill]
>    [] []
>    [\hfill\doifsomethingelse{\namedstructurevariable{section}{title}}
>            {\namedstructurevariable{section}{title}}
>            {\namedstructurevariable{chapter}{title}}\hfill]
> 
> 
> Only a minor detail: is there a more proper way to center both headings?


You can use the simple version of \setupheadertexts and use \doifoddpageelse
to check whether you’re on a left or right page. When you make a test for content
of a \getmarking command you have to use \doiftext because the \doifempty etc.
checks don’t work in this case.

\startsetups[header]
  \doifoddpageelse
    {
      \getmarking[chapter]
    }
    {
      \doiftextelse
        {
          \getmarking[section]
        }
        {
          \getmarking[section]
        }
        {
          \getmarking[chapter]
        }
    }
\stopsetups


\setupheadertexts[\directsetup{header}]
\setupfootertexts[pagenumber]

\starttext

\chapter{Chapter A}

\page

\chapter{Chapter B}

\page

\dorecurse{5}
  {\chapter{Chapter #1}
   \dorecurse{10}
     {\section{Section #1.##1}
	  \dorecurse{3}{\input knuth\par}}}

\stoptext

Wolfgang
___________________________________________________________________________________
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:[~2014-02-20 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 20:12 \doifemptyelse Pablo Rodriguez
2014-02-20 20:39 ` \doifemptyelse Wolfgang Schuster
2014-02-20 22:09   ` \doifemptyelse Pablo Rodriguez
2014-02-20 22:23     ` Wolfgang Schuster [this message]
2014-02-23  7:24       ` \doifemptyelse Pablo Rodriguez
2014-02-20 22:32     ` \doifemptyelse Thangalin
2014-02-23  7:28       ` \doifemptyelse Pablo Rodriguez

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=F5E6E32E-278E-4C5F-AF7C-46FC9276520F@gmail.com \
    --to=schuster.wolfgang@gmail.com \
    --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).