The LilyPond repository is the only one that I follow closely that
actually has (not quite but almost) daily updates anyway. I try to
keep up to date as to where it's going, how it works and who's
implicated (and in what capacity/portion). It is a big and complicated
project that seems to have a li
Le 18/08/2022 à 21:30, Pierre-Luc Gauthier a écrit :
I also read "git log -p" on a daily basis.
Just curious: are you really reading `git log -p` *on the LilyPond
repository* on a daily basis? Or is this a general method to learn
about software that you apply for various pieces of software on
d.org/doc/v2.23/Documentation/notation/common-chord-modifiers.en.html
> http://lilypond.org/doc/v2.23/Documentation/notation/percussion-notes.html
> http://fritz.rmi.de/dokumentation/lilypond/Documentation/user/lilypond/Chords-mode.html#Chords-mode
> https://lists.gnu.org/archive/html/lilypond-user/
>
> FWIW
> --
> Pierre-Luc Gauthier
/doc/v2.23/Documentation/notation/chord-name-chart.en.html
https://lilypond.org/doc/v2.23/Documentation/notation/common-chord-modifiers.en.html
http://lilypond.org/doc/v2.23/Documentation/notation/percussion-notes.html
http://fritz.rmi.de/dokumentation/lilypond/Documentation/user/lilypond/Chords-mode.html#C
Thank you, Aaron. Yes, I found that Wikipedia entry at about the same
time that I first struggled with the tremolo.
It really comes back to being able to think and write fluently, doesn't it? :-)
Thanks to you all for your great support on this list.
Ken
On Thu, Aug 18, 2022 at 9:09 AM Aaron H
ex':
>
> https://github.com/joram-berger/visualindex
>
> This gives you the name of the grob, which you can then use for a
> search in the Notation Reference.
>
> Eventually this will become part of the LilyPond documentation.
>
>
> Werner
then use for a
search in the Notation Reference.
Eventually this will become part of the LilyPond documentation.
Werner
On 2022-08-18 8:49 am, Kenneth Wolcott wrote:
What even makes it more difficult is when I don't even know what
something is called at all (no terminology) and/or when I have no clue
how to succinctly describe what it is that I don't know. For example,
the tremolo; I recognized the graphic but I
Thank you all for your commentary on my question.
I think there are some very nice responses here that give me some perspective.
What even makes it more difficult is when I don't even know what
something is called at all (no terminology) and/or when I have no clue
how to succinctly describe what
On 8/18/2022 5:48 AM, Andrew Bernard wrote:
Every layman seems to have a
different 'layman's term' for things, some of which are true
alternatives and some of which are just plain wrong.
Doing residential tech support, I will never forget the man who referred
to the desktop background picture
Hello Ken,
I also use Dorico, which currently has a 1720 page PDF manual. If I may
make a few comments. There's an active Steinberg Dorico forum. It's
continuously full of complaints about using the manual. It's also full
of complaints saying Dorico is not 'intuitive'. Finally somewhat annoyed
is very frustrating. The
Lilypond documentation is EXCELLENT, but I think that this might be
helpful for some people.
Example:
Q. Does Lilypond generate MIDI for articulations/ornaments (such as
mordant, prall, arpeggios)?
A. Yes/No; see articulate feature description.
I think that this might he
r PDF either does not result in any hits, or
> incorrect hits or too many hits; this is very frustrating. The
> Lilypond documentation is EXCELLENT, but I think that this might be
> helpful for some people.
>
> Example:
>
> Q. Does Lilypond generate MIDI for articulations/ornam
r.
Also, if the grouping or categorization of the concept is not where I
would expect it, I might not know where to find it. A text based
search of the HTML or PDF either does not result in any hits, or
incorrect hits or too many hits; this is very frustrating. The
Lilypond documentation is EX
Jean Abou Samra wrote:
[Robin]
The stroke width I see is 1px (Firefox at 100%). This makes the
stroke dominated by edge effects; the surrounding white dilutes its
colour.
Do the WCAG recommendations recognise this? If not, please don't
apply their levels to this case.
I don't know. I am
Hello Paul,
The documentation does not specify any fonts. It simply uses the and
tags. That means that the fonts used are whatever font your
browser chooses as default font, which on Windows systems appears to be
Courier for monospace and apparently in your case Georgia for the regular
text.
Le 04/01/2022 à 11:35, Thomas Morley a écrit :
Am Di., 4. Jan. 2022 um 11:15 Uhr schrieb Paul McKay :
Hi
Speaking as someone whose eyesight isn't quite as good as it used to be,
Same problem here
I'd like to suggest that anything in a colour is also in bold so that there are
enough pixels fo
Le 04/01/2022 à 23:19, Aaron Hill a écrit :
On 2022-01-04 1:42 pm, Jean Abou Samra wrote:
https://www.gnu.org/philosophy/javascript-trap.en.html
[ . . . ]
But I'm probably fretting for something that is
very easy in the end.
The code Lilypond's site would use would be entirely homegrown,
lice
oving
a problem here because LilyPond documentation examples
are so dense in different constructs that as soon
as you try to convey semantic distinctions, most of
the code becomes colored.
[Peter]
There are various types of colour-blindness - red-green is the most
common. I did a quick Google o
On 2022-01-04 1:42 pm, Jean Abou Samra wrote:
https://www.gnu.org/philosophy/javascript-trap.en.html
[ . . . ]
But I'm probably fretting for something that is
very easy in the end.
The code Lilypond's site would use would be entirely homegrown, licensed
under GPL. Not sure there is anything h
[Aaron]
On 2022-01-04 11:32 am, Jean Abou Samra wrote:
Always best to consult a lawyer on legal matters.
The wife of my cousin is actually a lawyer.
Sadly (but very happily in fact), she gave
birth yesterday, so she will not be in a position
to answer before a while :-)
My layman understa
On 04/01/2022 19:32, Jean Abou Samra wrote:
Forgive my igorance with the inner workings of the
Internet: what does this mean in connection with GDPR
and all that? Am I right that the fact that the
information stored on the user's device serves
a purpose essential to satisfying the very request
of
On 2022-01-04 11:32 am, Jean Abou Samra wrote:
Forgive my igorance with the inner workings of the
Internet: what does this mean in connection with GDPR
and all that? Am I right that the fact that the
information stored on the user's device serves
a purpose essential to satisfying the very request
Hello Jean,
The code Aaron provided is quite nice, but I suggest to rather use a linked
stylesheet like
And then use JS like
document.getElementById("syntax-highlighting") = "highlighting1.css"
This results in less complicated JS and allows for multiple styles.
Cheers,
Valentin
Am Dienstag,
[Aaron]
It is fairly straightforward with CSS and a little JavaScript:
Yeah, that is also what I was starting to muse with
more seriously. Thanks for providing ready-made code.
Forgive my igorance with the inner workings of the
Internet: what does this mean in connection with GDPR
and all that?
On 2022-01-04 10:04 am, Valentin Petzel wrote:
The problem is that we probably want to
remember the set color scheme for longer than just the current page,
so we'd need something like cookies.
Not a problem in the slightest. But not cookies... localStorage [1].
[1]:
https://developer.mozilla
In fact it is sufficient to have multiple stylesheets and load the one you want
to switch to. The problem is that we probably want to remember the set color
scheme for longer than just the current page, so we'd need something like
cookies.
We could also do this without JS by generating multiple
On 04/01/2022 16:23, Aaron Hill wrote:
On 2022-01-04 7:29 am, Erika Pirnes wrote:
Would it be terribly difficult to have a color setting on the
documentation page, so that people can choose between black and color?
It is fairly straightforward with CSS and a little JavaScript:
Is that on the
On 04/01/2022 15:14, J Martin Rushton wrote:
OK, I'll admit I only skimmed it, hence "I've saved the paper to read
later"! I've got Doob's "A Gentle Introduction to TeX" and Oetiker's
"The Not So Short Introduction to LaTeX2e" both of which keep to the
fixed width convention. Again, I'll be hon
On 2022-01-04 7:29 am, Erika Pirnes wrote:
Would it be terribly difficult to have a color setting on the
documentation page, so that people can choose between black and color?
It is fairly straightforward with CSS and a little JavaScript:
Dynamic styles
body { font-size:
I personally find the black text much easier to read than the syntax-highlighed
one in colors. I still have young eyes, but somehow the colored text feels
tiring. Maybe this is just what I am used to, as I am still using the standard
text editor to write my .ly files. Would it be terribly diffic
OK, I'll admit I only skimmed it, hence "I've saved the paper to read
later"! I've got Doob's "A Gentle Introduction to TeX" and Oetiker's
"The Not So Short Introduction to LaTeX2e" both of which keep to the
fixed width convention. Again, I'll be honest, I rarely use them since
I've retired thoug
J Martin Rushton writes:
> Interesting Aaron, but I do note that the paper is from 1983 and didn't
> catch on. I wonder if there is a reason for that? I've saved the
> paper to read later. Personally I don't know of a single language that
> is happy with word processor output as source code, b
Hello Robin,
as far as I know the Lilypond Documentation does not specify the font to be
used for this. So the system defaults to a standard monospace font.
So the font will depend on the system. We could ship a dedicated font with the
documentation, but I'm not sure if we want that.
C
Interesting Aaron, but I do note that the paper is from 1983 and didn't
catch on. I wonder if there is a reason for that? I've saved the
paper to read later. Personally I don't know of a single language that
is happy with word processor output as source code, but then I may be
proved wrong. Knu
On 2022-01-04 4:19 am, J Martin Rushton wrote:
Sorry to disagree, but fixed pitch is _so_ much easier to lay out in an
editor. Documentation flows nicely with variable pitch and fancy
hidden formats, but for code (and Lily's input is a programming
language) you just want the plain line-by-line A
Paul,
Sorry to disagree, but fixed pitch is _so_ much easier to lay out in an
editor. Documentation flows nicely with variable pitch and fancy
hidden formats, but for code (and Lily's input is a programming
language) you just want the plain line-by-line ASCII. It is, as you
say, industry standard
'Hear hear' to these recent posts from Thomas, Paul and the two Davids!
I don't object to the fixed width, but the code font has always been
spindly compared to the rest of the documentation text. I find this
makes it harder to read anyway.
The stroke width I see is 1px (Firefox at 100%).
Am Di., 4. Jan. 2022 um 11:15 Uhr schrieb Paul McKay :
>
> Hi
> Speaking as someone whose eyesight isn't quite as good as it used to be,
Same problem here
> I'd like to suggest that anything in a colour is also in bold so that there
> are enough pixels for me to see what the colour is.
I'd go e
Hi
Speaking as someone whose eyesight isn't quite as good as it used to be,
I'd like to suggest that anything in a colour is also in bold so that there
are enough pixels for me to see what the colour is.
And this seems the appropriate place to ask why the examples are all in
fixed pitch Courier in
Flaming Hakama by Elaine writes:
> In this sense, it seems like the place that has the most potential use
> for helping people distinguish different data types is where the
> syntax is the most complicated and dense, which is in music entry.
>
> The ability to quickly distinguish articulations, d
>
> Am Sonntag, 2. Jänner 2022, 01:06:35 CET schrieb David Kastrup:
> > Jean Abou Samra writes:
> > > Hi all,
> > >
> > > There is an ongoing proposal to add syntax highlighting
> > > in LilyPond's documentation. Since it is a notable change
> > > to the documentation reading experience, user feed
Jean Abou Samra writes:
> Hi all,
>
> There is an ongoing proposal to add syntax highlighting
> in LilyPond's documentation. Since it is a notable change
> to the documentation reading experience, user feedback would
> be appreciated. You can browse a syntax-highlighted version
> of the notation
the list at
> lilypond-user-ow...@gnu.org
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> Today's Topics:
> 1. Re: Feedback wanted: syntax highlighting in the LilyPond
>
On 02/01/2022 16:32, Jean Abou Samra wrote:
I am colorblind (which BTW means that it's hard to distinguish certain
colors, not that everything is gray).
Sorry if I gave a wrong impression. I didn't
mean that everything actually looked gray, just
that it was the extreme imaginary case encompa
Le 02/01/2022 à 17:01, Knute Snortum a écrit :
On Sun, Jan 2, 2022 at 7:10 AM Jean Abou Samra wrote:
...
[Marc]
It will be necessary to keep an uncolored version for men (in
principle women do not have this problem) who do not see well certain
colors.
This is taken care of -- the colors have
On 02/01/2022 09:34, Marc Lanoiselée via LilyPond user discussion wrote:
It will be necessary to keep an uncolored version for men (in principle
women do not have this problem) who do not see well certain colors.
In principle (and practice) women DO suffer this problem. It's caused by
a defect
On Sun, Jan 2, 2022 at 7:10 AM Jean Abou Samra wrote:
>
...
> [Marc]
> > It will be necessary to keep an uncolored version for men (in
> > principle women do not have this problem) who do not see well certain
> > colors.
>
>
> This is taken care of -- the colors have been
> chosen to have enough c
specially. The customizability you get
is on the colors used for the different categories, not
on the classification itself. However, this is not
really a problem here because the LilyPond
documentation does not use this convention of
double spaces. If you want to use the highlighting
in your own doc
Hi Jean,
I like the idea that it should be possible.
I would like for it to be (easily) customisable.
I already have a text editor colour scheme that I use for music, for
parts and scores I have found it is not so important.
My perspective is that I only need colour for highlighting key item
Le 02/01/2022 à 05:52, Jean Abou Samra a écrit :
Le 02/01/2022 à 01:06, David Kastrup a écrit :
Jean Abou Samra writes:
Hi all,
There is an ongoing proposal to add syntax highlighting
in LilyPond's documentation. Since it is a notable change
to the documentation reading experience, user fee
Here are the appended images. That’s the problem if you quickly send the mail
because you need to do something.
Cheers,
Valentin
signature.asc
Description: This is a digitally signed message part.
Hello Jean,
What I’ve done here is:
1) Make any macro that has a structural character bold. This helps in quickly
understanding the basic structure of the document. \tuplet is just a simple
music function with no real structural importance, so it is not bold. Of
course it is arguable if someth
Le 02/01/2022 à 01:06, David Kastrup a écrit :
Jean Abou Samra writes:
Hi all,
There is an ongoing proposal to add syntax highlighting
in LilyPond's documentation. Since it is a notable change
to the documentation reading experience, user feedback would
be appreciated. You can browse a syntax
om
Calvin Ransom
From: lilypond-user on behalf
of Valentin Petzel
Sent: Saturday, January 1, 2022 5:53 PM
To: Jean Abou Samra; lilypond-user@gnu.org
Cc: David Kastrup; Lilypond-User Mailing List
Subject: Re: Feedback wanted: syntax highlighting in th
Jean Abou Samra writes:
> Hi all,
>
> There is an ongoing proposal to add syntax highlighting
> in LilyPond's documentation. Since it is a notable change
> to the documentation reading experience, user feedback would
> be appreciated. You can browse a syntax-highlighted version
> of the notation
Hi all,
There is an ongoing proposal to add syntax highlighting
in LilyPond's documentation. Since it is a notable change
to the documentation reading experience, user feedback would
be appreciated. You can browse a syntax-highlighted version
of the notation manual here:
http://abou-samra.fr/hig
> Am 2020-02-11 um 23:11 schrieb David Kastrup :
>
> It _is_ the source format if I understand you correctly.
Yes, Inkscape’s SVG is "rich" but completely valid and displayable in browsers.
Inkscape can import/export other formats, but SVG is its native format.
It can also use SVGZ (compresse
Noeck writes:
> Hi David,
>
>> Is SVG the file format Inkscape saves in?
>
> Yes, SVG is the Inkscape file format. Inkscape adds some Inkscape
> specific name spaces but within the spec of SVG. To quote the website¹:
>
> Perfectly compliant SVG format file generation and editing
>
>
>> Or i
Hi David,
> Is SVG the file format Inkscape saves in?
Yes, SVG is the Inkscape file format. Inkscape adds some Inkscape
specific name spaces but within the spec of SVG. To quote the website¹:
Perfectly compliant SVG format file generation and editing
> Or is it only an export format fo
Noeck writes:
> Hi David,
>
>> Is there a source? Or is it hand-written SVG? If we are trying to
>> follow the spirit of the GPL, source is defined as "preferred form for
>> modification". For a cobbled-together version, that is tricky to
>> define, but we would not want to make it harder than
Hi David,
> Is there a source? Or is it hand-written SVG? If we are trying to
> follow the spirit of the GPL, source is defined as "preferred form for
> modification". For a cobbled-together version, that is tricky to
> define, but we would not want to make it harder than necessary to come
> up
:45 schrieb SoundsFromSound:
>> Hello all,
>>
>> I recently did a search for "edition-engraver" lilypond documentation and
>> couldn't really find anything at all.
>>
>> Can someone direct me to a manual or help file that explains what exactly
>>
hrieb SoundsFromSound:
Hello all,
I recently did a search for "edition-engraver" lilypond documentation and
couldn't really find anything at all.
Can someone direct me to a manual or help file that explains what exactly
the edition-engraver is, how it is used, how you can use it to tw
Am 02.12.2016 um 01:45 schrieb SoundsFromSound:
> Hello all,
>
> I recently did a search for "edition-engraver" lilypond documentation and
> couldn't really find anything at all.
>
> Can someone direct me to a manual or help file that explains what exactly
>
Hello all,
I recently did a search for "edition-engraver" lilypond documentation and
couldn't really find anything at all.
Can someone direct me to a manual or help file that explains what exactly
the edition-engraver is, how it is used, how you can use it to tweak
elements of
Am 23.03.2015 um 02:10 schrieb Colin Tennyson:
Colin Tennyson wrote:
so anyone who wants to create Lilypond files has to master english
anyway.
Simon Albrecht wrote:
You have to learn the English command names, indeed, but
it’s by no means necessary to read the source code for creating any
sc
the expression 'Lilypond source code' for
source-code-for-the-Lilypond-rendering-engine.
Colin Tennyson
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Narrow-down-search-of-Lilypond-documentation-to-English-tp1
uages. For example, for
"barnumbercheck" the second search result is in Japanese.
Feature request:
Restructure the Lilypond documentation in such a way that it becomes
possible for Google to narrow down searches to a single language, in my case
english.
Out of sheer curiosity: how did it
/lilypond.1069038.n5.nabble.com/Narrow-down-search-of-Lilypond-documentation-to-English-tp173423p173487.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
ager to learn whether my guesses are correct.
Robin Bannister wrote:
> Well, in previous URLs the code wasn't in the filename,
> but rather between slashes - on its own level.
The repositories for the translated documentation used to be in a level of
their own? (as in v2.18/it/ and v1.
lilypond.1069038.n5.nabble.com/Narrow-down-search-of-Lilypond-documentation-to-English-tp173423p173439.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
- Original Message -
From: "Colin Tennyson"
To:
Sent: Saturday, March 21, 2015 5:38 PM
Subject: Re: Narrow down search of Lilypond documentation to English
Subject: Re: Narrow down search of Lilypond documentation to English
Phil Holmes wrote:
At the bottom of _all_ th
Subject: Re: Narrow down search of Lilypond documentation to English
Phil Holmes wrote:
> At the bottom of _all_ the LilyPond manual pages, there's a link
> explaining
> automatic language selection.
err.. Phil,
I think you have overlooked something essential: the subject
in context:
http://lilypond.1069038.n5.nabble.com/Narrow-down-search-of-Lilypond-documentation-to-English-tp173423p173436.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Il giorno sab 21 mar 2015 alle 16:39, Colin Tennyson
ha scritto:
If you click on "Search tools", just below the search bar of
google, a
dropdown menu appears where you can choose to display only pages in
your
language.
Here's an odd thing: it seems that Google displays differently to
dif
- Original Message -
From: "Colin Tennyson"
To:
Sent: Saturday, March 21, 2015 3:39 PM
Subject: Re: Narrow down search of Lilypond documentation to English
That is new to me. I consider myself to be a heavy internet browsing user,
a
heavy Google user; I have not come a
er myself to be a heavy internet browsing user, a
heavy Google user; I have not come across this before.
Can you possibly direct me to more information about this?
Colin Tennyson
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Narrow-down-search-of-Lilypond-doc
down menu appears where you can choose to display only pages in your
language.
Is this what you need?
>
> Feature request:
> Restructure the Lilypond documentation in such a way that it becomes
> possible for Google to narrow down searches to a single language, in my
> case
> englis
second search result is in Japanese.
Feature request:
Restructure the Lilypond documentation in such a way that it becomes
possible for Google to narrow down searches to a single language, in my case
english.
Out of sheer curiosity: how did it come about that the language versions of
Dear Hwaen Ch'uqi,
Thank you for your reply. All I had to do was fill the dir file with the
same contents as yours and everything works now.
Perhaps someone should patch this file? Or show me how to do it.
Kevin
On 2 Dec 2014 22:42, "Hwaen Ch'uqi" wrote:
> Greetings Kevin,
>
> After much exper
Greetings Kevin,
After much experimentation in the past, this is how I solved the
problem. First, as root user, I used dired to enter the
/usr/lilypond/usr/share/info directory, where all the LilyPond info
files were placed. Then I created symbolic links for all the info
files to the directory /us
Dear lilypond users,
My apologies in advance if the answer to this is already out there and I
just didn't find it.
I would like to be able to access the lilypond docs in emacs using the
.info files. So I downloaded the docs tarball and extracted it, and then
made an entry in the init file to add
This is to say how very pleased I am with the latest Lilypond 2.12 Documentation
and Tutorial pages. They are so clearly laid out and it is easy to find just
what you want.
I have used Lilypond a number of times to set short choral pieces for a small
amateur choir (in which I sing) and must say t
downloading a file, the link should point to the first use
url instead. This is what solved my problem.
http://lilypond.org/web/download/getting-started.html
Thanks,
Dan
P.S. I would be willing to assist with the lilypond documentation effort
85 matches
Mail list logo
