Re: new release within a week
> I'm going to make a new release within a week. Is there anything > urgent that must be added/fixed/whatever? Ooops, wrong mailing list :-) Sorry for the noise. Werner
new release within a week
Folks, I'm going to make a new release within a week. Is there anything urgent that must be added/fixed/whatever? Werner
Re: New release
Am Dienstag, den 14.07.2020, 09:05 +0200 schrieb Jonas Hahnfeld: > Am Montag, den 13.07.2020, 22:38 +0200 schrieb Jonas Hahnfeld: > > Am Montag, den 13.07.2020, 21:07 +0200 schrieb Han-Wen Nienhuys: > > > On Mon, Jul 13, 2020 at 7:49 PM Phil Holmes wrote: > > > > I created a new release today. I know that (again) I got the news > > > > wrong and > > > > will need to fix that. However, it looks like the web docs are > > > > probably not > > > > correctly picking up a style sheet (see > > > > http://lilypond.org/doc/v2.21/Documentation/contributor/index_1#Introduction-to-contributing > > > > as a simple example) - they're certainly not presented correctly. Could > > > > anyone say what has gone wrong and what needs to be done to fix it? > > > > > > the 2.21 docs are missing a tocframe section in the manpages. Could > > > this be a fallout of the recent texi2html work? > > > > Ouch, that doesn't look good, but probably related to my work. (For all > > of the changes, I looked at diffs of the HTML docs before and after my > > changes and all looked clean, but that's only my environment...) > > > > From what I saw during a quick look, it could be our init file wasn't > > loaded at all - for example, all cross-links are prefixed with the > > linked book. I don't remember seeing this locally (does this happen for > > anyone?), so one possible difference is the Perl version. GUB has > > version 5.10 which is ... ancient. It could be that I'm using > > *something* (no Perl expert) that breaks loading the file in GUB. I'll > > investigate tomorrow. > > Pretty good guess: > $ ../gub/target/tools/root/usr/bin/perl -c > Documentation/lilypond-texi2html.init > Bareword found where operator expected at > Documentation/lilypond-texi2html.init line 827, near "s// class="toc_current">/r" > syntax error at Documentation/lilypond-texi2html.init line 827, near > "s///r" > Documentation/lilypond-texi2html.init had compilation errors. > > Okay, so let's do it the old way: > https://gitlab.com/lilypond/lilypond/-/merge_requests/246 > (not tested with GUB yet, will do later today) Took until today, but I can confirm it works with GUB on my system. (Note to future me: Don't include "-doc" in your branch name when testing with GUB. Just don't. GUB will strip the suffix and complain that it can't find the branch - big surprise...) signature.asc Description: This is a digitally signed message part
Re: New release
Am Dienstag, den 14.07.2020, 13:27 +0200 schrieb Francisco Vila: > El 13/7/20 a las 19:49, Phil Holmes escribió: > > I created a new release today. > > There are new translations since Sat 07/11. They can be merged onto > master for next release. Needed minor conflict resolutions due to @seealso -> @morerefs: https://gitlab.com/lilypond/lilypond/-/merge_requests/248 Thanks, Jonas signature.asc Description: This is a digitally signed message part
Re: New release
El 13/7/20 a las 19:49, Phil Holmes escribió: I created a new release today. There are new translations since Sat 07/11. They can be merged onto master for next release. -- Francisco Vila, Ph.D. - Badajoz (Spain) Tutoriales de LilyPond y Frescobaldi https://www.youtube.com/playlist?list=PLXMqW0liQ5oNFWgbHwgRdAQhaGm6pSn0Y
Re: New release
Am Montag, den 13.07.2020, 22:38 +0200 schrieb Jonas Hahnfeld: > Am Montag, den 13.07.2020, 21:07 +0200 schrieb Han-Wen Nienhuys: > > On Mon, Jul 13, 2020 at 7:49 PM Phil Holmes wrote: > > > I created a new release today. I know that (again) I got the news wrong > > > and > > > will need to fix that. However, it looks like the web docs are probably > > > not > > > correctly picking up a style sheet (see > > > http://lilypond.org/doc/v2.21/Documentation/contributor/index_1#Introduction-to-contributing > > > > > > as a simple example) - they're certainly not presented correctly. Could > > > anyone say what has gone wrong and what needs to be done to fix it? > > > > the 2.21 docs are missing a tocframe section in the manpages. Could > > this be a fallout of the recent texi2html work? > > Ouch, that doesn't look good, but probably related to my work. (For all > of the changes, I looked at diffs of the HTML docs before and after my > changes and all looked clean, but that's only my environment...) > > From what I saw during a quick look, it could be our init file wasn't > loaded at all - for example, all cross-links are prefixed with the > linked book. I don't remember seeing this locally (does this happen for > anyone?), so one possible difference is the Perl version. GUB has > version 5.10 which is ... ancient. It could be that I'm using > *something* (no Perl expert) that breaks loading the file in GUB. I'll > investigate tomorrow. Pretty good guess: $ ../gub/target/tools/root/usr/bin/perl -c Documentation/lilypond-texi2html.init Bareword found where operator expected at Documentation/lilypond-texi2html.init line 827, near "s///r" syntax error at Documentation/lilypond-texi2html.init line 827, near "s///r" Documentation/lilypond-texi2html.init had compilation errors. Okay, so let's do it the old way: https://gitlab.com/lilypond/lilypond/-/merge_requests/246 (not tested with GUB yet, will do later today) signature.asc Description: This is a digitally signed message part
Re: New release
Am Montag, den 13.07.2020, 21:07 +0200 schrieb Han-Wen Nienhuys: > On Mon, Jul 13, 2020 at 7:49 PM Phil Holmes wrote: > > I created a new release today. I know that (again) I got the news wrong and > > will need to fix that. However, it looks like the web docs are probably not > > correctly picking up a style sheet (see > > http://lilypond.org/doc/v2.21/Documentation/contributor/index_1#Introduction-to-contributing > > > > as a simple example) - they're certainly not presented correctly. Could > > anyone say what has gone wrong and what needs to be done to fix it? > > the 2.21 docs are missing a tocframe section in the manpages. Could > this be a fallout of the recent texi2html work? Ouch, that doesn't look good, but probably related to my work. (For all of the changes, I looked at diffs of the HTML docs before and after my changes and all looked clean, but that's only my environment...) From what I saw during a quick look, it could be our init file wasn't loaded at all - for example, all cross-links are prefixed with the linked book. I don't remember seeing this locally (does this happen for anyone?), so one possible difference is the Perl version. GUB has version 5.10 which is ... ancient. It could be that I'm using *something* (no Perl expert) that breaks loading the file in GUB. I'll investigate tomorrow. Phil, if you still have lilypond.log from your GUB build, that might be helpful - otherwise GUB is hopefully reproducible enough to re-create the problem. > should we install texi2html 5.0 on lilypond.org ? No, please don't. It would only affect the website build, so not related to the docs above. And there are "problems" with texi2html 5.0 that makes the result look less perfect than texi2html-1.82. Jonas signature.asc Description: This is a digitally signed message part
Re: New release
On Mon, Jul 13, 2020 at 7:49 PM Phil Holmes wrote: > > I created a new release today. I know that (again) I got the news wrong and > will need to fix that. However, it looks like the web docs are probably not > correctly picking up a style sheet (see > http://lilypond.org/doc/v2.21/Documentation/contributor/index_1#Introduction-to-contributing > as a simple example) - they're certainly not presented correctly. Could > anyone say what has gone wrong and what needs to be done to fix it? the 2.21 docs are missing a tocframe section in the manpages. Could this be a fallout of the recent texi2html work? should we install texi2html 5.0 on lilypond.org ? -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: New release
It appears to be a generalized problem. All of the navigation panes are gone. And don't have a link to the Documentation Index, so we can't easily go between manuals. Carl On 7/13/20, 12:46 PM, "lilypond-devel on behalf of Han-Wen Nienhuys" wrote: Is this a generalized problem, or just in the CG ? On Mon, Jul 13, 2020 at 7:49 PM Phil Holmes wrote: > > I created a new release today. I know that (again) I got the news wrong and > will need to fix that. However, it looks like the web docs are probably not > correctly picking up a style sheet (see > http://lilypond.org/doc/v2.21/Documentation/contributor/index_1#Introduction-to-contributing > as a simple example) - they're certainly not presented correctly. Could > anyone say what has gone wrong and what needs to be done to fix it? > > > -- > Phil Holmes > > > -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: New release
Is this a generalized problem, or just in the CG ? On Mon, Jul 13, 2020 at 7:49 PM Phil Holmes wrote: > > I created a new release today. I know that (again) I got the news wrong and > will need to fix that. However, it looks like the web docs are probably not > correctly picking up a style sheet (see > http://lilypond.org/doc/v2.21/Documentation/contributor/index_1#Introduction-to-contributing > as a simple example) - they're certainly not presented correctly. Could > anyone say what has gone wrong and what needs to be done to fix it? > > > -- > Phil Holmes > > > -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
New release
I created a new release today. I know that (again) I got the news wrong and will need to fix that. However, it looks like the web docs are probably not correctly picking up a style sheet (see http://lilypond.org/doc/v2.21/Documentation/contributor/index_1#Introduction-to-contributing as a simple example) - they're certainly not presented correctly. Could anyone say what has gone wrong and what needs to be done to fix it? -- Phil Holmes
Re: An exciting new release… of Sibelius!!!
Simon Albrecht writes: > Let's be honest, they really had to get their stuff together to keep > any ground all against Dorico. I think they may still have the higher ground. But Dorico is moving much faster. LilyPond is like Switzerland. High ground, but nobody goes there. -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
Re: Re: An exciting new release… of Sibelius!!!
Let's be honest, they really had to get their stuff together to keep any ground all against Dorico. Best, Simon > On 27.03.2020 - 15:26, Shane Brandes wrote: > > > They are really on the ball on that one. > > > -Shane > > > On Fri, Mar 27, 2020 at 10:09 AM Valentin Villenave > wrote: > > Hi everybody, > I know it’s off-topic but I wanted to share the news because, let’s be > honest, nobody in their right mind would want to miss it: > Yes! It’s finally here! The latest and brightest version of Sibelius > is out… *And* it offers one particularly exciting, exclusive new > feature: > https://is.gd/x16C0B > > … Oh wait, that’s the wrong link. There you go: > https://is.gd/ussdKG > > Seriously guys, how cool is that?? > > Cheers, > V.
Re: An exciting new release… of Sibelius!!!
Very amusing. I use LV ties a lot and exactly need lengthy ones all the time, not the short ones (despite the Bars book). One of our kind colleagues on the list gave me code to extend LV ties, just excellent. Not likely to be getting Sib. for that hot new feature. Andrew
Re: An exciting new release… of Sibelius!!!
They are really on the ball on that one. -Shane On Fri, Mar 27, 2020 at 10:09 AM Valentin Villenave wrote: > Hi everybody, > I know it’s off-topic but I wanted to share the news because, let’s be > honest, nobody in their right mind would want to miss it: > Yes! It’s finally here! The latest and brightest version of Sibelius > is out… *And* it offers one particularly exciting, exclusive new > feature: > https://is.gd/x16C0B > > … Oh wait, that’s the wrong link. There you go: > https://is.gd/ussdKG > > Seriously guys, how cool is that?? > > Cheers, > V. > >
Re: An exciting new release… of Sibelius!!!
Am 27.03.20 um 15:08 schrieb Valentin Villenave: Hi everybody, I know it’s off-topic but I wanted to share the news because, let’s be honest, nobody in their right mind would want to miss it: Yes! It’s finally here! The latest and brightest version of Sibelius is out… *And* it offers one particularly exciting, exclusive new feature: https://is.gd/x16C0B … Oh wait, that’s the wrong link. There you go: https://is.gd/ussdKG Seriously guys, how cool is that?? Cheers, V. Hi Valentin, mocking Finale/Sibelius for what they cannot (could not) do is fun but we have to admit that LilyPond’s LV ties aren’t exactly perfect. No one should have to use the hacky snippet 715 (http://lsr.di.unimi.it/LSR/Item?id=715) for setting the tie length. Sibelius—now that it has LV ties—seems to do the better job. Cheers, Malte
An exciting new release… of Sibelius!!!
Hi everybody, I know it’s off-topic but I wanted to share the news because, let’s be honest, nobody in their right mind would want to miss it: Yes! It’s finally here! The latest and brightest version of Sibelius is out… *And* it offers one particularly exciting, exclusive new feature: https://is.gd/x16C0B … Oh wait, that’s the wrong link. There you go: https://is.gd/ussdKG Seriously guys, how cool is that?? Cheers, V.
Fw: [Fontforge-devel] New release
FYI Werner --- Begin Message --- A new release, 20120731, is now available for download. This time there is also a MS/Windows binary package available, thanks to Matthew Petroff who provided it. Regards, Michał Nowakowski -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Fontforge-devel mailing list fontforge-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fontforge-devel --- End Message --- ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
