Re: [NTG-context] pagenumber suppression howto?

2014-07-21 Thread Meer, H. van der 
Would it be a good idea to add to the definition of \noheaderandfooterlines?
For example
\def\noheaderandfooterlines{..}
% Separately kill header and footerlines on the current page.
\def\noheaderlines{\setuplayoutelement[header][state=empty]}
\def\nofooterlines{\setuplayoutelement[footer][state=empty]}
I added these to my macroset, because I find \noheaderlines easier to remember 
than \setuplayoutelement[header][state=empty].

Hans van der Meer



On 20 Jul 2014, at 22:20, Wolfgang Schuster 
schuster.wolfg...@gmail.commailto:schuster.wolfg...@gmail.com wrote:


Am 20.07.2014 um 22:02 schrieb Meer, H. van der 
h.vanderm...@uva.nlmailto:h.vanderm...@uva.nl:



On 20 Jul 2014, at 21:51, Wolfgang Schuster 
schuster.wolfg...@gmail.commailto:schuster.wolfg...@gmail.com wrote:

Am 20.07.2014 um 21:35 schrieb Meer, H. van der 
h.vanderm...@uva.nlmailto:h.vanderm...@uva.nl:

Thanks. Please let us know if this addition of location=none will be taken up 
in a future beta.

I also realised that the effect wanted can be obtained by dividing the single
  \noheaderandfooterlines
into two additional macros
\noheaderlines and \nofooterlines
Is that a viable idea too?

When you want disable only one element you can use the \setupheader or 
\setupfooter command.


I guess no. That was just the thing that did not worked out, because the 
\noheaderandfooterlines did the effect of the \setupheader vanish.

What \noheaderandfooterlines does is to call the following two setups:

  - \setupheader[state=empty] and
  - \setupfooter[state=empty]

Wolfgang

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nlmailto:ntg-context@ntg.nl / 
http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nlhttp://www.pragma-ade.nl/ / 
http://tex.aanhet.nethttp://tex.aanhet.net/
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.nethttp://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
___

[NTG-context] \underbar

2014-07-21 Thread Herbert Voss 
From the contextref.pdf, p 262 \underbar


A disadvantage of this command is that words can no longer be
hyphenated. This is a nasty
side--effect. But we do support nested underlining.


This commant is wrong, right? Hyphenation is supported.

Herbert
___
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
___

Re: [NTG-context] \underbar

2014-07-21 Thread Hans Hagen 

On 7/21/2014 2:25 PM, Herbert Voss wrote:

 From the contextref.pdf, p 262 \underbar


A disadvantage of this command is that words can no longer be
hyphenated. This is a nasty
side--effect. But we do support nested underlining.


This commant is wrong, right? Hyphenation is supported.


indeed, in mkiv hyphenation works ok

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___