Re: [NTG-context] need defaults for \definehighlight

2015-02-08 Thread Keith J. Schultz
Hi Hans, Irdis, All,

It might sound like splitting hairs, but I find we should be careful how we 
call this beast!

Basically, a highlight allows one so setup a font style and color to be applied
to it contents.

The problem is that is this REALLY a Highlight! 

A style and color is applied so, what we have is a use color and style!

would it not be better to call it
definecharstyle
or
definetextstyle

For compatibility we could use keep the definehighlight as a synonym.

As to setting up defaults, the question is their a generic usage of such ways of
for so called highlights. These are, basically, by those that:
1) like this much fluff
2) idiosyncratic terminology

1) is supposed to avoided! And basically makes ConTeXt look like Word!

The use of another way of defining a command for the standard font styles
is proof enough for 2. Also, not everybody would want the predefined styles and 
colors
so they will have to be changed in the setuphighlight anyway!

The use of such a command is convient, but we should think about the 
nomenclature!
The nomenclature should reflect what it does. We can have synonyms to satisfy 
the
semantic usage of it!

regards
Keith


 Am 07.02.2015 um 13:53 schrieb Hans Hagen pra...@wxs.nl:
 
[snip, snip]

 Anyway, the problem with predefined highlights is that we won't overload 
 existing commands by default, so redefining is not an option in the core.
 
 An option is to provide a set like:
 
 \unprotect
 
 \definehighlight[\v!italic][\c!command=\v!no,\c!style=\v!italic]
 \definehighlight[\v!bold  ][\c!command=\v!no,\c!style=\v!bold]
 \definehighlight[\v!bolditalic][\c!command=\v!no,\c!style=\v!bolditalic]
 \definehighlight[\v!mono]  [\c!command=\v!no,\c!style=\v!mono]
 \definehighlight[\v!monobold]  [\c!command=\v!no,\c!style=\v!monobold]
 
 \definehighlight[important][\c!command=\v!no,\c!style=\v!bold]
 \definehighlight[unimportant]  [\c!command=\v!no,\c!color=darkgray]
 \definehighlight[warning] 
 [\c!command=\v!no,\c!style=\v!bold,\c!color=darkblue]
 \definehighlight[error] [\c!command=\v!no,\c!style=\v!bold,\c!color=darkred]
 
 \protect
 
 \starttext
 
\highlight[italic] {italic}
\highlight[bolditalic] {bolditalic}
\highlight[bold]   {bold}
\highlight[mono]   {mono}
\highlight[monobold]   {monobold}
\highlight[important]  {important}
\highlight[unimportant]{unimportant}
\highlight[warning]{warning}
\highlight[error]  {error}
 
 \stoptext
 
 Keep in mind that coding in terms of 'emph' is rather useless with respect to 
 highlights. Highlights relate to structure (while \it doesn't) so you need 
 tags like 'important' and so.

___
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] need defaults for \definehighlight

2015-02-08 Thread Wolfgang Schuster

 Am 08.02.2015 um 13:56 schrieb Keith J. Schultz keithjschu...@web.de:
 
 Hi Hans, Irdis, All,
 
 It might sound like splitting hairs, but I find we should be careful how we 
 call this beast!
 
 Basically, a highlight allows one so setup a font style and color to be 
 applied
 to it contents.
 
 The problem is that is this REALLY a Highlight! 
 
 A style and color is applied so, what we have is a use color and style!
 
 would it not be better to call it
 definecharstyle
 or
 definetextstyle
 
 For compatibility we could use keep the definehighlight as a synonym.
 
 As to setting up defaults, the question is their a generic usage of such ways 
 of
 for so called highlights. These are, basically, by those that:
 1) like this much fluff
 2) idiosyncratic terminology
 
 1) is supposed to avoided! And basically makes ConTeXt look like Word!
 
 The use of another way of defining a command for the standard font styles
 is proof enough for 2. Also, not everybody would want the predefined styles 
 and colors
 so they will have to be changed in the setuphighlight anyway!
 
 The use of such a command is convient, but we should think about the 
 nomenclature!
 The nomenclature should reflect what it does. We can have synonyms to satisfy 
 the
 semantic usage of it!

