beginner's questions

beginner's questions

[Wouter Verheijen]

Hi,

I am trying context at the moment, after experimenting somewhat with
LaTeX.
- Although I am Dutch, I have no problem at all with using the English
  words (e.g. \starttext instead of \starttekst).  I think this way, I
  can avoid language conflicts.  Do the Dutch people agree or is it
  normal to use the dutch words.  Most of my texts are in Dutch, so
  the spelling and hypenating language should remain Dutch.
  I did texexec --make en, but my standard language interface is still
  nl. It only works with texexec --int=en. How do I specify the
  default?

- The DVI files produced with context show up completely blank in
  KDVI. They do work in Xdvi, and my Latex files always worked in Kdvi
  as well. Who's to blame?

- Most of the work I plan to make with context are small (<20pages)
  reports. Mostly text with some tables and pictures, and a few
  graphs. Is context the program to handle this, or should I choose
  latex? After a quick look at the docs, it seems context is easier to
  do most things. Is this correct?

Thanks for your opinions!

-- 
Wouter Verheijen
wouter.verheijen@worldmail.nl

Re: beginner's questions

[Frans Goddijn]

Hi Wouter,

welcome to the world of ConTeXt!

>   can avoid language conflicts.  Do the Dutch people agree or
is it
>   normal to use the dutch words.

I don't think it matters much. I started in Dutch and I'm
confident that any new feature will be available in Dutch as well
as in other languages. I do not exchange source texts with
english language people at present so I don't need the english
option. And if I get an english source file I can still run it.

> - Most of the work I plan to make with context are small
(<20pages)
>   reports. Mostly text with some tables and pictures, and a few
>   graphs. Is context the program to handle this, or should I
choose
>   latex? After a quick look at the docs, it seems context is
easier to
>   do most things. Is this correct?

Especially if you start out, ConTeXt is the way to go today, I
think.

Even if you produce relatively simple documents today, eventually
you will want to add some new subtleties or complications to make
your docs just that bit better looking, or more portable, or
interactive. With LaTeX that makes you dependent on a series of
style-file-authors who don't usually communicate to keep their
joint maze of new commands non-conflicting.

This didn't bother me in the past but if I could do it all over
gain, and ConteXt was where it is now in say 1993, I'd have been
a ConTeXt user all along. LaTeX and its myriad clever plug-in
styles was way ahead of the rest some years back, but I think
that has changed now.

If you use ConTeXt and keep yourself updated, you are almost
automatically right there at the cutting edge of TeX typesetting.

That's fun and thrilling, plus you create fine documents, which
is what we all started out to do.

Enjoy!

Frans

frans@goddijn.com   www.goddijn.com
tel NL 0621-815 881   fax: 026-3211759
Postbus 30196      6803 AD  Arnhem NL

Re: beginner's questions

[Hans Hagen]

At 06:20 PM 11/9/00 +0100, Frans Goddijn wrote:

>I don't think it matters much. I started in Dutch and I'm
>confident that any new feature will be available in Dutch as well
>as in other languages. I do not exchange source texts with

that's true, since i use dutch -) as well as that the underlying code is
the same for all interfaces; interfaces are just translation lists 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: beginner's questions

[Hans Hagen]

At 05:51 PM 11/9/00 +0100, Wouter Verheijen wrote:
>Hi,

>- Although I am Dutch, I have no problem at all with using the English
>  words (e.g. \starttext instead of \starttekst).  I think this way, I
>  can avoid language conflicts.  Do the Dutch people agree or is it
>  normal to use the dutch words.  Most of my texts are in Dutch, so

I mostly use dutch for dutch projects and english for english documents.
Especially when you start defining your own structuring it makes more sense
to talk about vragen en antwoorden dan questions and answers etc. 

>  the spelling and hypenating language should remain Dutch.

\mainlanguage[nl]

>  I did texexec --make en, but my standard language interface is still
>  nl. It only works with texexec --int=en. How do I specify the
>  default?

you can add a first line to your file

% interface=en 

When you use english commands, texexec will recognize the doc as having an
enmglish interface, unless the doc is so small that there is nothing to
determine. You can also specify the default interface in texexec.ini

>- The DVI files produced with context show up completely blank in
>  KDVI. They do work in Xdvi, and my Latex files always worked in Kdvi
>  as well. Who's to blame?

You probably don't have any output or maybe you generated pdf output? 

>- Most of the work I plan to make with context are small (<20pages)
>  reports. Mostly text with some tables and pictures, and a few
>  graphs. Is context the program to handle this, or should I choose
>  latex? After a quick look at the docs, it seems context is easier to
>  do most things. Is this correct?

that's for others to answer -) 

Hans

PS. Next month the NTG will organize a context course. 
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: beginner's questions

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> >- Most of the work I plan to make with context are small (<20pages)
> >  reports. Mostly text with some tables and pictures, and a few
> >  graphs. Is context the program to handle this, or should I choose
> >  latex? After a quick look at the docs, it seems context is easier to
> >  do most things. Is this correct?
> 
> that's for others to answer -) 

The possible conditions for choosing LaTeX over ConTeXt that come to
mind are these:

  * if your publisher requires it

  * if you must collaborate with latex users on a document

  * if you do no unusual documents, only math papers and physics
    papers (then you won't notice the incompatibilities and
    limitations as much)

... but then again, there are a lot of LaTeX features that I don't
use, since I only produce English-language documents, so I don't know
about much of the LaTeX world.  But from what I've heard here, ConTeXt
is happy being multi-lingual, and I wouldn't guess that LaTeX has an
advantage.

But using ConTeXt is much more fun.  When I ask, "can I do this?" the
answer is "Yes."  With LaTeX the answer was often, "No."

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: beginner's questions

[siepo]

