Le mercredi 02 avril 2008 à 15:46 -0300, Han-Wen Nienhuys a écrit :
> 2008/4/2, Francisco Vila <[EMAIL PROTECTED]>:
> > [tex / ps output and '-' input]
> The '-' for stdin was a nice idea, but I haven't ever heard anyone use
> it, and it complicates file name handling. I vote for scrapping it.
> we used to output to .tex; when we switched to PS, Werner asked me
> to retain some tex functionality. It hasn't been used since. If it
> is broken, we should remove it.
I agree. LilyPond has become powerful enough to no longer need a TeX
interface.
Werner
___
2008/4/2, Francisco Vila <[EMAIL PROTECTED]>:
> [tex / ps output and '-' input]
Hi,
we used to output to .tex; when we switched to PS, Werner asked me to
retain some tex functionality. It hasn't been used since. If it is
broken, we should remove it.
The '-' for stdin was a nice idea, but I h
On Wed, 2 Apr 2008 18:13:24 +0200
"Francisco Vila" <[EMAIL PROTECTED]> wrote:
> I could send three separate messages for these, but I wonder that the
> response is simply that "program usage is outdated" for all three.
>
> I could update it if only I knew
nd/usr/share/lilypond/current/scm/framework-tex.scm:197:26:
While evaluating arguments to last-pair in expression (last-pair
pages):
/usr/local/lilypond/usr/share/lilypond/current/scm/framework-tex.scm:197:26:
Unbound variable: pages
I could send three separate messages for these, but I wonder tha
Le 03.11.2007 13:35, John Mandereau disait :
Le samedi 03 novembre 2007 à 00:42 -0700, Graham Percival a écrit :
There are four manuals about LilyPond: the @emph{Learning Manual},
the @emph{Notation Reference}, the @emph{Program Usage}, and the
@emph{Program Reference}.
This is
Le samedi 03 novembre 2007 à 00:42 -0700, Graham Percival a écrit :
>
> There are four manuals about LilyPond: the @emph{Learning Manual},
> the @emph{Notation Reference}, the @emph{Program Usage}, and the
> @emph{Program Reference}.
>
>
> This is somewhat confusing
There are four manuals about LilyPond: the @emph{Learning Manual},
the @emph{Notation Reference}, the @emph{Program Usage}, and the
@emph{Program Reference}.
This is somewhat confusing, since there are two very different manuals
whose name both begins with "Program".
Do
Till Rettig wrote:
John Mandereau wrote:
I seems that running.itely has not been revised for ages, so it contains
somewhat outdated info. If you feel comfortable with updating this
section in the English docs, please do it first, then go on translating
this file; otherwise, it may be more pro
John Mandereau wrote:
I seems that running.itely has not been revised for ages, so it contains
somewhat outdated info. If you feel comfortable with updating this
section in the English docs, please do it first, then go on translating
this file; otherwise, it may be more productive to give up t
Le mardi 18 septembre 2007 à 22:06 +0300, Till Rettig a écrit :
> Hi,
>
> while translating the running.itely I stumbled on the section 3.2.1 --
> invoking lilypond. Why are there .tex files and why should files with
> different \scores get output to numbered files? I have not yet heard
> about
Hi,
while translating the running.itely I stumbled on the section 3.2.1 --
invoking lilypond. Why are there .tex files and why should files with
different \scores get output to numbered files? I have not yet heard
about this, couldn't we tell it in a way, that I know what to translate?
To me
Till Rettig wrote:
I would suggest to remove lines 46 to 48 from
Documentation/user/setup.itely.
They are repetition of two lines earlier.
I don't think that this repetition is harmful; some OSX users are very
unfamiliar with unix, so pointing this out could be useful for some of them.
Ch
Hi,
I would suggest to remove lines 46 to 48 from
Documentation/user/setup.itely.
They are repetition of two lines earlier.
Greetings
Till
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Graham Percival escreveu:
> I think the Program Usage manual is good now. Anybody have any comments
> before the translators start working on it? It's on the web now in the
> 2.11.31 docs.
Replace lilypondtool -> jedit in the node name.
--
Han-Wen Nienhuys - [EMAIL
I think the Program Usage manual is good now. Anybody have any comments
before the translators start working on it? It's on the web now in the
2.11.31 docs.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
thinking of node names in particular -- when I'm
> working on big doc changes, I'll create new nodes, work on the
> section(s), change some node names, remove some nodes that I created a
> week ago, etc.
There is no problem with this: translators have the tools to handle
this, and t
eatest possible number of
bugs. I hope you can start working on the program usage docs with a
working infrastructure :-)
Thanks, it's working great!
In general I like to make multiple small changes (ie make many patches,
spread over a series of days). Will this cause a problem for the
un make and 'make web'
and check the docs, in order to fix the greatest possible number of
bugs. I hope you can start working on the program usage docs with a
working infrastructure :-)
Cheers,
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Le jeudi 26 juillet 2007 à 21:46 -0700, Graham Percival a écrit :
> John, I think you're quite familiar with our build system and whatnot
> from all the translation stuff -- could you create the basic framework
> for this? Once it's there, I'll rewrite the INSTALL, potentially add
> chapters, p
Le jeudi 26 juillet 2007 à 21:46 -0700, Graham Percival a écrit :
> I'd like to have a new manual "book": Program usage. This book would
> include the INSTALL docs, and chapters 13-15 (running lilypond,
> lilypond-book, and converting) from the existing manual. Basica
Le jeudi 26 juillet 2007 à 21:46 -0700, Graham Percival a écrit :
> John, I think you're quite familiar with our build system and whatnot
> from all the translation stuff -- could you create the basic framework
> for this? Once it's there, I'll rewrite the INSTALL, potentially add
> chapters, p
John Mandereau wrote:
Le jeudi 26 juillet 2007 à 22:41 -0700, Han-Wen Nienhuys a écrit :
Sounds good, but I'd leave out the INSTALL docs. We haven't looked at
this for a long time. People should get the gub builds or take the
lilypond that comse with their distro.
This is the driving force b
Le jeudi 26 juillet 2007 à 22:41 -0700, Han-Wen Nienhuys a écrit :
> Sounds good, but I'd leave out the INSTALL docs. We haven't looked at
> this for a long time. People should get the gub builds or take the
> lilypond that comse with their distro.
Right, but what about developers or contributor
Le jeudi 26 juillet 2007 à 21:46 -0700, Graham Percival a écrit :
> I'd like to have a new manual "book": Program usage. This book would
> include the INSTALL docs, and chapters 13-15 (running lilypond,
> lilypond-book, and converting) from the existing manual. Basica
2007/7/26, Graham Percival <[EMAIL PROTECTED]>:
> I'd like to have a new manual "book": Program usage. This book would
> include the INSTALL docs, and chapters 13-15 (running lilypond,
> lilypond-book, and converting) from the existing manual. Basically, the
>
I'd like to have a new manual "book": Program usage. This book would
include the INSTALL docs, and chapters 13-15 (running lilypond,
lilypond-book, and converting) from the existing manual. Basically, the
"user manual" deals with the .ly file format, and the "p
27 matches
Mail list logo
