Don’t misuse headings for your titlepage. As a titlepage is something special
you can use \midaligned, \definedfont etc. to format it, e.g.

Thanks for the answer, but -

- to describe better my situation:

I'm not creating a typical book, but a special kind of report, with many code 
generated by Lua, many \typefiles and many included PDFs.

And here, there are heads being used as:

- "normal" heads (left-aligned; appended by normal text) and
- "title-like" heads (mid-aligned) which should stand alone on a page (e.g. 
being appended by other pdf documents on the next page).

Both kinds of heads should be numbered and should be involved to TOC; so in 
this point of view, they have the same status.

So e.g.:

--- (page) ---
Chapter 1      <- Normally left-aligned
Section 1.1    <- Normally left-aligned

Some text
some text
some text
some text

--- (page) ---

  Chapter 2    <- Mid-aligned
 Section 2.1   <- Mid-aligned



--- (page) ---

+------------+
| Another    |
| pdf        |
+------------+



--- (page) ---


So "Chapter 1" and "Section 1.1" are "normal" heads, probably typeset by 
\chapter and \section.

As my primary intention was not to "force" normal heads to be aligned otherwise, I derived new head 
styles \chapterMiddle and \sectionMiddle, which are used to generate "Chapter 2" and "Section 
2.1".

But the problem is that TOC becomes visually "crashed" once \sectionMiddle has 
been defined.

So how to solve it?

Lukas


--
Ing. Lukáš Procházka [mailto:l...@pontex.cz]
Pontex s. r. o.      [mailto:pon...@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4

Tel: +420 244 062 238
Fax: +420 244 461 038

___________________________________________________________________________________
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 via email to