From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Page Numbering Hell
Date: Wed, 21 Oct 2009 22:57:49 +0200 [thread overview]
Message-ID: <4C80A4C0-DBD4-4B7C-A9CB-A16265F22462@uni-bonn.de> (raw)
In-Reply-To: <51CAD0CE1504444DBE77CBBE51A0135D6CE2B0@slcmail.slc.mew.int>
Since you weren't satisfied with the reply you got, here's another
attempt to please you:
On Oct 21, 2009, at 8:36 AM, Bryant Eastham wrote:
> All-
>
> A few days ago when I first stumbled on ConTeXt I was very, very
> excited. I have some 500 pages of technical documentation that could
> benefit from this, particularly since I need Japanese font support.
> But it has to be real.
>
> I’m sorry if this sounds caustic, but after 12 hours of failed
> attempts to even get a minimal document formatted I have some
> serious questions for the list:
What do you mean "get even a minimal document formatted"? You're
complaining that you don't find "current examples that actually work,"
yet instead of a real minimal example, you post only rants. Give us a
real example of what you have tried, and someone may be able to help
you.
>
> 1. Is Mark IV real? I am only somewhat joking here – after
> spending hours searching for reasonable documentation on even the
> most trivial options, I am left wondering whether this is something
> I want to use…
No Mkiv isn't real. For two years, we've all been part of this
elaborate hoax. We pretend we're using a software that doesn't exist.
> 2. ConTeXt looks great. But what is current? Seriously, I like
> the look and the support (particularly Unicode). But going over
> documentation I cannot make heads or tails of what to do. Mark II?
> Mark IV? TeTeX? LuaTeX? If I really want to use this, what should I
> use?
TeTeX is the odd item in your list. It's a defunct TeX system that
hasn't been updated in three years or so. You may have meant XeTeX. On
a serious note: For 95 % of ConTeXt, it doesn't matter what engine you
use. The high-level code in your document should give identical output
with pdftext (= mkii), XeTeX, or the new luatex engine (= mkiv). If
you need Japanese, you will probably want to use XeTeX or luatex. For
the differences between mkiv and mkii, see http://wiki.contextgarden.net/MkIV_Differences
> 3. Having answered #2, where in the world is a reference
> manual!!! I mean one that actually *documents the options*.
What documentation did you read? cont-eni.pdf? The wiki? Have you
looked at all the manuals available on http://www.pragma-ade.com/show-man-1.htm
? cont-eni.pdf is still the current documentation; if you want to
have a brief look at options, I would recommend http://texshow.contextgarden.net/
> 4. Having answered #3, are there any current examples that
> actually work? The snippets from the mailing are great, but they are
> just snippets. That doesn’t help me.
What is missing on http://wiki.contextgarden.net/Sample_documents ?
There are several sample documents.
>
> Now, to resolve my immediate issue, and just because I will not be
> able to sleep well until I figure this out (yes, I am fixated on
> this).
>
> I want this document structure:
>
> Contents
> 1. Chapter 1-1
> 1.1 Section 1-2
> 2. Chapter 2 2-1
> 2.1 Section 2-2
>
> Table of contents on page “i”.
> Even/odd, each chapter starts on right page.
> Page number (as in 2-2) in top margin.
> Mark IV, Lua document.
>
> I have tried hundreds of different combinations. If it cannot do
> this, the I will (with sadness) move on. I’m sure that it would take
> someone who understands this about 5 minutes to write (if that).
>
Then show us a minimal example of one of these hundreds of
combinations, and somebody will look at it and may have an idea. But I
doubt that anybody will want to write this for you.
Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-10-21 20:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 6:36 Bryant Eastham
2009-10-21 7:13 ` Alan BRASLAU
2009-10-21 7:46 ` luigi scarso
2009-10-21 14:24 ` Bryant Eastham
2009-10-21 16:00 ` Alan BRASLAU
2009-10-21 16:52 ` Bryant Eastham
2009-10-21 17:42 ` Alan BRASLAU
2009-10-23 7:19 ` Taco Hoekwater
2009-10-23 7:38 ` luigi scarso
2009-10-23 7:45 ` Aditya Mahajan
2009-10-23 20:41 ` Aditya Mahajan
2009-10-26 6:42 ` Thomas Floeren
2009-10-23 7:57 ` luigi scarso
2009-10-24 11:48 ` Spam:*****, " Hans Hagen
2009-10-22 8:03 ` Boštjan Vesnicer
2009-10-25 14:57 ` Hans Hagen
2009-10-21 15:49 ` Aditya Mahajan
2009-10-23 16:34 ` Bryant Eastham
2009-10-21 20:57 ` Thomas A. Schmitz [this message]
2009-10-23 8:30 ` Bryant Eastham
2009-10-23 8:49 ` luigi scarso
2009-10-23 9:39 ` Alan BRASLAU
2009-10-24 11:57 ` Spam:*****, " Hans Hagen
2009-10-23 19:57 ` Page Numbering Hell (SOLVED) Bryant Eastham
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=4C80A4C0-DBD4-4B7C-A9CB-A16265F22462@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).