david & Paul:
This morning I run a ly file with jianpu6b.ly and I notice the lyrics is not
lining vertically to the note for 3 - - and 2 - (bar 1 % 2)please refer to .png
David, any progress about missing underline for 8th-note and 16th-note in my
previous email?
Immanuel,Ming.
On Sunday, April 26, 2015 2:45 PM, MING TSANG <[email protected]> wrote:
David & Paul: I understood and I can wait.
David: jianpu6.ly not working properly, Missing underline 8th-note and
double-underline 16th-note for both "numbered" & "solfege" versions. Please
refer to png. Can you have a look see if this can be fixed?In the mean time I
will use jianpu6b.ly for my present use for now until jianpu6.ly is fixed and
merged with jianpu6b.ly OR until new approach by Paul is available with options
in jianpu6.ly.
Immanuel,mING.
On Sunday, April 26, 2015 12:53 PM, Super-User <[email protected]> wrote:
Hi, Paul!
I agree better merge after your refactoring to new approach.Looking forward to
see your new version.
David Zhang
------------------ 原始邮件 ------------------发件人: "Paul
Morris"<[email protected]>; 发送时间: 2015年4月26日(星期天) 晚上11:38收件人:
"Super-User"<[email protected]>; "Urs Liska"<[email protected]>; 抄送: "MING
TSANG"<[email protected]>; "lilypond-user"<[email protected]>; 主题: Re:
Jianpu Notation
Hi David and Ming,
> On Apr 25, 2015, at 10:51 PM, Super-User <[email protected]> wrote:
>
> May I suggest having this project hosted on Github also?
> The facilities on Github enables better managements of issues, goal, test
>cases, and of course, the codebase itself, especially code merges.
> In addition, programmers unaware of / non-subscribing this mail-list can also
>contribute by making pull requests, as in any open-sourced projects.
> To push it forward, I need consent of anyone else who have also contribute
>the code, and agree on the license GPL v3.
This is fine with me. At some point I think it would be a good idea to add
this to openLilyLib, but I’m not sure if it makes sense to go ahead and do that
now, or to work on it on github independently and then move it to openLilyLib
later once it’s more mature.
https://github.com/openlilylib/openlilylib
Urs, what say you?
I think my preference would be to add it to openLilyLib directly rather than
set up a separate repo and migrate it later.
Ming is correct, my latest version does not include David’s latest changes. I
hadn’t seen them before working on my revisions and I haven’t taken the time to
merge them since I think the changes in my “6b" file will be
superseded/obsolete after I implement the new approach. In short, I don’t
think the changes in my version “6b” are worth merging with David’s version “6”.
In other words, the new approach will bring so many changes it makes sense to
wait until I finish it before doing any merging. (It might even make sense to
hold off on further development or setting up of github too. On the other
hand, I don’t want to discourage David from working on this. So maybe we just
figure out the merging when the I have a new version worth merging… probably
with Github’s help.)
Cheers,
-Paul
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
