From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: type and typing comments for TeX and Lua
Date: Thu, 21 Dec 2017 21:16:45 +0100 [thread overview]
Message-ID: <4be5b6a0-30f3-ffa9-d636-545ac0ed8905@gmx.es> (raw)
In-Reply-To: <CAO8LnPGHk_Ym+-JLGjRV-5cSgHtrWaLzmu4A9NQ0t2PLJrqmSw@mail.gmail.com>
On 12/21/2017 05:04 PM, Christoph Reller wrote:
> Dear Pablo,
>
> At least for XML you could use my module highlight-xml:
>
> \usemodule[highlight-xml]
> \definetype[xml][option=xml]
> [...]
> Note that even partial XML is highlighted correctly.
Dear Christoph,
many thanks for your reply.
Your module is really great fine. It supports both \setuptype and
\setuptyping options.
It is really a pity that it lacks TeX, since I’m focused on ConTeXt yet
(after all, it would be a Spanish introduction to ConTeXt ;-)). XML will
come later.
I’m afraid that XML comments are colored the same way with your module
and with standard ConTeXt.
Comment marks in are colored as standard tags, I’m afraid. I mean,
"<!--" and "-->" are colored in blue as "<p>".
To show a comment as a whole, setting up both comment text and marks in
a single and unique color is required.
This is why I thought that SnippetCommentMark and SnippetCommentText
would be a fine way to typeset full comments.
Sorry for insisting. It isn’t perfectionism. My friends and family
members aren’t computer scientists. I have to explain what a comment is
from the very beginning. If colors are misleading, they are lost.
This is why I have to solve this before resuming text composition.
It would be great that you also offered a highlight-tex (with
SnippetCommentText and SnippetCommentMark). Or to ease the module
loading, it would be useful to have a context-highlight (or similar name).
If your implementation could be latter added (if Hans agrees) to the
ConTeXt core.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-12-21 20:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 16:04 Christoph Reller
2017-12-21 20:16 ` Pablo Rodriguez [this message]
2017-12-27 1:14 ` SteamedFish
2017-12-27 18:44 ` Pablo Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2017-12-28 7:38 Christoph Reller
2017-12-21 21:16 Christoph Reller
2017-12-26 18:07 ` Pablo Rodriguez
2017-12-27 18:53 ` Pablo Rodriguez
2017-12-18 22:50 Pablo Rodriguez
2017-12-19 19:26 ` Aditya Mahajan
2017-12-19 21:29 ` Pablo Rodriguez
2017-12-19 23:20 ` Aditya Mahajan
2017-12-21 18:54 ` Pablo Rodriguez
2017-12-21 19:05 ` Aditya Mahajan
2017-12-21 20:49 ` Pablo Rodriguez
2017-12-21 21:53 ` Aditya Mahajan
2017-12-26 18:36 ` Pablo Rodriguez
2017-12-27 22:32 ` Aditya Mahajan
2017-12-20 11:53 ` Hans Hagen
2017-12-20 19:45 ` Pablo Rodriguez
2017-12-20 21:18 ` Hans Hagen
2017-12-21 19:53 ` Pablo Rodriguez
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=4be5b6a0-30f3-ffa9-d636-545ac0ed8905@gmx.es \
--to=oinos@gmx.es \
--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).