You can produce images from the Source and Summit editor. Apple Pages treats the PDF as something to be dragged and dropped just like a JPEG, PNG etc. Otherwise, I just do it all in LaTeX myself and cut out the intermediate steps.

When I care about the end product looking really nice and having a consistent style, I use LaTeX and put the GABC straight into the code.

If I'm just doing something fast and sloppy, I'll export pdfs or pngs from source and summit editor. I'll put the pngs in a google doc if I need to arrange them with text or other pictures.

Or sometimes I'll use scribus.

> This page will convert from pdf to jpeg:

Probably don't want jpegs for print-destined material. PNG or TIFF are gonna end up looking better.

---

I don't *exactly* remember how I did it, but I used to make nice looking bulletins for a (weird) monastic community more-or-less as follows:

- prayer "script" in a markdown file, with insert tags referencing gabc files for chants (or maybe they referenced names of rendered png images?)
- chants in individual gabc files
- a bash script that called gregorio to render the chants and then pandoc to render the markdown and spit out a pdf all in one go

(I played around with also being able to incorporate lilypond files as well, but it was too complicated for me at the time [this was before I got good at coding... i think it's probablt doable] and so I just did everything in four-line notation even if it wasn't really Gregorian in nature (everything was un-metered -- like we did some Orthodox chant and similar things -- so it still worked, even if under other circumstances I might have done five line stemless round notes)

I *think* I still have the files and scripts somewhere so if this approach sounds helpful I can look for them and share more specific details.

In MS, I have a file which I duplicate and then modify. I find the style aspects rather painful. I export as a PDF, which looks pretty good when added in LaTeX with graphicx (these images don’t break over pages so you have to play with scaling, and between my printer and a pesky bug in macOS Preview, the file scales incorrectly but with my parish printer, it’s fine). I am chaotic and print on full sheets, so this trick may be less appealing if you use folded letter paper. (Folded legal is better anyway.) You could print on folded paper too, I just don’t need to do that luckily.

For example, for Benediction, I inserted the usual hymn melodies for weeknights per annum here (we do melodies from the Gregorian repertoire after Vespers and in the other seasons.)

Playing around with the scale and other settings worked pretty well.

To OMM’s point: Matthias Bry (who is doing the new nocturnale) convinced me to just use LaTeX. I tried something else for the Laus in Ecclesia score book, and I said “forget it…”.

Also, I repeat that Source and Summit doesn’t use Gregorio now, it uses gabc but those aren’t strictly the same, so as a result, it doesn’t support features of gabc introduced later on (notably suppressing the custos and control over EUOUAE). It’s good for quick checks that your own transcription is correct.

But since we’re advocating for the best, reiterating this point is necessary.

I should add by the way that if you use gabc, and if it doesn’t work but everything looks right online, check that there are no invisible characters that don’t belong. I’ve had some strange errors (maybe due to my workflow on macOS where typing characters like “æ”, including the accented version with Unicode entry, is easy with find and replace but where I won’t see, obviously, an incorrect invisible character…)

@lmassery Inkscape also takes PDFs, and then you can save vector graphic files as I describe

That’s the other big thing. I focus on the non-chant things as an advantage, but of course, being able to tweak the score itself, the annotations, etc. is huge.