Carl Sorensen writes:
> On 11/12/11 2:17 PM, "Nick Payne" wrote:
>
>>There's a music function I use in virtually every guitar score I've done
>>with Lilypond, to move glissandi that I use to indicate that a finger
>>should be kept on a string when moving frets. I just downloaded and
>>installed
On 13/11/11 13:51, Carl Sorensen wrote:
On 11/12/11 2:17 PM, "Nick Payne" wrote:
There's a music function I use in virtually every guitar score I've done
with Lilypond, to move glissandi that I use to indicate that a finger
should be kept on a string when moving frets. I just downloaded and
in
On 11/12/11 2:17 PM, "Nick Payne" wrote:
>There's a music function I use in virtually every guitar score I've done
>with Lilypond, to move glissandi that I use to indicate that a finger
>should be kept on a string when moving frets. I just downloaded and
>installed 2.15.18 (Linux amd64 version r
Updates:
Status: Fixed
Owner: carl.d.s...@gmail.com
Comment #2 on issue 2031 by carl.d.s...@gmail.com: no lilydev available
http://code.google.com/p/lilypond/issues/detail?id=2031
Fixed in dev/staging, with commit 6800afe0054da580434c95e2708a5e0767c10eb0
To verify, make doc, and
Nick Payne writes:
> There's a music function I use in virtually every guitar score I've
> done with Lilypond, to move glissandi that I use to indicate that a
> finger should be kept on a string when moving frets. I just downloaded
> and installed 2.15.18 (Linux amd64 version running on Ubuntu 10
There's a music function I use in virtually every guitar score I've done
with Lilypond, to move glissandi that I use to indicate that a finger
should be kept on a string when moving frets. I just downloaded and
installed 2.15.18 (Linux amd64 version running on Ubuntu 10.04), and the
parameters
Updates:
Labels: -Patch-review Patch-needs_work
Comment #3 on issue 2037 by d...@gnu.org: Patch: Bring argument processing
of chord music functions in line with the rest
http://code.google.com/p/lilypond/issues/detail?id=2037
First screenshot shows indeed a tricky problem. The first
Updates:
Labels: -Patch-new Patch-review
Comment #2 on issue 2037 by pkx1...@gmail.com: Patch: Bring argument
processing of chord music functions in line with the rest
http://code.google.com/p/lilypond/issues/detail?id=2037
passes make and two reg tests show up.
James
Attachments:
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2037 by d...@gnu.org: Patch: Bring argument processing of chord
music functions in line with the rest
http://code.google.com/p/lilypond/issues/detail?id=2037
Bring argument processing of chord music functions in line with th
On 12 Nov 2011, at 16:46, Graham Percival wrote:
> We are happy to announce the release of LilyPond 2.15.18.
The Mac OS X application "Show Info" gives the version as 2.14.2. However,
lilypond --version is the correct 2.15.18.
Hans
___
bug-lilypond
On 12 Nov 2011, at 17:44, Carl Sorensen wrote:
>>> It's not exactly a bug, more like a feature request :)
>>>
>>> I have noticed that convert-ly removes the \encoding and converts
>>> everything to UTF-8.
>>
>> I hacked together some code, scm/define-note-names.scm, with a language
>> "unicode"
On 11/12/11 6:29 AM, "Hans Aberg" wrote:
>On 11 Nov 2011, at 23:04, Pavel Roskin wrote:
>
>> It's not exactly a bug, more like a feature request :)
>>
>> I have noticed that convert-ly removes the \encoding and converts
>> everything to UTF-8.
>
>I hacked together some code, scm/define-note-na
- Original Message -
> From: David Kastrup
> To: Hans Aberg
> Cc: bug-lilypond@gnu.org
> Sent: Saturday, November 12, 2011 4:19 AM
> Subject: Re: Using Unicode symbols for accidentals
>
> Hans Aberg writes:
>
>> On 12 Nov 2011, at 05:38, David Kastrup wrote:
>>
>>> Unfortunately
On 12 Nov 2011, at 15:31, Pavel Roskin wrote:
>> I hacked together some code, scm/define-note-names.scm, with a language
>> "unicode" added.
>
> I wish I looked at that file before starting this thread. Even though
> Unicode symbols are international, the note names are not. The English B is
Comment #8 on issue 2032 by d...@gnu.org: Patch: Fold set-time-signature
into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
After the last version bump should now verify without tampering with
VERSION.
___
bug-lilypond mailing l
Quoting Hans Aberg :
I hacked together some code, scm/define-note-names.scm, with a
language "unicode" added.
I wish I looked at that file before starting this thread. Even though
Unicode symbols are international, the note names are not. The
English B is not the same as the German B.
Updates:
Status: Started
Labels: -Patch-new Patch-review
Comment #6 on issue 2033 by pkx1...@gmail.com: Patch: This removes
ly:export for real and separates read/eval for Scheme expressions.
http://code.google.com/p/lilypond/issues/detail?id=2033
Thanks again David, passes mak
On 12 Nov 2011, at 10:19, David Kastrup wrote:
>>> Unfortunately, it is just programmers and not musicians who have a
>>> reasonable chance of being able to figure out how to produce ♯ on a
>>> computer keyboard.
>>
>> One approach is having an editor which can provide replacements for
>> input t
Hans Aberg writes:
> On 12 Nov 2011, at 05:38, David Kastrup wrote:
>
>> Unfortunately, it is just programmers and not musicians who have a
>> reasonable chance of being able to figure out how to produce ♯ on a
>> computer keyboard.
>
> One approach is having an editor which can provide replaceme
Updates:
Labels: -Patch-new Patch-review
Comment #28 on issue 2000 by pkx1...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000
Passes Make and reg tests are all here
http://lilypond-stuff.1065243.n5.nabble.com/Tracker-i
On 12 Nov 2011, at 05:38, David Kastrup wrote:
> Unfortunately, it is just programmers and not musicians who have a
> reasonable chance of being able to figure out how to produce ♯ on a
> computer keyboard.
One approach is having an editor which can provide replacements for input text.
So one ju
On 11 Nov 2011, at 23:04, Pavel Roskin wrote:
> It's not exactly a bug, more like a feature request :)
>
> I have noticed that convert-ly removes the \encoding and converts
> everything to UTF-8. So I hoped I could use some Unicode symbols to
> make the sources more compact and readable:
>
> \v
22 matches
Mail list logo
