[pstricks] PSTricks and dvisvgm

[Alexander Grahn]

Dear Herbert,

On Fri, Feb 04, 2022 at 05:04:17PM +0100, Alexander Grahn wrote:
>
>On Fri, Feb 04, 2022 at 04:24:12PM +0100, Herbert Voss wrote:
>>
>>
>>Am 04.02.22 um 15:52 schrieb Alexander Grahn:
>>> Dear Herbert,
>>>
>>> since some recent update, PSTricks does not accept a global `dvisvgm'
>>> option anymore and complains with
>>>
>>> \c at lor@to at ps ->\PSTricks
>>>                           _Not_Configured_For_This_Format
>>>
>>> The dvisvgm driver supports almost all Postscript operators and
>>> graciously converts DVI with PSTricks content into correct SVG. Giving
>>> `dvisvgm' as a class option is a convenient way to pass it to any
>>> package that understands it and this used to work without a problem in
>>> the past. Currently, this can be worked around by passing `dvisvgm'
>>> one by one to all packages that need to know it and to hide it from
>>> PSTricks in this way. However, it would be nice to have PSTricks
>>> tolerate dvisvgm again.
>>
>>Alexander,
>>
>>with \documentclass[dvisvgm]{book}
>>
>>I get
>>
>>(/usr/local/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvisvgm.def)
>>(./document1.aux)
>>! Undefined control sequence.
>><recently read> \c at lor@to at ps
>>
>>which creates later the abobe message.
>>
>>I cannot remember that I changed anything in this area.
>>
>>Herbert
>>
>
>Thank you for your reply, Herbert!
>
>So it is not PSTricks' fault. I have just double checked; with TL2020
>an example picked at random from the PSTricks page at tug.org compiles
>without any problem, e. g.
>
>\documentclass[dvisvgm]{article}
>\usepackage[dvipsnames]{pstricks}
>\usepackage{pstricks-add}
>\pagestyle{empty}
>\begin{document}
>
>\psscalebox{0.5}{ %
>\begin{pspicture}(12,12)
>\pnode(0,0){A}\pnode(12,0){B}\pnode(12;60){C}
>\pspolygon[fillstyle=solid,fillcolor=MidnightBlue!20](A)(B)(C)
>\multido{\iA=1+1,\iB=20+4}{20}{%
>  \pnode(A){X}\pnode(B){Y}\pnode(C){Z}
>  \psRelNode(X)(Z){0.1}{A} \psRelNode(Z)(Y){0.1}{C}
>  \psRelNode(Y)(X){0.1}{B}
>  \pspolygon[fillstyle=solid,fillcolor=MidnightBlue!\iB!red!\iB,opacity=0.4](A)(B)(C)}
>\end{pspicture}}
>
>\end{document}
>
>Maybe it has to do with driver detection in the current formats.

I contacted the L3 team. They are going to fix this.

Kind regards

Alexander