ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henry House <hajhouse@hajhouse.org>
To: ntg-context@ntg.nl
Subject: Re: Ideas for restructuring the ConTeXt garden?
Date: Sat, 12 Mar 2011 15:35:54 -0800	[thread overview]
Message-ID: <20110312233554.GB25891@houseag.com> (raw)

Procházka Lukáš wrote:
[...]
> > 5) how to better promote context to new/latex users?
> 
> For LaTeX incomers: it would be good to provide a sample setup (module?) which would make Ctx generated .pdf looking very closely to that been generated by LaTeX.
> 
> Now, if you see a .pdf document and you are familiar with LaTeX, you recognize immediately whether or not it was generated by LaTeX (Word's signature is also unmatchable).
> 
> If you create a first document with ConTeXt (moreover when migrating from LaTeX), you probably won't be satisfied with the default look (letters too big, heads not bold, spacing before/after heads too different from LaTeX's; and the LaTeX default document looks very "symphonic" in my opinion) (but also I can imagine that many Ctx defaults cannot be changed due to backward compatibility reasons).
> 
> The perfect feature of ConTeXt is that all these features may be systematically altered (often [almost] impossible in LaTeX) but you must search enough and study (and maybe ask the forum) to get the result which would fulfil your aesthetic requirements.

I strongly agree that sample set-up code (ideally well-commented so that
it also serves as a tutorial of sorts) to reproduce the style of LaTeX
would be helpful. The appearance of LaTeX documents isn't perfect but it
produces reasonably high-quality results suitable for complex technical
documents right out of the box of the box without any tweaking, whereas
ConTeXt requires (at least it did for me) some trouble to set it up for
the first time. To some extent this is not because of the merit of the
LaTeX design itself but the fact that it is familiar and therefore
highly readable to someone used to reading it. It is also the point of
departure for a LaTeX user wanting to convert to using ConTeXt; hence, i
would imagine many such people would prefer to tweak a LaTeX-like
document appearance to better suit their needs rather than starting with
something quite different. Certainly, this was the case for me; being
basically satisfied with my LaTeX documents but wanting more control and
the option to use the advanced features of ConTeXt. Having sample set-up
code that emulated LaTeX would have eased the initial transition for me.
___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2011-03-12 23:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 23:35 Henry House [this message]
2011-03-13  7:54 ` Taco Hoekwater
2011-03-13  9:00 ` Thomas Schmitz
2011-03-13 11:43 ` "latex style" (was : Re: Ideas for restructuring the ConTeXt garden?) Peter Münster
2011-03-13 20:34 ` Ideas for restructuring the ConTeXt garden? Aditya Mahajan
2011-03-14  0:07   ` Alasdair McAndrew
2011-03-14  3:12     ` Aditya Mahajan
2011-03-14 10:42       ` Philipp Gesang
2011-03-14  3:32     ` mathew
2011-03-14  4:21       ` Alasdair McAndrew
2011-03-14  4:54         ` Aditya Mahajan
2011-03-14  6:33           ` Alasdair McAndrew
2011-03-14  7:07             ` Henning Hraban Ramm
2011-03-14  9:17           ` Martin Schröder
2011-03-14 10:43             ` Alasdair McAndrew
  -- strict thread matches above, loose matches on Subject: below --
2011-03-10 14:38 \setuppublications problem Jean Magnan de Bornier
2011-03-11 12:00 ` Thomas A. Schmitz
2011-03-12  7:37   ` Jean Magnan de Bornier
2011-03-12 10:09     ` Thomas Schmitz
2011-03-12 10:45       ` Florian Wobbe
2011-03-12 11:08         ` Thomas Schmitz
2011-03-12 12:21           ` Ideas for restructuring the ConTeXt garden? Florian Wobbe
2011-03-12 13:05             ` Marco
2011-03-12 14:08               ` Mojca Miklavec
2011-03-12 16:20             ` Procházka Lukáš
2011-03-12 20:02               ` Jaroslav Hajtmar
2011-03-12 20:08             ` C.
2011-03-12 23:04               ` Pontus Lurcock
2011-03-14  7:46                 ` Taco Hoekwater
2011-03-14 20:26                   ` Mojca Miklavec
2011-03-14 21:15                     ` mathew
2011-03-13  7:01               ` Vnpenguin
2011-03-13  4:48             ` mathew
2011-03-13  5:03               ` Pontus Lurcock
2011-03-13  6:25                 ` luigi scarso
2011-03-14 13:04             ` Carlos Breton Besnier
2011-03-14 15:16             ` Carlos Breton Besnier
2011-03-16 12:37               ` Vedran Miletić
2011-04-26 10:27                 ` Ian Lawrence
2011-03-14 15:17             ` Carlos Breton

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=20110312233554.GB25891@houseag.com \
    --to=hajhouse@hajhouse.org \
    --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).