Further notes. So far this has been working great for me on the HTML side. On the PDF side, if I use render -p to try and make PDFs in parallel, the processes finish really fast with no errors, and no output of any kind.
My PDF template follows the approach in the tutorials of making a temp folder, writing the LaTeX into it, running xelatex and then spitting out the bytes. >From testing and some unanswered threads in the Racket Users group, it seems like `current-directory` (and maybe `current-project-root`) evaluate to "/" specifically when being evaluated *inside a template *from within a Racket "place". Which means there is probably a permissions error happening pretty quick when the temporary folder is created, short-circuiting the render before it even gets to the `system` call. I need to do more work to figure out how to fix it, but I've been busy. It just seems like a caveat that should probably be mentioned in the docs eventually. -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
