From: "Procházka Lukáš Ing." <LPr@pontex.cz>
To: ConTeXt <ntg-context@ntg.nl>
Subject: \startsectionlevel broken?
Date: Mon, 08 Aug 2016 17:34:36 +0200 [thread overview]
Message-ID: <op.ylvuvyk262epfj@lpr> (raw)
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Hello,
I'm getting weird output with \startsectionlevel - its parameters are flushed into page.
I copied a sample from
http://source.contextgarden.net/tex/context/base/strc-lev.mkvi?search=dodo
and I compiled it with:
"
This is LuaTeX, Version 0.98.0 (TeX Live 2016/W32TeX)
system commands enabled.
system > synctex functionality is enabled (1), expect runtime overhead!
open source > 1 > 1 > d:/Ctx-Beta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv
ConTeXt ver: 2016.08.01 14:16 MKIV beta fmt: 2016.8.4 int: english/english
"
The source and result are attached... What's wrong?
Best regards,
Lukas
--
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn
Bezová 1658
147 14 Praha 4
Tel: +420 241 096 751 (+420 720 951 172)
Fax: +420 244 461 038
[-- Attachment #2: t3.mkiv --]
[-- Type: application/octet-stream, Size: 943 bytes --]
\starttext
\definehead[xxxxxxsection][subsubsection]
\setuphead [xxxxxxsection][color=red]
\definesectionlevels[main][chapter,section,subsection,subsubsection]
\definesectionlevels[next][chapter,section,subsection,xxxxxxsection]
\startsectionlevel [main] [title=first top level]
\startsectionlevel [main] [title=first lower level]
\startsectionlevel [main] [title=second lower level]
\startsectionlevel [main] [title=third lower level]
test
\stopsectionlevel
\stopsectionlevel
\stopsectionlevel
\startsectionlevel [main] [title=first lower level]
\startsectionlevel [main] [title=second lower level]
\startsectionlevel [next] [title=third lower level]
test
\stopsectionlevel
\stopsectionlevel
\stopsectionlevel
\stopsectionlevel
\stoptext
[-- Attachment #3: t3.pdf --]
[-- Type: application/pdf, Size: 8274 bytes --]
[-- Attachment #4: Type: text/plain, Size: 485 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2016-08-08 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 15:34 Procházka Lukáš Ing. [this message]
2016-08-08 19:05 ` Hans Hagen
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=op.ylvuvyk262epfj@lpr \
--to=lpr@pontex.cz \
--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).