[NTG-context] pagenumber suppression howto?

2014-07-20 Thread Meer, H. van der
My goal is pages without header info at the top and text plus a pagenumber on 
the bottom. This can be accomplished by:
\setupheader[state=stop]
\setupfooter[text][before=\hairline,style=small,location=left,strut=yes]
\setupfootertexts[some text][pagenumber]

I want the first page without that footer, to be done with:
\noheaderandfooterlines

But then comes the problem, because afterwards the default takes over and on 
the subsequent pages the pagenumber starts to appear in the header (the default 
setting apparently). Thus the \noheaderandfooterlines annuls the 
\setupheader[state=stop]

I did not find out how to get rid of the default pagenumber. 
\setuppagenumber[state=stop] kills all pagenumbering, the programmed one in the 
leftbottom corner too.
\setuppagenumbering[state=stop] kills all pagenumbers, included the one I want 
to appear.
\setuppagenumbering[location=none] merely puts the pagenumber in the middle of 
the footer, obviously location=none has no meaning in ConTeXt.

So, I am at the end of the possibilities I can think of. How to?

Hans van der Meer



___
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] State of documentation of ConTeXt?

2014-07-20 Thread Gerben Wierda
On 15 Jul 2014, at 16:42, Mojca Miklavec mojca.miklavec.li...@gmail.com wrote:

 ConTeXt comes with full source code, so users can easily study the
 source code.

This is crazy. Sorry, you can’t expect users to be able to do that. Lamport 
created LaTeX *and* wrote the “LaTeX User’s Guide and Reference manual”.  The 
authors mentioned below were all developers too. You need that level of 
understanding to write a manual.

 The project could easily employ two people to work full
 time just to keep up with the pace of development (once they would
 catch up). 


I would expect it to be far less than that once you have the documentation. 
What a project needs is discipline. If the ConTeXt stays a 
tinkered-tool-in-flux (because that is how Hans needs it for his own work), a 
decent manual will never arrive unless there is the discipline that any new 
functionality is documented (“user manual  reference”) in full before 
proceeding to the next development.

On 16 Jul 2014, at 00:26, David Wooten d...@trichotomic.net wrote:

 It’s suspect to take umbrage on another’s behalf, but “tinkering researchers 
 may not be inclined to do that, they want to tinker” — It’s absurd to suggest 
 that Hans co. are “tinkering” for the sake of tinkering.

I never suggested that. Hans  Co tinker because they want to make progress and 
develop functionality they need. But because the project is in constant flux, 
even if you would have time (money) to fund documentation, the documentation 
would be out-of-date soon.

I would immediately buy any book that explains ConTeXt such as the books that 
are there for LaTeX. But then, LaTeX is moribund and doesn’t change at all. An 
easier target.

Hans  Taco: how much money would need to be raised to produce something of the 
quality of Kopka  Daly’s “Guide to LaTeX”?  or Goossens, Mittelbach  
Samarin’s “The LaTeX Companion”? Because, I don’t think this will happen unless 
some money is raised to pay for it.

I would gladly donate in a crowdfunding initiative for a good book. But how 
much is needed to make it happen?

G
___
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] State of documentation of ConTeXt?

2014-07-20 Thread Gerben Wierda
On 20 Jul 2014, at 14:14, Gerben Wierda gerben.wie...@rna.nl wrote:

 I would gladly donate in a crowdfunding initiative for a good book. But how 
 much is needed to make it happen?

BTW, as I have become a publisher in recent years I know now what to do, I can 
maybe help by acting as the publisher for the book. If an author of a group of 
authors can write a manuscript, I would be happy to fund the production of the 
book and host the sales of a PDF version (see http://bit.ly/1iNacG8 for how 
selling both print and PDF would work).

If money is needed in advance for authors so they can live while writing, we 
could crowdsource that and repay the investors form the proceeds of the book. 
When the investment has been paid back, we could distribute the PDF for free or 
use the proceeds to fund updates and such.

G

___
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] pagenumber suppression howto?

2014-07-20 Thread Wolfgang Schuster

