Tool for automatic pointing of psalm texts for the traditional formulae of Gregorian chant psalmody.
Problem and it's solutions
When preparing booklets for chanted Divine Office, you probably have to - unless your schola is extremely skilled in Latin and psalmody - deal with pointing of the psalm texts.
- You can do so manually, which is a boring, tedious, error-prone task.
- You can use Benjamin Bloomfields online Psalm Tone Tool, which will also generate notated first verse for you
- or you can use pslm
gem install pslm
Take prepared psalm texts
- Latin texts prepared by me
- Latin texts further extended by Jakub Jelínek
- Czech texts (from Denní modlitba církve)
Or prepare your own
pslm executable and it's invocation
pslm path/to/ps109.pslmBy default pslm formats the psalm for LaTeX and prints the output to standard output. You can redirect the output to a file using your shell's capabilities or by means of the
pslm -o ps109.tex path/to/ps109.pslm
LaTeX output - is default
pointing for a given tone -
pslm -t VII.a path/to/ps109.pslmPslm knows a basic set of psalm tones (based on 196x books) by name.
pointing for custom tone
pslm -a 2:2 -p 0:0 path/to/ps109.pslmIf your favourite tone isn't supported or you don't like the default psalm tone set, you can specify number of accentuated (
-a) and preparatory (
-p) syllables in each half-verse.
pslm -s underline path/to/ps109.pslmto underline accentuated syllables,
pslm -s bold path/to/ps109.pslmto make them bold
print to console with highlighting
pslm -f console path/to/ps109.pslm(for geeks who prefer to chant psalms from the terminal :) )
print all available options
Use pslm when programming your own build tool
Especially if you use build scripts written in Ruby it may be
more convenient to gain better control over
pslm by using
the underlying Ruby library directly instead of invoking
TODO add examples
I once wrote psalmpreprocessor as a relatively simple ad-hoc sollution; then I extended it step by step. It was ugly and dirty at the beginning and got only dirtier. Then I restructured it, but it didn't get much cleaner. Then I needed it for another, quite different typesetting project. ...
Years later I decided to make a standalone gem with the same (and some additional) functionality. (Hey, there is a bug in psalmpreprocessor.rb. I want to fix it. In a few weeks I should deliver that book for which the bug should be fixed. It means I don't want to break anything. It means I want to be secured by automatic tests. But psalmpreprocessor isn't easily unit-testable. ...)