Done!
/Mats
Graham Percival wrote:
Mats Bengtsson wrote:
I hope you don't mind if I modify the
text and remove the current first paragraph under Windows.
Please do. In general, feel free to change anything relating to
Windows stuff (installation, font-specific information) and anything
Sorry to come back to this one, but I just noticed that the current text
on Windows in Compiling a file isn't really coherent, since it first
mentions
start-up a text editor and then later describes how to do the same
thing with
the text editor bundled with LilyPond. I hope you don't mind if I
Mats Bengtsson wrote:
I hope you don't mind if I modify
the
text and remove the current first paragraph under Windows.
Please do. In general, feel free to change anything relating to Windows
stuff (installation, font-specific information) and anything in chapter
7. Since I don't have any
Such an overview of different editors, should of course also mention the
simple text editors included in the LilyPond distribution for Mac and
Windows.
/Mats
Graham Percival wrote:
Bertalan Fodor wrote:
Ok, I'm happy to do this. But what should I write about emacs, vim
etc? Should I write
Ok, I'm happy to do this. But what should I write about emacs, vim etc?
Should I write about configuration, or link to the manual?
Bert
So spend 30 minutes and create a general editor webpage for lilypond.
If you omit emacs or vim you'll probably have a riot, but you only
need one paragraph
Graham Percival wrote:
We don't _have_ a webpage about editors. At least, not that I'm aware
of.
How about Section 13.6 Editor support?
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Mats Bengtsson wrote:
Graham Percival wrote:
We don't _have_ a webpage about editors. At least, not that I'm aware
of.
How about Section 13.6 Editor support?
That's part of the manual, not the docs. I'd like to remove that
section and point to a nice, colorful webpage instead.
Cheers,
Bertalan Fodor wrote:
Ok, I'm happy to do this. But what should I write about emacs, vim etc?
Should I write about configuration, or link to the manual?
I don't know. How about you start with the info currently in the manual
(then nobody can complain that we're deleting info). If you think
Mats Bengtsson wrote:
\chords {...} is just a shorthand for \new ChordNames \chordmode {...}
just as \figures{...} is a shorthand for \new FiguredBass \figuremode and
similarly for \drums and \lyrics. See also
http://lists.gnu.org/archive/html/lilypond-devel/2006-04/msg00332.html
Without really
On 23/01/07, Graham Percival [EMAIL PROTECTED] wrote:
The rewritten tutorial is online,
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Tutorial
Could a few people proofread it? In the near future the translation
teams will be working on it, so it would be good if we finalized node
Alard de Boer wrote:
The tutorial is great! Some minor comments:
2.1.1 second footnote: These easiest - The easiest
2.1.1 Section MacOS X, 2nd par: lilypond - LilyPond (all other uses
except the Unix command line have the two capital letters)
2.3.1 3rd paragraph: means that are - means that
Graham Percival wrote:
Mats Bengtsson wrote:
- The instructions for Windows need some polishing. Basically,
you could more or less the same as on Mac, namely double-click
the LilyPond icon on the desktop to start a simple text editor.
I can come back with more details when I have a
Finally, it's probably a good idea to add a footnote with a link to
some overview
of different text editors, since the one supplied with LilyPond on
Windows and
probably also on Mac is fairly rudimentary. This should replace the
current
footnote 1.
I don't think it should be a footnote.
Bertalan Fodor wrote:
Finally, it's probably a good idea to add a footnote with a link to
some overview
of different text editors, since the one supplied with LilyPond on
Windows and
probably also on Mac is fairly rudimentary. This should replace the
current
footnote 1.
I don't think it
Mats Bengtsson wrote:
Some more information that might be worth adding already in the tutorial
(again specifically for Windows):
Thanks, I did all these updates.
Finally, it's probably a good idea to add a footnote with a link to some
overview
of different text editors, since the one
Bertalan Fodor wrote:
I don't think it should be in the manual at all; I'd prefer this info
to be on the webpages.
Ok, but the link to the webpage about editors should be at an emphasized
place in the doc.
We don't _have_ a webpage about editors. At least, not that I'm aware of.
Cheers,
-
Well, we have a webpage about at least one quite good editor:
http://lilypondtool.organum.hu ;-)
Graham Percival írta:
Bertalan Fodor wrote:
I don't think it should be in the manual at all; I'd prefer this
info to be on the webpages.
Ok, but the link to the webpage about editors should be
Bertalan Fodor wrote:
Well, we have a webpage about at least one quite good editor:
http://lilypondtool.organum.hu ;-)
So spend 30 minutes and create a general editor webpage for lilypond.
If you omit emacs or vim you'll probably have a riot, but you only need
one paragraph about each. Then
The rewritten tutorial is online,
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Tutorial
Could a few people proofread it? In the near future the translation
teams will be working on it, so it would be good if we finalized node
names and caught any major mistakes.
Cheers,
-
Thanks for all your ambituous documentation updates!
I've just looked at the first few pages, but have a couple of comments:
- The cut--pastable-section of the first example contains lots
of lines that are just confusing and should never be included
in a stand-alone .ly file. Maybe it's
Mats Bengtsson wrote:
- The cut--pastable-section of the first example contains lots
of lines that are just confusing and should never be included
in a stand-alone .ly file. Maybe it's better to not use the fragment
option of lilypond-book and recommend the reader to only
cut the lines after
21 matches
Mail list logo
