Use of the number sign (#) in exported filename

Dorico scripts can already write to the file system. @HaraldS is just asking for the ability for Dorico to call scripts automatically at certain points in the workflow and pass in defined parameters – a big ask, and one that would need a lot of thought and design (and one that I’m not sure is generally useful).

They can trigger a save, but they can’t modify existing files on disk, which seemed to be what he was asking for – after print, rename file.

Dorico scripts are just Lua scripts. You can put any Lua code in there that you want, including code that writes to the file system. You’re not limited to commands that get sent to Dorico.

Indeed, my point is that a script could get called after the file is written, with the file’s path as a parameter. It should not be Dorico’s task to take care about arbitrary file naming conventions, but it could offer the user a way to change the filename to his preferences after Dorico wrote the file’s content.

Sure, it is a crucial decision how and where a script can be invoked and how much access it is granted to Dorico’s internal database. But the way we had access to Finale’s internal data via JWLua et al was a good start and an acceptable substitute for a SDK. I do hope, Dorico is being developed into a comparable direction.