There is a \definestyle command (you can disable the creation of command [e.g. 
\strong]
when you add “method=” to \definestyle) but it doesn’t add tags in the export 
command.

\definestyle [strong] [style=bold]
\definestyle [emphasized] [style=italic]

\starttext

Strong: You can use \style[strong]{strong} or \strong{strong} or 
\startstyle[strong]strong\stopstyle.

Emphasized: You can use \style[emphasized]{emphasized} or 
\emphasized{emphasized} or \startstyle[emphasized]emphasized\stopstyle.

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

Re: [NTG-context] need defaults for \definehighlight

2015-02-08 Thread Hans Hagen

On 2/8/2015 3:40 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

On Sun, 08 Feb 2015 07:01:31 -0700, Hans Hagen pra...@wxs.nl wrote:


the only reason why highlight exists is that it can be used to tag
stuff that is otherwise untagged in the exporter to xml


Ok, so I suppose \quote and \quotation already work in the exporter. The
following iteration then:

=
\unprotect

\definehighlight[\v!italic] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[\v!bold  ] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[\v!bolditalic] [\c!command=\v!no,\c!style=\v!bolditalic]
\definehighlight[\v!mono]   [\c!command=\v!no,\c!style=\v!mono]
\definehighlight[\v!monobold]   [\c!command=\v!no,\c!style=\v!monobold]
\definehighlight[\v!smallcaps]  [\c!command=\v!no,\c!style=\v!smallcaps]


i don't like these as tags (you can define start-stops if needed)


\definehighlight[emphasis]  [\c!command=\v!no,\c!style=\v!italic] %
Does Hans prefer slanted here for default??


depends \em would do


\definehighlight[important] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[veryimportant] [\c!command=\v!no,\c!style=\v!smallcaps]
\definehighlight[unimportant]   [\c!command=\v!no,\c!color=darkgray]
\definehighlight[warning]
[\c!command=\v!no,\c!style=\v!bold,\c!color=darkblue]
\definehighlight[error]
[\c!command=\v!no,\c!style=\v!bold,\c!color=darkred]

\definehighlight[booktitle] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[abbreviation]  [\c!command=\v!no,\c!style=\v!smallcaps]
\definehighlight[propername][\c!command=\v!no,\c!style=\v!smallcaps]


we have an abbreviations mechanism already


\definehighlight[typing][\c!command=\v!no,\c!style=\v!mono]


we have a typing environment already


\protect

\starttext

 \highlight[italic] {italic}
 \highlight[bolditalic] {bolditalic}
 \highlight[bold]   {bold}
 \highlight[mono]   {mono}
 \highlight[monobold]   {monobold}
 \highlight[smallcaps]  {smallcaps}

 {\sc smallcaps}% this works
 \smallcaps{smallcaps}  % this command doesn't work!!
 {\smallcaps smallcaps} % this command doesn't work!!

 \highlight[important]  {important}
 \highlight[veryimportant]  {very important}
 \highlight[extraimportant] {extra important}
 \highlight[unimportant]{unimportant}
 \highlight[warning]{warning}
 \highlight[error]  {error}

 \highlight[emphasis] {emphasis}
 \highlight[abbreviation] {abbreviation}
 \highlight[booktitle]{Book Title}
 \highlight[propername]   {Proper Name}

 \highlight[typing]{typing}
\stoptext
=

There seems to be a bug with \smallcaps. Otherwise I think the above
makes a good default set to start with.

Best wishes
Idris



--

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

Re: [NTG-context] need defaults for \definehighlight

2015-02-08 Thread Idris Samawi Hamid ادريس سماوي حامد

On Sun, 08 Feb 2015 10:38:14 -0700, Hans Hagen pra...@wxs.nl wrote:


On 2/8/2015 3:40 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

On Sun, 08 Feb 2015 07:01:31 -0700, Hans Hagen pra...@wxs.nl wrote:


the only reason why highlight exists is that it can be used to tag
stuff that is otherwise untagged in the exporter to xml


Ok, so I suppose \quote and \quotation already work in the exporter. The
following iteration then:

=
\unprotect

\definehighlight[\v!italic] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[\v!bold  ] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[\v!bolditalic]  
[\c!command=\v!no,\c!style=\v!bolditalic]

