ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Seeking a Deeper ConTeXt: Questions for Initializing
Date: Mon, 25 May 2009 14:35:34 -0400	[thread overview]
Message-ID: <4c1f1f860905251135p278920bfw3bc3a6c23cc317fa@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0905251409250.5080@ybpnyubfg.ybpnyqbznva>


[-- Attachment #1.1: Type: text/plain, Size: 2807 bytes --]

Thank you Aditya. All that makes sense to me. It is quite clear from
everyone's responses that the person on c.t.t who claimed ConTeXt is "only"
for one-offs was not correct.

On Mon, May 25, 2009 at 2:26 PM, Aditya Mahajan <adityam@umich.edu> wrote:

> On Mon, 25 May 2009, John Haltiwanger wrote:
>
>  unlike document classes), there are no pre-rolled environments available.
>> I
>> am thinking here of standardized thesis environments for universities, or
>> a
>>
>
> There are no standardized thesis styles for universities mainly because
> there are no consistent specs. Most univs want you to use times, double
> spaced lines, wide margins, and some formatting guidelines regarding the
> chapter headings, table of content, page headers and footers. Setting these
> are easy in ConTeXt (and also LaTeX if you know the relevant packages).
> Universities do not provide an official thesis style (either in LaTeX or
> ConTeXt) because in most cases they do not have the resources to maintain
> them. Students figure something out, and then pass along their styles to the
> next generation. If the formatting guidelines change, the burden is on the
> students to correct the style, rather than on the university.
>
> When I was writing my thesis, it took me about a few hours to understand
> the formatting guidelines, which were a jigjaw puzzle. Statements like:
> Always use Times New Roman at 12pt as the main font. ... two pages down ...
> The abstract can be in 10pt or 12pt ... a few pages later, use any of the
> standard fonts. It also used vague terminology. Statements like leave two
> blank lines after the title (blank lines, er... for what fontsize, the
> bodyfont or the title font?).
>
> ConTeXt makes it really easy to make the formatting changes. Once I
> understood the formatting guidelines, writing the main style was very easy
> (with a few trips to the manual, and a few questions here on the mailing
> list). Making sure that the resultant style looked visually appealing while
> not violating the formatting guidelines too a lot of experimentation.
>
> As Hans said, you can think of ConTeXt as the "standard" thesis style.
> Setup a few commands, and you meet your formatting requirements. Write it in
> an environment or a module, and you can reuse it.
>
> Aditya
>
>
> ___________________________________________________________________________________
> 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  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 3716 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2009-05-25 18:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 17:17 John Haltiwanger
2009-05-24 18:35 ` Henning Hraban Ramm
2009-05-25 16:30   ` John Haltiwanger
2009-05-25 16:39     ` Hans Hagen
2009-05-25 16:53       ` John Haltiwanger
2009-05-25 16:59         ` Hans Hagen
2009-05-26 15:54       ` Bruce D'Arcus
2009-05-26 21:26         ` John Haltiwanger
2009-05-26 22:08           ` luigi scarso
2009-05-26 23:07           ` Bruce D'Arcus
2009-05-25 16:50     ` Wolfgang Schuster
2009-05-25 17:00       ` John Haltiwanger
2009-05-25 17:12         ` Mohamed Bana
2009-05-25 17:24         ` Hans Hagen
2009-05-25 17:51           ` John Haltiwanger
2009-05-25 18:00             ` Arthur Reutenauer
2009-05-25 18:09               ` John Haltiwanger
2009-05-25 18:21                 ` Arthur Reutenauer
2009-05-25 18:24                   ` John Haltiwanger
2009-05-25 18:55                 ` Hans Hagen
2009-05-25 21:09                   ` luigi scarso
2009-05-25 21:14                     ` Hans Hagen
2009-05-25 21:16                     ` Arthur Reutenauer
2009-05-25 20:25             ` Mohamed Bana
2009-05-25 21:02               ` John Haltiwanger
2009-05-26 22:27               ` Wolfgang Schuster
2009-05-25 17:23     ` Arthur Reutenauer
2009-05-25 18:26     ` Aditya Mahajan
2009-05-25 18:35       ` John Haltiwanger [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=4c1f1f860905251135p278920bfw3bc3a6c23cc317fa@mail.gmail.com \
    --to=john.haltiwanger@gmail.com \
    --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).