Re: Please test new lilypond installers
Am 2019-01-30 um 09:45 schrieb Knut Petersen : > Thanks for testing the installers. Below I try to summarize your results: Thanks for your work! (And to everyone involved, of course!) > lilypond-2.21.0-1.darwin-x86.tar.bz2 > OK: > • Works on MacBook Air (mid 2012) with Intel Core i5 and macOS Mojave > 10.14.2 [Karlin High] > • iMac with High Sierra (installer worked ok but Michael reports a > problem with lilypond not finding the external lilyjazz font) [Michael Hendry] Looks OK on Mac mini Server Core i7 (2013) and OSX 10.9.5: works. Long first-run delay, to be expected. Chokes on my old code, didn’t check further. Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm https://www.fiee.net ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: A thought on Windows Experience
Am 2013-12-05 um 01:12 schrieb David Kastrup : > Francisco Vila writes: > >> 2013/12/4 David Kastrup : >>> The last time this discussion came up, Frescobaldi did not work on >>> MacOSX. And it comes with its own dependencies. And installers. >> >> Fresco is now in Macports (whatever that means) and I think that means >> it is now very easy to install there. > > "It is very easy to install there" is not the same as "it is very easy > to integrate into LilyPond's installer". Right, and „very easy to install“ is not true for the average Mac user - MacPorts is kind of a Linux parallel installation on your mac, controlled by command line. And Frescobaldi has so much dependencies, it pulls in nearly a complete Linux with some hours of compile time. I’m glad it works, but it doesn’t avoid the command line problem for clicky users. Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Where do the Century Font files come from?
Am 2014-02-12 um 19:54 schrieb Urs Liska : > I don't find any sources, and trying to understand mf/GNUmakefile I get the > impression that they are somehow pulled from the latex installation that is > part of the LilyPond build dependencies. > I'm asking because I'd like to have an estimate on the amount of work or > complexity needed to add font faces to Century, a condensed version in > particular. A narrow variant would be great, but never underestimate the work for a good typeface! If you’re serious, you should get in contact with the Polish font guys that are responsible for TeX Gyre (Schola etc.): http://www.gust.org.pl/projects/e-foundry/tex-gyre I don’t think the new font face is possible without some major funding - the current faces still lack Cyrillic (there once was, like in LilyPond’s variant, but it was removed AFAIK due to licensing and also quality issues). > If Century came from metafont source it should be in theory be comparably > simple to add a narrower variant, isn't it? AFAIK only the music fonts are from MF sources. > But that's probably useless hope? Just hope is useless ;-) Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Serious feedback and improvement headroom
Hi Urs, really interesting! I have just some short comments. Am 2014-04-04 um 16:43 schrieb Urs Liska : > treble F 4/4 is the equivalent to > > \clef treble > \key f \major > \time 4/4 > > (,9 ),10_a140140h30 > seems to be an equivalent to a \shape invocation > > Personally I think that LilyPond's approach is a very good compromise between > Amadeus' assembler-like appearance and the confusing verbosity of e.g. XML > formats. But this is something Henle's engraver would consider a significant > problem because he thinks that he needs considerably less time entering the > music in Amadeus. I learned LinoSetting in vocational school and saw colleagues use a Berthold system at the newspaper where I studied typesetter. I learned to write PostScript by hand and I use TeX. My second word processor was WordStar (you know those dot commands?) on DOS (my first was Scripsit on TRSDOS). Just to prove I know old input methods... These „ancient“ typesetting „languages“ (Lino, Berthold) are very similar to that Amadeus „assembler“ as LilyPond is to TeX. (Maybe NOTE is like PostScript, I don’t care.) LinoSetting could do great things, but I really prefer TeX, it’s much more readable. And that’s the advantage of LilyPond over Amadeus, I think. Of course a professional daily working in „Assembler“ is faster in writing. But is he in reading/bugfixing? > I don't suggest any significant changes in our input syntax. But I want to > point out that editing efficiency on that level _is_ an issue we should keep > taking into account when it comes to professional work. For this guy it makes > a difference if he can (thousands of times) type "ho" instead of "\stemUp". > And we all know that the process of tweaking output isn't that > straightforward with LilyPond (although I very much appreciate all the little > and bigger improvements we constantly see). The backslash is a slow-downer in fast typing, at least on German keyboards, esp. on German Mac keyboards, where you have to press Alt-Shift-7. But for everyone who is NOT producing scores on piece-rate – and that is MOST users of ANY music typesetting system, I’m sure – this doesn’t matter. If the typing speed would really be so important, more people would use advanced keyboard layouts like Neo. > In another context I see a similar thing with LaTeX: Compiling a file with > lualatex and fontspec takes longer by orders of magnitude than with plain > latex. So maybe we really have a conceptual issue with the efficiency of > LilyPond's runtime work. Hm, ConTeXt (MkIV/LuaTeX) can be really slow - on the other hand you have a lot of control over internals. I guess you can’t script Amadeus like you can LilyPond with Scheme – if the whole code is hard-compiled, it must be faster. Or is this a false assumption? Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Change default MIDI file extension to '.mid'
Am 2015-01-05 um 18:34 schrieb David Kastrup : > Ambivalent at best. What is the actual problem case we are talking > about? Which programs are "many other programs", under which systems? Without personal settings, OSX (and Safari on OSX) knows to play only .mid, not .midi. Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: The status of Lilypond and Guile 2?
Am 2015-02-09 um 01:34 schrieb Edward d'Auvergne : > I was wondering what the current status of Guile 2 support in Lilypond > is? The dev/guilev2 branch hasn't been touched since 2014-10-13. It > is becoming more and more impossible to run Lilypond on modern Linux > distributions (for example see > https://bugs.mageia.org/show_bug.cgi?id=10969). Is there any relief > in sight? Have a look at the mailing list’s archives, it was discussed just yesterday or maybe two days before in the GSoC thread: The problem is Guile 2’s garbage collection that’s incompatible with LilyPond’s internal data structures. Only the Guile developers can really solve this; as far as I understood, there are a lot more issues in Guile 2; looks to me like nobody uses Guile as much as LilyPond... Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Ghostscript 9.15
Am 2015-03-24 um 20:35 schrieb Masamichi HOSODA : > I've succeed to upgrade GUB's pango to 1.28.3. > https://github.com/trueroad/gub/tree/pango-1.28 > > Then, I've checked some environments. > The results are following: > > linux-64 binary on Ubuntu 14.04 LTS 64 bit: >ligatured pdf is generated. > > linux-x86 binary on Ubuntu 14.04 LTS 64 bit: >ligatured pdf is generated. > > linux-x86 binary on Ubuntu 14.04 LTS 32 bit (minimal install): >Serif font (CenturySchL-Roma) is ligatured. >Sans-serif font (TakaoPGothic) is non-ligatured. > >I think that the reason is that >the system doesn't have ligature possible sans-serif fonts. >In other environment, selected sans-serif font is DejaVuSans. So that’s probably a matter of the font, not of its style - not every font defines ligatures, and the name „TakaoPGothic“ tells me its main focus would be Japanese (is this true?), so the designers probably didn’t put so much work in features of Latin script. Would you care to try a different font? > mingw (Windows) on Windows 8.1 64 bit: >ligatured pdf is generated. > > Note that I haven't build all platform's lilypond installer, yet. Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Sans-serif free Unicode font (was Re: Ghostscript 9.15)
Am 2015-03-26 um 00:11 schrieb Marc Hohl : > Is there any recommendation whether to use sans serif fonts for chord names? > I used the text font (serif) in the latest projects of mine where chord > symbols were needed. I don’t know, but I tried several fonts for chord names, and if you use a serif font, the chords are not easily distinguishable from lyrics etc. My default font for chord names is now Latin Modern Sans (a descendant of Knuth’s Computer Modern), also a font from the TeX distribution. Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Remove old "News" entry from home page
Am 2015-07-19 um 17:36 schrieb Joram : >> I seem to remember that Henning similarly did some LilyPond integration >> into Context and don't think that this is general knowledge. > > This means compared to lilypond-book, one only has to compile it once > with context and not in two steps? That sounds interesting. Yes, it’s not using lilypond-book, but calls LilyPond within the TeX run - as needed, i.e. the „compiled pictures“ are kept and their source code checked against an md5 checksum (as long as the order of your snippets didn’t change or you did name them). Again, see http://wiki.contextgarden.net/LilyPond I should update the example to LilyPond 2.18. „Once“ depends on the product (references, ToC etc.) - ConTeXt cares for the several runs that LaTeX might need. Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Remove old "News" entry from home page
Am 2015-07-19 um 14:37 schrieb David Kastrup : > I seem to remember that Henning similarly did some LilyPond integration > into Context and don't think that this is general knowledge. Probably not, but ConTeXt at all is not really general knowledge ;) But users who manage the learning curve of LilyPond, I would suppose to also manage to learn ConTeXt - not that it’s as difficult, but because you need to find your way through the documentation that is, ehm, not quite as well structured as LilyPond’s. But if you’re not content with LaTeX’s layout classes, then ConTeXt is the way to go IMO - better define everything from scratch than tweak the code of others. Anyway, my „integration“ is not much more than a setup for a general „filter“ module by one of our wizards, Aditya, that can be used to call arbitrary tools for inline processing. see wiki.contextgarden.net/LilyPond Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Change the LilyPond default fonts to TeX Gyre
Am 2015-08-20 um 15:32 schrieb Masamichi HOSODA : > I'm going to push Issue 4552: Change the LilyPond default fonts to TeX Gyre > https://code.google.com/p/lilypond/issues/detail?id=4552 > > This changes LilyPond default fonts from URW++ to TeX Gyre. > Along with it, this also changes a configure option. Hi, sorry for chiming in that late. You are aware that the current version of TeX Gyre fonts don’t contain Cyrillic letters, are you? "Our" old version has them, and TeX Gyre 0.996 had them, too, but they were removed for quality (and AFAIK licensing) reasons. For me, Cyrillic support is important, but I’ll just use one of the old fonts. Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
