| Re: [frogs] Enhancement request: Define output-suffix as a configurable context property. |
[ Thread Index |
Date Index
| More lilynet.net/frogs Archives
]
- To: frogs@xxxxxxxxxxx
- Subject: Re: [frogs] Enhancement request: Define output-suffix as a configurable context property.
- From: Patrick McCarty <pnorcks@xxxxxxxxx>
- Date: Mon, 21 Sep 2009 13:54:50 -0700
- Cc: "lilypond-devel@xxxxxxx" <lilypond-devel@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aX1uBYs8gdz4N/B9rGxJL78XALdpFn2xl8DUienq9co=; b=U8dtG9ApZqlXayhn/oQI+7eKePVqdysbgHaFcGa9JPXoThJuR3RYBOrXlAIuILXzXM Ac+6lu/m/IBc5rZepUoUSRgpy5sn0cEUP4WPNoZop6KNyDpnW2vOscluelDp4Viaw0UD 8gihXO9oE7kI8h44gY1NxWK2PhyhvAlMtc1DY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Y9IQwXn884KGm7cAJp6W2jGYxQMaREyTw1iPoUWLF0OenDxWlv/t6dv01gh53BZ6WT m766FdTLL8CAznCt+3NzS7Dx+BS530q/buWuzj97czYSD6s9jAtjbsb7to+WeQCkpvvt OTBri4dycHUqZo5yN4xfpNGdJYC22SUTXXfHo=
On Mon, Sep 21, 2009 at 1:48 PM, Carl Sorensen <c_sorensen@xxxxxxx> wrote:
>
> On 9/21/09 2:38 PM, "Neil Puttock" <n.puttock@xxxxxxxxx> wrote:
>
>> 2009/9/19 Carl Sorensen <c_sorensen@xxxxxxx>:
>>
>>> Well, during the translation step the translators write output to the output
>>> file using the appropriate output calls, don't they? So they make use of
>>> the file that was created using the output-prefix. So this has *something*
>>> to do with translation, even though it's not a characteristic of an
>>> engraver.
>>
>> I don't think so, since the output file doesn't exist until a
>> Paper_book object has been finalized and sent to the appropriate
>> output framework.
>
> OK, so what sends Paper_book objects to output frameworks?
I think this occurs in Paper_book::output(), line 183.
The self_scm() call applies to the Paper_book object, and this object
becomes the 2nd argument in the call to output-framework. Thus the
output frameworks have access to the Paper_book object.
-Patrick
---
----
Join the Frogs!