On  9 Nov, Ed L Cashin wrote:
> Hans Hagen <pragma@wxs.nl> writes:
> 
>> >- Most of the work I plan to make with context are small (<20pages)
>> >  reports. Mostly text with some tables and pictures, and a few
>> >  graphs. Is context the program to handle this, or should I choose
>> >  latex? After a quick look at the docs, it seems context is easier
>> >  to do most things. Is this correct?
>> 
>> that's for others to answer -) 
> 
> The possible conditions for choosing LaTeX over ConTeXt that come to
> mind are these:
> 
>   * if your publisher requires it
> 
>   * if you must collaborate with latex users on a document
> 
>   * if you do no unusual documents, only math papers and physics
>     papers (then you won't notice the incompatibilities and
>     limitations as much)
> 
> ... but then again, there are a lot of LaTeX features that I don't
> use, since I only produce English-language documents, so I don't know
> about much of the LaTeX world.  But from what I've heard here, ConTeXt
> is happy being multi-lingual, and I wouldn't guess that LaTeX has an
> advantage.
> 
> But using ConTeXt is much more fun.  When I ask, "can I do this?" the
> answer is "Yes."  With LaTeX the answer was often, "No."

A dissenting voice: I don't think Context is easier than LaTeX. One
stumbling block is the documentation - there is a lot of it, but I find
it hard to find my way around in it - another is the sheer mass of
Context, which makes it hard to find things and to debug problems.
Debugging is hampered even more by the multilingual interface and by all
the internal space-eating dummy parameters.

In practice, I need to write just as much plain TeX with Context as with
LaTeX, and I need to ask a lot more questions in order to get the job
done. And in Context I encounter just as many mysterious goings-on as in
LaTeX.

I use Context when I have to, but in general I much prefer LaTeX.

Two things in favour of Context: other than LaTeX, it is capable of
producing a tight column layout. Also, Hans is very responsive and
helpful when you have a problem.

-- 
Siep Kroonenberg

Re: beginner's questions

[Frans Goddijn]

> A dissenting voice: I don't think Context is easier than LaTeX.
One
> stumbling block is the documentation - there is a lot of it,
but I find

Quite tolerable voice ;-)) I agree insofar as I have to get used
to the documentation and often things look so simple that I see
right through the transparancy and make things unnecessarily
complicated for myself. If I get something to work and I show my
source file to Hans, he shows me that the same can be done with
90% less effort.

I wish I could order The ConTeXt manual somewhere, finished,
complete, with examples, nicely bound ;-)) But we have to wait
until it's finished and it seems there's a race going on: ConTeXt
gets new features, calling for an update on the manual and while
the manual gets updates, nearing the End, ConTeXt gets more new
features documented in an exciting sub-manual which will
eventually be inserted in the Big Manual...

> Two things in favour of Context: other than LaTeX, it is
capable of
> producing a tight column layout. Also, Hans is very responsive
and
> helpful when you have a problem.

Which makes it fun to use, and this forum is very much alive with
people doing new things. I can't say I can follow all the codings
at all that I see passing and I call myself lucky for not needing
to be on the cutting edge ;-}}

Groet!

Frans

Re: beginner's questions

[Christopher Tipper]

Frans Goddijn writes 11-11-2000:

> I wish I could order The ConTeXt manual somewhere, finished,
> complete, with examples, nicely bound ;-)) But we have to wait

I too like nicely bound books, but I find that I have been using Context for nearly a year and I've never had to print anything. This says a lot about Hans' design efforts as much as the PDF features. The only manual I have had problems navigating is the Beginners Manual, compounded by the fact that page numbers are not aligned with the PDF.

Also the fact that the manuals are not finished is good as well as bad. OK, so we don't have everything at our finger tips, but Hans is the only tech support guy I know who will 'rewrite' the software if we have a problem. He doesn't get enough thanks to be honest, but I'm sure the VCs will be knocking soon! :-) 

Hopefully, eventually the package will stabilise, but I don't think Adobe have finished designing PDF, so it is too much to hope that we have all the features 'right-now'. And lets not forget to give credit to the module authors. Taco has done some fine stuff with the m-bib module, and with this addition Context becomes a complete replacement for latex with many of the desirable features of plain-TeX thrown in in a nicely abstracted way. Thank you!

Best wishes,
Christopher

Re: beginner's questions

[Berend de Boer]

siepo@client44-3.kabelA.oprit.rug.nl wrote:

> A dissenting voice: I don't think Context is easier than LaTeX. 

Hai Siep,

How many years of LaTeX experience do you have?

> One
> stumbling block is the documentation - there is a lot of it, but I find
> it hard to find my way around in it - 

I can't believe the latex docs are better. And consistency across the
(docs of the) many packages??

But could you be a bit more specific about "hard to find my way around
it." Because that is at least true for one person in this world, and if
there is one there are more. So if you can (try to) formulate what kind
of documentation would have helped you, perhaps this situation can be
improved.

Groetjes,

