9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] troff book
Date: Mon, 12 Dec 2011 09:15:18 +0000	[thread overview]
Message-ID: <CAOw7k5ix40ZSO3Q+ne0E2iRRahkbYAcMThR=EgRFD7E_giYKiw@mail.gmail.com> (raw)
In-Reply-To: <CAFo14L2gEk_MCjGh183bMR78hJd1pnuBWpP3eOjPEGkp+apnOg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

Having read the replies, I thought I'd offer slightly different advice.
You are writing a dissertation. The formatting just needs to be what
satisfies your university's format requirements, which usually are
broad. I'd be surprised if they required an index for instance. Don't
waste time and effort on the formatting. For one thing, few people
will actually read your dissertation, unless what you're doing is
stupendous (and then they won't care about the format): your proof-reader
(you have got one, haven't you?), your supervisor, your examiners,
and ... that's usually about it. (Your parents will look at it.) If your
supervisor
supervisor can start fussing about the prettiness of (say) your equations
and tables rather than their content, you can reasonably suggest to him
that you
would appear to be finished. Just do a few test runs first of typical
equations
just to check that the output is at least reasonable.

Much later, when your topic turns out to be important again, someone like
me will remember seeing your dissertation mentioned, or find it through
Google^,
but I can assure you that by we'll still be more interested in the content.

I'd use the system with which you're most familiar. You don't want the
added distractions of trying to debug the typesetting software, and when
something goes wrong, it's much easier if you've used it before. (In my own
case, the night of the submission deadline, when I came to do
the final copy, I discovered that the troff installation Had Somehow Changed
and the output was completely messed up. Unfortunately that predated Plan 9
and yesterday(1),
but fortunately it's easy to check each stage of the pipeline, and
I could work out where to look for the change to undo.

If you're using troff, pick up a copy of refer from contrib.

On 2 December 2011 13:02, hugo rivera <uair00@gmail.com> wrote:

> soon I'll begin to write my thesis and I am planing to use ...

[-- Attachment #2: Type: text/html, Size: 2565 bytes --]

  parent reply	other threads:[~2011-12-12  9:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 13:02 hugo rivera
2011-12-02 13:15 ` simon softnet
2011-12-02 13:23 ` Aharon Robbins
2011-12-02 13:33   ` Gabriel Díaz López de la llave
2011-12-02 13:40   ` Steve Simon
2011-12-02 16:08     ` hugo rivera
2011-12-02 17:54 ` John Floren
2011-12-02 18:00   ` Francisco J Ballesteros
2011-12-02 18:13     ` Австин Ким
2011-12-02 18:21       ` tlaronde
2011-12-02 18:16     ` ron minnich
2011-12-02 18:20       ` Francisco J Ballesteros
2011-12-02 18:29         ` Lyndon Nerenberg
2011-12-02 18:29       ` tlaronde
2011-12-02 18:45         ` John Floren
2011-12-02 21:02           ` tlaronde
2011-12-02 22:24             ` simon softnet
2011-12-02 22:29               ` simon softnet
2011-12-02 22:42                 ` hugo rivera
2011-12-03  1:26                   ` Akshat Kumar
2011-12-11 22:57                 ` Gabriel Díaz López de la llave
2011-12-12  9:15 ` Charles Forsyth [this message]
2011-12-12  9:59   ` simon softnet
2011-12-12 10:28   ` John Stalker
2011-12-12 10:52     ` Rudolf Sykora
2011-12-12 12:04       ` John Stalker
2011-12-12 12:37         ` tlaronde
2011-12-12 12:18     ` Charles Forsyth
2011-12-12 12:42       ` John Stalker
2011-12-12 14:10         ` Michael Kerpan
2011-12-12 17:46           ` tlaronde
2011-12-12 17:48         ` tlaronde
2011-12-12 18:42           ` tlaronde
2011-12-12 19:22         ` Bakul Shah
2011-12-12 19:45           ` Steve Simon

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='CAOw7k5ix40ZSO3Q+ne0E2iRRahkbYAcMThR=EgRFD7E_giYKiw@mail.gmail.com' \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    /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).