You guys know much better, but I would be wondering "was it
baseBeatLength or beatBaseLenth"? A shorter name would be easier to
remember. How about
baseLength?
nts
#:music "emmentaler"
#:brace "emmentaler"
#:roman "TeXGyre Schola"
#:sans "TeXGyre Heros"
#:typewriter "TeXGyre Cursor"
#:factor (/ staff-height pt 20)
))
}
Cheers,
Joram
the record:
You can use all code from https://github.com/joram-berger/visualindex
and in particular the visualindex*.ly files under the terms of the GNU
Free Documentation License (GFDL). That way it can be integrated into
the LilyPond documenation. I also made that clear in the readme.
By the
hey would look really strange in
there position on the margin.
Joram
> I would very much like that LilyPond has the ability of automatically
> adjusting the horizontal position of some grobs, in particular dynamic
> signs, bar numbers, and rehearsal marks. The idea is that a large
> delta from the optimum vertical position would make LilyPond retry to
> horizontall
numbers on the right margin look odd. They should definitely be
right aligned in that position (if the user turns them on at all)
Therefore, I would center-align it like your MR does for begin-of-line
and middle-of-line positions, but not at the end of a line.
Cheers,
Joram
lypond/-/merge_requests/363
Cheers,
Joram
"
5 \version "2.8.2"
1 \version "2.8.3"
11 \version "2.8.4"
58 \version "2.8.5"
2 \version "2.8.6"
2 \version "2.8.7"
4 \version "2.8.8"
1 \version "2.9.16"
1 \version "2.9.18"
4 \version "2.9.2"
9 \version "2.9.9"
tl;dr: I would not drop conversion rules unless we know that they fail.
Cheers,
Joram
ul to reflect in git what actually happens.
Cheers,
Joram
ster/custom-music-fonts/smufl/definitions.ily
All taken from OpenLilyLib:
https://github.com/openlilylib/openlilylib/tree/master/custom-music-fonts/smufl
It is probably not the way to go for GSoC but might be interesting or
save some typing work.
Cheers,
Joram
use ssh keys. In
combination with the ssh-agent, you can then enter your ssh key password
only once and push and pull afterwards.
As `git remote -v` lists two separate urls for fetch and push I suspect
there should be a way around that issue.
Cheers,
Joram
/frescobaldi
Cheers,
Joram
> 'abc', u'abc', b'abc', 'abc'.encode()
('abc', u'abc', 'abc', 'abc')
python3 [3.6.9]
>>> 'abc', u'abc', b'abc', 'abc'.encode()
('abc', 'abc', b'abc', b'abc')
Best,
Joram
ctly from lilypond.org via https.
Joram
PS: Btw, the only other warning I get is about -moz-border-radius which
was renamed to border-radius (without vendor prefix) in 2011 if I am not
mistaken. I also see commits that changed this in 2015¹, but perhaps
too late for the 2.18 website? Or I don&#
y complete what
was already agreed back then (me saying that without having read the
patches).
Best
Joram
I /think/ it is Unicode in NTFS now, but UCS/UTF-16 and not UTF-8:
https://stackoverflow.com/questions/2050973/what-encoding-are-filenames-in-ntfs-stored-as
https://en.wikipedia.org/wiki/Universal_Coded_Character_Set#Relationship_with_Unicode
Joram
the
latter (modulo your naming conventions w.r.t case) – just as one more
data point, feel free to ignore it.
Joram
org/
It requires a modern (>2013) browser as it works via WebRTC,
platform-independent, open source (according to their website).
Audio/video calls and screen sharing is available and works (tried on
Ubuntu and Windows).
Cheers,
Joram
at you can see those discussions as a fruitful way to improve things.
In my opinion it matters for potential new developers.
Cheers,
Joram
I’ve nothing more to add. That sounds all very nice.
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
h those by John Ruggero
> (https://notat.io/viewtopic.php?f=2&t=522) I’d vote for numbers only as
> a default. I’ll make another patch set.
+1 for numbers as default. That’s also what I found in scores (Schott,
Boosey & Hawkes) when I looked for it some time ago.
Will the new patc
e SMuFL 1.3 specifications ("Implementation
notes") about "ma" vs. "mb" convinced me that 15mb does not make sense
and I’d suggest to use 15ma etc. as default setting.
I would even change the style to bold italic.
Cheers,
Joram
¹ https://codereview.appspot.com/568970
Am 27.09.19 um 22:34 schrieb Matthew Peveler:
> long vs int, unicode vs str, StringIO vs io, iter.next vs
> iter.__next__, reload, xrange vs range.
It is very well feasible to support both version. I hope by shims you
mean something like¹
from __future__ import division, print_function
fr
> commit 7e39a11c08e6a2a321a2da9c81bd0c62ff6da006
Sorry for the noise and thanks for the change!
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
Am 10.02.19 um 19:41 schrieb carl.d.soren...@gmail.com:
> Simple strings -- don't need #
Sometimes they do:
\markup \with-url #"http://lilypond.org"; "abc"
works.
\markup \with-url "http://lilypond.or
thing, but thanks for taking care!
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Will it also look good for custom key signatures?
\relative {
\set Staff.keyAlterations = #`((6 . ,FLAT)
(5 . ,FLAT)
(3 . ,SHARP))
c'4 d e fis
aes4 bes c2
\key c \major
c
}
Best,
Hi Simon,
you can also look at the variable before changing it:
echo $PS1
You'll probably find the colors there like '\[\033[00m\]'.
The git-part you want to add is just the '$(__git_ps1)' part. So you can
use the original $PS1 and add that part if you don't wa
Hi David,
> The same as before, except that I am a whole lot more pissed.
I am sorry. I leave this discussion. It does not lead anywhere.
Best,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listi
king again)? It is really not meant as an offence. I am just trying to
understand in which state this issue is.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
tch as it is? It looks like you are not comfortable with that but it
is not clear why and how a patch would look like that would be better.
Or do I understand you right that no release manager exists and thus no
commit would be merged to a 2.20 release branch at all? Then
hat would have to change
to include it? What would the road for inclusion look like? (Am I right
that it's more about the 'how and when' then about the 'if ever' of such
a functionality?)
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
the open document format (via ooolilypond) and html. So
for me it is a big step forward for which I was waiting for years.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Wow. Thanks for sharing! And thanks to all who have contributed to the
syntax we have now.
— Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
my mails do not reach lilypond-user, even not through the webinterface.
With this mail, I just test, whether this is specific to lilypond-user
or if it happens for another gnu mailing list, too.
Please ignore this mail.
Joram
___
lilypond-devel
Hi Urs,
I totally overlooked the 'LilyPond-to-MEI' part (the central part) of
your question. And I wondered why you ask that question while knowing
already so many good answers to it. Sorry.
> This may not be something that you, Joram, are after, but something that
> could be con
would have expected
that an a and a c' are two single notes and if they are combined into a
chord, they are inside it. But it without involving <...>, the
attributes are not inside (and therefore outside) of the chord. I would
call that counter-intuitive. It di
d including their
properties like ties when single-note voices are combined to one.
I feel like saying similar things like Simon and I probably will hear
the same answer as you gave before :)
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-de
Hi Simon,
I see. The difference is: I would not have expected that to work. But I
can see the benefit if it would, now.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
make no sense and therefore throw warnings for
syntax that would work in a more sensible context.
At first I thought tie directions (^_) would not work without chords,
but they do for single notes, inside chords and for whole chords as I
would expect it.
So, sorry Simon, this is
' } >> ?
Two voices in the same voice? Does it form two subsequent chords?
With \new Staff instead of \new Voice it is clear and LilyPond also
understands it and does not show the same warning.
Cheers,
Joram
___
lilypond-devel mailing list
li
or differing from the composer.
I don't know the exact procedure and I have no account. In case there
are no objections from you, I would be happy if someone could open an
issue and/or apply this small patch in the right way.
Cheers,
Joram
>From d3826bd7267b2a233c86365b35b885917e26ae92 Mon
ontext and not in two steps? That sounds interesting.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Markdown and
LilyPond users. And I have written a Markdown extension to integrate ly
snippets into markdown.
On the other hand, this means I wrote this extension because I could not
find anything existing.
Joram
___
lilypond-devel mailing list
lilyp
elpful to tell ideas that won't work from good ones.
So please, be friendly and bring together new ideas (innovation) and
experience with proven and reliable workflows. It's not easy and quickly
done, but imho it's worth the efforts.
Cheers,
Joram
___
velopping it any longer because it
fulfils his needs. And he said the code is open* I and he would be happy
if others adapt it and improve it.
I can also share the mail address but rather privately.
Cheers,
Joram
* Tools --> Macros --> Organize Macros --> LibreOffice Basic Macros
I never used \absolute and I don't know
where I would need it. For backwards compatibility I like a), the best
solution in my opinion is d). And yes, it's difficult.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
kind of
non-absolute notation.
Cheers,
Joram
[1]: http://en.wikipedia.org/wiki/Helmholtz_pitch_notation
Am 18.05.2015 um 03:12 schrieb k-ohara5...@oco.net:
>> I strongly prefer just two input modes, \relative and \absolute,
___
lilypond-devel maili
And I would not change the names of \relative but rather invent a new
one (like \octavate – just as a (non-convincing) example from the top of
my head), if at all.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/ma
... ok I found the original post. Well I don't know why you need to use
variables here. But in this case, just forget my mail – I don't know how
to solve this.
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.o
the problem.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
reate the image, I could come up with a proposal.
>
> Anything wrong with @lilypond ... @end lilypond?
I do not know how to add arrows, labels, boxes in lilypond code to
create something similar to the right part of:
http://joramberger.de/files/LilypondSpaci
addressed by:
1. images only in addition to the text explanation
2.+3. use image-creating scripts (post script, svg, tikz, whatever is
best suited)
If there are changes to include that to the docs and I hear about the
way/program to create the image, I could come up with a proposal.
Cheers,
Joram
e-layout-problem.cc;h=426299f0ad08001f480890a5081de8a8e6bd8b8e;hb=HEAD#l734
I don't know the context and scheme, but I would expect that %.1f in
("compressing over-full page by %.1f staff-spaces", overflow)
renders the float value ‘overflow’ as a string with one digit after the
point. E.g. 1.
Hi Paul,
Am 01.03.2015 um 20:22 schrieb Paul Morris:
> Joram Berger wrote
>> all versions have the green background fading in on the top right edge.
>> I do not like that.
>
> Hi Joram, Based on previous feedback from Phil and Trevor, I'm taking it as
> a
owsers like ff and chrome, and which makes it accessible. If emacs
follows web-standards that's of course good.
If I find some time, I might do some more specific proposals on small
rearrangements of the content of the main page. For the layout I w
web site.
Cheers,
Joram
In general, I think, there are so many beautiful, modern, elegant and
responsive layouts on the web, that it would be best to find such a
layout or create it from scratch instead of infinitesimal changes to the
current design. To present a high qualitiy tool like
> So I'd like to keep this thread focused on discussing those.
Hi Paul,
yes, I won't hijack this thread further. And I appreciate your work on
the website – it goes in the right direction.
Cheers,
Joram
___
lilypond-devel mailing list
l
c ones) or only 1 or 2,
linking to http://lilypond.org/examples.html
- an (incomplete) list of interesting and new features
- notes on the latest release (but only this one)
- Keep the Best Edition award and the LilyPond Blog
Or (after one example image), three colu
ntent of an ancient staff in a
modern staff to show a modern equivalent?
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
lor more
towards a neutral white than yellow (somewhere near #66C266).
Cheers and thanks for your work,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Dan,
Am 26.10.2014 um 22:19 schrieb Dan Eble:
On Oct 26, 2014, at 16:21 , Joram wrote:
The way I have been looking at it, c represents quadruple meter and ¢
represents duple.
This is an interpretation I guessed from 4/4=c and 2/2=¢, too. But I don’t
think it is correct from the
Hi Dan,
Am 26.10.2014 um 19:30 schrieb Dan Eble:
On Oct 26, 2014, at 13:36 , Joram wrote:
So C instead of 4/4 because of the quarter notes (and not the 4 of them) and ¢
instead of 2/2 for the halves (not the 2 of them). A 4/2 would then be ¢ not C,
right?
I might be persuaded that you are
halves (not the 2 of them). A 4/2 would then be ¢ not C, right?
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
t it is
similar to the \tempo command with
\tempo Allegro 4=100
That would be easy for my question some days ago.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
s not meant like this, I just wanted to state that.)
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
at way you loose the font-series switch.
Is there a way to specify a font such that all variants available on the
computer are usable through the font-series (etc.) switches?
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
works for me now.
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 13.01.2014 14:04, schrieb Werner LEMBERG:
>
>> For me it now looks heavily distorted (wrong aspect ratio)
>
> Which browser?
Firefox 26, Chromium and Konqueror 4.8.5 - also after reload.
> On the other hand, the uncropped SVG image
>
>
> http://upload.wikimedia.org/wikipedia/de/archive
For me it now looks heavily distorted (wrong aspect ratio)
Joram
Am 13.01.2014 12:26, schrieb Werner LEMBERG:
>
>> Attached are a source version, without the font change for the time
>> sig which crashes SVG creation, and the SVG output.
>
> Thanks! Looks great. I
.”
Best,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
there better scans for this glyph?
>
Hi,
this perhaps does not count as reference, but the Bravura font by
Steinberg has this clef (the 3rd from the right in the attached image).
The "angles" are here centered around the c'' (not the d'') and they are
rectangular a
roposal from my side:
x-offset, y-extent, … (changed)
#UP, #LEFT, #X, … (as before)
\stemUp, \slurDown, … (as before)
Not that I would insist on it. That's just my view on consistency.
In the end, Frescobaldi chooses the correct writing for me.
Cheers,
Joram
__
es.
I think knowing TeX should be not precondition for learning LilyPond.
And (at least to my understanding) \phantom in LaTeX is a bit different
from what is discussed here: It reserves space without writing the
object – like the \hideNotes commands.
Joram
current behaviour
if given? I mean could this change request be implemented without
affecting the recommended way at present? Probably not, because of
ambiguities, and because the following notes would take the same duration.
Cheers,
Joram
___
lilypond
s
probably difficult to cover all situations with a music function of the
parts. Having commands (not LSR snippets) producing the symbols would be
a first step, even if that would not be followed by the midi output in a
first place.
Cheers,
Joram
___
lil
like to ask if that work would be welcomed
by the community, in case someone did it?
Cheers,
Joram
Just for comparison and reference:
http://upload.wikimedia.org/wikipedia/commons/0/03/LilyPond-logo-with-music.png
http://de.wikipedia.org/wiki/Datei:Frescobaldi-logo.svg
http://upload.wikimedia.org/
ch reach that level of details?
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I summarize the open issues, concerning the German translation (point 3
is could be also concerns the English documentation).
Am 13.11.2012 21:15, schrieb Joram Berger:
> Hi,
>
> recently, I noticed some spots in the documentation, where I think that
> could be wrong – at l
Am 14.11.2012 00:15, schrieb Trevor Daniels:
>
> Joram Berger wrote Tuesday, November 13, 2012 8:15 PM
>
>> recently, I noticed some spots in the documentation, where I think that
>> could be wrong – at least I don't understand why it is documented like that:
>>
Am 13.11.2012 23:59, schrieb Keith OHara:
> Joram Berger gmx.de> writes:
>
>> http://lilypond.org/doc/v2.16/Documentation/notation/writing-rhythms#scaling-
> durations
>> It is:
>> % Scale music by *2
>> Should it be?
>> [ ... ] % Divide duration
e developers list to bring up
issues like that?
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
main the only
thing to add by hand in the lyrics.
In addition, extender lines below long notes (e.g. wholes) could make
sense from occationally, but do not work currently:
note barline
o |
text
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 07.11.2012 00:10, schrieb David Kastrup:
> Joram Berger writes:
>
>> Am 06.11.2012 22:10, schrieb David Kastrup:
>>> Joram Berger writes:
>>>
>>>> Hi,
>>>>
>>>> here is another (probably not so well thought) idea:
>>&g
Am 06.11.2012 22:10, schrieb David Kastrup:
> Joram Berger writes:
>
>> Hi,
>>
>> here is another (probably not so well thought) idea:
>>
>> Issue: \noBeam is a quite long command if used heavily and for the
>> opposite feature [ and ] represent much
just an idea, which might be no good one.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
makes sense, I don't know. I
just wanted to let you know. Feel free to just comment it as "bad idea".
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
he common task to put something below it.
I do not know if that collides with the possible use of "s" outside of a <>.
Cheers,
Joram
PS: I have no google account and I don't know if this is a useful idea,
that's why I post here instead of commenting the bug report.
Am 04.11.2012 00:17, schrieb David Kastrup:
> Joram Berger writes:
>> Would it be an idea to add … "français" as aliases to "italiano"?
>>
>> According to my knowledge in French, the note names are the same and
>> bémol/dièse also fits with the Ita
Am 04.11.2012 01:36, schrieb David Kastrup:
> Eluze writes:
>> do you really want to add /francais/?
>
> It's not likely more scary to the French than "espanol" is to the
> Spanish. Basically there are two options making sense to me: native
> language name in utf-8, or English language name ("fr
ch documentation already uses "italiano" as example:
http://lilypond.org/doc/v2.16/Documentation/notation/writing-pitches.fr.html#note-names-in-other-languages
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ch documentation already uses "italiano" as example:
http://lilypond.org/doc/v2.16/Documentation/notation/writing-pitches.fr.html#note-names-in-other-languages
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 23.10.2012 09:08, Federico Bruni:
> 2012/10/23 Joram Berger :
>> Even though things are perhaps a little bit different, I would suggest
>> to include svg (or the whole backend-options) into formats, if possible.
>> Because thats essentially what the user wants: get the ou
(or the whole backend-options) into formats, if possible.
Because thats essentially what the user wants: get the output in the
format svg.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo
clamation mark
forces the "is" to be shown and the octave check checks the octavation.
In (b) the tokens with a related meaning would be closer together. Is
this done on purpose?
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gn
ly. And I do not vote for a democratic choice. The
decision is always up to you developers, because I don't have the
knowledge to decide what the best solution would be.
(And I appreciate that my mail has been taken notice of - that's enough
for me. I have trust in the decisions made wit
ter on.
>
> you are right.
> Following David's suggestions and accepting his code never did us any harm.
>
> best,
> Janek
>
Hi,
sorry for joining the discussion too late (I joined the mailinglist just
now).
In short: I would be very fond of a syntax like (no # or&#x
lypond to music students, I see some spots where
they have difficulties - and perhaps something can be improved during
GLISS (examples will follow). And I hope it can become more widespread.
Keep up the good work!
Cheers,
Joram
___
lilypond-devel mailing list
98 matches
Mail list logo
