From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: "Semi-verbatim" - preserve whitespace - don't escape characters
Date: Sat, 8 Dec 2007 23:59:35 +0100 [thread overview]
Message-ID: <20071208235935.972d0bfa.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.0.9999.0712081727240.5700@nqv-yncgbc>
On Sat, 8 Dec 2007 17:30:38 -0500 (EST)
Aditya Mahajan <adityam@umich.edu> wrote:
> On Sat, 8 Dec 2007, Wolfgang Schuster wrote:
>
> > On Sat, 8 Dec 2007 09:44:52 -0500 (EST)
> > Aditya Mahajan <adityam@umich.edu> wrote:
>
> >>> \startlines
> >>> verbatin text
> >>> \stoplines
> >>
> >> Note that everything between start-stop lines is normal tex code.
> >
> > you mean start/stoplines need style and color keys.
>
> That would not be bad :) but it is not what I meant. I meant that it is
> the author's (or in the case the convertor's) responsibility to make sure
> that everything inside is valid tex code. So something like
I know but setup keys are the best way to change the layout of
environemnts and keep the document clean. Using a converter is no
answer why you should't you this mechanism and write the styyle change
in the document and not in preamble.
> \startlines
> \undefinedmacro blah blah
> \stoplines
>
> will not work.
>
> Aditya
As Dexter? already mentioned, he writes the escaped commands in the
document \undefinedmacro will end up as \tex{undefinedmacro} or
\type{\undefinedmacro} in the output file.
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2007-12-08 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 17:26 dexterclarke
2007-12-08 9:24 ` Wolfgang Schuster
2007-12-08 14:44 ` Aditya Mahajan
2007-12-08 14:51 ` Wolfgang Schuster
2007-12-08 22:30 ` Aditya Mahajan
2007-12-08 22:59 ` Wolfgang Schuster [this message]
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=20071208235935.972d0bfa.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).