Re: Translation string problem

[Carl D. Sorensen]

On 12/9/08 4:38 PM, "Francisco Vila" <address@hidden> wrote:

> 2008/12/9 Jean-Charles Malahieude <address@hidden>:
>> Le 09.12.2008 21:55, Francisco Vila disait :
>>> 
>>> 2008/12/9 Francisco Vila:
>>>>> 
>>>>> Yes, let's use @c KEEP LY, a good solution.
>>>> 
>>>> I've done this adding a comment:
>>>> 
>>>> 
>>>> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=6d7edb962
>>>> 644c9b657f88d8bfe5b480494996f94
>>> 
>>> I am doing something badly, as the verbatim output insists on being
>>> translated despite of the KEEP LY. What are your results?
>>> 
>> 
>> I've found an "intermediate" way, which consists in doubling the snippet:
>> 
>> 1) it becomes an @example
>> 2) the @lilypond loses its verbatim option
>> 
>> The only nuisance is that we then obtain two frames: one for the "example"
>> and one for the "image". We might add a simple sentence between them in
>> order to "make the linkage".
> 
> That is easy, but I still don't understand why a KEEPt snippet suffers
> an undesired translation. The image link points to the real (kept)
> code, which is what should appear shown as verbatim.
> 
> Maybe when John finds the time he could fix it.
> 
> Trevor, I think the idea from Jean-Charles would serve now and forever
> in any case. Could you compose it, including the glue paragraph?

Oh, I hope we can find another way.  I hate the thought of keeping
@example around, and having to make sure that the code is the same in both
the @example piece and the @lilypond piece.

Thanks,


Carl