bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apply @code{} to two instances of `\book` in NR


From: Jean Abou Samra
Subject: Re: Apply @code{} to two instances of `\book` in NR
Date: Tue, 28 Mar 2023 08:56:17 +0200
User-agent: Evolution 3.46.4 (3.46.4-1.fc37)

Jason,

Le lundi 27 mars 2023 à 22:35 -0500, Jason Yip via bug-lilypond a écrit :
> In NR 3.2.1 "Structure of a score", 2 references to the `\book` command  
> are not in a `@code{}` command in the 2nd last paragraph.
> 
> 
> diff --git a/Documentation/en/notation/input.itely  
> b/Documentation/en/notation/input.itely  
> index f7a6ea6..9e7bfd3 100644  
> --- a/Documentation/en/notation/input.itely  
> +++ b/Documentation/en/notation/input.itely  
> @@ -235,7 +235,7 @@ block, and inside or outside the single music  
> expression within a  
>   @code{\score} block.
> 
>   Remember that even in a file containing only a @code{\score} block, it  
> -is implicitly enclosed in a \book block.  A \book block in a source  
> +is implicitly enclosed in a @code{\book} block.  A @code{\book} block  
> in a source  
>   file produces at least one output file, and by default the name of the  
>   output file produced is derived from the name of the input file, so  
>   @file{fandangoforelephants.ly} will produce


The (old) instructions given in the Contributor's Guide are intended to make it 
easy for non-technical people to contribute to the documentation.

If you are comfortable with GitLab, it is much simpler to submit a merge 
request.

Best,

Jean

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]