Re: (dsssl) character repertoire?

Subject: Re: (dsssl) character repertoire?
From: "Christopher R. Maden" <crism@xxxxxxxxx>
Date: Wed, 02 Apr 2003 00:13:40 -0800
Hash: SHA1

At 18:07 1/4/03, Ian Zimmerman wrote:
>Ok, this answered my question, thanks!  Unfortunately, it wasn't the
>question I wanted to ask :)
>What I really want is to make the TeX backend output a macro call of
>my choosing.  When I do as above Jade escapes the backslash to a
>'\char92' instead.  How to prevent that?

Generally, the formatting-instruction extension flow object will put stuff 
directly into the output file, so try

(make formatting-instruction
   data: "\\char92")

And at 18:28 1/4/03, Tim McDaniel wrote:
>Thanks.  That indeed works.  I'm a bit surprised, because \ is a
>little different in Jade/DSSSL compared to, say, C++: "\n" and "\
>" and such don't work, for example.

The \ is an escape character, as in C++.  However, the escape *sequences* 
vary; in C++, "\n" is the escape sequence for a newline; that sequence, in 
DSSSL, is an 'n'.  The commonality is that if you want the escape character 
literally, you escape it - thus \\ in DSSSL and C++, {{ in XSLT, ... uh, 
well, really \ is the most common one, so I'm having trouble coming up with 
other examples.

>     &#92;
>does not; for example,

>Since a DSSSL program is SGML input, "&#92;" is getting translated to
>"\" pretty early, before DSSSL sees it.

Bingo.  The DSSSL stylesheet is an SGML document; the SGML parser parses 
&#92; and passes on only a single backslash.  I routinely enclose my entire 
stylesheet bodies in CDATA marked sections, unless for some reason I really 
*need* to use SGML general entities inside them.

- -- 
Christopher R. Maden, Principal Consultant, crism consulting
XML - SGML - HTML - DTDs/schemas - conversion - training - ebooks - B2B
<URL: >
PGP Fingerprint: BBA6 4085 DED0 E176 D6D4  5DFC AC52 F825 AFEC 58DA
Version: PGP Personal Privacy 6.5.8


 DSSSList info and archive:

Current Thread