Am 07.03.2016 um 10:49 schrieb Urs Liska:
>
> Am 07.03.2016 um 09:58 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Am 07.03.2016 um 09:26 schrieb David Kastrup:
>>>> Urs Liska writes:
>>>>
>>>>> Hi guys,
>>>&
Hi devs,
this question may seem somewhat far-fetched and maybe even
out-of-the-blue, but it actually has a concrete context (if you don't
know what I mean you may ask me off-list).
Consider the scenario that I have a specific XML format where a number
of external formats can be converted to (e.g.
Given the advent of a fifth potential applicant I find it inacceptable that we
don't seem to make any progress in raising our mentor number beyond two.
Is it really true that I am the only one pushing this?
Urs
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
y freely be shared among developers, and Google
explicitly endorses to have code review shared by the devs and not only
been done by the mentor.
So depending on the project and the student it *may* be a rather easy
task. Or not.
Urs
>
> Cheers
> Jan-Peter
>
> Am 14. März 2016 01:08:0
Just a heads-up for us to know:
The student application window has now opened, but we need to list our
mentors only until the window closes again, that is until March 25.
Urs
Am 14.03.2016 um 01:08 schrieb Urs Liska:
> Given the advent of a fifth potential applicant I find it inacceptable t
Hi Karl (and Phil),
Am 22.03.2016 um 09:25 schrieb Phil Holmes:
> I believe you can contribute to the tracker without an account: it's
> just that the contributions require moderation. Could I suggest you
> start like that and see how you progress?
I think Karl talks about uploading patches with
Am 22.03.2016 um 15:32 schrieb Karl O. Pinc:
>>> I'm thinking about someday contributing to lilypond
>> Great! The first step is to post specific issues that
>> you have identified to the bug list:
>> http://lists.gnu.org/archive/html/bug-lilypond/
>> for discussion and to have an Issue created.
Am 23. März 2016 15:06:59 MEZ, schrieb Federico Bruni :
>I've started looking at Analytics, which gives two warnings:
>
>1. We are using the old script urchin.js, which was replaced by
>analytics.js
>
>$ git grep urchin.js
>scripts/build/website_post.py:
so only one
of these two projects can be done.
Nathan Chou has applied for the "Let Spanners Cross Voices" project,
which would be mentored by Jan-Peter Voigt.
Jeffery Shivers has applied for "ScholarLY", which I would mentor.
Best
Urs
--
Urs Liska
www.openlilylib.org
lways works, and works easily.
>>
>> I would really recommend using LilyDev in a VM.
>>
>> Carl
>>
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
--
Urs Liska
www.openlilylib.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
can someone tell me where I should look for code that generates code examples
in the HTML docs?
Thanks
Urs
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https
Hi Carl,
Am 06.04.2016 um 02:09 schrieb Carl Sorensen:
> On 4/5/16 5:09 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Urs Liska" behalf of u...@openlilylib.org> wrote:
>
>> Hi,
>>
>> can someone tell me where I should look for cod
Am 06.04.2016 um 09:37 schrieb Urs Liska:
> Hi Carl,
>
> Am 06.04.2016 um 02:09 schrieb Carl Sorensen:
>> On 4/5/16 5:09 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
>> behalf of Urs Liska" > behalf of u...@openlilylib.org> wrote:
>>
Am 07.04.2016 um 07:50 schrieb Noeck:
> Hi Urs,
>
> a very uneducated guess: Could it be that the html pages are only
> generated if the input has changed and as you change the generating code
> and not the doc-input, the generation is skipped? It is still strange
> that it works if you empty the
Am 07.04.2016 um 07:54 schrieb Urs Liska:
>
> Am 07.04.2016 um 07:50 schrieb Noeck:
>> Hi Urs,
>>
>> a very uneducated guess: Could it be that the html pages are only
>> generated if the input has changed and as you change the generating code
>> and not the
Am 07.04.2016 um 08:03 schrieb David Kastrup:
> Urs Liska writes:
>
>> Hm, I'm puzzled.
>>
>> I must say that this file and particularly
>> BookHTMLOutputFormat.snippet_output() looks like it's exactly the code
>> I'm looking for. What I ne
Am 07.04.2016 um 12:11 schrieb David Kastrup:
> David Kastrup writes:
>
>> Carl Sorensen writes:
>>
>>> What about if you delete python/out and redo make doc?
>>>
>>> Just wondering if there's something wrong with the build script that
>>> python/out isn't properly recreated when python/*.py ch
Am 07.04.2016 um 11:11 schrieb Carl Sorensen:
> On 4/7/16 12:11 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Urs Liska" behalf of
> u...@openlilylib.org> wrote:
>
>> However, when *deleting* the .py and .pyc files an error was triggered,
Weitergeleitete Nachricht
Betreff:Re: Code examples in docs
Datum: Sat, 9 Apr 2016 12:56:12 +0100
Von:James
An: Urs Liska
Hello Urs
On 09/04/16 12:27, Urs Liska wrote:
>
> Am 9. April 2016 12:56:42 MESZ, schrieb James :
>> Urs,
>>
Am 09.04.2016 um 15:27 schrieb Phil Holmes:
> - Original Message - From: "Urs Liska"
> To:
> Sent: Thursday, April 07, 2016 7:11 AM
> Subject: Re: Code examples in docs
>
>
>>
>>
>> Am 07.04.2016 um 07:54 schrieb Urs Liska:
>>>
If I'm not misunderstanding you you should rebase your branch on top of
staging. Then you don't have a merge commit.
HTH
Urs
Am 10. April 2016 21:50:59 MESZ, schrieb Paul Morris :
>Hi all,
>
>In CG 3.4.10 “Pushing to staging” it describes ways to push to staging
>from a patch file or from a bra
Am 11. April 2016 12:16:50 MESZ, schrieb Federico Bruni :
>Il giorno dom 10 apr 2016 alle 21:50, Paul Morris
> ha scritto:
>> Hi all,
>>
>> In CG 3.4.10 “Pushing to staging” it describes ways to push to
>> staging from a patch file or from a branch:
>>
>>
>http://lilypond.org/doc/v2.19/Docume
Am 12.04.2016 um 09:20 schrieb Thomas Morley:
> 2016-04-12 8:06 GMT+02:00 Andrew Bernard :
>> What is the current status wirh respect to porting lilypond to use guile 2.*?
>>
>> I am not seeking long disquisition on all the issues with guile 2, but
>> rather wondering if there is anything I can
Am 15.04.2016 um 04:25 schrieb Bryan Jacobowitz:
> Hi, I'm interested in contributing to Lilypond but I could use some
> direction in starting out. How can I get in touch with a mentor?
>
> I have some C++ and Python experience, and I've been using Lilypond off and
> on for about 4 years now. So
Am 23.04.2016 um 07:09 schrieb Paul Morris:
> (Also, while I’m at it, your recent dotted list work, allowing "violin.1”
> etc, is also really nice.)
Oh, I seem to have missed this, but that's great. Finally we can write
indexed parts/variables!
Thanks for adding this, David.
Best
Urs
far push access yourself.
HTH
Urs
>
>
>
> Thanks!
>
>
>
> --Steven
>
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
--
Urs Liska
www.openlilylib.o
Am 13. Juni 2016 19:51:48 MESZ, schrieb Phil Holmes :
>Can anyone explain why the f in the attached code is 2 octaves above
>where
>I would expect them?
Where *do* you expect it?
>
>testy = #(define-music-function (note)
> (ly:music?)
>#{
> \tag #'a { #note }
> \tag #'b { #note }
>#})
>
>\s
Am 30.06.2016 um 11:52 schrieb David Kastrup:
>> There is a detail I would like to clarify. David suggested allowing \=
>> > to optionally specify the parent context in which a cross-voice
>> > spanner's information is shared (although I am not sure how that would
>> > be done with a key-list, si
Am 30.06.2016 um 14:05 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 30.06.2016 um 11:52 schrieb David Kastrup:
>>>> There is a detail I would like to clarify. David suggested allowing \=
>>>>> to optionally specify the parent context in which a cro
Am 30.06.2016 um 14:37 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 30.06.2016 um 14:05 schrieb David Kastrup:
>>> Urs Liska writes:
>>>
>>>> Am 30.06.2016 um 11:52 schrieb David Kastrup:
>>>>>> There is a detail I would like t
Am 30.06.2016 um 14:47 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 30.06.2016 um 14:37 schrieb David Kastrup:
>>
>>> How does that differ from symbols?
>> Ah, not in the Scheme domain, of course. But you can't *enter* them as
>> LilyPond c
Am 01.07.2016 um 09:01 schrieb Nathan Chou:
> Thanks David and Urs for replying.
>
>>> There is a detail I would like to clarify. David suggested allowing \=
>>> to optionally specify the parent context in which a cross-voice
>>> spanner's information is shared (although I am not sure how that wo
Am 01.07.2016 um 09:28 schrieb Jan-Peter Voigt:
>> Hm. If this is a limitation required by the implementation then it's
>> acceptable. But from a user perspective I would be very surprised if an
>> ID isn't recognized without an explicitly named context around it. Isn't
>> that the (one) idea of
Am 03.07.2016 um 14:49 schrieb benko@gmail.com:
> LGTM
>
> https://codereview.appspot.com/299510043/
Discussion on lilypond-user
(http://lists.gnu.org/archive/html/lilypond-user/2016-07/msg00058.html)
show that it isn't that good. I think there *is* something to be done
about the current sta
Am 03.07.2016 um 23:05 schrieb d...@gnu.org:
> I think this chapter would deserve a lot more love
I agree, but I can't provide that currently.
Maybe things look differently when I'm more into (or through) the
current project, which is my first encounter (engraving-wise) with
figured bass.
andling infrastructure
where it would look something like
\registerOption scholarly.editorial-functions.additions #'()
\setOption scholarly.editorial-functions.addition.slur #some-function
Don't know if that helps with your problem but please consider using the
existing inf
Have fun.
I just read they have 29 degrees Celsius during summer: 14 in the
morning and 15 in the afternoon ;-)
Am 11.07.2016 um 10:05 schrieb Thomas Morley:
> Hi all,
>
> I'll be on vacations for the next two weeks, doing camping in Normandie.
> Thus completely without net-access.
>
> Cheers,
>
Am 12.07.2016 um 10:00 schrieb Marc Hohl:
>> The Productions page has now a long column of concerts on the left and a
>> short column of published sheet music on the right. I think that
>> "published" in this case means just publicly available? I mean, Mutopia
>> is not a publishing company.
>
>
Am 10.08.2016 um 19:09 schrieb David Kastrup:
> C++ is a good career move, but the C++ in LilyPond's code base is of
> rather mixed quality and of rather mixed age: the early parts had to
> rely on the features available in early language standards. So C++
> skills acquired while working with Li
Am 12.08.2016 um 07:21 schrieb littlesincanada:
> Hi,
>
> On 11/08/16 21:18, David Kastrup wrote:
>> littlesincanada writes:
>>
>>> On the face of it, a rebase is the obvious solution, but I'm told that
>>> it's a cardinal sin to rebase commits that have already been pushed.
>> So forget about t
Hi,
I have written a function to return the lowercase version of a symbol
for use in my library as
% Return the lowercase version of a symbol
#(define (symbol->lowercase sym)
(string->symbol
(string-downcase
(symbol->string sym
Just a small question: this seems so general that I
Am 13.08.2016 um 08:10 schrieb David Kastrup:
> Urs Liska writes:
>
>> I have written a function to return the lowercase version of a symbol
>> for use in my library as
>>
>> % Return the lowercase version of a symbol
>> #(define (symbol->lowercase sy
>Case insensitivity is almost never a good idea. It leads to stuff that
>sometimes works and sometimes fails under mysterious circumstances.
>
>For example, you are aware that in a Turkish locale, I downcases to ı
>instead of i , and i uppercases to İ instead of I ?
>
>And if you do search-and-
Hi all,
I just thought giving GUB a try, despite all the numerous issues people
seem to have with it.
So I went to my server, cloned GUB and ran bin/gub lilypond-installer.
This ran for quite some time and finished with a simple "done", so
obviously successfully (for this limited single target).
Am 31. August 2016 16:11:14 MESZ, schrieb Paul :
>On 08/30/2016 06:05 PM, carl.d.soren...@gmail.com wrote:
>
>> I'm not comfortable with the really long, scrolling, home page.
>
>Ok, given these concerns that Carl and David raised, let me think some
>more and see what I can come up with.
>
>Mayb
Am 06.09.2016 um 17:49 schrieb paulwmor...@gmail.com:
> Patch set 3 uploaded, with just one example image on the home page and a
> list of links to the other examples on the examples page. I like how
> this gets an image of sheet music onto the home page and helps
> communicate the wide range of
Am 15.09.2016 um 02:51 schrieb paulwmor...@gmail.com:
> Now using the Bach BWV861 example from the essay. Screenshot:
> https://drive.google.com/open?id=0ByNTIEA63_a_ZGZrZzlkSUhJeU0
>
> I like the cleaner look since this image doesn't have any title, text,
> etc. like the previous one. If you c
Am 16. September 2016 02:37:53 MESZ, schrieb Paul :
>Hi all, I'd like to improve on the "id" grob property but I wanted to
>ask about the best way to migrate users if/when we made the change I'm
>thinking of.
>
First of all, I think this is a good idea, and it comes at a good moment,
shortl
s-init.ly:30: (ice-9 optargs))
> These are artifacts from Frescobaldi auto-formatting, I suppose.
>
> https://codereview.appspot.com/303650043/
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> htt
Am 27.09.2016 um 20:46 schrieb paulwmor...@gmail.com:
> I considered this, but it's simpler for both code and user if all these
> svg output attributes are in the same alist property rather than split
> across two. Currently the id property is not used for anything else, so
> no need to keep it
Am 18.10.2016 um 22:43 schrieb Simon Albrecht:
> Hi Janek,
>
> great to see you back in the Pond :-)
;-)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 22. Oktober 2016 16:29:10 MESZ, schrieb Simon Albrecht
:
>On 22.10.2016 10:00, Thomas Morley wrote:
>> Hi,
>>
>> I recently mentioned my work to create the very special notation for
>> Akkordzither.
>> http://lists.gnu.org/archive/html/lilypond-user/2016-10/msg00349.html
>>
>> I consider to p
Am 27. Oktober 2016 04:40:14 GMT-07:00, schrieb David Kastrup :
>
>This concerns << ... \\ ... \\ ... ... >>
>
>If we have more than one voice, voices are assigned in order:
>
>1/2, 1/2/3, 1/2/3/4, 1/2/3/4/5, 1/2/3/4/5/6 ...
>
>while the documentation is quite explicit that, ordered from top to
>
Is there any notion (or the potential for a notion) of unit testing in
LilyPond's development process?
Urs
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://l
Am 29. Oktober 2016 12:06:20 GMT-07:00, schrieb Carl Sorensen
:
>
>
>On 10/29/16 11:34 AM, "lilypond-devel on behalf of Urs Liska"
>u...@openlilylib.org> wrote:
>
>>Is there any notion (or the potential for a notion) of unit testing in
>>LilyPond&#x
Am 05.12.2016 um 09:05 schrieb gra...@percival-music.ca:
> Looks good to me, especially with Trevor's suggestion.
>
>
> https://codereview.appspot.com/315130043/diff/1/Documentation/contributor/website-work.itexi
>
> File Documentation/contributor/website-work.itexi (right):
>
> https://coderevie
Am 07.11.2016 um 17:08 schrieb Federico Bruni:
> In case you don't know already, last news about guile2 and debian:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005#216
Just for the record (although it's probably evident):
This doesn't only mean one can't install "lilypond" from Debian
Am 07.12.2016 um 09:53 schrieb Federico Bruni:
> Yesterday I was updating LilyDev to stretch (now testing) and I found
> that ttf- packages are no more in Debian. B
I wanted to install ttf-inconsolata and was directed to install
fonts-inconsolata instead. Does that help?
___
Am 07.12.2016 um 09:53 schrieb Federico Bruni:
> Il giorno mer 7 dic 2016 alle 8:42, Urs Liska ha
> scritto:
>>> In case you don't know already, last news about guile2 and debian:
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005#216
>>
&g
Am 07.12.2016 um 10:31 schrieb Antonio Ospite:
> On Wed, 7 Dec 2016 08:42:29 +0100
> Urs Liska wrote:
>
>> Am 07.11.2016 um 17:08 schrieb Federico Bruni:
>>> In case you don't know already, last news about guile2 and debian:
>>> https://bugs.debian.or
Am 07.12.2016 um 11:34 schrieb Federico Bruni:
> Il giorno mer 7 dic 2016 alle 10:28, Urs Liska ha
> scritto:
>> OK, thank you.
>> After installing these building LilyPond fails with the following error:
>>
>> WARNING: Please consider installing optional programs
Am 7. Dezember 2016 19:20:26 MEZ, schrieb David Kastrup :
>Jeffery Shivers writes:
>
>> Hi LP team,
>>
>> I am working on automating editorial commands with ScholarLY, and I
>am
>> having some trouble pulling a music function that is stored in a hash
>> table. If I make a table and assign a key
Am 7. Dezember 2016 23:34:39 MEZ, schrieb Graham Percival
:
>I was going to wait a month or two before suggesting this, just to
>make sure I was fully "up to date", but I'll jump in now.
>
>We instituted the policy of patch countdowns and Patchy after the
>lengthy wait for 2.14.0, which was due
Am 8. Dezember 2016 08:17:17 MEZ, schrieb Werner LEMBERG :
>
>> Moving a thread across from the user list, I just wanted to let
>> people know that I will be starting on the work of upgrading
>> lilypond to use Python 3 - yes, with all the complexity that
>> entails. I am happy to have a serious
Am 14.12.2016 um 10:43 schrieb Alexander Kobel:
>> Q2: Obviously the definition of \autoextenders does not match the coding
>> style used in scm/*. It does not even
>> work if it is added to music-functions.scm. Some advice is needed ...
>> the extending-manual is not a real help in
>> this case.
Am 14.12.2016 um 10:43 schrieb Alexander Kobel:
>> To allow automated creation of lyric extenders a helper function is
>> needed
>
> ... that does exactly this, adding extenders everywhere.
>
> IMHO, the actual question to decide upon is: Do we want this to be
> enabled by default? IIUC, the fact
Am 14. Dezember 2016 18:03:09 MEZ, schrieb Simon Albrecht
:
>On 14.12.2016 14:54, Knut Petersen wrote:
>> With a music function \autoextenders that adds extender events to
>> every syllable you
>> - can be sure never to forget extenders,
>> - can be sure never to generate too short extenders
>>
Am 15. Dezember 2016 18:58:13 MEZ, schrieb Knut Petersen
:
>Am 15.12.2016 um 17:17 schrieb Francisco Vila:
>>
>> Excuse my brevity for now, but I think lyrics extenders are meant
>only for the last syllable of a word. What does Gould say, for example?
>I can check later, @home.
>>
>I don't know
Am 16. Dezember 2016 14:31:43 MEZ, schrieb Knut Petersen
:
>Hi Alexander et. al.!
>
>For me scheme still is the most counterintuitive way to program a
>computer. I believe that I discovered a
>thousand ways to trigger the message "[...] warning: Ignoring
>non-music expression". Could we switch
Am 16. Dezember 2016 15:11:59 MEZ, schrieb David Nalesnik
:
>On Fri, Dec 16, 2016 at 8:07 AM, Knut Petersen
> wrote:
>> Am 16.12.2016 um 14:38 schrieb Urs Liska:
>>>
>>>
>>>> As your knowledge of scheme seems to be well developed, c
reasonable request.
Urs
>
> Cheers,
> Knut
>
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Urs Liska
www.openlilylib.org
___
l mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
Urs Liska
https://openlilylib.org
http://lilypondblog.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Joseph,
welcome to the LilyPond community. It is great to see someone volunteering for
such a task.
It is a good idea to ask for a mentor, although that person would probably be
mostly a mediator between you and the developers.
Personally I don't think I could be that mentor but I wanted to
Am 27. Dezember 2016 13:33:11 MEZ, schrieb Simon Albrecht
:
>Hello everybody,
>
>just now I tried to login with Google in order to close my two recent
>Rietveld reviews. However, Google decided that despite entering a
>verification code from e-mail it couldn’t confirm me being authorised
>to
ebruary. Bot OTOH it would be so much worth the effort to
have in a 2.20, considering that a 2.22 is presumably quite some time away.
What do you think?
Best
Urs
--
Urs Liska
https://openlilylib.org
http://lilypondblog.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi David,
Am 19.01.2017 um 11:18 schrieb David Kastrup:
> But at any rate, I hope to be on board at least for making LilyPond 2.20
> a thing.
to cut your long story even shorter: sad but glad to read that.
Urs
--
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org
__
Hi,
I'm drafting a new section on our GSoC page goving more information for
achieving a mutually satisfying project.
I'd add that to the bottom of the page, after the project ideas. However, the
page isn't properly structured, and while it's acceptable in the current
incarnation it becomes unw
Hi all,
GSoC has started and the timeline is proceeding quickly
(https://summerofcode.withgoogle.com/).
GNU is going to apply until February 9, and by February 27 I expect them
to be accepted to the program, which will make LilyPond applicable as well.
Students will apply between March 20 and Ap
>
>PS:
>I've also provided a patch containing a section with recommendations to
>potential students. They draw from my own experience as a mentor last
>year and suggestions discussed both on the mentors' mailing list and
>the
>mentors' summit last year. Please consider these paragraphs too, as
>
snippets repo and the other,
"new-style", packages. This would actually bring openLilyLib a huge step
forward to be usable on a broader base.
Urs
>
> On Mon, Jan 23, 2017 at 8:06 PM, Urs Liska wrote:
>
>> Hi all,
>>
>> GSoC has started and the timeline
Am 23.01.2017 um 23:11 schrieb Simon Albrecht:
> On 23.01.2017 22:47, Urs Liska wrote:
>> So while it's perfectly possible to put OLL projects on the list and to
>> apply for them (or others not listed there) in case of doubt projects
>> working on LilyPond itself migh
>>>
>>> Is there any chance for completion? If it helps, I'm willing to put
>>> an
>>> resonable amount of money into this and fund the completion of this
>>> feature.
>> I'd probably be interested in working on this, especially if you are
Am 02.02.2017 um 15:05 schrieb James:
> Hello,
>
> Would someone tell me (as a person who doesn't really use explicit
> 'Staff' commands what the purpose of the \new Staff = 'some string' is?
>
> That is looking at many of the examples in our Docs and Snippets, the
> '=' doesn't appear to do anyt
Am 02.02.2017 um 21:25 schrieb SoundsFromSound:
> Urs Liska wrote
>> You can use the explicit staff name to access the context (or compare to
>> some arbitrary value), and it's for example used in the \change Staff =
>> "upper" command.
>
> Can you g
u it's
not *that* much work to commit to.
We really need more activity here, and it can't be true that I have to
be permanently pushing to get things forward. So please someone or many
get involved ...
Best
Urs
--
Urs Liska
https://openlilylib.org
http://lilypondblog.org
Am 5. Februar 2017 15:21:54 MEZ schrieb d...@gnu.org:
>The problem with "mentoring" this is that the expertise for
>successfully
>mentoring this project is the same as for doing it yourself. This is
>not a question of making a plan and then implementing its parts over
>the
>course of several wee
Hi all,
I'm somewhat worried about LilyPond's GSoC project proposals list. Right
now I'm purging the web page
(http://lilypond.org/google-summer-of-code.html) from projects without
mentors, and I have the feeling when this process is completed we're
left with an unsatisfactory state.
>From the 9
Am 6. Februar 2017 07:56:34 MEZ schrieb Jan-Peter Voigt :
>Hi Urs,
>
>
>Am 06.02.2017 um 00:24 schrieb Urs Liska:
>> Hi all,
>>
>> I'm somewhat worried about LilyPond's GSoC project proposals list.
>Right
>> now I'm purging the web page
&g
Am 06.02.2017 um 08:48 schrieb Werner LEMBERG:
>> So essentially per now we will have only 4/5 projects left:
>>
>> * Improving internal chord structure
>> * Adopting SMuFL
>> * Adding glyph variants
>> * openLilyLib testing and documentation
>>
>> I find this list quite disappointing, an
omposers out there
willing to join?
Urs
Am 06.02.2017 um 00:24 schrieb Urs Liska:
>
> Hi all,
>
> I'm somewhat worried about LilyPond's GSoC project proposals list.
> Right now I'm purging the web page
> (http://lilypond.org/google-summer-of-code.html) from projects
Am 06.02.2017 um 15:40 schrieb Paul:
> On 02/02/2017 04:10 PM, Urs Liska wrote:
>
>> However, I suggest that we either remove such orphaned projects or at
>> least compress and move them down to the bottom of the page. A concise
>> page with actual and current project
inclusion of images or accessing glyphs from
specialized fonts.
Indeed this should be discussed thoroughly before actually investing
substantial energy in implementation. But for now I'd defer this to a
moment if there should be a student interested in the project. This
discussion would be
gs that we didn't expect most people to need but they, in fact, do
> and thus we add those things to the core contemporary notation
> library, but it's just silly and ignorant to assume those things until
> we get there.
>
> But what do I know - I'm only a contempora
Am 6. Februar 2017 20:34:36 MEZ schrieb Simon Albrecht :
>On 06.02.2017 20:15, "Jürgen Reuter" wrote:
>> Another thing, I guess, is making it easy for musicians without
>> programming knowledge to smoothly embed their own articulation signs,
>> note heads, clefs, and other font symbols into LilyP
Am 06.02.2017 um 20:15 schrieb "Jürgen Reuter":
> Hi all,
>
> personally, I think, it is as always in software development that
> addresses a wide audience: the challenge to find an appropriate level
> of abstraction.
> If you want to support *any* kind of notation, then just use a
> painting o
Am 06.02.2017 um 09:24 schrieb Werner LEMBERG:
>>> . Developing and implementing an OpenType Scheme API.
>> Do you mean a way to access the extended font features from
>> LilyPond, so I can get real caps or swash alternates etc.?
> Yes.
>
Would it be in line with that project to also add some ty
Am 8. Februar 2017 07:26:16 MEZ schrieb Werner LEMBERG :
>
>> I have resurrected my Braille music output project, which was
>> originated around 12 years ago [...] I've been beavering away it it
>> for the past few months and I have a rough prototype, probably sort
>> of a proof of concept reall
Am 10. Februar 2017 06:43:55 MEZ schrieb Werner LEMBERG :
>
>> Some ideas, without being able to mentor them. [...]
>
>Here's another one:
>
> . Make lilypond support automatic line breaks for piano four hands
>scores.
Nice one.
>
>However, this must be tagged as `difficult'.
>
What's th
Hi,
my patch https://sourceforge.net/p/testlilyissues/issues/5067/
http://codereview.appspot.com/317270043 is currently on countdown. It
introduces the procedures
- lilypond>?
- lilypond>=?
- lilypondhttps://openlilylib.org
http://lilypondblog.org
___
Hi Harm,
Am 14.02.2017 um 22:03 schrieb thomasmorle...@gmail.com:
> To throw in my own 2cts.
>
> Why not compare strings, looks more straight forward to me.
>
>
Indeed your code looks simpler, and your measurement indicates that the
computational cost is very similar.
However, David's last comme
601 - 700 of 754 matches
Mail list logo
