On Thu, 2022-02-17 at 18:50 +0000, Joe Wilkinson wrote: > I'll have a look tomorrow then. > Presumably you could use \\ rather than /??
At first I assumed it was a matter of escaping the backslashes - the whole thing being complicated by both the debugger and guile displaying the path as containing \\ - just their way of displaying a backslash. But Windows has supported / as a file name separator for years now, but the temporary filename generator doesn't use it. So I had to come up with this delicious piece of gobbledy-gook to replace all \ with / in the (d-GetCurrentTypesetPDF) (string-map (lambda (c) (if (equal? c #\\) #\/ c))(d-GetCurrentTypesetPDF)) this would have the unfortunate consequence of garbling any file name that actually had an embedded backslash :) (only possible in Unix where filenames can contain anything except a 0). Besides testing if gs.exe shipped with Denemo would work I also didn't test that you can create more than one book in succession - there is always some doubt because Windows often thinks a file is "in use" and refuses to re-use it. Richard > Joe > > On 17/02/2022 17:32, Richard Shann wrote: > > On Tue, 2022-02-15 at 16:27 +0000, angelaandjoe.wilkinson wrote: > > > Hi Richard, > > > Beginners page tells me that perhaps we need a different > > > version of > > > Ghostscript, not gs.exe? > > Well, those are pre-built versions of ghostscript with whatever > > name > > Artifex's build system chooses to give them, the gs.exe that is > > shipped > > with Denemo is built from source. It is there as part of the > > LilyPond > > which is also built from source, but it may well need some > > environment > > variables set to get it going, which LilyPond will be taking care > > of. > > > > After a hard battle I've got the export of a book of layouts > > working on > > a windows laptop using a installed version of ghostscript; I've not > > tested it on the internal version, but it would be worth doing > > that. > > You choose what to use in Edit->Change Preferences->ghostscript > > putting the full path to gswin64c.exe should work. > > Remarkably, despite all assurances in chatter on the internet > > ghostscript was barfing on the windows backslash path separator, I > > had > > to switch them to forward slashes to get it working. > > > > It will be built tonight as usual. > > > > Richard > > > > > > > > > Joe > > > System Invocation Name Unix gs VMS gs MS Windows 95 and > > > later > > > gswin32.exe > > > gswin32c.exe > > > gswin64.exe > > > gswin64c.exe OS/2 gsos2 > > >
