ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "R. Bastian" <rbastian@free.fr>
To: ntg-context@ntg.nl
Subject: Re: Thoughts on ConTeXt: ditched
Date: Mon, 28 Dec 2009 13:36:57 +0100	[thread overview]
Message-ID: <20091228133657.73f7dd4c@KUBUNTU64> (raw)
In-Reply-To: <4B378347.8020700@gmail.com>

On Sun, 27 Dec 2009 16:54:47 +0100
"Manuel P." <ayeye.sysforge@gmail.com> scribit:

> ConTeXt is a good software. I was impressed with a manual typesetted [...]
 
I also

> 
> ConTeXt is beautiful because it's very configurable, [...]
 
Yes

> 
> I've had some unpleasant surprises:
> - Bibliography doesn't work the way it should

It is not a good idea to use no-languages (TeX, LaTeX & friends) for
bibliography. Write the biblio and your source text
in your own format and use a true language 
(Python, C, Pascal, Python, ...) to translate the brute source (with refs) 
and the biblio base to a typesetter code (TeX or ConText).

The last days I had to edit Python-listings (my scores).
\starttyping ... \stoptyping. Fine! but there are no headers. But I need
headers. Not easy to understand \setupheads, \setupheaders \setupheader etc.
there are no examples given.

I re-tried reSt, asciidoc : ugly like Latex.

So I wrote a Python-script which reads the Python-score and writes a
plain tex file (merci Raymond Seroul et le "Petit livre de TeX" ;-).

Nevertheless, ConText beeing the best choice, I am volunteer to help
for _french_ (and german) wiki pages in the contextgarden.

[...]
> 
> -- 
> Manuel P.
> 


-- 
René Bastian
www.pythoneon.org
www.musiques-rb.org


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


      parent reply	other threads:[~2009-12-28 12:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-27 15:54 Manuel P.
2009-12-27 18:41 ` Wolfgang Schuster
2009-12-28 13:44   ` Manuel P.
2009-12-28 15:12     ` Khaled Hosny
2009-12-28 17:59     ` Hans Hagen
2009-12-29 12:48       ` Manuel P.
2009-12-29  2:48     ` berend
2009-12-29 12:57       ` Manuel P.
2010-01-03 18:45         ` Piotr Kopszak
2010-01-04 21:46           ` Manuel P.
2009-12-27 19:16 ` Peter Münster
2009-12-27 21:11   ` Hans Hagen
2009-12-28 13:48   ` Manuel P.
2009-12-28 17:19     ` Peter Münster
2009-12-28 11:30 ` Gour
2009-12-28 12:36 ` R. Bastian [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091228133657.73f7dd4c@KUBUNTU64 \
    --to=rbastian@free.fr \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).