Re: Keep parsed document in memory

2016-02-22 Thread Sharon Rosner
> I worked on a large score with about 100 A3 pages with 13 point staff > size (~ 50 minutes of huge orchestra). > > Compiling the full score using manual breaks took around 7 minutes, with > the console output seemingly indicating the switch from parsing to > engraving after around 1'30. > Then I

Re: Keep parsed document in memory

2016-02-22 Thread Sharon Rosner
> That’s true for proofreading, but it’s not true for beautification, and > making the full score publication-ready. Horizontal and vertical spacing > will be completely different if only individual parts are compiled, or > if sections of the full score are compiled without having a notion of >

Re: OT: Using built-in ghostscript by itself

2016-03-03 Thread Sharon Rosner
> I couldn't figure it out. When I call [LP_dir]/usr/bin/gs.exe I get the > error that it can't find gs_init.ps which is located in > [LP_dir]/usr/share/ghostscript/9.15/Resource/Init/. How do I tell gs.exe > where to find its files? Am I even using the right command? Possible answer here: htt