Re: \times - \tuplet
Mats Bengtsson [EMAIL PROTECTED] writes:
Valentin Villenave wrote:
Maybe we should just explain as a commonprop how to easily create an
alias for the \times keyword, so that the users can be free to choose
whatever they want.
The problem is (as was discussed in that thread that we are repeating
more and more of here) that you cannot create any such alias, at least
not if you want to keep the syntax 2/3. You can certainly make an
alias with syntax \t #2 #3 {music} but that's not very attractive.
Encouraging aliasing for basic functionality is a bad idea since it
impacts the portability of document fragments and thus encumbers the
usefulness of Mutopia and similar sites for score interchange and
adaptations.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \times - \tuplet (was Re: Issue 566 in lilypond: showStaffSwitch - \staffSwitchOn)
2008/1/29, Mats Bengtsson [EMAIL PROTECTED]:
The problem is (as was discussed in that thread that we are repeating
more and
more of here) that you cannot create any such alias, at least not if you
want to
keep the syntax 2/3. You can certainly make an alias with syntax
\t #2 #3 {music} but that's not very attractive.
Oh yes! as a matter of fact, the whole \times 2/3 is included in my
\t variable.
Maybe the whole point is that users cannot define their own alias
here. Would it be consistent to make it possible, by removing the
hardcoded \times keyword and creating some ly:make-tuplet-music
function for instance?
... And sorry about the multiple threads, I just have no idea which
one is the *real* one :)
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \times - \tuplet (was Re: Issue 566 in lilypond: showStaffSwitch - \staffSwitchOn)
Valentin Villenave wrote:
2008/1/28, Graham Percival [EMAIL PROTECTED]:
... hmm, I admit that it's annoying that your right hand needs to
hit the \ and then m keys; \tuplet has the advantage of using the
left hand for the t...
Definitely.
A year ago, I proposed to use the simple, minimalistic \t keyword that
is both short and easy to type, plus is can mean aither times,
tuplet or whatever. This is actually what I've been using since
then, and I have to say I'm very happy with it.
Maybe we should just explain as a commonprop how to easily create an
alias for the \times keyword, so that the users can be free to choose
whatever they want.
The problem is (as was discussed in that thread that we are repeating
more and
more of here) that you cannot create any such alias, at least not if you
want to
keep the syntax 2/3. You can certainly make an alias with syntax
\t #2 #3 {music} but that's not very attractive.
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \times - \tuplet
2008/1/29, David Kastrup [EMAIL PROTECTED]: Encouraging aliasing for basic functionality is a bad idea since it impacts the portability of document fragments and thus encumbers the usefulness of Mutopia and similar sites for score interchange and adaptations. But Mutopia files are already plenty of tricks, definitions, includes, aliases... some even need the make utility. If they are a bit old, there is nothing that convert-ly or you can do to recreate the PDF. A shame, because this is a great project. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \times - \tuplet (was Re: Issue 566 in lilypond: showStaffSwitch - \staffSwitchOn)
2008/1/28, Graham Percival [EMAIL PROTECTED]: ... hmm, I admit that it's annoying that your right hand needs to hit the \ and then m keys; \tuplet has the advantage of using the left hand for the t... Definitely. A year ago, I proposed to use the simple, minimalistic \t keyword that is both short and easy to type, plus is can mean aither times, tuplet or whatever. This is actually what I've been using since then, and I have to say I'm very happy with it. Maybe we should just explain as a commonprop how to easily create an alias for the \times keyword, so that the users can be free to choose whatever they want. Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: replacing Century Schoolbook font
2008/1/28, Werner LEMBERG [EMAIL PROTECTED]: You can insert any UTF-8 character and LilyPond will render it as long as Pango can find a font installed on your system that includes a glyph for that symbol. Pango also handles kerning and ligatures automatically, if the font(s) you use provide enough information and glyphs (for example, Century Schoolbook shipped with LilyPond include ligatures glyphs such as fl, whereas Liberation fonts don't, at least not fl I tested with flûte), [...] Well, Till doesn't mean this. He talks about OpenType features like `smallcaps'. I have no idea about this. You'd have to ask on the pango list, and port their suggestions to pango-font.cc. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: replacing Century Schoolbook font
2008/1/28, Werner LEMBERG [EMAIL PROTECTED]: What use would the pfb fonts have? Good question. Han-Wen, is there still a reason why we distribute the PFB versions? Do we? I thought we only distributed the OTFs, although a regular install (through make) might install them for completeness sake. Definitely something we can junk. Except feta-alphabet[1] they aren't directly used. [1] This is something I consider a bug. I can't see a reason to use feta-alphabet separately since the glyphs are already in the emmentaler font. It's sheer laziness. The font-selection for (IIRC) time-signature and dynamic glyphs still uses the font-encoding property (with values fetaNumber / fetaDynamic). There used to be a reason for this, but it may have disappeared by now. Feel free to fix this. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: replacing Century Schoolbook font
2008/1/28, Werner LEMBERG [EMAIL PROTECTED]: Cyrillic block have been fixed). As an additional benefit, the fonts are directly available as full-featured OpenType fonts (this is, they come with a large bunch of OpenType features). While the metrics are slightly different (due to improvements), the overall shapes of the glyphs are almost identical. The replacement for Century Schoolbook is called TeXGyreSchola: http://www.gust.org.pl/projects/e-foundry/tex-gyre/schola I strongly suggest to use those fonts, and I'm willing to update lilypond so that they get included and used. Sounds great! Go for it! PS: Two questions in case you think the above is a good idea: Shall we distribute SVG and PFB versions of TeXGyreSchola? Since all of the SVG renderers are broken wrt fonts, let's drop the SVG ones. The PFB will be lacking all the interesting features, so let's not dist those either. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: replacing Century Schoolbook font
I strongly suggest to use those fonts, and I'm willing to update lilypond so that they get included and used. Sounds great! Go for it! OK. PS: Two questions in case you think the above is a good idea: Shall we distribute SVG and PFB versions of TeXGyreSchola? Since all of the SVG renderers are broken wrt fonts, let's drop the SVG ones. The PFB will be lacking all the interesting features, so let's not dist those either. OK. I've actually restored the installation of SVG version of the lilypond fonts (I thought it was an error of you because there wasn't any log entry), but it seems this was an intentional change, right? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Postponed Bugs #83 and #297: a Someone Else Problem
2008/1/27, Juergen Reuter [EMAIL PROTECTED]:
The ligature events are implemented as 'command-event', like \bar and
\time, which fall in between the notes.This is inconsistent with
start/stop commands like [ ] , but I can't really judge if that is the
best way to do it.
Hmmh, I don't understand. In Lily 2.7.x, in define-music-types.scm,
LigatureEvent has (types . (general-music span-event ligature-event
event)), i.e. it is a SpanEvent, or am I missing something? In Lily
2.11.x, it is implemented as StreamEvent, due to Erik's changes. How is
this related to command-event (which, btw, I could not find in the
sources)?
this distinction is not in the music 'type-system', but rather how the
events are attached to other things. Beam/slur/etc. start/stop are
attached to the notes, so in
c4]
the ] starts at the beginning of the note. Commands like \bar , \clef
and \] are not attached to notes, so for
c4 \]
the event registers at the end of the note, at the start of the new time-step.
I don't know what the best solution is, but for consistency, it would
probably be best if they were attached to notes like beams. The
downside to attaching to notes is that you would not be able to do
ligs = { \[ s2 \] }
{ c8 d e f }
\ligs
and have the ligature enclose the 4 notes.
(Oh, you are right, it's difficult to find me on the web, since my old
home page unfortunately died a while ago; there is now a new one at
www.juergen-reuter.de).
maybe you can update the relevant web-pages? That would be a useful
exercise in git use :-)
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
commit message
Hi Erlend, could you be a little more verbose in your messages? ** Fix issue 558 ** -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
upstream fixes
Just curious, will these changes propagate to upstream? Or are we effectively forking mf2pt1 ? Author: Werner Lemberg [EMAIL PROTECTED] 2008-01-26 00:42:35 Committer: Werner Lemberg [EMAIL PROTECTED] 2008-01-26 00:42:35 Branches: master, origin Follows: release/2.11.37-1 Precedes: mf2ptf1.pl: Sort MetaPost output files. Fixes #565. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: commit message
Shure, no problem. I'll try to remember to document my commits better from now on. E On 30. jan. 2008, at 01:12, Han-Wen Nienhuys wrote: Hi Erlend, could you be a little more verbose in your messages? ** Fix issue 558 ** -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: upstream fixes
Just curious, will these changes propagate to upstream? Or are we effectively forking mf2pt1 ? Scott has already submitted a new version to CTAN which contains this fix (and which I'll import to the lilypond repository as soon as it is available). Normally, I won't apply such fixes immediately, but this was an emergency case. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Chord fonts
Hi Werner, The chord font seems to be messed up after the mf2pt1 change. The letter m and s is chosen from the dynamic font (see attached picture). Can you reproduce this? I guess you can fix this pretty quick :-) Best regards, Erlend inline: pastedGraphic.png inline: pastedGraphic.png ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
