Hi everyone,
I want to avoid excessive ledger lines in my score and have LilyPond change the
clef automatically.
I am creating a computer generated piece with LilyPond that covers the entire
pitch gamut.
\autochange does not work for this application because it can only use two
clefs and it
For the records, I've added an issue on Frescobaldi tracker:
https://github.com/frescobaldi/frescobaldi/issues/1412
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
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
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,
Le 04/01/2022 à 00:33, David Kastrup a écrit :
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
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
[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
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
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
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
Harm,
Thanks so much for sharing and tightening up this code for hiding redundant
bass notes in successive slash chords, and thanks Elaine Alt for initiating
the thread. It's a really useful feature to have in a leadsheet, and one I
had been hoping was possible in Lilypond without too much
[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
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]:
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
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
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
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
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
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,
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.
Cheers,
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.
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
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
'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
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
This is perfect, thanks a lot Valentin.
And best wishes for the new year.
Le 03/01/2022 à 22:47, Valentin Petzel a écrit :
Hello Vincent,
The first problem seems to be something internal to Lilypond. Basically the
header markup seems to get called for the 0th page even though we don’t need
29 matches
Mail list logo
