Am 11.02.2018 um 11:19 schrieb Gregrs:
Hi Simon,

On Sat, Feb 10, 2018 at 07:01:52PM +0100, Simon Albrecht wrote:

Looks nice, thanks for sharing!
Did you consider using Urs’ lilyglyphs package for the dynamics? Of course that would require compiling with xelatex or lualatex…

Thanks. I wanted to use plain LaTeX but using the lilyglyphs package would certainly be a nice option for the dynamics, and not having to consider what the bold italic variant of a font looks like for the dynamics would allow a greater range of fonts for the text.

I've just experimented with this, and for anyone wanting to try this out, you'd need to do the following:

In psalm.ltx add \usepackage{fontspec} and \usepackage{lilyglyphs}, and in \includegraphics, change the resolution and scale options to just scale=0.1164.

In psalm.sty, change the definition of \dyn to \lilyDynamics{#1}.

In Makefile, change pdflatex to xelatex.

I've added a xelatex branch to the GitHub repository with these changes but I think I'll stick with LaTeX as the default option for now.

Reading your reply I don't think that's an option, but I wanted to throw yet anothe tool into the mix: if LuaLaTeX would be acceptable as a requirement it would be possible to realize that in LaTeX, using lyluatex (https://github.com/jperon/lyluatex) to manage included LilyPond code. Probably it would be even possible to prepare a Pandoc template (see https://github.com/jperon/lyluatex/issues/64) and then write the files in Markdown. (Please don't look at the package as included in TeXLive, that version is essentially a first shot and the package is currently under heavy development, with a comprehensive release to be expected soon.)

Best
Urs


Thanks,
Greg



_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to