ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: andrea valle <valle@di.unito.it>
Subject: lilypond inclusion + pdf crop
Date: Fri, 16 Sep 2005 16:13:33 +0200	[thread overview]
Message-ID: <4cb3b40c6ad7bd94817da990d820bc60@di.unito.it> (raw)
In-Reply-To: <34FA5046-6B82-41A7-9C7C-7187B6AAAAD2@fiee.net>

>
> How did you get your LilyPond fragments?
> The only way I know would be to cut them from whole PDF pages with 
> Acrobat.

Ah, I understand the point.
Yes, in my new composition I create a graph connecting some musical 
fragment (I don't wanna bore yuo too much with these details). In any 
case, I use Context as general typesetting environment, Metafun as 
vectorial, scalable, scriptable drawing engine, and lilypond as 
notation generator.
The idea is to produce lily files, to render them, to include them in a 
metafun drawing, where I can clip and place them opportunely, and to 
render context files. My program is written in Python.

But, it's true, I got involved in the problem of cropping PDFs output 
by lily (from the a6 format I chose). I solved using externalfigure 
clip in metafun.
I tried Imagemagik: it crops the PDFs but it seems that it rasterizes 
the image.
So, what can one use to crop a pdf? Preview in macosx, as acrobat, does 
the job, but I'd prefer too to use something from the command line.

> But I'm only a newbie (and I don't really feel like learning Scheme).
I don't want, too. I'd like to have python :)

Here are two of the resulting scores (not totally finished yet)
www.semiotiche.it/andrea/membrana/nodi-I.pdf
www.semiotiche.it/andrea/membrana/nodi-II.pdf

and one of the context file
www.semiotiche.it/andrea/membrana/nodi-I.tex

Best

-a-

PS: ah, thanks to the list, without support I won't be able to draw a 
line...

  reply	other threads:[~2005-09-16 14:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15  9:49 lilypond inclusion Christopher Creutzig
2005-09-15 10:35 ` Hans Hagen
2005-09-15 13:07   ` Christopher Creutzig
2005-09-15 13:53     ` Hans Hagen
2005-09-15 14:34 ` Henning Hraban Ramm
2005-09-15 21:00   ` andrea valle
2005-09-16  0:37     ` Henning Hraban Ramm
2005-09-16 14:13       ` andrea valle [this message]
2005-09-16 15:25         ` [OT] lilypond inclusion + pdf crop luigi.scarso
2005-09-16 15:29         ` Hans Hagen
2005-09-16 17:18           ` Willi Egger
2005-09-16 21:08           ` andrea valle
2005-09-18 19:38             ` Hans Hagen
2005-09-19  9:51               ` Taco Hoekwater
2005-09-17 11:26           ` Christopher Creutzig
2005-09-17 13:23             ` andrea valle
2005-09-16 16:23         ` lilypond inclusion + pdf crop (getting off-topic) Adam Lindsay
2005-09-16 17:37           ` Hans Hagen
2005-09-17  9:28             ` Re[2]: " Giuseppe Bilotta
2005-09-18 18:23               ` Hans Hagen
2005-09-18 19:19                 ` Re[2]: " Giuseppe Bilotta
2005-09-16 15:40     ` lilypond inclusion Christopher Creutzig
2005-09-16 16:10       ` andrea valle
2005-09-16 15:42   ` Christopher Creutzig
2005-09-16 16:39     ` Patrick Gundlach
2005-09-16 16:56 ` Mojca Miklavec
2005-09-16 17:45   ` Hans Hagen
2005-09-16 18:51   ` Christopher Creutzig
2005-09-16 19:20     ` Mojca Miklavec
2005-09-16 19:45       ` Hans Hagen
2005-09-16 20:25         ` Mojca Miklavec
2005-09-18 18:07           ` Hans Hagen
2005-09-16 20:46       ` Christopher Creutzig
2005-09-18 18:09         ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4cb3b40c6ad7bd94817da990d820bc60@di.unito.it \
    --to=valle@di.unito.it \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).