Am 20.07.2014 um 12:03 schrieb Meer, H. van der h.vanderm...@uva.nl:

 My goal is pages without header info at the top and text plus a pagenumber on 
 the bottom. This can be accomplished by:
 \setupheader[state=stop]
 \setupfooter[text][before=\hairline,style=small,location=left,strut=yes]
 \setupfootertexts[some text][pagenumber]
 
 I want the first page without that footer, to be done with:
 \noheaderandfooterlines
 
 But then comes the problem, because afterwards the default takes over and on 
 the subsequent pages the pagenumber starts to appear in the header (the 
 default setting apparently). Thus the \noheaderandfooterlines annuls the 
 \setupheader[state=stop]
 
 I did not find out how to get rid of the default pagenumber. 
 \setuppagenumber[state=stop] kills all pagenumbering, the programmed one in 
 the leftbottom corner too.
 \setuppagenumbering[state=stop] kills all pagenumbers, included the one I 
 want to appear.
 \setuppagenumbering[location=none] merely puts the pagenumber in the middle 
 of the footer, obviously location=none has no meaning in ConTeXt.
 
 So, I am at the end of the possibilities I can think of. How to?

Context performs only a check for a empty argument of the location key
(i.e. \setuppagenumbering[location=]) and in all other keys checks the argument
for a valid keyword, all unknown keywords are ignored. The ignored  “none” 
keyword
can be added by a simple change in the file page-txt.mkvi and I think such a 
change
would make sense because there are many places “none” is used when you disable
a function.

\unexpanded\def\strc_pagenumbers_set_location
  {\edef\p_strc_pagenumbers_location{\directpagenumberingparameter\c!location}%
   \ifx\p_strc_pagenumbers_location\m_page_layouts_page_number_location
  % unchanged
   \else
 \let\m_page_layouts_page_number_location\p_strc_pagenumbers_location
 \page_layouts_reset_page_number_location
 \ifx\p_strc_pagenumbers_location\empty
   % set otherwise
-\else
+\else\ifx\p_strc_pagenumbers_location\v!none
+  % set otherwise
+\else
   \page_layouts_identify_page_number_location
   \page_layouts_set_page_number_location
-\fi
+\fi\fi
   \fi}


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] pagenumber suppression howto?

2014-07-20 Thread Wolfgang Schuster

Am 20.07.2014 um 21:35 schrieb Meer, H. van der 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.

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] pagenumber suppression howto?

2014-07-20 Thread Meer, H. van der


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.

Hans van der Meer

___
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] pagenumber suppression howto?

2014-07-20 Thread Wolfgang Schuster

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

 
 
 On 20 Jul 2014, at 21:51, Wolfgang Schuster schuster.wolfg...@gmail.com 
 wrote:
 
 Am 20.07.2014 um 21:35 schrieb Meer, H. van der 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.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] State of documentation of ConTeXt?

2014-07-20 Thread Mojca Miklavec
On Sun, Jul 20, 2014 at 2:14 PM, Gerben Wierda wrote:

 Sorry, you can’t expect users to be able to do that. Lamport
 created LaTeX *and* wrote the “LaTeX User’s Guide and Reference manual”.

teasing
Indeed. Sorry, you can't do that to users. Christian Schenk also
created MikTeX (I still have MikTeX files from 23 years ago) *and* is
still developing it actively and answering emails from users.
/teasing

 The authors mentioned below were all developers too. You need that level of
 understanding to write a manual.

What kind of developers? Did they contribute to the LaTeX core? (Many
ConTeXt users are developers, but it highly depends what you count as
a developer.)

 The project could easily employ two people to work full
 time just to keep up with the pace of development (once they would
 catch up).

 I would expect it to be far less than that once you have the documentation.

(a) You probably never tried to follow how fast ConTeXt is being developed.
(b) There's a tricky once in the sentence.

Ad (a): I've heard a rumour (that might just as well be false
information) that authors of the LaTeX companion or maybe LaTeX
Graphics companion had a serious problem. They hardly managed writing
as fast as the packages described in the book kept developing.

Also, if I see correctly, the book Guide to LaTeX has been published
in 2003. Even for LaTeX that's a totally outdated book and doesn't
even scratch the surface of LuaTeX, XeTeX and OpenType fonts - the
most useful things that most users should switch to nowadays. The
LaTeX Companion is probably even more outdated and useless as it
doesn't even scratch the surface of many useful packages that surfaced
since the last release. I have the LaTeX Graphics Companion on my
bookshelf for example, but even if I was still using LaTeX, the book
would be almost useless to me nowadays. Almost none of the things I
would want to use are covered there (starting with TikZ for example).