\definehighlight[\v!mono]   [\c!command=\v!no,\c!style=\v!mono]
\definehighlight[\v!monobold]   [\c!command=\v!no,\c!style=\v!monobold]
\definehighlight[\v!smallcaps]  [\c!command=\v!no,\c!style=\v!smallcaps]


i don't like these as tags (you can define start-stops if needed)


You don't like them? But these were in your original sample file!


\definehighlight[emphasis]  [\c!command=\v!no,\c!style=\v!italic] %
Does Hans prefer slanted here for default??


depends \em would do


Ah, \em can go outside now... So we have

\definehighlight[emphasis]  [\c!command=\v!no,\c!style=\em] % without  
the 'v!'



\definehighlight[important] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[veryimportant] [\c!command=\v!no,\c!style=\v!smallcaps]
\definehighlight[unimportant]   [\c!command=\v!no,\c!color=darkgray]
\definehighlight[warning]
[\c!command=\v!no,\c!style=\v!bold,\c!color=darkblue]
\definehighlight[error]
[\c!command=\v!no,\c!style=\v!bold,\c!color=darkred]

\definehighlight[booktitle] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[abbreviation]  [\c!command=\v!no,\c!style=\v!smallcaps]
\definehighlight[propername][\c!command=\v!no,\c!style=\v!smallcaps]


we have an abbreviations mechanism already


Ok


\definehighlight[typing][\c!command=\v!no,\c!style=\v!mono]


we have a typing environment already


Ok. It's clear that I'm doing a lot of guessing, so question: Can you  
specify exactly what does *not* get tagged in xml-export? What exactly do  
we need to worry about? Then we can go from there...


[snip]


There seems to be a bug with \smallcaps.


Can you look at \smallcaps? Thanks and

Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___
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] need defaults for \definehighlight

2015-02-08 Thread Wolfgang Schuster

 Am 08.02.2015 um 15:40 schrieb Idris Samawi Hamid ادريس سماوي حامد 
 isha...@colostate.edu:
 
 […]
 
 There seems to be a bug with \smallcaps. Otherwise I think the above makes a 
 good default set to start with.

Hans changed the effect of “style=smallcaps”, in the ConTeXt used \sc when you 
did this setups
but now ConTeXt just enables small capitals in the active font. The problem 
here is that ConTeXt’s
default font Latin Modern uses a separate file for small capitals unlike other 
fonts like TeX Gyre Pagella.

What you can do to avoid this problem with Latin Modern is to use “style=\sc” 
in your setup.

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
___

Re: [NTG-context] need defaults for \definehighlight

2015-02-08 Thread Hans Hagen

On 2/8/2015 1:56 PM, Keith J. Schultz wrote:


Basically, a highlight allows one so setup a font style and color to be
applied
to it contents.


the only reason why highlight exists is that it can be used to tag stuff 
that is otherwise untagged in the exporter to xml which is why there is 
nothing predefined


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
___

Re: [NTG-context] need defaults for \definehighlight

2015-02-08 Thread Idris Samawi Hamid ادريس سماوي حامد

Hi Keith,

On Sun, 08 Feb 2015 05:56:54 -0700, Keith J. Schultz  
keithjschu...@web.de wrote:



Also, not everybody would want the predefined styles and colors
so they will have to be changed in the setuphighlight anyway!


Indeed, but the point is not to predefine the styles but to predefine the  
highlights. E.g., \highlight[emphasis]: The user can redefine/setup the  
style anyway one likes, but the tag 'emphasis' should be standard. Put  
another way: We need some standard tags for maximum portability and fancy  
editor setups.


Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___
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] need defaults for \definehighlight

2015-02-08 Thread Idris Samawi Hamid ادريس سماوي حامد

On Sun, 08 Feb 2015 07:01:31 -0700, Hans Hagen pra...@wxs.nl wrote:

the only reason why highlight exists is that it can be used to tag stuff  
that is otherwise untagged in the exporter to xml


Ok, so I suppose \quote and \quotation already work in the exporter. The  
following iteration then:


=
\unprotect

