From: Tobias Burnus <burnus@gmx.de>
Cc: NTG-ConTeXt <ntg-context@ntg.nl>
Subject: Re: Two more questions
Date: Thu, 11 Nov 1999 15:19:18 +0100 [thread overview]
Message-ID: <382AD066.7D9C078B@gmx.de> (raw)
In-Reply-To: <199911111034.KAA31737@interzone.ucc.ie>
Hallo Marc,
> 1) I have used pdftex before and have created a number
> of macros for handling forms, hyperlinks and the like.
> When I tried to use them in combination with \CONTEXT
> it turned out they didn't work (I haven't started
> using things depending on forms yet.).
(then there shouldn't be a problem simply switching to the context ons, this
makes is more likely that your hyperlinks work when using a different path, e.g.
dvips->distiller/ghostscript->[pdf])
> E.g. I compared two pdf files, one created using
> \CONTEXT and one without. The pdf for a hyperlink
> seems identical. The hyperlinks generated with the
> \CONTEX macros (i.e. not with my own) do work.
> Any suggestions as to what I am overseeing?
I think this is almost impossible to answer this -- at least without seeing an
example and/or your macros. (If you really need them, you can make an example
else simply use the ConTeXt commands.) Apropos PDFTeX, there exists a mailing
list concerning pdf (and mainly pdftex) at pdftex@tug.org, subscribe pdftex,
majordomo@tug.org, where you can ask questions concerning plain TeX (which is
basicly what you are trying to achive; the list is also about pdfLaTeX, hyperref
and "pdf-ConTeXt".)
> 2) Is there a ``fancyverb'' like thing which would allow
> mo to carry out commands in a ``verbatim'' environment?
Even after scanning the fancyvrb.ps file, I'm not totally sure what is ment by
'carry out commands', but I think I got an idea of the features. The features of
ConTeXt are not always the same but also advanced.
Have a look at the source documentation in the files:
verb-ini.tex -- this gives a nice overview about the verbatim possibilities.
verb-*.tex contain the basics used for syntacs highlighting of PERL,
Java/JavaScript, TeX, MetaPost and SQL. (This file is a must, if you want to add
a language, else better skip it, it isn't that well (cp. to verb-ini commented
and contains fewer examples.)
You probably already know \typefile, \type, \starttyping ... \stoptyping.
But do you know:
\type<<a <<slanted>> word>>
\type<<with <</bf boldfaced>> text>>
(from verb-ini.tex a very nice reference!)
If you have special needs, drop a note to this list.
Tobias
PS: From TeXShow (texshow setuptyping en):
------------------------------------------------
\setuptyping[...][..,..=..,..]
\setuptyping
[file, typing, name]
[space=on|off,
page=yes|no,
option=slanted|normal|commands|color|none,
before=command,
after=command,
margin=dimension|standard,
evenmargin=dimension,
oddmargin=dimension,
blank=dimension|small|medium|big|standard|halfline|line,
escape=,
indentnext=yes|no,
palet=name]
------------------------------------------------
\setuptype[..=..]
\setuptype
[space=on|off,
option=slanted|normal|none]
------------------------------------------------
Using before/after you can also use \startlinenumbering, \startframed etc.
next prev parent reply other threads:[~1999-11-11 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-11 10:34 Marc van Dongen
1999-11-11 14:19 ` Tobias Burnus [this message]
1999-11-11 23:43 ` Hans Hagen
[not found] <199911111431.OAA03745@interzone.ucc.ie>
1999-11-11 14:41 ` Tobias Burnus
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=382AD066.7D9C078B@gmx.de \
--to=burnus@gmx.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).