[XeTeX] Some problems with PSTricks

[Ulrike Fischer]

Am Sat, 21 Jun 2008 12:34:56 +0100 schrieb Jonathan Kew:

> If you can try the pre-release TL2008 packages and report any  
> problems, with appropriate test cases, that will improve the chances  
> that we can deal with the glitches. I don't use either PSTricks or  
> Windows myself, so I am unlikely to run into the issues personally; I  
> do try to follow up on reported problems, though, if they're easy for  
> me to reproduce here.

The good news are: it now works on miktex.

So I tried the examples of Vafa.

***********1. Example*****************

\documentclass{article}
\usepackage{pstricks,pst-light3d}
\DeclareFixedFont{\Rmb}{T1}{ptm}{m}{n}{15mm}
\begin{document}
\PstLightThreeDText[linestyle=none,fillstyle=solid,
                 fillcolor=black!20]{\Rmb Hallo}
\end{document}

Doesn't work with xetex, the first step is ok but then:

)Error: /undefined in Resolution
Operand stack:
   LightThreeDDXa   5.69046
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval-
-   2   %stopped_push   --nostringval--   --nostringval--
--nostringval--   fa
lse   1   %stopped_push   1889   1   3   %oparray_pop   1888   1   3
%oparray_
pop   1872   1   3   %oparray_pop   1755   1   3   %oparray_pop
--nostringval-
-   %errorexec_pop   .runexec2   --nostringval--   --nostringval--
--nostringv
al--   2   %stopped_push   --nostringval--   1889   1   3   %oparray_pop
1888
  1   3   %oparray_pop   1872   1   3   %oparray_pop   1755   1   3
%oparray_p
op   --nostringval--   %errorexec_pop   .runexec2   --nostringval--
--nostring
val--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1155/1684(ro)(G)--   --dict:0/20(G)--   --dict:77/200(L)--
--dict:12
/40(L)--
Current allocation mode is local
Current file position is 461
MiKTeX GPL Ghostscript 8.60: Unrecoverable error, exit code 1

** WARNING ** Filtering file via command -->mgs.exe -q -dNOPAUSE -dBATCH
-sPAPER
SIZE=a0 -sDEVICE=pdfwrite -dCompatibilityLevel=1.3
-dAutoFilterGrayImages=false
-dGrayImageFilter=/FlateEncode -dAutoFilterColorImages=false
-dColorImageFilter=
/FlateEncode -dUseFlateCompression=true
-sOutputFile="C:/DOKUME~1/Ulle/LOKALE~1/
Temp/mik4BB.tmp" "C:/DOKUME~1/Ulle/LOKALE~1/Temp/mik4BA.tmp" -c quit<--
failed.
** WARNING ** Image format conversion for PSTricks failed.
** WARNING ** Interpreting special command PST: (ps:) failed.
** WARNING ** >> at page="1" position="(243.19, 688.19)" (in PDF)
** WARNING ** >> xxx "PST: tx at Dict begin gsave STV 0.8 SLW 0  setgray
gsave 0.8
  set"

Output written on test-xetex.pdf (1 page).
Transcript written on test-xetex.log.
Drücken Sie eine beliebige Taste . . . 


************2. example*****************
\documentclass{article}
\usepackage{pst-calendar}
\begin{document}
\psset{Year=2008,unit=0.5cm}
\psCalDodecaeder[style=june]
\end{document}

Result like in the links sent by Vafa.

xdvipdfmx -vv shows that a lot of temporary images are created
successfully, but there a not combined correctly. I would suspect that
coordinate transformations are involved and xdvipdfmx can't use them. 



I also saw often messages like

** WARNING ** -26 memory objects still allocated

at the end of my tests. Is this normal?


-- 
Ulrike Fischer