* Manual
@ 2006-03-10 18:29 Jeffrey Drake
2006-03-10 23:32 ` Manual John R. Culleton
0 siblings, 1 reply; 7+ messages in thread
From: Jeffrey Drake @ 2006-03-10 18:29 UTC (permalink / raw)
I have heard a bit of talk about 'if the manual is updated' or some
such like that. I was going to have the manual printed in a book so I
have a hardcopy. Is the manual still current and relevant that it
would be worth it?
- Jeff
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Manual
2006-03-10 18:29 Manual Jeffrey Drake
@ 2006-03-10 23:32 ` John R. Culleton
2006-03-13 22:52 ` Manual or Book Geert Stappers
0 siblings, 1 reply; 7+ messages in thread
From: John R. Culleton @ 2006-03-10 23:32 UTC (permalink / raw)
On Friday 10 March 2006 13:29, Jeffrey Drake wrote:
> I have heard a bit of talk about 'if the manual is updated' or some
> such like that. I was going to have the manual printed in a book so I
> have a hardcopy. Is the manual still current and relevant that it
> would be worth it?
>
> - Jeff
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
The manual is five years old. the pattern has been to issue
additional documentation rather than update the "big" manual.
I printed mine out, have it in my manual rack, and it is getting
worn out from use.
You may as well print it out. I have not heard of a new edition
pending.
--
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf
Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Manual or Book
2006-03-10 23:32 ` Manual John R. Culleton
@ 2006-03-13 22:52 ` Geert Stappers
2006-03-13 23:05 ` Steve Peter
0 siblings, 1 reply; 7+ messages in thread
From: Geert Stappers @ 2006-03-13 22:52 UTC (permalink / raw)
[-- Attachment #1.1: Type: text/plain, Size: 981 bytes --]
On Fri, Mar 10, 2006 at 06:32:59PM -0500, John R. Culleton wrote:
> On Friday 10 March 2006 13:29, Jeffrey Drake wrote:
> > I have heard a bit of talk about 'if the manual is updated' or some
> > such like that. I was going to have the manual printed in a book so I
> > have a hardcopy. Is the manual still current and relevant that it
> > would be worth it?
> >
>
> The manual is five years old. the pattern has been to issue
> additional documentation rather than update the "big" manual.
> I printed mine out, have it in my manual rack, and it is getting
> worn out from use.
Worn out from use is one of the better things that can happen to a manual.
> You may as well print it out.
> I have not heard of a new edition pending.
Mmmm, I'm also looking for a printed edition of the ConTeXt manual.
Does this ML have publishers subscribed that have some VC to burn?
Or does see someone else see a possibilty for a ConTeXt book?
Geert Stappers
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
^ permalink raw reply [flat|nested] 7+ messages in thread
* manual
@ 2013-04-03 9:57 Meer H. van der
2013-04-03 10:06 ` manual Marco Patzer
0 siblings, 1 reply; 7+ messages in thread
From: Meer H. van der @ 2013-04-03 9:57 UTC (permalink / raw)
To: ConTeXt NTG
[-- Attachment #1.1: Type: text/plain, Size: 288 bytes --]
The latest downloaded ConTeXt manual to be found on my system is:
ConTeXt reference manual
Hans Hagen, Taco Hoekwater
June 1,2011
Is there a more recent one?
I searched the Pragma site, expecting to find it there. Did I look in the wrong place?
Hans van der Meer
[-- Attachment #1.2: Type: text/html, Size: 1822 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
* notation, manual
@ 2000-08-12 10:09 siepo
2000-08-12 10:29 ` Berend de Boer
0 siblings, 1 reply; 7+ messages in thread
From: siepo @ 2000-08-12 10:09 UTC (permalink / raw)
(sorry Berend, het vorige bericht aan jou was voor de lijst bedoeld;
dit is een uitgebreidere versie ervan)
Berend de Boer writes:
> siepo@client44-3.kabelA.oprit.rug.nl wrote:
>
> > So the number of brackets doesn't necessarily mean anything?
>
> Some brackets are optional (they're in italics).
>
>
>
> > Another obscure point is when you want to apply more than one
> > `value-keyword', e.g. if you want a small bold sectionhead. I tried
> > the following constructs:
> >
> > \setuphead[mysection][style=bold]
> > \setuphead[mysection][style=small]
> >
> > This produces small headers. Apparently, values for a single keyword
> > are not accumulated. Well, this is more or less what Berend was
> > saying.
> >
> > \setuphead[mysection[style={bold,small}]
>
> The style is really a single macro and really is an alias for a font
> switch. What you want it to do is:
>
> \def\style{\bold\small}
>
> But it doesn't work that way. Say something like:
>
> \setuphead
> [mysection]
> [style={\switchtobodyfont[small]\bf}]
>
> Groetjes,
>
> Berend. (-:
>
>
>
> >
> > Doesn't work either; it puts the text `bold,smallbold,small' before
> > both the section number and the section title. I seem to remember that
> > in some other cases such a construct DOES produce the desired
> > effect. Am I missing something? (Of course, in this particular case
> > there are other ways to do it.)
> >
> > Siep
So this is the TeX command as value. Other alternatives: {\bfx} or
\bfx or bfx.
Are you meaning that in general you can't combine `value keywords', or
that in some cases you can and in others you can't?
Also some remarks about the manual: since it is intended as reference
manual, it should facilitate quick lookup and not require close
reading of an entire chapter.
For quickly locating examples, the side-by-side display of code and
their output as in the LaTeX books (Lamport and the LaTeX companion)
could be very effective.
Different settings for some typographic parameters would also help:
-> Reserving vertical space only for displayed material and for
sectioning. Using it to separate paragraphs detracts too much from
its effectiveness in making displayed material stand out.
-> Indenting of displayed material. The measure of the manual is wide
enough for it. In general, indenting is overused in TeX manuscripts,
and in a multicolumn layout indenting it can look very awful very
quickly but that is no reason not to use it at all.
Siep
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: notation, manual
2000-08-12 10:09 notation, manual siepo
@ 2000-08-12 10:29 ` Berend de Boer
2000-08-12 12:05 ` manual siepo
0 siblings, 1 reply; 7+ messages in thread
From: Berend de Boer @ 2000-08-12 10:29 UTC (permalink / raw)
Cc: ntg-context
siepo@client44-3.kabelA.oprit.rug.nl wrote:
> (sorry Berend, het vorige bericht aan jou was voor de lijst bedoeld;
> dit is een uitgebreidere versie ervan)
Yes, I also hate it that reply replies to the sender instead of the
list. That doesn't facilitate list communication.
> Are you meaning that in general you can't combine `value keywords', or
> that in some cases you can and in others you can't?
Exactly.
> Also some remarks about the manual: since it is intended as reference
> manual, it should facilitate quick lookup and not require close
> reading of an entire chapter.
Hmm, I find it served its purpose. But I agree that we can have more
manuals, one with lots of examples would be nice. Usually I test with a
small test file or look in the source of the manual is not clear, but
usually the manual is clear enough. Perhaps you need to get adjusted to
its style.
Groetjes,
Berend. (-:
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: manual
2000-08-12 10:29 ` Berend de Boer
@ 2000-08-12 12:05 ` siepo
0 siblings, 0 replies; 7+ messages in thread
From: siepo @ 2000-08-12 12:05 UTC (permalink / raw)
Berend de Boer writes:
>
> > Also some remarks about the manual: since it is intended as reference
> > manual, it should facilitate quick lookup and not require close
> > reading of an entire chapter.
>
> Hmm, I find it served its purpose. But I agree that we can have more
> manuals, one with lots of examples would be nice. Usually I test with a
> small test file or look in the source of the manual is not clear, but
> usually the manual is clear enough. Perhaps you need to get adjusted to
> its style.
>
> Groetjes,
>
> Berend. (-:
Yes, I also write small testfiles when the meaning of the manual is
not clear. But when it is necessary to look at the source then there
is clearly something wrong. Especially since Context has pretensions
to user-friendliness that LaTeX doesn't have.
I suspect that the manual fares better for continuous reading than for
lookup. The suggested typographic changes are intended to make lookup
more efficient.
Siep
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2013-04-03 10:06 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-03-10 18:29 Manual Jeffrey Drake
2006-03-10 23:32 ` Manual John R. Culleton
2006-03-13 22:52 ` Manual or Book Geert Stappers
2006-03-13 23:05 ` Steve Peter
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 9:57 manual Meer H. van der
2013-04-03 10:06 ` manual Marco Patzer
2000-08-12 10:09 notation, manual siepo
2000-08-12 10:29 ` Berend de Boer
2000-08-12 12:05 ` manual siepo
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).