Hi,
The change to add syntax highlighting in the HTML version of the
LilyPond documentation, discussed at
https://lists.gnu.org/archive/html/lilypond-user/2022-01/msg00012.html
on the lilypond-user list and in various lilypond-devel and GitLab
threads, has now landed in the source tree and
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
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 abilit
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,
V
[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.
Cheers,
V
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 chang
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 ve
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
Le 02/01/2022 à 10:16, Valentin Petzel a écrit :
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
and sorry that you will have 1001
conflicting opinions on how to progress!
Good luck.
On 2022-01-01 23:45, Jean Abou Samra wrote:
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
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,
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 bro
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 ve
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-sam
Hi all,
This is what I've been doing to test, after cloning the repo. Instructions
start halfway down this page: https://pygments.org/docs/lexerdevelopment/
You probably don;t even have to `make mapfiles` on this LilyPond branch.
1.
Run make mapfiles
2.
Run the lexer to convert th
> Am 2020-01-25 um 10:45 schrieb Urs Liska :
>
> Am Samstag, den 25.01.2020, 17:48 +1000 schrieb Craig Dabelstein:
>> Hi everyone,
>>
>> I've written a LilyPond syntax highlighter for pygments. It's not perfect
>> but it's mostly working. Is there anyone out there who could test it?
>>
>> htt
Am Samstag, den 25.01.2020, 17:48 +1000 schrieb Craig Dabelstein:
> Hi everyone,
> I've written a LilyPond syntax highlighter for pygments. It's not
> perfect but it's mostly working. Is there anyone out there who could
> test it?
>
> https://github.com/craigdab/pygments/tree/LilyPond
Thank you f
Hi everyone,
I've written a LilyPond syntax highlighter for pygments. It's not perfect
but it's mostly working. Is there anyone out there who could test it?
https://github.com/craigdab/pygments/tree/LilyPond
I'm sure there is lots that could be improved on it. It is running without
errors, but i
gentlemen,
>>
>> I'll have a go at taking the python-ly work and seeing if I can use it
>> work to make syntax highlighting with pygments. It's highly possible that I
>> will totally fail, but I'll give it a try.
>>
>> Craig
>>
>>
>> On
t I really have
no idea what I'm doing.
Craig
On Wed, 15 Jan 2020 at 10:38, Craig Dabelstein
wrote:
> Thank you gentlemen,
>
> I'll have a go at taking the python-ly work and seeing if I can use it
> work to make syntax highlighting with pygments. It's highly possible
Thank you gentlemen,
I'll have a go at taking the python-ly work and seeing if I can use it work
to make syntax highlighting with pygments. It's highly possible that I will
totally fail, but I'll give it a try.
Craig
On Tue, 14 Jan 2020 at 23:38, Federico Bruni wrote:
> Il
Il giorno mar 14 gen 2020 alle 12:34, Urs Liska
ha scritto:
Pygments is also what Pandoc uses for its syntax highlighting, so that
would also make sense for that (e.g. generating PDF documentation from
Markdown).
Are you sure?
I think that pygments is the name of the default style in Pandoc
Am Dienstag, den 14.01.2020, 12:27 +0100 schrieb Federico Bruni:
>
> Il giorno mar 14 gen 2020 alle 09:13, Craig Dabelstein
> ha scritto:
> > Hi all,
> >
> > I'd like to add LilyPond syntax highlighting to highlight.js (
> > https://highlightjs.rea
Il giorno mar 14 gen 2020 alle 09:13, Craig Dabelstein
ha scritto:
Hi all,
I'd like to add LilyPond syntax highlighting to highlight.js (
https://highlightjs.readthedocs.io/en/latest/ ) so that I can
experiment with documentation tools such as mkDocs/readthedocs. Does
anyone hav
Hi all,
I'd like to add LilyPond syntax highlighting to highlight.js (
https://highlightjs.readthedocs.io/en/latest/ ) so that I can experiment
with documentation tools such as mkDocs/readthedocs. Does anyone have
any experience with this? Would it just be a matter of getting one of
the cu
Hi others and Pierre,
They or someone has changed the syntax highlighting colors in Fedora 22.
I hope it was not you Pierre. I find the syntax highlighting terrible on
my notebook.
I don't know if users of this list can effect any changes so parallel I
will try to contact someone in
Hi Federico,
2012/2/3 Federico Bruni :
> Il 02/02/2012 22:22, Thomas Morley ha scritto:
>
>> 1. Am I right you resigned of every highlighting within scheme?
>
>
> Yes, almost.
> I know nothing about Scheme. The only highlighting within Scheme that I'd
> like to preserve are the strings "". I've ju
Il 02/02/2012 22:22, Thomas Morley ha scritto:
1. Am I right you resigned of every highlighting within scheme?
Yes, almost.
I know nothing about Scheme. The only highlighting within Scheme that
I'd like to preserve are the strings "". I've just edited the scheme
definition and it works.
Is
Hi Federico,
2012/2/2 Federico Bruni :
> Il 02/01/2012 15:58, Thomas Morley ha scritto:
>>
>> I tested a file with a large scheme-definition.
>>
>> In the attached file you may notice some inconsequences:
>
>
> Hi Thomas,
>
> I have fixed the error in the scheme definition, so your file is highlig
Il 02/01/2012 15:58, Thomas Morley ha scritto:
I tested a file with a large scheme-definition.
In the attached file you may notice some inconsequences:
Hi Thomas,
I have fixed the error in the scheme definition, so your file is
highlighted correctly now.
I've done also some other improvement
Hi Harm,
thanks for your feedback.
Your example let me notice that I forgot that R (upper case) is a note
as well, so I've updated the note_duration regexp.
Il 02/01/2012 15:58, Thomas Morley ha scritto:
I tested a file with a large scheme-definition.
In the attached file you may notice some
Hi LilyPonders,
I'm following Graham's suggestion[0] and I'm asking here if you could
please test the attached lilypond language file for source-highlight.
There's an issue on the tracker[1] about syntax highlighting in the doc.
The first step to make it happen is writing
On 20 Jun 2011, at 19:00, Garrett Fitzgerald wrote:
> I usually use the emacs tool to write lilypond code, but I use Notepad++ for
> the rest of my editing. I'm trying to do a lilypond UDL for the Zenburn
> scheme I'm currently using (http://victorgavin.co.uk/zenburn/), but I'm
> having troubl
I usually use the emacs tool to write lilypond code, but I use Notepad++ for
the rest of my editing. I'm trying to do a lilypond UDL for the Zenburn
scheme I'm currently using (http://victorgavin.co.uk/zenburn/), but I'm
having trouble matching a couple of the items up. Working off the list from
li
for syntax highlighting in Lilypad?
I suppose you're using a mac and you prefer the Lilypad app instead of
the Lilypond editor. Till now I could not find a nice way for editing
in Lilypond as you have it in TeXShop for example.
I just tried to integrate Lilypond in TeXShop (which shou
looks good, nice to see some support for kate which i use from time
to time
d
On 5 Oct 2007, at 19:00, Wilbert Berendsen wrote:
Hi,
please find attached a massively improved Lilypond highlighting
definition
file for KDE's Katepart, based on Andrea Primiani's first version.
Improvements
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 5. Oktober 2007 schrieb Wilbert Berendsen:
> please find attached a massively improved Lilypond highlighting definition
> file for KDE's Katepart, based on Andrea Primiani's first version.
Great! Thanks for you work.
> Improvements:
> - b
>> I apparently need to find lilypond.words.vim for the
>> operation to be complete. Where can I get it?
>It should be distributed with LilyPond. You don't say which
>package you installed so we can't help more; recent Debian
>packages put it into /usr/share/doc/lilypond. Tell at least
>a versi
Lyle Raymond <[EMAIL PROTECTED]> writes:
> I apparently need to find lilypond.words.vim for the
> operation to be complete. Where can I get it?
It should be distributed with LilyPond. You don't say which
package you installed so we can't help more; recent Debian
packages put it into /usr/share/
Hi Lyle,
I also use vim (gvim) for lilypond editing.
I am looking for others to who use vim to create some sort of group to
work on an extented vim mode for lilypond.
I made a lilypond ftplugin for vim but it is now out of date and needs
much debugging.
If you are interested or anyone else let
I spend most of my time editing in vi, so I cut and pasted Heikki Junes'
lilypond.vim file into /syntax and inserted the appropriate text into
filetype.vim, but now I apparently need to find lilypond.words.vim for the
operation to be complete. Where can I get it?
71 matches
Mail list logo