\definehighlight[\v!italic] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[\v!bold  ] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[\v!bolditalic] [\c!command=\v!no,\c!style=\v!bolditalic]
\definehighlight[\v!mono]   [\c!command=\v!no,\c!style=\v!mono]
\definehighlight[\v!monobold]   [\c!command=\v!no,\c!style=\v!monobold]
\definehighlight[\v!smallcaps]  [\c!command=\v!no,\c!style=\v!smallcaps]

\definehighlight[emphasis]  [\c!command=\v!no,\c!style=\v!italic] %  
Does Hans prefer slanted here for default??


\definehighlight[important] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[veryimportant] [\c!command=\v!no,\c!style=\v!smallcaps]
\definehighlight[unimportant]   [\c!command=\v!no,\c!color=darkgray]
\definehighlight[warning]
[\c!command=\v!no,\c!style=\v!bold,\c!color=darkblue]
\definehighlight[error]  
[\c!command=\v!no,\c!style=\v!bold,\c!color=darkred]


\definehighlight[booktitle] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[abbreviation]  [\c!command=\v!no,\c!style=\v!smallcaps]
\definehighlight[propername][\c!command=\v!no,\c!style=\v!smallcaps]

\definehighlight[typing][\c!command=\v!no,\c!style=\v!mono]

\protect

\starttext

\highlight[italic] {italic}
\highlight[bolditalic] {bolditalic}
\highlight[bold]   {bold}
\highlight[mono]   {mono}
\highlight[monobold]   {monobold}
\highlight[smallcaps]  {smallcaps}

{\sc smallcaps}% this works
\smallcaps{smallcaps}  % this command doesn't work!!
{\smallcaps smallcaps} % this command doesn't work!!

\highlight[important]  {important}
\highlight[veryimportant]  {very important}
\highlight[extraimportant] {extra important}
\highlight[unimportant]{unimportant}
\highlight[warning]{warning}
\highlight[error]  {error}

\highlight[emphasis] {emphasis}
\highlight[abbreviation] {abbreviation}
\highlight[booktitle]{Book Title}
\highlight[propername]   {Proper Name}

\highlight[typing]{typing}
\stoptext
=

There seems to be a bug with \smallcaps. Otherwise I think the above makes  
a good default set to start with.


Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___
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] need defaults for \definehighlight

2015-02-08 Thread Hans Hagen

On 2/8/2015 8:08 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:


Ok. It's clear that I'm doing a lot of guessing, so question: Can you
specify exactly what does *not* get tagged in xml-export? What exactly
do we need to worry about? Then we can go from there...


everything that has some structure or meaning gets tagged

font/colors have no meaning they're appearance so they don't get tagged

highlights are for the few things left ... but often one can also use 
\startelement for that


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
___

Re: [NTG-context] need defaults for \definehighlight

2015-02-08 Thread Idris Samawi Hamid ادريس سماوي حامد

Hi Wolfgang,

On Sun, 08 Feb 2015 12:17:11 -0700, Wolfgang Schuster  
schuster.wolfg...@gmail.com wrote:




Am 08.02.2015 um 15:40 schrieb Idris Samawi Hamid ادريس سماوي حامد  
isha...@colostate.edu:


[…]

There seems to be a bug with \smallcaps. Otherwise I think the above  
makes a good default set to start with.


Hans changed the effect of “style=smallcaps”, in the ConTeXt used \sc  
when you did this setups
but now ConTeXt just enables small capitals in the active font. The  
problem here is that ConTeXt’s
default font Latin Modern uses a separate file for small capitals unlike  
other fonts like TeX Gyre Pagella.


What you can do to avoid this problem with Latin Modern is to use  
“style=\sc” in your setup.


Thanks for this pointer! Yes, it does work now (tried both LM and  
TeX-Gyre). And I see that \smallcaps works in TeX-Gyre but not LM... an  
interesting subtlety.


So to sum: \sc [etc. I presume] is defined for the typescript and  
\smallcaps [etc. I presume] is defined for the font itself (where can add  
and subtract opentype features etc.). Thanks again and


Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___
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] need defaults for \definehighlight

2015-02-08 Thread Idris Samawi Hamid ادريس سماوي حامد

On Sun, 08 Feb 2015 14:51:44 -0700, Hans Hagen pra...@wxs.nl wrote:


