ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: dexterclarke@Safe-mail.net
To: ntg-context@ntg.nl
Subject: "Semi-verbatim" - preserve whitespace - don't escape characters
Date: Fri, 7 Dec 2007 12:26:07 -0500	[thread overview]
Message-ID: <N1-vCdVZ8Irde@Safe-mail.net> (raw)

Hi.

I'm working on a document processor that has multiple backends
for different output formats (XHTML, nroff, plain text, ConTeXt).

The processor uses s-expression syntax with commands such as:

  (para "this is a paragraph")

The various backends then convert this statement in their own
way (using <p></p> tags in XHTML, for example).

There is one command that allows rendering of external files
based on whatever backend is selected:

  (render "file")

The XHTML backend includes "file", escaping all 'illegal' characters
such as <, >, & etc. The ConTeXt backend reads the file and also
escapes characters, placing their TeX equivalent in the output -
$\}$, $\backslash$ etc. Both backends place the contents of "file"
directly in the output, they don't, for example, use the <object>
tags in XHTML, or any ConTeXt file inclusion directives. This is
desirable for many reasons that are out of scope for this post...

The problem I am having is that one may do this:

  (para-verbatim (render "file"))

The para-verbatim tag is meant to preserve whitespace in the output.

For example, this becomes:

  <pre>contents of file</pre>

in the XHTML output. Unfortunately, I've hit a wall when it comes
to the ConTeXt equivalent: The ConTeXt backend reads
in "file" and prints it to the output, escaping all reserved TeX
characters, as mentioned earlier, but unfortunately there doesn't
seem to be the equivalent of:

  \preservewhitespace
  contents of file
  \stoppreservingwhitespace

"\starttyping" is too heavy handed in that it also escapes characters
rather than just preserving whitespace (they've already been escaped
by my document processor, as mentioned earlier). What I need is a 
directive that says "preserve whitespace" but does not escape reserved 
TeX characters.

Does any such thing exist in ConTeXt? Unfortunately, I'm inexperienced
with TeX so I don't know how feasible this is.

--
dc
___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2007-12-07 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 17:26 dexterclarke [this message]
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

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=N1-vCdVZ8Irde@Safe-mail.net \
    --to=dexterclarke@safe-mail.net \
    --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).