The AUTHORS / THANKS list is now in
Documentation/web/basic-authors.itexi. (I'm considering moving it to
a more central location such as Documentation/included/ )
For the THANKS file, we have a policy that people listed as Developer
aren't listed in the Contributors section. However, what
Unfortunately, it may be quite difficult to implement without changing
major parts of LilyPond, since currently the MIDI generation and the
printed output are done completely separately, one after the other,
whereas they would have to be done jointly to be able to implement your
feature
Graham Percival wrote Tuesday, December 08, 2009 8:42 AM
For the THANKS file, we have a policy that people listed as
Developer
aren't listed in the Contributors section. However, what should
we do
about people who are now Developers, but who were merely
Contributors
in the past? Should
On Tue, Dec 8, 2009 at 9:51 AM, Mats Bengtsson mats.bengts...@ee.kth.se wrote:
Graham Percival wrote:
in the past? Should we continue to list them in the previous
contributors section, or remove those once they become developers?
(I favor removing somebody from Contributors once they become
On Tue, Dec 8, 2009 at 1:13 AM, Patrick McCarty pnor...@gmail.com wrote:
I'll add this to the issue tracker tomorrow sometime, hopefully,
unless someone else beats me to it.
I certainly won't, since you have a better understanding of these
things than I do. Just remember to post the link in
On 07.12.2009, at 16:35, Peter Dingley wrote:
I was searching for a way to print out midi elapsed time
in my score to be able to easily start the midi file
at the location I am currently working on. At the moment
I write these in by hand but they change as I
make changes to the music in other
On 07.12.2009, at 16:35, Peter Dingley wrote:
I was searching for a way to print out midi elapsed time
in my score to be able to easily start the midi file
at the location I am currently working on. At the moment
I write these in by hand but they change as I
make changes to the music in other
Hi guys,
Dénes made a bunch of suggestions to avoid repetitions in docs, which
would require a fair amount of maintenance work. I'm replying on the
lists for the record and possibly for discussion, but I'm too budy to
tackle these suggestions before next year; I propose to register these
I was amused by the recent punctuation fix commit: [...]
BTW, may I remind to have TWO spaces after a full stop, exclamation
mark and question mark at the end of a sentence.
That is the practice I recall from my time typing others doctoral thesi.
Sadly it is not the norm for html or many
Check out
URL:http://en.wikipedia.org/wiki/File:Calligraphy.malmesbury.bible.arp.jpg,
first letter in the next to last line. cognationum starts with a c.
You'll see where the confusion about blackletter c being either r or
gamma arises.
the line above that has a better exemplar, at the
BTW, may I remind to have TWO spaces after a full stop, exclamation
mark and question mark at the end of a sentence.
That is the practice I recall from my time typing others doctoral
thesi. Sadly it is not the norm for html or many modern
text-setting applications which ruthlessly trim
From: dem...@suffolk.lib.ny.us Tuesday, December 08, 2009 6:28 PM
I was amused by the recent punctuation fix commit: [...]
BTW, may I remind to have TWO spaces after a full stop,
exclamation
mark and question mark at the end of a sentence.
That is the practice I recall from my time
On Tue, Dec 8, 2009 at 5:04 AM, Valentin Villenave
v.villen...@gmail.com wrote:
On Tue, Dec 8, 2009 at 1:13 AM, Patrick McCarty pnor...@gmail.com wrote:
I'll add this to the issue tracker tomorrow sometime, hopefully,
unless someone else beats me to it.
I certainly won't, since you have a
Reviewers: ,
Message:
Patch for Tracker 918 available on Rietveld - Issue 165096. This
includes updated/enhanced regression tests.
Description:
Fix Tracker 918, Add extra RemoveEmpty*StaffContext functions to support
Frenched scores
with DrumStaff, TabStaff and RhythmicStaff staves.
Add new
James Bailey derhindemith at googlemail.com writes:
For MacOSX, the program Mighty MIDI can start playback at a
particular measure and beat.
The tip to use Mighty Midi (I tried it) is perfect for my use as the bars
are numbered by default. Thanks
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
Unfortunately, it may be quite difficult to implement without changing
major parts of LilyPond, since currently the MIDI generation and the
printed output are done completely separately, one after the other,
whereas they would have to
On Tue, Dec 08, 2009 at 09:54:45PM +0100, Werner LEMBERG wrote:
BTW, may I remind to have TWO spaces after a full stop, exclamation
mark and question mark at the end of a sentence.
That is the practice I recall from my time typing others doctoral
thesi. Sadly it is not the norm for
On Tue, Dec 08, 2009 at 07:23:01PM +0100, John Mandereau wrote:
Le dimanche 06 décembre 2009 à 22:23 +0100, Harmath Dénes a écrit :
An example from macros.itexi:
@ifset bigpage
@macro rglos{TEXT}
@vindex \TEXT\
@ref{\TEXT\,,,music-glossary-big-page,Zenei fogalomtár}
@end macro
Could translations of texi2html stuff be done in a separate file? I'm
sure that perl has some way of reading a {} data type from a file.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Since git master is still borked, I thought I'd make a stab at 2.12. When I do:
make LILYPOND_BRANCH=stable/2.12 lilypond
it builds the binaries (apparently) ok[1], but then it goes on to execute:
python bin/gub --platform=linux-x86 --offline lilypond-test
which attempts to build
20 matches
Mail list logo
