From: "Robert F. Beeger" <5beeger@informatik.uni-hamburg.de>
Subject: Verbatim modules
Date: Thu, 21 Feb 2002 13:07:17 +0100 [thread overview]
Message-ID: <1647893640.20020221130717@informatik.uni-hamburg.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
Hello!
I searched for a possibility to include listings with syntax
highlighting in my current text.
First I thought it would be nice to embed HTML in ConTeXt since my
Java-IDE can export Java-Files with syntax highlighting to HTML.
Then I found the verbatim modules of ConTeXt and think they are a much
better idea. It is more lightweight than having the HTML-export with
all those font settings and so on.
Those verbatim modules do nearly everything I need. Thanks to Pragma
ADE for this. But now I have some questions.
There are is a JS and a JV verbatim environment defined in ConTeXt.
What is the difference between those two. Is it only to make the
intention clear : If you have some Java-code, use JV to make clear
that it is Java and not JavaScript. If it is JavaScript use JS. Or is
there more to it.
I have one problem with the Java/JavaScript verbatim module. I would
like the comments to be grayed out like it is done by the XML module.
If I have
\startJV
// bla
public void bla();
\stopJV
the "//" gets typeset in red and the "bla" after the "//" gets typeset in
black, which is the normal color for non-keywords.
How do I make it that the "bla" after the "//"is grayed out.
An other problem occurres when I use a JavaDoc-Comment
\startJV
/**
* bla
* @param blub Blub bla blub.
*/
\stopJV
Now "/*" and "*/" gets typeset in red, the "*" after "/*" and the text
in the comment gets typeset in black and the two remaining "*" get
grayed out. Here I would like to have "/*", "*/" and the other stars
to be typeset in one color´, be it red or what ever, and the text to
be grayed out. I know this is not that easy to accomplish and is more a
feature request for the future. But since I am into this now, I
thought it would not do any harm, if mentioned it.
Greets
Robert
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 1992 bytes --]
next reply other threads:[~2002-02-21 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 12:07 Robert F. Beeger [this message]
2002-02-25 15:32 ` Hans Hagen
2002-02-25 21:35 ` Re[2]: " Giuseppe Bilotta
2002-02-26 11:01 ` Hans Hagen
2002-02-27 7:52 ` Robert F. Beeger
2002-02-27 23:09 ` 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=1647893640.20020221130717@informatik.uni-hamburg.de \
--to=5beeger@informatik.uni-hamburg.de \
/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).