From: Hans van der Meer <hansm@science.uva.nl>
Subject: textbackground > bug
Date: Sat, 17 Dec 2005 21:29:38 +0100 [thread overview]
Message-ID: <B3CDDC4A-98C3-44A9-B36C-FADD27972A23@science.uva.nl> (raw)
Something strange happens with textbackground (again, I am afraid).
I defined:
% Java typesetting with background.
\definetyping[JAVA]
\setuptyping[JAVA][option=JV,
before={\bgroup\setupinterlinespace[line=2.2ex]%
\testpage[1]\starttextbackground[code]},
after={\stoptextbackground\egroup}]
Then I typeset some text:
\startJAVA
public void setUserManager( UserManager um ) {
......
\stopJava
If this falls precisely at the start of a new page I get the
following error:
! Undefined control sequence.
l.17 \s
tartpdffontresource[ec]
Forcing the typesetting to run further the output contains the rest
of the source of macro \startpdffontresource[ec] .
I.e. the output then shows (the \s has disappeared):
tartpdffontresource[ec]
/CIDInit /ProcSet findresource begin
...
--------- and goes on until (the last part of the macro "end end
\stoppdffontresource" not appearing)
... CMapName currentdict /CMap defineresource pop
Hereafter typesetting is resumed.
>>>Introducing something that puts another line of text at the top
of the page results in normal typesetting.<<<
Further experiment
replacing "\startJava" by "\starttextbackground[somecolor]" leads to
the same error.
Therefore I suspect it has something to do with the output routine
where \s is taken as the next macro.
A simpe experiment (\def\s{something}) shows that indeed a macro \s
is executed.
Is someone here messing up the catcode's of the letters?
It is of cource very annoying if one constantly has to shift
textmaterial up and down to move it away from page breaks!
yours sincerely,
dr. H. van der Meer
next reply other threads:[~2005-12-17 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-17 20:29 Hans van der Meer [this message]
2005-12-18 10:40 ` Taco Hoekwater
2005-12-18 19:11 ` Hans van der Meer
2005-12-18 21:10 ` 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=B3CDDC4A-98C3-44A9-B36C-FADD27972A23@science.uva.nl \
--to=hansm@science.uva.nl \
--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).