Re: Three questions about good German usage?
Duden - Die neue deutsche Rechtschreibung: Flageolettton three t! ;-) Thomas 1. Are natürlichen Flageolettönen and künstlichen Flageolettönen the correct terms for natural and artificial harmonics? Plural with article: 1. Fall: die natürlichen/künstlichen Flageolettöne 2. Fall: der natürlichen/künstlichen Flageolettöne 3. Fall: den natürlichen/künstlichen Flageolettönen 4. Fall: die natürlichen/künstlichen Flageolettöne Plural without article: 1. Fall: natürliche/künstliche Flageolettöne 2. Fall: natürlicher/künstlicher Flagoelettöne 3. Fall: natürlichen/künstlichen Flageolettönen 4. Fall: natürliche/künstliche Flageolettöne 2. Is there a German term to describe the stopped note in an artificial harmonic? (In Italian we would say capotasto ... I've never heard one. Probably I would call it `der Basiston des Flegeolets'. 3. How does German translate the interval of a twelth? Say c' g'' ? Duodezime? Yes. `Duodezime' or `Duodezim'. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Snippet/template how to use lilypond-book with xelatex
Hi,
I was writing about this already some time ago, now I prepared a small
file that demonstrates how to use xelatex (and its advanced font
selection features) whith lilypond-book. This is only a workaround since
it pretends to lilypond-book to use pdflatex instead. But something like
this could be nice in the template section of the LM. I only cannot add
it myself to lsr, because it is not a lilypond snippet.
How are the lilypond-book templates handled, are they added also from lsr?
Greetings
Till
\documentclass{article}
\usepackage{ifxetex}
\ifxetex
%xetex specific stuff
\usepackage{xunicode,fontspec,xltxtra}
\setmainfont[Numbers=OldStyle]{Times New Roman}
\setsansfont{Arial}
\else
%This can be empty if you are not going to use pdftex
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{mathptmx}%Times
\usepackage{helvet}%Helvetica
\fi
%Here you can insert all packages that pdftex also understands
\usepackage[ngerman,finnish,english]{babel}
\usepackage{graphicx}
\begin{document}
\title{A short document with lilypond and xelatex}
\maketitle
Normal \textbf{font} commands inside the \emph{text} work,
because they \textsf{are supported by \LaTeX{} and XeteX.}
If you want to use specific commands like \verb+\XeTeX+, you
should include them again in a \verb+\ifxetex+ environment.
You can use this to print the \ifxetex \XeTeX{} command \else
XeTeX command \fi which is not known to normal \LaTeX .
In normal text you can easily use lilypond commands, like this:
\begin{lilypond}
{a2 b c'8 c' c' c'}
\end{lilypond}
\noindent
and so on.
The fonts of snippets set with lilypond will have to be set from inside
of the snippet. For this you should read the AU on how to use lilypond-book.
\selectlanguage{ngerman}
Auch Umlaute funktionieren ohne die \LaTeX -Befehle, wie auch alle anderen
seltsamen Zeichen: à ÄÄÅ, wenn sie von der Schriftart unterstützt werden.
\end{document}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Three questions about good German usage?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 1. März 2008 schrieb Trevor Bača: 1. Are natürlichen Flageolettönen and künstlichen Flageolettönen the correct terms for natural and artificial harmonics? Yes, see Wikipedia: http://de.wikipedia.org/wiki/Flageolettton Also note that the correct German version of harmonics is Flageolett (with double t), as defined by the Duden (which is the dictionary defining the German language). http://www.duden.de/suche/index.php?begriff=flageoletbereich=mixed Thus, Flageoletttöne should have three t's. Also, please use the correct nominativ case: - -) natürlicher Flageoletton (Sing.) / natürliche Flageolettöne (Plural) - -) künstlicher Flageoletton (Sing.) / künstliche Flageolettöne (Plural) 3. How does German translate the interval of a twelth? Say c' g'' ? Duodezime? Yes, that's the correct term. However, it's also possible (and I suppose more common) to leave out the e at the end: Doudezim. Again, duden.de allows both versions of the intervalls, with and without ending e (does not contain Duodezime, but e.g. 'Quint': http://www.duden.de/suche/index.php?begriff=Quintbereich=mixed References: http://de.wikipedia.org/wiki/Tonintervall (They use the ending e) http://www.musiklehre.at/7_001.htm (A book on music theory, not using the ending e) Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung Jung-Wien, http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHyTGpTqjEwhXvPN0RAl2HAJ9yxbkv0BFk8Clle1caHyaFx8MaSACgn/u1 fBuk1O6IX5mq49N6Vev7ms4= =g+XY -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Three questions about good German usage?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 1. März 2008 schrieb Reinhold Kainhofer: Thus, Flageoletttöne should have three t's. Also, please use the correct nominativ case: -) natürlicher Flageoletton (Sing.) / natürliche Flageolettöne (Plural) -) künstlicher Flageoletton (Sing.) / künstliche Flageolettöne (Plural) Oops, should not have copied your strings. The correct versions with three t are: - -) natürlicher Flageolettton (Sing.) / natürliche Flageoletttöne (Plural) - -) künstlicher Flageolettton (Sing.) / künstliche Flageoletttöne (Plural) Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung Jung-Wien, http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHyTTgTqjEwhXvPN0RAl9tAJ41LhZdZq7H0T1GYogTkB2XgoLxHACeLR1z gBW/Ty72aWyDh1hRzMW89vE= =ZtX1 -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cross-staff synchronized grace-note figure
David Fedoruk david.fedoruk at gmail.com writes: I'm not sure which notes are grace and which are not. The problem is interesting *think* i'm encountering a similar one, but you haven't given me enough information to tell. All the left-hand (bass clef) pitches will look like grace notes. The right hand pitch in the treble clef is a normal (and hence normal-sized) note. This all unfolds in one measure of 3/8 time, with the pitches as follows: Right hand: D#4 (i.e. just above middle C), dotted quarter-note Left hand: D2 - D#4 - C#3 - F#3 G3 (dyad), all grace notes. (The second grace note coincides with the main note in the right hand.) I'm using standard pitch notation, where the digit after the pitch-class name denotes the octave, i.e. not pitch-registral designations as would be given in Lilypond – those could be converted easily enough. The main issue is how one makes the second of the group of grace notes coincide with the right-hand pitch. This also requires cross-staff beaming with the grace notes, and a double-stemmed notehead on the D#4. I have found a post on a similar topic, dealing with synchronizing grace and normal notes between staves, but it only references synchronizing the first grace of the figure with the normal note, and there is no cross-staff beaming of the graces. Thanks! EF ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
LSR how to move clefs on uneven staff lines?
Hi, I tried to get the clef right for this example from lsr:
upper = \relative c'' {
c1 d e f
}
lower = \relative c {
c1 b a g
}
\score {
\context PianoStaff
\new Staff
\upper
\new Staff {
\override Staff.StaffSymbol #'line-count = #4
\set Staff.clefGlyph = #clefs.F
\set Staff.middleCPosition = #6
\set Staff.clefPosition = #2
\set Staff.clefOctavation = #0
%\clef bass
\lower
}
}
But it doesn't change the position of the notes or the clefs. What is
here wrong? I tried as in NR 1.1.3.1
Greetings
Till
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Defining an Ossia context
Afternoon.
I have been tidying up my lilypond source files and decided to try to
be clever and define an 'ossia' context in one of my layout template
files. I started to regret the decision when I realised I had to list
every single engraver I would need to use (I thought that \alias Staff
would do that - but was wrong.)
What I have done seems to work except for two things. 1) I can't get
the slurs to display. 2) The layout engine does not allocate any
vertical space to the Ossia and allows beams from the staff above and
below to collide. I included the Vertically_spaced_contexts_engraver
and Vertical_align_engraver in a fit of guess-work, but it didn't solve
the problem.
Is there a simple solution,other than manually tweaking the system
positions?
Regards - Dave P.
Example below:
\version 2.11.41
\include English.ly
\layout {
% Define a context for ossia sections
\context {
\name Ossia
\alias Staff
\consists Note_heads_engraver
\consists Text_engraver
\consists Stem_engraver
\consists Accidental_engraver
\consists Staff_symbol_engraver
\consists Rest_engraver
\consists Slur_engraver
\consists Spacing_engraver
\consists Bar_engraver
\consists Script_engraver
\consists Font_size_engraver
\consists Auto_beam_engraver
\consists Key_engraver
\consists Vertical_align_engraver
\consists Vertically_spaced_contexts_engraver
\type Engraver_group
fontSize = #-2
\override StaffSymbol #'staff-space = #(magstep -2)
\override KeySignature #'stencil = ##f
}
\context {
\Score
\accepts Ossia
}
}
Notes = \relative c'' {
% snip
% Bar 13
cs8. d16 e8 cs a4 e8 a |
d,8. e16 fs8 a d4 cs8 d |
e4 e, e'8. cs16 b8 cs |
{ a4 a8. b16 a4 s }
\new Ossia \with { alignAboveContext = Main }
\relative c'' {
\key a \major
a8^\markup \tiny \bold Last Time
b16 ( cs ) d e fs gs ( a-. ) r r8 s4 \bar |.
}
}
\score {
\new Staff = Main { \clef treble \key a \major \time 4/4 \Notes }
\layout { }
}
__
Up to 33% off Norton Security from Tiscali - http://www.tiscali.co.uk/securepc/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: LSR how to move clefs on uneven staff lines?
I'm not sure what you mean. It works as expected when
I try this in 2.11.34. You ask for a staff of four
lines, with middle C 6 half-staff-spaces above the center.
So the lower C will be 1 half-staff-space below the center,
which it is. The clef is 2 half-staff-spaces above the
center, also as specified. So what do you think is wrong?
Trevor D
-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED] Behalf Of
Till Rettig
Sent: 01 March 2008 14:52
To: lilypond-user Mailinglist
Subject: LSR how to move clefs on uneven staff lines?
Hi, I tried to get the clef right for this
example from lsr:
upper = \relative c'' {
c1 d e f
}
lower = \relative c {
c1 b a g
}
\score {
\context PianoStaff
\new Staff
\upper
\new Staff {
\override Staff.StaffSymbol #'line-count = #4
\set Staff.clefGlyph = #clefs.F
\set Staff.middleCPosition = #6
\set Staff.clefPosition = #2
\set Staff.clefOctavation = #0
%\clef bass
\lower
}
}
But it doesn't change the position of the notes
or the clefs. What is
here wrong? I tried as in NR 1.1.3.1
Greetings
Till
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR how to move clefs on uneven staff lines?
OK, yes, it does work... :-) what I meant was with the settings of
middleC =7 and clef position =1. But: When I set the clef settings and
let the clef print explicitly with \clef bass it is again at the wrong
position (middleCPosition 6 and ClefPosition 2) even though I had said
it should be 7 and 1.
so you can't obviously use the \clef command with setting that way? Does
it read the defaults from engraver-init.ly?
Till
Trevor Daniels schrieb:
I'm not sure what you mean. It works as expected when
I try this in 2.11.34. You ask for a staff of four
lines, with middle C 6 half-staff-spaces above the center.
So the lower C will be 1 half-staff-space below the center,
which it is. The clef is 2 half-staff-spaces above the
center, also as specified. So what do you think is wrong?
Trevor D
-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED] Behalf Of
Till Rettig
Sent: 01 March 2008 14:52
To: lilypond-user Mailinglist
Subject: LSR how to move clefs on uneven staff lines?
Hi, I tried to get the clef right for this
example from lsr:
upper = \relative c'' {
c1 d e f
}
lower = \relative c {
c1 b a g
}
\score {
\context PianoStaff
\new Staff
\upper
\new Staff {
\override Staff.StaffSymbol #'line-count = #4
\set Staff.clefGlyph = #clefs.F
\set Staff.middleCPosition = #6
\set Staff.clefPosition = #2
\set Staff.clefOctavation = #0
%\clef bass
\lower
}
}
But it doesn't change the position of the notes
or the clefs. What is
here wrong? I tried as in NR 1.1.3.1
Greetings
Till
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: LSR how to move clefs on uneven staff lines?
The \clef command sets clefGlyph, clefPosition, middleCPosition and
clefOctavation, so issuing it after setting these destroys the values you have
just set explicitly. But just changing any of these four properties will cause
a clef to be printed anyway, so the \clef command is not required. In effect
you've issued a \clef command by setting these properties.
The values in engraver.init are the values for the default clef in each of the
staves. The \clef command is defined as a music function in
music-functions-init.ly, but this doesn't help you much.
Trevor D
-Original Message-
From: Till Rettig [mailto:[EMAIL PROTECTED]
Sent: 01 March 2008 18:22
To: [EMAIL PROTECTED]
Cc: lilypond-user Mailinglist
Subject: Re: LSR how to move clefs on uneven staff lines?
OK, yes, it does work... :-) what I meant was with the settings of middleC =7
and clef position =1. But: When I set the clef settings and let the clef print
explicitly with \clef bass it is again at the wrong position (middleCPosition 6
and ClefPosition 2) even though I had said it should be 7 and 1.
so you can't obviously use the \clef command with setting that way? Does it
read the defaults from engraver-init.ly?
Till
Trevor Daniels schrieb:
I'm not sure what you mean. It works as expected when
I try this in 2.11.34. You ask for a staff of four
lines, with middle C 6 half-staff-spaces above the center.
So the lower C will be 1 half-staff-space below the center,
which it is. The clef is 2 half-staff-spaces above the
center, also as specified. So what do you think is wrong?
Trevor D
-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED] Behalf Of
Till Rettig
Sent: 01 March 2008 14:52
To: lilypond-user Mailinglist
Subject: LSR how to move clefs on uneven staff lines?
Hi, I tried to get the clef right for this
example from lsr:
upper = \relative c'' {
c1 d e f
}
lower = \relative c {
c1 b a g
}
\score {
\context PianoStaff
\new Staff
\upper
\new Staff {
\override Staff.StaffSymbol #'line-count = #4
\set Staff.clefGlyph = #clefs.F
\set Staff.middleCPosition = #6
\set Staff.clefPosition = #2
\set Staff.clefOctavation = #0
%\clef bass
\lower
}
}
But it doesn't change the position of the notes
or the clefs. What is
here wrong? I tried as in NR 1.1.3.1
Greetings
Till
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Three questions about good German usage?
Hi Orm, Werner, Reinhold and Thomas, Thank you very much for the fast and extremely helpful replies. I'm privileged to work with an exceptional German translator when putting score notes together; even so we sometimes find it important to check certain details of German usage when we are working together. Thank you all very much for the help! Trevor. On Sat, Mar 1, 2008 at 4:50 AM, Reinhold Kainhofer [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 1. März 2008 schrieb Reinhold Kainhofer: Thus, Flageoletttöne should have three t's. Also, please use the correct nominativ case: -) natürlicher Flageoletton (Sing.) / natürliche Flageolettöne (Plural) -) künstlicher Flageoletton (Sing.) / künstliche Flageolettöne (Plural) Oops, should not have copied your strings. The correct versions with three t are: - -) natürlicher Flageolettton (Sing.) / natürliche Flageoletttöne (Plural) - -) künstlicher Flageolettton (Sing.) / künstliche Flageoletttöne (Plural) Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung Jung-Wien, http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHyTTgTqjEwhXvPN0RAl9tAJ41LhZdZq7H0T1GYogTkB2XgoLxHACeLR1z gBW/Ty72aWyDh1hRzMW89vE= =ZtX1 -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Three questions about good German usage?
Also note that the correct German version of harmonics is Flageolett (with double t), Ouch. Well, I'm Viennese, and I say phonetically fjaʒojeː (and I've actually never heard fjaʃojɛt or something similar). as defined by the Duden (which is the dictionary defining the German language). Fortunately, the Duden no longer `defines' the German language. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Three questions about good German usage?
Also note that the correct German version of harmonics is Flageolett (with double t), Ouch. Well, I'm Viennese, and I say phonetically fjaʒojeː (and I've actually never heard fjaʃojɛt or something similar). Hmm. Looks like a bug in the IPA mapping in Emacs: The `j' must be a `l', of course. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Chord changes under voltas?
There was a short thread on this topic in Feb-March 2003 (Chords under voltas?), apparently unresolved, and I could find no more recent discussion of this topic. I am using Lilypond to produce jazz leadsheets. Lilypond prints chord symbols above volta lines. This is most unorthodox and disconcerting--the symbols should be above the staff but below the volta. I am using 2.10.29. Is there a workaround, or should this be reported as a bug? Thanks, -Eric ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