The beginner's tutorial for ConTeXt is no more outdated than these
books are (but of course these books were more complete at the time of
writing and probably went under many more proofreading than the
ConTeXt tutorial, with professional writers involved).

I'm exaggerating a bit on purpose. But not much.

 Hans  Taco: how much money would need to be raised to produce something of
 the quality of Kopka  Daly’s “Guide to LaTeX”?  or Goossens, Mittelbach 
 Samarin’s “The LaTeX Companion”?

What do you mean with of the quality of these books? Having a
similar number of pages written in comparable quality (something like
a revised beginner's manual) or so complete in description of the
functionality as the mentioned manuals?

My estimate would be that a complete context reference with
well-described options and including trivial examples would require
cca. 10.000-50.000 pages. Maybe others have different estimates, but
now do the math. (Existing manuals like MetaFun or the old cont-en.pdf
are roughly 400 pages. But that's nowhere near 10 % of the ConTeXt
functionality. One would need to document the whole TeX part, the
whole metapost part, the whole lua part, the whole xml, all perl, ruby
and lua scripts, write better man pages, probably list the whole
Unicode to show the ConTeXt names in one appendix ...)

 Because, I don’t think this will happen
 unless some money is raised to pay for it.

 I would gladly donate in a crowdfunding initiative for a good book. But how
 much is needed to make it happen?

I would gladly donate as well. But probably not anywhere near the
amount that would suffice even if a nontrivial number of users
contributed the same.

Mojca

PS: the example you linked to asks for 30 EUR for a 220 page book. If
the same calculation is applied to my estimate of the number of
required pages, 22.000 pages would translate to 3000 EUR per copy.
___
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] Figure whitespace overflows page

2014-07-20 Thread Rik Kabel
On 2014-03-26 19:35, Rik Kabel wrote, originally with the subject 
Caption whitespace overflows page:
How can I get rid of the space at the top of the first line of text on 
page three in the following MWE. The \setupfloats[spaceafter=none] 
masks the problem rather than addresses the problem directly. Playing 
with the size of the figures (changing them to 3cm) shows that the  
caption text is not pushed to the second page, just some whitespace 
imputed to them. This happens with TL2013 and with the latest 
(20140325) standalone beta.


I may be able to get away with the figure overflowing into the 
footnote space by avoiding footnotes, but the space on the next page 
is just ugly.


\setuppapersize[A6]
\setupexternalfigures[location={local,default}]
\setupfloats[spaceafter=none]
\starttext
\input{knuth}
\placefigure[left]{Caption}
  {\startcombination[1*3]
{\externalfigure[cow.pdf][height=2cm]}{cow}
{\externalfigure[cow.pdf][height=2cm]}{cow}
{\externalfigure[cow.pdf][height=2cm]}{cow}
  \stopcombination}
\input{knuth}

\input{knuth}
\stoptext



Can anyone suggest a fix for this, or declare that there is nothing that 
can be done except to change the page content? It is still a problem.


The problem is not with caption space /per se/, but with the space taken 
for the figure as a whole. I would think that, once the page with the 
figure is finalized, additional reserved whitespace below it can be 
discarded.


I did notice that it was also raised without apparent resolution in 
March 2007 (http://www.mail-archive.com/ntg-context%40ntg.nl/msg21269.html).


--
Rik Kabel
___
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] State of documentation of ConTeXt?

2014-07-20 Thread Gerben Wierda
On 20 Jul 2014, at 22:24, Mojca Miklavec mojca.miklavec.li...@gmail.com wrote:

 On Sun, Jul 20, 2014 at 2:14 PM, Gerben Wierda wrote:
 
 Sorry, you can’t expect users to be able to do that. Lamport
 created LaTeX *and* wrote the “LaTeX User’s Guide and Reference manual”.
 
 teasing
 Indeed. Sorry, you can't do that to users. Christian Schenk also
 created MikTeX (I still have MikTeX files from 23 years ago) *and* is
 still developing it actively and answering emails from users.
 /teasing
 
 The authors mentioned below were all developers too. You need that level of
 understanding to write a manual.
 
 What kind of developers? Did they contribute to the LaTeX core? (Many
 ConTeXt users are developers, but it highly depends what you count as
 a developer.)