Berend. (-:

Re: beginner's questions

[siepo]

On 11 Nov, Berend de Boer wrote:
> siepo@client44-3.kabelA.oprit.rug.nl wrote:
> 
>> A dissenting voice: I don't think Context is easier than LaTeX. 
> 
> Hai Siep,
> 
> How many years of LaTeX experience do you have?

In my first year with LaTeX, I designed a custom stylefile, even without
the benefit of the LaTeX Companion.

>> One
>> stumbling block is the documentation - there is a lot of it, but I
>> find it hard to find my way around in it -
> 
> I can't believe the latex docs are better. And consistency across the
> (docs of the) many packages??

Lamports book is concise and to the point. If you can't find something 
there then you can be pretty sure that it is not a built-in user-level 
command or parameter. The guides for the graphics package and the guide 
for class and package writers are models of good documentation.

> But could you be a bit more specific about "hard to find my way around
> it." Because that is at least true for one person in this world, and
> if there is one there are more. So if you can (try to) formulate what
> kind of documentation would have helped you, perhaps this situation
> can be improved.

On the other hand: my first attempt at Context stranded when I tried to
figure out from the beginners manual how to include a figure. When I got
my hands on the regular manual, I had high hopes that now I would have
formal and complete documentation. However, nothing could be further
from the truth: time and again, documentation on parameters is
incomplete. Try to figure out from the official documentation how to set
linespacing for a fontsize. Recall also our discussion on this list on
the syntax of parameter values.

My second attempt at Context stranded due to competing demands on my
time. My third attempt resulted in a set of very basic sample files
(www.pragma-ade.com/pragma-ade/third/siep/samples.zip). It required
quite a bit of correspondence with Hans to complete this set, and I left
various issues unsolved because I was not working towards a specific
layout.

Nowadays, when I am working on existing Context code, with the sources,
the manual, the texshow utility and tons of testfiles all at hand, I
only need to ask Taco every other time how something is supposed to work
in Context.

One problem with the documentation is its informality: it presents
commands and a sometimes incomplete list of parameters. Instead of a
description of all parameters, there is only a series of examples, which
typically don't include the feature I am looking for.

Other problems are really problems of Context itself: there is more of
it than can be documented in a finite amount of time, and some things
are oddly named (e.g. right- and left alignment) or oddly organized
(e.g. you need to define some aspects of page layout via the
\setuppagenumbering macro).

> Groetjes,
> 
> Berend. (-:
> 

Siep

Re: beginner's questions

[Denis B. Roegel]

`siepo@client44-3.kabelA.oprit.rug.nl' wrote
>   
>   On 11 Nov, Berend de Boer wrote:
>   > siepo@client44-3.kabelA.oprit.rug.nl wrote:
>   > 
>   >> A dissenting voice: I don't think Context is easier than LaTeX. 
>   > 
>   > Hai Siep,
>   > 
>   > How many years of LaTeX experience do you have?
>   
>   In my first year with LaTeX, I designed a custom stylefile, even without
>   the benefit of the LaTeX Companion.
>   
>   >> One
>   >> stumbling block is the documentation - there is a lot of it, but I
>   >> find it hard to find my way around in it -
>   > 
>   > I can't believe the latex docs are better. And consistency across the
>   > (docs of the) many packages??

I am certainly not the right person to comment on this,
as I have 9 years of experience with tex (& latex, mf, etc.),
6 or 7 years with mpost, and very little with context (of which I have
only the knowledge found in the metafun manual), but the main thing
that annoyed me was the sometimes lack of clear diagnostic
in case of errors (either in my installation or in what I typed,
see the series of messages I sent recently). This of course is
made more difficult by the fact that context is evolving,
since one can make a mistake when updating his/her installation.
But I am confident many or all of these problems will vanish
eventually.

It must also be said that the quality of context is quite
stunning, given that it is used by a very small number of (free) people.
But there may be many people who use it through pragma, and I guess
they helped shape context into what it has become. And the fact
that people are paid for it has certainly something to do with it.

Denis Roegel

Re: beginner's questions

[Hans Hagen]

At 07:56 PM 11/12/00 +0100, Denis B. Roegel wrote:

>only the knowledge found in the metafun manual), but the main thing
>that annoyed me was the sometimes lack of clear diagnostic
>in case of errors (either in my installation or in what I typed,

Diagnostics are very hard to implement in a macro language like tex,
especially since error recovery is nearly impossible. However, when someone
finds a place where a status message can help, please let me know and I'll
add it. 

There are a few low level tracing options, but so far they have not yet be
documented. Tracing of key/value handling is very time and memory demanding
but can make it into future versions. 

>see the series of messages I sent recently). This of course is
>made more difficult by the fact that context is evolving,
>since one can make a mistake when updating his/her installation.

I must admit that bringing new features into the open is quite dangerous.
Although the basics of metapost inclusion are there for some time now, the
new features are new indeed, and therefore kind of beta. This is
complicated by the fact that support for mp in tex distributions is nearly
nil, so there texexec cum suis have to handle it all.  

>But I am confident many or all of these problems will vanish
>eventually.

With the help/input of users they will eventually vanish. Keep in mind that
it is not always easy to foresee what users do on their systems, and
although texmf tree's are more and more standardized, differences remain.
Fonts for instance will always be kind of messy.    

>It must also be said that the quality of context is quite
>stunning, given that it is used by a very small number of (free) people.
>But there may be many people who use it through pragma, and I guess
>they helped shape context into what it has become. And the fact
>that people are paid for it has certainly something to do with it.

A bit of history: 

- Pragma is currently two people; we hire hands when needed, and have an
association with an it-company.

- We originate in educational technology, and we may safely assume that
people working for us have no computer skils as demanded by tex. 

- When we started using tex, we looked into latex first [actually, we
bought it from aw] and since we wanted dutch labels and so we ended up in
kind of messy and not-understood patches. So we started writing a small
wrapper [not even knowning what macros actually were]

- Before we made the definitive decission, we looked into professional
publishing systems, but finally decided to go on with tex. 

- Since we had to pay for updates and even hyphenation patterns [indeed, we
were not on any internet] we looked into other tex macro packages, like
amstex, lamstex an inrstex. I think that we spend some thousands of
guilders on bying licences and manuals. 

- Lamstex looked very promissing, and I never understood why this more
configurable latex alternative never made it [i must have a few manuals
somewhere]. We used it a couple of month, after which we switched to
inrstex. This latter package had pretty good defaults, and was quite
configurable. Some of the context defaults stem from inrstex. 

- When writing educational material [which in many aspects can have quite
complicated typo] we wanted to have more control over structure and
automate as much as possible. 

- The basic idea is: no manual intervention, so 'no user supplied vskips'
and 'no manual page breaks'. A lot of effort went into spacing, and we're
still improving that bit. Another idea is abstraction, which is why right
from the start there were mechanisms for abbreviations and block reuse.

- This means that for using context to the full extend, you have to start
from scratch. Think of what you need [which will happen when you key in the
same thing for the tenth time] and look if there is an easy way. This is
how context evolved: people coming to me and asking for simple less time
consuming methods. The first users were those who never \def'ed a macro,
didn't know anything about fonts etc.  

- When context went public, and when this list was started, people started
asking for features. Given that we need context for rather complicated
documents, you may assume that there are more features than currently
covered in the manual. Many of them are still in development, so I can
choose: either say 'it can't be done' or just reveal the details. I've
chosen for the latter at teh cost of complaints about lack of documentation.  

- There is only a limited amount of functionality that can be hard coded.
This is why there are hooks. There are for instance some 10 table of
content configs, but one can implement his/her own. Experienced tex users
will do so, but at the same time will have the automatisms available deep
down. [Believe me, there are gory details no sound person wants to know, i
may describe them in more fundamental discussions about functionality.]  

- The multi lingual user interface is there for a good reason: non
technical users. We want to be be able to assign tasks with regards to
entering tex documents [and even changing layout specs] to virtually
everyone, but especially people with no math / tex / computer background.   

- Documentation is an ongoing process. When working on the ref manual [the
new one] i decided to split off metapost graphic in a separate manual. I
will do the same with interactive documents, which will be combined with
designing layouts, since thiose layouts are the most demanding. The ref
manual will then only cover the basics. The complete interface will be
covered in the interface documentation.  

- One problem that people will encounter when using context aside latex or
any tex, is that they need to forget things. As soon as you start looking
for similar things, you will not easilly find them. The reason is that
stucturing documents is the starting point and not so much designing them.
Here we use context for collections of [often large] educational documents,
and there we want for instance a 500 page document with 400 figures to be
processed without any manual intervention in often more than one
incarnation. Or, a collection of quality assurance manual, made up out of a
multitude of procedures, with flow charts and so, with extensive cross
referencing, tocs at every level, a high level of data abstraction [no
name, function, number or id is coded more than once]. Or, a recently
started project, a math school method to be developped by a team of
teachers, with a broad range of products, and therefore extensive reuse of
resources. Most of the context features deal with those issues and in
detail typo control [which for instance siep wants] is actually the second
agenda. This control also depends on the level of module documentation. For
instance, core-rul, is a good example of a finished and stable module,
which in my opinion is also documented in an acceptable way. On the other
hand, the otr, output routine and spacing engine, is still not fully
finished and documented. It will be since i;m working on it now. As an
example, i just implemented, willy egger may like that, multi column spread
control, with page imposition support for figures or whatever spanning a
page and so. Now this is no easy topic and will never be, even if i write
500 pages about it. -) 

- Whatever is implemented, using tex (context) as a dtp system is always
complicated. No matter how many hooks are provided.  

- So, don't consider context finished yet, but you may enjoy [or hate] it
nevertheless,  

Hans    
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

...
> As an example, i just implemented, willy egger may like that, multi
> column spread control, with page imposition support for figures or
> whatever spanning a page and so. Now this is no easy topic and will
> never be, even if i write 500 pages about it. -)

By multi-column spread control do you mean the ability to have
balanced columns?

There is an issue in one of the documents that my employer wants me to
do (but they keep pulling me off the job) where there is a series of
vboxes in a two-column page.

In order for the columns to balance (i.e. have the baselines of their
bottom lines line up perfectly) the glue between the vboxes has to be
balanced in a sophisticated way.  

It's been a while since I've worked on it, but here's an example:

\setupbodyfont	[9pt]
\setupcolumns	[balance=yes]
\showmakeup

\def\myText{Maggie comes fleet foot
   	    face full of black soot
   	    talkin' that the heat put
   	    plants in the bed but
   	    the phone's tapped anyway
   	    Maggie says that many say
   	    they must bust in early May ---
   	    orders from the D. A.}
% plenty of stretch
\def\interGlue{\vskip 1ex plus 4cm minus .1ex}

\starttext
\startcolumns[n=2]
\dorecurse{7}{\vbox{\myText}\interGlue}
\stopcolumns

\blank[2*big]

\startcolumns[n=3]
\dorecurse{7}{\vbox{\myText}\interGlue}
\stopcolumns

\stoptext

... since there's lots of stretchability in the interGlue, and the
columns are set to balance, I'd expect the glue between the boxes to
stretch such that the columns were balanced.  

I know that this is a hard problem, and so I'm just wondering if
that's what you meant by spread control.

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 11:54 AM 11/13/00 -0500, Ed L Cashin wrote:

>By multi-column spread control do you mean the ability to have
>balanced columns?

No, a spread is something that crosses a page, so a figure or title that
spans a left and right page. I'll send you a sample. 

>In order for the columns to balance (i.e. have the baselines of their
>bottom lines line up perfectly) the glue between the vboxes has to be
>balanced in a sophisticated way.  

That's called snapping. 

\starttext

\setuplayout[grid=yes] \showgrid

\setupbodyfont[9pt]

\def\myText
  {\strut Maggie comes fleet foot face full of black soot
   talkin' that the heat put plants in the bed but the phone's
   tapped anyway Maggie says that many say they must bust in
   early May --- orders from the D. A.\strut}

\startcolumns[n=2]
  \dorecurse{7}{\snaptogrid\vbox{\myText}\blank}
\stopcolumns

\blank[2*big]

\startcolumns[n=3]
  \dorecurse{7}{\snaptogrid\vbox{\myText}\blank}
\stopcolumns

\stoptext

>I know that this is a hard problem, and so I'm just wondering if
>that's what you meant by spread control.

Actually it's not that hard, but since context tries hard to snap, it is
hard to convince it to do otherwise. What i'm currently doing is isolating
the otr code into modules. There will be a series of basic otr's like:
single column, mixed single multi, and multi, plus a mechanism to implement
your own as well as communicate with the otr. The new multi routine will
give quite some control over float placement and other trickery. It is a
combination of all kind of code snippets and ideas I collected over the
past years, so i can finally clean up my machine -) 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> At 11:54 AM 11/13/00 -0500, Ed L Cashin wrote:
...
> >In order for the columns to balance (i.e. have the baselines of their
> >bottom lines line up perfectly) the glue between the vboxes has to be
> >balanced in a sophisticated way.  
> 
> That's called snapping. 

Snapping makes the boxes line up, but I'm talking about something
different: getting the bottoms of the columns to line up.  

When I compile the example you sent I see this kind of thing:

     ------------------
     | xxxxxx  xxxxxx |
     | xxxxxx  xxxxxx | 
     |                |
     | xxxxxx  xxxxxx | 
     | xxxxxx  xxxxxx | 
     |                |
     | xxxxxx         |
     | xxxxxx         |
     ------------------

The boxes line up, but I am not trying to get the boxes to line up,
just the bottoms of the columns, like this:

     ------------------
     | xxxxxx  xxxxxx |
     | xxxxxx  xxxxxx | 
     |                |
     | xxxxxx         |
     | xxxxxx         |
     |                |
     | xxxxxx  xxxxxx | 
     | xxxxxx  xxxxxx | 
     ------------------

In this example, it's very ugly, but the point is that the bottoms of
the columns line up.  They can line up because I've made the glue
between the vboxes very stretchable.  

Although the ASCII diagram doesn't show it, the vertical size of the
boxes may change from box to box.

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> Actually it's not that hard, but since context tries hard to snap,
> it is hard to convince it to do otherwise. What i'm currently doing
> is isolating the otr code into modules. There will be a series of
> basic otr's like: single column, mixed single multi, and multi, plus
> a mechanism to implement your own as well as communicate with the
> otr. The new multi routine will give quite some control over float
> placement and other trickery. It is a combination of all kind of
> code snippets and ideas I collected over the past years, so i can
> finally clean up my machine -)

That sounds interesting.  What's an otr?  :)

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 01:44 PM 11/13/00 -0500, Ed L Cashin wrote:
>Hans Hagen <pragma@wxs.nl> writes:

>That sounds interesting.  What's an otr?  :)

an output routine, when tex has collected enough content to fit in the
page, or when explicitly asked for, tex will invoke the otr, which then is
supposed to do something with the collected content, like wrapping it up
and shipping it out; the call is actually an expansion of the token list
\output. 

\output
  {\shipout\vbox
     {\ruledhbox{Hi Ed}
      \ruledvbox{\box255}
      \ruledhbox{Do You Get it?}}}

\input tufte

Normally you want to stay far away from this, since misuse may spoil all
housekeeping. 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> At 01:44 PM 11/13/00 -0500, Ed L Cashin wrote:
> >Hans Hagen <pragma@wxs.nl> writes:
> 
> >That sounds interesting.  What's an otr?  :)
> 
> an output routine, when tex has collected enough content to fit in the
> page, or when explicitly asked for, tex will invoke the otr, which then is
> supposed to do something with the collected content, like wrapping it up
> and shipping it out; the call is actually an expansion of the token list
> \output. 
> 
> \output
>   {\shipout\vbox
>      {\ruledhbox{Hi Ed}
>       \ruledvbox{\box255}
>       \ruledhbox{Do You Get it?}}}

Um, the \output command sets up a handler, and box255 contains the
finished page that tex is "shipping out"?  Yes, after looking at p.125
of the TeXbook, I see that's it.

> \input tufte
> 
> Normally you want to stay far away from this, since misuse may spoil all
> housekeeping. 

Columns are always done this way though, right?  (Usually by a
macropackage.) 

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 08:27 AM 11/14/00 -0500, Ed L Cashin wrote:
>Hans Hagen <pragma@wxs.nl> writes:
>
>> At 01:44 PM 11/13/00 -0500, Ed L Cashin wrote:
>> >Hans Hagen <pragma@wxs.nl> writes:
>> 
>> >That sounds interesting.  What's an otr?  :)
>> 
>> an output routine, when tex has collected enough content to fit in the
>> page, or when explicitly asked for, tex will invoke the otr, which then is
>> supposed to do something with the collected content, like wrapping it up
>> and shipping it out; the call is actually an expansion of the token list
>> \output. 
>> 
>> \output
>>   {\shipout\vbox
>>      {\ruledhbox{Hi Ed}
>>       \ruledvbox{\box255}
>>       \ruledhbox{Do You Get it?}}}
>
>Um, the \output command sets up a handler, and box255 contains the
>finished page that tex is "shipping out"?  Yes, after looking at p.125
>of the TeXbook, I see that's it.
>
>> \input tufte
>> 
>> Normally you want to stay far away from this, since misuse may spoil all
>> housekeeping. 
>
>Columns are always done this way though, right?  (Usually by a
>macropackage.) 

Kind of, either by multiple output per page or by making a page n times as
high as possible and then splitting. A painful programming process,
especially if you want spacing okey. 

\input tufte 

\startcolumns
\input tufte 
\stopcolumns 

\input tufte 

is far from trivial.

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> Kind of, either by multiple output per page or by making a page n times as
> high as possible and then splitting. A painful programming process,
> especially if you want spacing okey. 
> 
> \input tufte 
> 
> \startcolumns
> \input tufte 
> \stopcolumns 
> 
> \input tufte 
> 
> is far from trivial.

Yes, I remember you saying that.  Is the problem with balancing
columns something like this:

given a sequence of vboxes and vglue with infinite stretchability,
arrange the little vboxes into two big vboxes such that ...

        - the two big vboxes have equal height

        - the following distance must be the same for the two big
          vboxes: the distance from the top of the big vbox to the
          bottom of the last little vbox in the big vbox

So the trick is to do something like what tex does with pagination,
but I don't know what that is ... maybe ...

        put as many little vboxes into big vbox 1 as will fit

        discard glue after the last little vbox in big vbox 1

        put as many little vboxes into big vbox 2 as will fit

        discard glue after the last little vbox in big vbox 2

        evaluate for penalty and re-try if necessary

The glue between the little vboxes in each big vbox will expand, and
the bottoms of the columns (big vboxes) will certainly align.

Is that the kind of problem it is?

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 09:49 AM 11/14/00 -0500, Ed L Cashin wrote:
>Hans Hagen <pragma@wxs.nl> writes:
>
>> Kind of, either by multiple output per page or by making a page n times as
>> high as possible and then splitting. A painful programming process,
>> especially if you want spacing okey. 
>> 
>> \input tufte 
>> 
>> \startcolumns
>> \input tufte 
>> \stopcolumns 
>> 
>> \input tufte 
>> 
>> is far from trivial.
>
>Yes, I remember you saying that.  Is the problem with balancing
>columns something like this:
>
>given a sequence of vboxes and vglue with infinite stretchability,
>arrange the little vboxes into two big vboxes such that ...
>
>        - the two big vboxes have equal height
>
>        - the following distance must be the same for the two big
>          vboxes: the distance from the top of the big vbox to the
>          bottom of the last little vbox in the big vbox
>
>So the trick is to do something like what tex does with pagination,
>but I don't know what that is ... maybe ...
>
>        put as many little vboxes into big vbox 1 as will fit
>
>        discard glue after the last little vbox in big vbox 1
>
>        put as many little vboxes into big vbox 2 as will fit
>
>        discard glue after the last little vbox in big vbox 2
>
>        evaluate for penalty and re-try if necessary
>
>The glue between the little vboxes in each big vbox will expand, and
>the bottoms of the columns (big vboxes) will certainly align.
>
>Is that the kind of problem it is?

Right, something 

\newdimen\naturalvsize \naturalvsize=10cm

\vsize=2\naturalvsize
\hsize=10cm

\def\Split%
  {\setbox0=\vsplit255 to \naturalvsize \setbox0=\vbox to
\naturalvsize{\unvbox0} % left column
   \setbox2=\vsplit255 to \naturalvsize \setbox2=\vbox to
\naturalvsize{\unvbox2} % right column 
   \shipout{\hbox{\box0\hskip1em\box2} % page 
   \unvbox255 } % leftovers

\output{\Split}

plus compensations plus test plus balancing plus nightmares 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> At 09:49 AM 11/14/00 -0500, Ed L Cashin wrote:
...
> >Is that the kind of problem it is?
> 
> Right, something 
> 
> \newdimen\naturalvsize \naturalvsize=10cm
> 
> \vsize=2\naturalvsize
> \hsize=10cm
> 
> \def\Split%
>   {\setbox0=\vsplit255 to \naturalvsize \setbox0=\vbox to
> \naturalvsize{\unvbox0} % left column
>    \setbox2=\vsplit255 to \naturalvsize \setbox2=\vbox to
> \naturalvsize{\unvbox2} % right column 
>    \shipout{\hbox{\box0\hskip1em\box2} % page 
>    \unvbox255 } % leftovers
>    
> \output{\Split}
> 
> plus compensations plus test plus balancing plus nightmares 

I reviewed vsplit in the TeXbook, and it looks like by getting very
fancy with low-level glues and penalties (like the fancy index
example, "Paragraph Manuvers", number seven in Appendix D., but
vertically instead of horizontally) one could control exactly how the
columns balanced.

But for a macropackage author like yourself, that would mean breaking
open the box255 and changing the vertical glue between the elements.
Maybe that's the kind of compensation and nightmare you're talking
about?

It's too bad there's not an easier way to do perfectly balanced
columns with metapost.  ;)

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 11:45 AM 11/14/00 -0500, Ed L Cashin wrote:

>I reviewed vsplit in the TeXbook, and it looks like by getting very
>fancy with low-level glues and penalties (like the fancy index
>example, "Paragraph Manuvers", number seven in Appendix D., but
>vertically instead of horizontally) one could control exactly how the
>columns balanced.
>
>But for a macropackage author like yourself, that would mean breaking
>open the box255 and changing the vertical glue between the elements.
>Maybe that's the kind of compensation and nightmare you're talking
>about?

Balancing is not that hard: 

loop 
  split box to height 
  if left over is larger than split off part 
  then 
   decrease height 
  else 
   exitloop
endloop

but you're right, there are a few gory details. If you want to manipulate
boxes:

  texexec --modu supp-box 

is your friend

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

>   texexec --modu supp-box 
> 
> is your friend

Thanks.  

BTW, with texexec 2.2 I notice it claims that the output was
texexec.dvi, when it was really supp-box.dvi.

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 01:25 PM 11/14/00 -0500, Ed L Cashin wrote:
>Hans Hagen <pragma@wxs.nl> writes:
>
>>   texexec --modu supp-box 
>> 
>> is your friend
>
>Thanks.  
>
>BTW, with texexec 2.2 I notice it claims that the output was
>texexec.dvi, when it was really supp-box.dvi.

If things go well, it should rename to supp-box.dvi, since texexec is uses
as temp name [so that existing tuo files are not screwed up]. 

Hans

PS Ed, I really enjoy these funny elections, makes a great television show;
how can that such a badly designed (read: non designed) election form can
be used, seems like a nice job for tex/mp  -) 
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: multi-column spread control (was Re: beginner's questions)

[Ed L Cashin]

Hans Hagen <pragma@wxs.nl> writes:

> PS Ed, I really enjoy these funny elections, makes a great
> television show; how can that such a badly designed (read: non
> designed) election form can be used, seems like a nice job for
> tex/mp -)

Yes, the voting machine that I used was quite poorly laid out.  We
should all switch to context-generated ballots.  

   ;)

Maybe the ballots would be so clear and attractive that we would have
a greater voter turnout!

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/

voting & form design (was: multi-column spread control)

[Hraban]

Ed L Cashin wrote:
> Maybe the ballots would be so clear and attractive that we would have
> a greater voter turnout!

Perhaps you could personalize them (totally anonymous, of course ;-)
with fitting ads...

But really: Form design is not an easy job!

Grüßlis vom Hraban!
---
http://angerweit.tikon.ch/lieder/
http://www.planet-interkom.de/fiee.visuelle/formelsammlung.html

Re: multi-column spread control (was Re: beginner's questions)

[Denis B. Roegel]

`Hans Hagen' wrote
>   
>     texexec --modu supp-box 
>   
>   is your friend

This doesn't produce anything here. Do I need a more recent version?
(I have the file tex/context/base/supp-box.tex)

Denis

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 10:51 PM 11/14/00 +0100, Denis B. Roegel wrote:
>`Hans Hagen' wrote
>>   
>>     texexec --modu supp-box 
>>   
>>   is your friend
>
>This doesn't produce anything here. Do I need a more recent version?
>(I have the file tex/context/base/supp-box.tex)

You need to download the cont-doc.zip file from the beta page, since you
need the documentation styles.

[--modu converts supp-box.tex into supp-box.ted and typesets the docu]

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: multi-column spread control (was Re: beginner's questions)

[Denis B. Roegel]

`Hans Hagen' wrote
>   
>   At 10:51 PM 11/14/00 +0100, Denis B. Roegel wrote:
>   >`Hans Hagen' wrote
>   >>   
>   >>     texexec --modu supp-box 
>   >>   
>   >>   is your friend
>   >
>   >This doesn't produce anything here. Do I need a more recent version?
>   >(I have the file tex/context/base/supp-box.tex)
>    
>   You need to download the cont-doc.zip file from the beta page, since you
>   need the documentation styles.
>   
>   [--modu converts supp-box.tex into supp-box.ted and typesets the docu]

Ok, I got the cont-doc.zip file, but I was able to make 
texexec --modu supp-box work only after copying supp-box.tex in the local
directory. Also, I got:

Underfull \vbox (badness 10000) detected at line 1118
[16.14] . [17.15] . . . . . [18.16] . [19.17] . . . . . . . [20.18] . . .
<texexec.tmp> (./texexec.tmp (./tufte.tex) (./knuth.tex)) [21.19] .
<texexec.tmp> (./texexec.tmp [22.20] Didn't you forget something?) . . . . .
<texexec.tmp> (./texexec.tmp) . [23.21] . . . . [24.22] . <texexec.tmp>
(./texexec.tmp
figuren        : figuur koe is niet te vinden
figuren        : figuurobject koe wordt opnieuw gebruikt
) . . [25.23] . . . . . . [26.24] . . . . . . . . [27.25] . . . . . . .
[28.26] . . . . . [29.27] . . . . <texexec.tmp> (./texexec.tmp
! Undefined control sequence.
l.1 \normbox
            [1cm][bba]{m}  % b(efore) a(fter) v(box) s(trut) f(rame)
? 
! Undefined control sequence.
l.2 \normbox
            [1cm][bba]{m}
? 
! Undefined control sequence.
l.3 \normbox
            [1cm][bba]{m}
? 
) . . [30.28]
systeem        : index niet gevonden/geplaatst
)
systems        : end file texexec at line 10
 )
Output written on texexec.dvi (30 pages, 199820 bytes).
Transcript written on texexec.log.

              run time : 137 seconds
bar sources 226 % 

------

Denis

Re: multi-column spread control (was Re: beginner's questions)

[Hans Hagen]

At 12:28 AM 11/16/00 +0100, Denis B. Roegel wrote:
> 
>Ok, I got the cont-doc.zip file, but I was able to make 
>texexec --modu supp-box work only after copying supp-box.tex in the local
>directory. Also, I got:

That's right. Documentation is generated on the local path. 

Concerning the error, it concerns docu processed while the macros are not
yet officially there. I forgot to comment the preceding %D lines. 

BTW, documentation can be produced for tex/mp/perl files that contain %D
directives. 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Documentation Tasks (was: beginner's questions)

[Hraban]

Berend de Boer wrote:
> I can't believe the latex docs are better. And consistency across the
> (docs of the) many packages??

They are better, because there are many buyable books on it,
even in german ;-)
But you are right: None of this books covers all packages,
and some packages are nearly undocumented.
But further there are more people you can ask...

> But could you be a bit more specific about "hard to find my way around
> it." Because that is at least true for one person in this world, and if
> there is one there are more. So if you can (try to) formulate what kind
> of documentation would have helped you, perhaps this situation can be
> improved.

I miss such a elaborated FAQ like the german LaTeX-FAQ, that covers 
really most questions.
I miss a table of the useable accents and symbols (math and other).
I miss german docs. (Sorry, my english is a bit poor, and complicated
matter is better to be understood without dictionary...)

I miss a how-to-use-fonts introduction for dummies. (That's a critical
point in LaTeX, too.) It should answer: What files for what type of
fonts are needed, how can I make/get them, where must they go etc.
I know that this is different on every system (and many of my problems
may be caused by my deficient knowledge of Linux/X)...

The beta manual could have hyperlinks (that would make its use easier).
Further: It lists not all options of the commands, but some are/seem 
nowhere explained. (You've to try around a while.)
Beside of these critics the beta manual is already better than many
LaTeX books! (Siep, you may like the Companion -- at least the german
translation is a bit chaotic.)

At this state I can't convince publishing professionals to work
with ConTeXt. Even if the local (La)Tex users group was excited
about the nice ConTeXt code -- they asked too much questions that
I couldn't answer or that I knew to be a problem (yet). And they
said ConTeXt would be known to be slow.

I don't only want to grumble -- I'm willing to co-work on the docs,
but I must find some time first... :-(
Thank you very much again, Hans -- I can't understand how you manage
to earn money beside all your helpful work! ;-)

Grüßlis vom Hraban!
---
http://angerweit.tikon.ch/lieder/
http://www.planet-interkom.de/fiee.visuelle/formelsammlung.html

Re: beginner's questions

[Hans Hagen]

At 06:34 PM 11/11/00 +0100, siepo@client44-3.kabelA.oprit.rug.nl wrote:

>the internal space-eating dummy parameters.

The overhead of the interface is not that large, since mapping key/values
on \cs's is rather efficient [actually this is how it started in order to
fit context in those smaller tex's]

>In practice, I need to write just as much plain TeX with Context as with
>LaTeX, and I need to ask a lot more questions in order to get the job
>done. And in Context I encounter just as many mysterious goings-on as in
>LaTeX.

That's true as soon as you want control over every aspect of the layout. I
fear that there is no way out of this, apart from providing as many hooks
as needed. 

>I use Context when I have to, but in general I much prefer LaTeX.
>
>Two things in favour of Context: other than LaTeX, it is capable of
>producing a tight column layout. Also, Hans is very responsive and

Then I hope that you will not hate the alternative multi column mechanism
I'm working on now -) 

Hans

-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Re: beginner's questions

[siepo]

On 13 Nov, Hans Hagen wrote:
> At 06:34 PM 11/11/00 +0100, siepo@client44-3.kabelA.oprit.rug.nl wrote:
> 
>>the internal space-eating dummy parameters.
> 
> The overhead of the interface is not that large, since mapping
> key/values on \cs's is rather efficient [actually this is how it
> started in order to fit context in those smaller tex's]

The point I tried to make was that it makes the internal code messier.

>>In practice, I need to write just as much plain TeX with Context as
>>with LaTeX, and I need to ask a lot more questions in order to get the
>>job done. And in Context I encounter just as many mysterious goings-on
>>as in LaTeX.
> 
> That's true as soon as you want control over every aspect of the
> layout. I fear that there is no way out of this, apart from providing
> as many hooks as needed.

The hooks are also a nice thing of Context, although it often takes
quite a bit of trial and error to make something work.

>>I use Context when I have to, but in general I much prefer LaTeX.
>>
>>Two things in favour of Context: other than LaTeX, it is capable of
>>producing a tight column layout. Also, Hans is very responsive and
> 
> Then I hope that you will not hate the alternative multi column
> mechanism I'm working on now -)

Keep your fingers crossed...

Siep

Re: beginner's questions

[Berend de Boer]

Wouter Verheijen wrote:

> - Although I am Dutch, I have no problem at all with using the English
>   words (e.g. \starttext instead of \starttekst).  I think this way, I
>   can avoid language conflicts.  Do the Dutch people agree or is it
>   normal to use the dutch words.  

I use the dutch interface for dutch documents, the english for english
documents.

> - The DVI files produced with context show up completely blank in
>   KDVI. They do work in Xdvi, and my Latex files always worked in Kdvi
>   as well. Who's to blame?

I always use DVI.

> - Most of the work I plan to make with context are small (<20pages)
>   reports. Mostly text with some tables and pictures, and a few
>   graphs. Is context the program to handle this, or should I choose
>   latex? After a quick look at the docs, it seems context is easier to
>   do most things. Is this correct?

ConTeXt has the advantage that you have everything in one package, for
LaTeX you usually need quite a few other packages 
which potentially can conflict.

Also look and feel is easier to change in ConTeXt. I seldom feel the
need to hack low level macro's :-)

Groetjes,

Berend. (-:

beginner's questions

[Michael Na Li]

I've used LaTeX for several years but am new to ConTeXt.  Here are a couple
questions I had:

1.  With m-bib module, how can I achieve \nocite{} (no citation but have the
    reference listed in the end) as in LaTeX?  

2.  Is there a command similar to \section*{} effect (no numbering of the
    section)?

Michael

Re: beginner's questions

[Michael Na Li]

>>>>> On Fri, 27 Sep 2002 14:14:05 -0700, Michael Na Li <lina@u.washington.edu> said:

Michael> 2.  Is there a command similar to \section*{} effect (no numbering of
Michael>     the section)?

Found the answer myself :).  Either use \subject or
\setuphead[section][number=no].

New questions pop up, though.  The following example doesn't work because of
the "textstyle" option (gives some cryptic error messages).  After textstyle
is removed, it does compile but the section title is not aligned to the right.
Is it because my ConTeXt (ConTeXt  ver: 2002.1.28  fmt: 2002.7.15  int:
english  mes: english) is older than the manual (the English version, just
downloaded a couple of days ago)?

===============================

\setuphead
    [section]
    [align=right,
     textstyle=cap]

\starttext

\section{a test}

Some test text.

\stoptext

================================

Cheers,

Michael

-- 
----------------------------------------------------------------------------
Michael Na Li                               
Email: lina@u.washington.edu
Department of Biostatistics, Box 357232
University of Washington, Seattle, WA 98195  
---------------------------------------------------------------------------

Re: beginner's questions

[Jens-Uwe Morawski]

On Fri, 27 Sep 2002 14:14:05 -0700
Michael Na Li <lina@u.washington.edu> wrote:

> 
> I've used LaTeX for several years but am new to ConTeXt.  Here are a couple
> questions I had:
> 
> 1.  With m-bib module, how can I achieve \nocite{} (no citation but have the
>     reference listed in the end) as in LaTeX?  

sorry, i don't know. You could limit your bib-entries to the entries
needed. Then you can set \setuppublications[criterium=all].

> 2.  Is there a command similar to \section*{} effect (no numbering of the
>     section)?

\subject

Jens

Re: beginner's questions

[Michael Na Li]

>>>>> On Sat, 28 Sep 2002 11:35:06 +0200, Jens-Uwe Morawski <morawski@gmx.net> said:
Jens-Uwe> On Fri, 27 Sep 2002 14:14:05 -0700
Jens-Uwe> Michael Na Li <lina@u.washington.edu> wrote:
>> 
>> I've used LaTeX for several years but am new to ConTeXt.  Here are a couple
>> questions I had:
>> 
>> 1.  With m-bib module, how can I achieve \nocite{} (no citation but have the
>> reference listed in the end) as in LaTeX?  

Jens-Uwe> sorry, i don't know. You could limit your bib-entries to the entries
Jens-Uwe> needed. Then you can set \setuppublications[criterium=all].

I use \setupbibtex[] (which is great since many people will probably need hang
on to their bib files) to use external bib files.  It is a lot of trouble
having to modify those bib files.

Michael

Re: beginner's questions

[Henning Hraban Ramm]

Am Freitag, 27. September 2002 23:14 schrieb Michael Na Li:
> 2.  Is there a command similar to \section*{} effect (no numbering of the
>     section)?

Look at "ms-cb-en.pdf" or the manual!
ConTeXt has different sets for numbered and unnumbered headers:
\chapter		\title
\section		\subject
\subsection	\subsubject
...			...
The unnumbered (right) doesn't show up in tocs etc.
If you need headers without numbering that show up in tocs, you need to setup 
them with e.g.
\setuphead		[chapter]
			[number=no, % no numbering 
			page=yes,	% new page at chapter
			style={\ss\bfd},	% sans serif bold
			align=right,	% left aligned(!), right means "raggedright"
			color=red]

Grüßlis vom Hraban!
-- 
http://www.fiee.net/texnique/
http://www.ramm.ch/context/
---

Re: beginner's questions

[Taco Hoekwater]

For 1., you need something like this:

\def\nocite#1{\setbox0\hbox{\cite[#1]}}

On Fri, 27 Sep 2002 14:14:05 -0700, Michael wrote:

> 
> I've used LaTeX for several years but am new to ConTeXt.  Here are a couple
> questions I had:
> 
> 1.  With m-bib module, how can I achieve \nocite{} (no citation but have the
>     reference listed in the end) as in LaTeX?  
> 
> 2.  Is there a command similar to \section*{} effect (no numbering of the
>     section)?
> 
> Michael

-- 
groeten,

Taco