Graham Percival wrote:
>>> Oh, sorry. I misread your comment as linking the two...
>>> yes, all @lilypond should have [quote].
>>
>> Well, not *all* @lilypond instances. Certainly [quote]
>> would be bad inside a table. I'm thinking of NR A.2
>> "Common chord modifiers" or NR B. "Cheat sheet".
>
On Sun, Sep 26, 2010 at 05:53:15PM -0700, Mark Polesky wrote:
> Graham Percival wrote:
> > Oh, sorry. I misread your comment as linking the two...
> > yes, all @lilypond should have [quote].
>
> Well, not *all* @lilypond instances. Certainly [quote]
> would be bad inside a table. I'm thinking o
Graham Percival wrote:
> Oh, sorry. I misread your comment as linking the two...
> yes, all @lilypond should have [quote].
Well, not *all* @lilypond instances. Certainly [quote]
would be bad inside a table. I'm thinking of
NR A.2 "Common chord modifiers" or
NR B. "Cheat sheet".
- Mark
On Sun, Sep 26, 2010 at 8:05 PM, Mark Polesky wrote:
> Also, while we're here, we might as well update our
> texinfo.tex file, right? It's more than a year out of date.
> Compare the two:
> http://cvs.savannah.gnu.org/viewvc/*checkout*/texinfo/doc/texinfo.tex?root=texinfo&content-type=text%2Fpla
On Sun, Sep 26, 2010 at 8:14 PM, Mark Polesky wrote:
> Graham Percival wrote:
>>> Should I just replace "fragment" with "quote", or are
>>> there reasons to keep "fragment"?
>>
>> No, because [quote] means [indent this image]...
>
> Did you look at the examples in the html? I think they
> should
Graham Percival wrote:
>> Should I just replace "fragment" with "quote", or are
>> there reasons to keep "fragment"?
>
> No, because [quote] means [indent this image]...
Did you look at the examples in the html? I think they
should all be indented, no?
- Mark
_
Mark Polesky wrote:
> This work may have already been done by the texinfo
> developers; I told them about it some months ago. IIRC,
> the @w trick works for info and pdf, and the html version
> is fixed in the texinfo sources, but I don't think they've
> released a stable version that includes tha
On Sun, Sep 26, 2010 at 7:47 PM, Mark Polesky wrote:
> David Kastrup wrote:
>> The code is likely a one-liner if done correctly, but I
>> already spent 10 minutes digging through the details.
>>
>> So I'll turn to wait mode right now.
ok.
> This work may have already been done by the texinfo
> d
Reviewers: Neil Puttock, Patrick McCarty, carl.d.sorensen_gmail.com,
hanwenn,
Message:
On 2010/09/25 22:07:53, Neil Puttock wrote:
Hi Ian,
Can you upload a revised patchset without all the tab->space changes
please?
Working ...
I'm not sure about gutting guile-compatibility.hh: as part
On Sun, Sep 26, 2010 at 7:39 PM, Mark Polesky wrote:
> changing-defaults.itely:2497
> changing-defaults.itely:2552
> changing-defaults.itely:2966
> changing-defaults.itely:2983
These are untouched from GDP.
> rhythms.itely:1342
delete [frament]
> rhythms.itely:1354
delete [fragment]
> rhythm
David Kastrup wrote:
>>> Should be easy enough to do for the TeX backends,
>>> effectively wrapping every @code inside of a @w. Is
>>> that desirable?
>>
>> I consider it desirable, but I'm not the only person
>> involved. :) Maybe wait a few days before doing a lot of
>> work, in case anybody co
I found some suspicious instances of @lilypond[fragment,...]
that were missing the "quote" option:
$ cd Documenation/notation
$ git grep -n -e "@lilypond\[.*fragment.*\]" --and \
--not -e quote -- changing-defaults.itely rhythms.itely
changing-defaults.itely:2497
changing-defaults.itely:2552
ch
Graham Percival writes:
> On Sun, Sep 26, 2010 at 07:43:36PM +0200, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > I expect that there's a mechanism our texinfo.tex to do this.
>>
>> Should be easy enough to do for the TeX backends, effectively wrapping
>> every @code inside of a @w.
On Sun, Sep 26, 2010 at 07:43:36PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > I expect that there's a mechanism our texinfo.tex to do this.
>
> Should be easy enough to do for the TeX backends, effectively wrapping
> every @code inside of a @w. Is that desirable?
I consider it
Graham Percival writes:
> On Sun, Sep 26, 2010 at 07:29:26PM +0200, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > Nope; we get line breaks in stuff like @code{\override
>> > Voice.textscript #'padding = #3}. :(
>> >
>> > I'm not certain whether this constitutes a bug with texinfo its
On Sun, Sep 26, 2010 at 07:29:26PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > Nope; we get line breaks in stuff like @code{\override
> > Voice.textscript #'padding = #3}. :(
> >
> > I'm not certain whether this constitutes a bug with texinfo itself
> > (i.e. I'm not going to arg
Graham Percival writes:
> On Sun, Sep 26, 2010 at 08:31:10AM +0200, David Kastrup wrote:
>> Mark Polesky writes:
>>
>> > +Use the @code{@@c...@{@dot...@}} command when referring to
>> > +individual language-specific tokens (keywords, commands,
>> > +engravers, scheme symbols, etc.) in the text.
LGTM, although I didn't check that it still compiles.
http://codereview.appspot.com/2217046/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
http://codereview.appspot.com/2217046/diff/1/Documentation/notation/pitches.itely#newcode142
Documentation/n
On Sun, Sep 26, 2010 at 08:31:10AM +0200, David Kastrup wrote:
> Mark Polesky writes:
>
> > +Use the @code{@@c...@{@dot...@}} command when referring to
> > +individual language-specific tokens (keywords, commands,
> > +engravers, scheme symbols, etc.) in the text. Ideally, a single
> > +...@code
On Sun, Sep 26, 2010 at 11:42:55AM +0200, Marc Hohl wrote:
> I opened both files in an editor and compared. In the english
> source, I found two consecutive
> @divEnd-entries at line 141 and 143. If this is intended, the
> following patch does the same
> for the german translation.
Each @divClass{
On 26 September 2010 12:09, Xavier Scheuer wrote:
> MetronomeMark #'break-align-symbols seems to fail with everything
> (clef, left-edge, staff-bar, ...) except key-signature and
> time-signature
I'm afraid this is partly due to the way I fixed the bad alignment
when key signatures are present (
Hi all,
When this gets fixed, I'm happy to up my sponsorship by C$50 -- this has
definitely turned out to be more work than it first appeared.
Thanks,
Kieren.
On 2010-Sep-26, at 08:43, Carl Sorensen wrote:
>
>
>
> On 9/26/10 5:09 AM, "Xavier Scheuer" wrote:
>
>> Hi Jan!
>>
>> No, I'm *no
On 9/26/10 5:09 AM, "Xavier Scheuer" wrote:
> Hi Jan!
>
> No, I'm *not* obsessed with Tempo indications placement
> (or maybe, am I?)... ;-p
> Actually this time the issue was reported on the French-speaking
> mailing list, I'm just relaying it.
>
> MetronomeMark #'break-align-symbols seem
Hi Jan!
No, I'm *not* obsessed with Tempo indications placement
(or maybe, am I?)... ;-p
Actually this time the issue was reported on the French-speaking
mailing list, I'm just relaying it.
MetronomeMark #'break-align-symbols seems to fail with everything
(clef, left-edge, staff-bar, ...) excep
On 2010/09/26 00:00:27, Neil Puttock wrote:
On 2010/09/25 23:39:33, ianhulin44 wrote:
> Looking at warn.cc I can see ly:progress and ly:message are
synonymous.
ly:message always starts on a new line.
ly:progress calls progress_indication () directly, which has this
comment above
it:
Graham Percival schrieb:
On Fri, Sep 24, 2010 at 10:59:18AM +0200, Marc Hohl wrote:
Graham Percival schrieb:
2) website has been switched over. At first glance, I think I can
close issue 1244 now, but I want to double-check and wait for
feedback.
The menu bar is misplaced here,
While working with the new spacing settings, I think I found
some typos.
In general, the names of variables should not be translated within
code examples, otherwise cut&paste does not work anymore.
Marc
From eab315b158dc295fd1234eae4966e822e32709af Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date:
Reviewers: ,
Message:
Anyone want to double-check this doc patch?
Just trying to clean up the NR a little bit
in light of recent discussions on -devel.
Thanks
- Mark
Description:
Doc: NR 1: Use @co...@var{...}} for variables.
Please review this at http://codereview.appspot.com/2217046/
Affec
28 matches
Mail list logo