Some contributed packages, some other stuff (even printer drivers). They all 
were deeply involved with the inside of TeX and LaTeX at a level that they 
would have to understand TeX and LaTeX to the core as they were developers in 
that environment

 Hans  Taco: how much money would need to be raised to produce something of
 the quality of Kopka  Daly’s “Guide to LaTeX”?  or Goossens, Mittelbach 
 Samarin’s “The LaTeX Companion”?
 
 What do you mean with of the quality of these books? Having a
 similar number of pages written in comparable quality (something like
 a revised beginner's manual) or so complete in description of the
 functionality as the mentioned manuals?

I agree these are now outdated in several areas and less useful as they were 
half a decade ago. But something that is complete enough for a user (not a 
TeXnician), doesn’t contain too many white spots and certainly does not contain 
stuff that isn’t true anymore.

 My estimate would be that a complete context reference with
 well-described options and including trivial examples would require
 cca. 10.000-50.000 pages. Maybe others have different estimates, but
 now do the math. (Existing manuals like MetaFun or the old cont-en.pdf
 are roughly 400 pages. But that's nowhere near 10 % of the ConTeXt
 functionality. One would need to document the whole TeX part, the
 whole metapost part, the whole lua part, the whole xml, all perl, ruby
 and lua scripts, write better man pages, probably list the whole
 Unicode to show the ConTeXt names in one appendix …)

If a tool needs 50.000 pages to document its use, you are in trouble (in more 
ways than one). 

I think in reality a set of manuals, with core functionality and all kinds of 
extras a manual of 500 pages and maybe a reference manual of the same size 
would be something useful and thus meaningful. Stuff like MetaFun can have its 
own manual and doesn’t need to be in a core ConTeXt manual.

A user manual is enough. You don’t need a developer manual. So, documenting all 
the development you can do with ConTeXt (programming in lua and whatnot) would 
for me not be what is needed for a user manual. What a user manual does is what 
cont-en.pdf does, but then up to date and complete.

G
___
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] State of documentation of ConTeXt?

2014-07-20 Thread Henning Hraban Ramm
Am 2014-07-21 um 03:07 schrieb Gerben Wierda gerben.wie...@rna.nl:

 My estimate would be that a complete context reference with
 well-described options and including trivial examples would require
 cca. 10.000-50.000 pages. Maybe others have different estimates, but
 now do the math. (Existing manuals like MetaFun or the old cont-en.pdf
 are roughly 400 pages. But that's nowhere near 10 % of the ConTeXt
 functionality. One would need to document the whole TeX part, the
 whole metapost part, the whole lua part, the whole xml, all perl, ruby
 and lua scripts, write better man pages, probably list the whole
 Unicode to show the ConTeXt names in one appendix …)
 
 If a tool needs 50.000 pages to document its use, you are in trouble (in more 
 ways than one). 
 
 I think in reality a set of manuals, with core functionality and all kinds of 
 extras a manual of 500 pages and maybe a reference manual of the same size 
 would be something useful and thus meaningful. Stuff like MetaFun can have 
 its own manual and doesn’t need to be in a core ConTeXt manual.
 
 A user manual is enough. You don’t need a developer manual. So, documenting 
 all the development you can do with ConTeXt (programming in lua and whatnot) 
 would for me not be what is needed for a user manual. What a user manual does 
 is what cont-en.pdf does, but then up to date and complete.

If I might chime in …

What we really need (and what „simple“ users like me cannot write, even if I 
sometimes look into the sources) is a usable command reference, covering all 
„usable“ commands and all their „usable“ options (i.e. omit too experimental 
stuff).
What we have on the wiki now is much too incomplete in all regards. I don’t 
know if there’s something (more?) that can be automated.

I don’t know if Hans, Taco or Wolfgang (any other candidates?) would be able 
and willing to do that work, if e.g. DANTE would fund it. Would you, and what 
do you think how much funding would be required to at least document the 
current state of MkIV?

I would not try to write a (printed/printable) reference manual for ConTeXt, 
that really makes not much sense.
We don’t need to argue about page estimates, that depends too much on layout 
anyway …

I thought the previous ConTeXt meeting was about documentation? Didn’t you 
agree on a better wiki structure?


Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

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