Open pablgonz opened 3 years ago
The only thing that is not working at the moment is:
\begin{pspicture}[shift=*](-.2,-.2)(1.2,1.2) % \psframe[fillstyle= penrose,psscale=.5](1,1) % \psframe[fillstyle= penrose*,psscale=.5](1,1) \end{pspicture}
In which way do these fail for you? (On my system they "work", they are just very slow (~30 seconds each) and they somehow break the linearc example (not quite sure yet how this can happen).)
Ohh...I really didn't wait that long :) ...it just kept waiting and didn't finish.
Not the slow performance, but the weird "affects future drawing commands" issue with the penrose fillstyle can be reproduced even without LuaTeX with
% arara: latex
% arara: dvips
% arara: ps2pdf: { options : [ -dALLOWPSTRANSPARENCY ] }
% arara: clean: { extensions : [ aux, log, dvi ] }
\RequirePackage{pdfmanagement-testphase}
\DeclareDocumentMetadata{uncompress}
\documentclass{article}
\usepackage{pstricks}
\usepackage{pstricks-add}
\begin{document}
\parbox{4.5cm}{%
\psclip{\psccurve[linestyle=none,fillstyle=penrose,psscale=.2](-3,-2)
(0.3,-1.5)(2.3,-2)(4.3,-1.5)(6.3,-2)(8,-1.5)(8,2)(-3,2)}
“One of the best new plays I have seen all year: cool, poetic,
ironic \ldots” proclaimed \emph{The Guardian} upon the London
premiere of this extraordinary play about a Czech director and
his actress wife, confronting exile in America.\vspace{-1cm}
\endpsclip}
\begin{pspicture}[shift=*](-1,-1)(2,2)
\psline[linearc=0.5cm,showpoints=true,dotstyle=|]{<<->>}(0,1)(1,-1)(2,1)
\end{pspicture}
\end{document}
I'll add a workaround, but I guess a proper fix should come from upstream. (Update: Herbert agreed that this should be fixed in pstricks directly)
I'll add a workaround, but I guess a proper fix should come from upstream. (Update: Herbert agreed that this should be fixed in pstricks directly)
That's great!!! (recent update modifies the font for \psdots
).
Ohh...I really didn't wait that long :) ...it just kept waiting and didn't finish.
It does compile (with the wrong image of course), but the text on page 5 is no longer selectable (at least not with evince/atril).
Separate question, can you explain me what is the role of these two lines (I have seen them in several codes in the TeXSX chat).
\RequirePackage{pdfmanagement-testphase}
\DeclareDocumentMetadata{uncompress}
I know it creates a non-compressed pdf, but what's the use of that? (I've never been able to look inside the structure of a PDF, other than using Acrobat DC pro to see something).
I know it creates a non-compressed pdf, but what's the use of that? (I've never been able to look inside the structure of a PDF, other than using Acrobat DC pro to see something).
As a typical user you shouldn't need this, it's mostly necessary when you write code which generates PDF literals and you need to find errors with them (or just want to see the context they appear in). E.g. luapstricks
directly generates PDF instructions, so if something generates wrong graphics than it is helpful to see if these instructions look correct, if they get added at the right location etc. Also it allows to change the instructions in the PDF file directly so you can test which instructions work better before adapting the code.
More generally useful, you can use the two lines without specifying uncompress
to just activate the pdfmanagement-testphase
package. So just
\RequirePackage{pdfmanagement-testphase}
\DeclareDocumentMetadata{}
This provides package authors a new unified interface to add some stuff to PDF files which is used e.g. by luapstricks
. (You need this to avoid some warnings and enable e.g. transparency support)
Thank you very much for the explanation!
I have updated the example file by adding eofill
.
Question, why does the layout of the images on the pages change when using lualatex
?
Question, why does the layout of the images on the pages change when using
lualatex
?
The "colors available" table places the color name purple in a column of type p{.8cm}
which is too small to fit the word "purple" properly. LuaTeX therefore hyphenates purple and plots it into two lines. Other engines have a rule never to hyphenate the first word in a paragraph, so "purple" which is the only word (and therefore especially the first) in it's paragraph can't be hyphenates and the box is made overfull instead. Of course, splitting a word over two lines needs more vertical space than keeping it on one line, so the vertical spacing gets out of sync moving the page breaks.
With today's update works OK
I am pleased to be able to present this second file, testing the parameters that (basic) using it, compiles without problems.