On Tue, 22 Apr 2008 00:29:14 +0200
John Mandereau <[EMAIL PROTECTED]> wrote:
> I don't know whether you already decided to do so, but why not make
> everyone happy with keeping the current big list sorted alphabetically
> among the appendices, and considering the new splitted lists as an
> additio
Valentin Villenave wrote:
> - Then I told him: "the huge Appendix page is really hard to use right
> now. Neil can add examples but this wont make browsing it easier". So,
> I tried to figure out a way to sort these commands and make them
> easier to find -- and Mats, you may find it less usable; j
On Fri, 18 Apr 2008 14:10:47 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/4/18 Mats Bengtsson <[EMAIL PROTECTED]>:
>
> > Please note that the current "Global" list is not the full list,
Sorry. I definitely wasn't paying attention.
> > If all the different categories (subsecti
2008/4/18 Mats Bengtsson <[EMAIL PROTECTED]>:
> Please note that the current "Global" list is not the full list, it's just
> the ones
> that so far haven't been sorted into the different categories, as far as I
> can see.
> If all the different categories (subsections!?) end up on the same HTML
Graham Percival wrote:
That's why I said that we're keeping the "all markup commands" --
people who like the entire list can see that, while people who
only want to see "alignment issues" can see that list.
...
I think that "common" is supposed to be "formatting text". It
certainly shoul
On Fri, 18 Apr 2008 13:14:03 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> I'm not fully convinced that I agree, especially if we talk about the
> on-line version of
> the manual, since you now will have to figure out which of all the
> different HTML
> pages you should look at.
That's why
John Mandereau wrote:
Valentin Villenave wrote:
OK. Graham, I did implement something that could be useful -- or not.
It's not very elegant, but at least it doesn't break anything.
Here's a patch, in case you'd like to check it out:
http://valentin.villenave.info/lilypond/new_markup_docs.p
John Mandereau wrote
Valentin Villenave wrote:
OK. Graham, I did implement something that could be useful -- or not.
It's not very elegant, but at least it doesn't break anything.
Here's a patch, in case you'd like to check it out:
http://valentin.villenave.info/lilypond/new_markup_docs.patch
On 17/04/2008, Graham Percival <[EMAIL PROTECTED]> wrote:
> On Thu, 17 Apr 2008 19:09:35 +0200
>
> "Valentin Villenave" <[EMAIL PROTECTED]> wrote:
>
>
> > OK. Graham, I did implement something that could be useful -- or not.
> > It's not very elegant, but at least it doesn't break anything.
> >
>
Valentin Villenave wrote:
> OK. Graham, I did implement something that could be useful -- or not.
> It's not very elegant, but at least it doesn't break anything.
>
> Here's a patch, in case you'd like to check it out:
> http://valentin.villenave.info/lilypond/new_markup_docs.patch
>
> Here's wha
On Thu, 17 Apr 2008 19:09:35 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> OK. Graham, I did implement something that could be useful -- or not.
> It's not very elegant, but at least it doesn't break anything.
>
> Here's what it looks like (look at the appendix):
> http://valentin.ville
2008/4/6 Graham Percival <[EMAIL PROTECTED]>:
> Hey, scheme guys: how hard would it be to introduce our own sorting to
> B.6 ? scm/document-markup.scm contains this:
[...]
> which sorts things alphabetically. Could we instead group things by
> function... ideally with our own headings? ie
On Sun, 6 Apr 2008 11:05:52 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> * 1.8.2 Formatting text
> o 1.8.2.1 Introduction to markup mode
> ( \markup basics; basic text alignment)
> o 1.8.2.2 Common markup commands
>
On Sun, 6 Apr 2008 11:05:52 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> - how can I put @lilypond examples to document these features? Do I
> need to use \book? Is there a way to prevent lilypond-book to add the
> usual header around my code?
RTFGDPTXT.
@lilypond[quote,ragged-right,v
Le 6 avr. 08 à 11:05, Valentin Villenave a écrit :
- I need some suggestions on how to document \markuplines vs \markup.
The question behind it being: Nicolas, is the \markuplines syntax
likely to change? e.g. could, at some point, \markuplines be included
in \markup blocks? Is \markuplines a su
Hi everybody, hi Graham, hi Nicolas, hi Neil, hi Trevor,
As you may have noticed (or not), the NR1.8 Text section is going
through several major changes.
##
1- I have added a new subsection in Text, called "Separate text":
http://kainhofer.com/~lilypond/Documentation/user/li
16 matches
Mail list logo