On 2/8/2015 8:08 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:


Ok. It's clear that I'm doing a lot of guessing, so question: Can you
specify exactly what does *not* get tagged in xml-export? What exactly
do we need to worry about? Then we can go from there...


everything that has some structure or meaning gets tagged

font/colors have no meaning they're appearance so they don't get tagged


Ok, but here: http://wiki.contextgarden.net/Export it says,

==
Also note that switches like \em don’t translate into output structure,  
you need to \definehighlight[emph][style=italic] and use as  
\emph{emphasized}.

==

Now \em does have structural meaning (emphasis) so either the wiki is  
wrong or we have some inconsistency here -)


highlights are for the few things left ... but often one can also use  
\startelement for that


Do you have any good examples for using \start-stopelement? Thanks and

Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___
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] Disappearing backgrounds/pagenumbers with \page[none]

2015-02-08 Thread Wolfgang Schuster
Hi,

there was a problem on TeX SE [1]  where page numbers disappear for a whole 
chapter when \page[none] is used to hide the numbers on empty left pages in a 
double sided document.

As can be seen in the following example the page numbers and background on the 
last two pages disappear when “missing” mode is enabled. This happens when the 
“blank” option for \page is used without a change in the page number (we are 
already at page 3 when \page[yes,blank,right] is expanded).

 begin example
\setupbackgrounds[page][background=color,backgroundcolor=gray]

%\enablemode[missing]

\starttext

\dorecurse{6}{\input knuth\par}

% End the current page before \page[blank] is called
\doifmode{missing}{\page}

\page[yes,blank,right]

\dorecurse{6}{\input knuth\par}

\stoptext
 end example

[1] 
http://tex.stackexchange.com/questions/225603/missing-page-numbers-first-chapter-only-context
 
http://tex.stackexchange.com/questions/225603/missing-page-numbers-first-chapter-only-context

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
___

Re: [NTG-context] Disappearing backgrounds/pagenumbers with \page[none]

2015-02-08 Thread Wolfgang Schuster

 Am 09.02.2015 um 00:10 schrieb Wolfgang Schuster 
 schuster.wolfg...@gmail.com:
 
 Hi,
 
 there was a problem on TeX SE [1]  where page numbers disappear for a whole 
 chapter when \page[none] is used to hide the numbers on empty left pages in a 
 double sided document.
 
 As can be seen in the following example the page numbers and background on 
 the last two pages disappear when “missing” mode is enabled. This happens 
 when the “blank” option for \page is used without a change in the page number 
 (we are already at page 3 when \page[yes,blank,right] is expanded).
 
  begin example
 \setupbackgrounds[page][background=color,backgroundcolor=gray]
 
 %\enablemode[missing]
 
 \starttext
 
 \dorecurse{6}{\input knuth\par}
 
 % End the current page before \page[blank] is called
 \doifmode{missing}{\page}
 
 \page[yes,blank,right]
 
 \dorecurse{6}{\input knuth\par}
 
 \stoptext
  end example
 
 [1] 
 http://tex.stackexchange.com/questions/225603/missing-page-numbers-first-chapter-only-context
  
 http://tex.stackexchange.com/questions/225603/missing-page-numbers-first-chapter-only-context
BTW: Shouldn’t the following assignment in page-ini.miv be global?

\appendtoks
\ifcase\pageornamentstate \or
\pageornamentstate\zerocount
\fi
\to \everyaftershipout

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
___

Re: [NTG-context] need defaults for \definehighlight

2015-02-08 Thread Keith Schultz
Hi Hans, Idris, All,

Then we should call it definetag of definestyletag ! It would describe
its function better!

Like I said I find the command highlight nice because it is alot easier than
define my own commands for setting styles with color!

regards
Keith.

 Am 08.02.2015 um 15:01 schrieb Hans Hagen pra...@wxs.nl:
 
 On 2/8/2015 1:56 PM, Keith J. Schultz wrote:
 
 Basically, a highlight allows one so setup a font style and color to be
 applied
 to it contents.
 
 the only reason why highlight exists is that it can be used to tag stuff that 
 is otherwise untagged in the exporter to xml which is why there is nothing 
 predefined
 
 Hans

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