\documentclass{minimal}
\begin{document}
\makeatletter
\null
\special{ps:\@percentchar\space
I'd really prefer it if dvips didn't wrap lines of PostScript that are included via a backend special.}
\makeatother
\end{document}
Run the above through LaTeX and you'll see that the whatsit is correct
in the DVI file:
$ dvitype junk.dvi | fgrep xxx
105: xxx 'ps:% I'd really prefer it if dvips didn't wrap lines of PostScript that are included via a backend special.'
However, dvips splits the text at ~70 characters:
$ dvips junk.dvi
This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com)
' TeX output 2006.04.20:0032' -> junk.ps
<texc.pro><special.pro>. [1]
$ grep -A1 prefer junk.ps
% I'd really prefer it if dvips didn't wrap lines of PostScript that
are included via a backend special.
Naturally, the resulting PostScript is invalid here.
Is there some way I can force dvips to include literal PostScript _literally_?
Thanks in advance,
-- Scott
I guess you are trying to put a comment in the ps, right?
I found this in an old answer of David Carlisle which is perhaps
helpful:
> \catcode`\%=12
> \special{"%% This is a Comment in PS}
> \catcode`\%=14
Don't try that. don't try anything!
.....
% This is a Comment in PS
does end up in the resulting postscript, but you have no way to force
that it ends up on a line by itself. As postscript comments are line
based this means that whatever postscript code for the rest of the
document that dvips happens to put on the same line of the postscript
file will also get commented out.
You can put comments in a separate header .ps file and include them
with the header special or -h option. Then tex never sees the file and
dvips copies it verbatim, so the comments will get copied in to the
result.
--
Ulrike Fischer
e-mail: zusätzlich meinen Vornamen vor dem @ einfügen.
e-mail: add my first name between the news and the @.
Thanks. It's good to know that I'm not merely doing something stupid.
-- Scott