Reinhold Kainhofer reinhold at kainhofer.com writes:
Am Mittwoch, 24. Dezember 2008 22:13:57 schrieb Trevor Daniels:
Neil Puttock wrote Wednesday, December 24, 2008 3:36 PM
Should tick barlines be the same thickness as nornal barlines?
Currently they get their width from
Graham Percival graham at percival-music.ca writes:
I'm trying to decide how to build the new website. In particular,
I'd like to be able to create pdfs as well as the html.
...
4) Abandon the complete website as pdf idea and just give
people a tarball of the website for off-online
Carl D. Sorensen c_sorensen at byu.edu writes:
Happy new year, all!
I've completed a major patch of fret diagrams, adding a new orientation and
cleaning up a bunch of ugly stuff in the code.
Please review the patch at
http://codereview.appspot.com/11857/diff/1/3
Thanks,
Carl
I
Anne Ghisla a.ghisla at gmail.com writes:
Hello all,
I started working with LilyPond some time ago and I am impressed of its high
quality output and richness of features.
I was wondering if I could propose a project for Google Summer of Code [1],
since I have participated last year and
I have a new patch available. I responded to all comments, plus
added a NEWS entry and put a snippet in the docs.
Please comment:
http://codereview.appspot.com/24044
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Johannes Asal johannes.asal at gmx.de writes:
What do you think about that as a first step:
(define-public (note-name-≥roman-markup pitch root)
Return roman markup for PITCH relative to ROOT.
(make-line-markup
(list
(make-simple-markup
(vector-ref #(I II III IV V VI
Nicolas Sceaux nicolas.sceaux at free.fr writes:
- test.ly -
#(display (current-module))
#(top-repl)
---
==
#module 33965d0
guile (current-module)
#directory (guile-user) 22416f0
guile
So after invoking (top-repl), we are not the same module as the one
David Kastrup dak at gnu.org writes:
When typesetting the following, in the transposed variant
some chord diagrams are pretty, some chord diagrams are absurd.
Fixed in git.
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Nicolas Sceaux nicolas.sceaux at free.fr writes:
you can try that:
-foo.ly-
#(module-define! (resolve-module '(guile-user)) 'lilypond-module
(current-module))
#(top-repl)
guile (set-current-module lilypond-module)
#directory (guile-user) 22416f0
guile
Keith OHara k-ohara5...@oco.net writes:
I looked for a case in my scores where I wanted a stack, where I wanted to
temporarily override something that I had already overridden, and then put
back my first override. I did not find any.
I love having the ability to write a music function that
Two years ago, David and I had a discussion about the existence of /tweak,
/set, and /override. David pointed out the confusing nature of the
different ways of changing properties, and the difficulty of explaining
this to the user.
On Sep 15, 2013, at 4:41 AM, Werner LEMBERG w...@gnu.org wrote:
This is slightly off-topic, but maybe you enjoy the reading :-)
http://www.heracliteanriver.com/?p=324
However, the above holds for printed output. For input files, I think
that two spaces after a full stop makes sense
On 10/20/13 11:39 AM, Joseph Rushton Wakeling
joseph.wakel...@webdrake.net wrote:
I submitted a trial merge request just so we could all explore the
experience of
reviewing a proposed change to the library. It's as near the GitHub
experience
as makes almost no difference (although there are a
On 10/20/13 9:04 PM, Joseph Rushton Wakeling
joseph.wakel...@webdrake.net wrote:
On 21/10/13 04:00, Carl Sorensen wrote:
I have to say that I much prefer the Lilypond method for handling tasks
and reviews to the Gitlab method.
Can you describe in more detail what it is that you like about how
On 10/21/13 2:01 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Having worked with Carl for some years I respect his opinion,
and for me his bottom line: I'm seriously thinking of junking
Gitlab because the benefit seems to be more promised than realized,
based on his experience of actually
On 10/21/13 1:09 AM, Werner LEMBERG w...@gnu.org wrote:
As far as I can see, github's ticketing system doesn't allow to
simply update the patch; instead, you have to open a new ticket.
Not true at all. Rebase your branch, then,
git push -f origin my-branch
... will overwrite the
On 11/27/13 8:04 AM, David Kastrup d...@gnu.org wrote:
Urs Liska u...@openlilylib.org writes:
But also in this case I would come back and suggest including functions
like
originalBreak =
#(define-music-function (parser location)()
( #{ \tag #'keep-original-breaks \break #} ))
in
On 11/27/13 8:32 AM, Urs Liska u...@openlilylib.org wrote:
For me this sounds good.
Requiring to write \include original-breaks.ly is significantly better
than requiring to define the commands.
But it would still need a separate switch, presumably through the
command line.
This is true, but it
On 11/27/13 8:45 AM, Urs Liska u...@openlilylib.org wrote:
Am 27.11.2013 16:36, schrieb Carl Sorensen:
On 11/27/13 8:32 AM, Urs Liska u...@openlilylib.org wrote:
For me this sounds good.
Requiring to write \include original-breaks.ly is significantly
better
than requiring to define
On 11/28/13 3:33 AM, David Kastrup d...@gnu.org wrote:
Phil Holmes m...@philholmes.net writes:
From: James pkx1...@gmail.com
To: Devel lilypond-devel@gnu.org
We have the problem that lily-git.tcl is a well-meant tool. The
people who have written and changed it are not the people using it.
On 11/28/13 2:53 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
Hi,
2013/11/28 Carl Sorensen c_soren...@byu.edu:
On 11/28/13 3:33 AM, David Kastrup d...@gnu.org wrote:
It
would appear that at the current point of time, just rowing back some
selected changes will already accomplish a lot
On 11/30/13 5:52 PM, k-ohara5...@oco.net k-ohara5...@oco.net wrote:
Do you know a better quantity on which to scale the raising of
superscripts?
What about font-size?
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 11/29/13 12:52 PM, James pkx1...@gmail.com wrote:
1. Git checkout [branch] on the command line. That's fine I can handle
that :)
Where [branch] is going to be Staging 99% of the time (but for the case
where I whined, it was stable/2.18)
2. Then run lily-git.tcl from the same session which
On 12/10/13 5:42 AM, Mike Solomon m...@mikesolomon.org wrote:
Hey all,
As 2.18 draws near, I¹d like to work with everyone to establish a system
of branching for LilyPond development. After several rounds of
discussing things with David K, this emerged as the best way to avoid
arguments about
On 12/13/13 8:02 AM, Carl Peterson carlopeter...@gmail.com wrote:
On Thu, Dec 12, 2013 at 7:36 PM, carl.d.soren...@gmail.com wrote:
I think that the index sidebar colors are too dark. They dominate the
page, in my opinon. In the current design, the sidebar color and the
highlight box fill
On 12/13/13 6:04 AM, Phil Holmes m...@philholmes.net wrote:
Thanks for what you're doing, but please don't put a lot of images on the
Google Issue tracker. For bizarre reasons only known to themselves, the
storage available for attachments is _very_ limited. By accident you've
just
used about
On 12/31/13 4:30 PM, David Kastrup d...@gnu.org wrote:
Sven Axelsson sven.axels...@gmail.com writes:
Fantastic work everyone with getting version 2.18 out of the door.
When I saw the release notice, I immediately wanted to update the
Homebrew
formula (Homebrew is a package manager for Mac OS
On 1/3/14 9:26 AM, David Kastrup d...@gnu.org wrote:
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Hello all,
Now that 2.18 has been released (kudos, by the way!!!), when is the
unstable branch going to be updated?
What do you mean, updated? There are a lot of changes in the
On 1/2/14 9:41 AM, Carl Peterson carlopeter...@gmail.com wrote:
Just now seeing this (I don't think I was subscribed when Carl S.
wrote this). After my recent experience with lily-git.tcl and
submitting a patch, one thing I would request is that, if possible,
some kind of automatic line
On 1/5/14 12:09 AM, Werner LEMBERG w...@gnu.org wrote:
I'm not a lawyer, but the year in a copyright notice is supposed to
be the year of original publication. If you have a document first
published in 2012 with a Copyright 2012 notice and you change the
year to 2014 without making any
On 1/5/14 12:00 AM, David Kastrup d...@gnu.org wrote:
According to Savannah, you still have push privileges (and I should be
surprised if not). What did you try? What was the error message? Did
you perhaps not use a member checkout?
URL:http://savannah.gnu.org/git/?group=lilypond
Yes, that
On Jan 7, 2014, at 3:56 AM, Phil Holmes m...@philholmes.net wrote:
- Original Message - From: lilyli...@googlemail.com
To: philehol...@googlemail.com
Cc: re...@codereview-hr.appspotmail.com; lilypond-devel@gnu.org
Sent: Tuesday, January 07, 2014 10:45 AM
Subject: Re:
On 1/9/14 9:43 PM, SoundsFromSound soundsfromso...@gmail.com wrote:
dak wrote
Joseph Rushton Wakeling lt;That must be the reason why the typical
Word document features the
consistent use of document styles for arriving at typographically
superior results.
--
David Kastrup
On Jan 10, 2014, at 11:41 PM, Paul Morris p...@paulwmorris.com wrote:
Seems like getting just the notes (not layout) out of an
imported musicXML file should be an easy and straightforward thing, but I
guess not?
I can't speak for Carl P's work. For me, effective LP input files require
On 1/12/14 8:04 AM, Phil Holmes m...@philholmes.net wrote:
- Original Message -
From: Phil Holmes m...@philholmes.net
To: James pkx1...@gmail.com; Werner LEMBERG w...@gnu.org; Devel
lilypond-devel@gnu.org
Sent: Sunday, January 12, 2014 1:32 PM
Subject: Re: fixing German's Wikipedia
I now have lilypond 2.3.5 running on a Fedora 2 box (built just for
lilypond).
I found some mistakes in fret-diagrams.scm when run on lilypond 2.3.
Please use this patch, instead of the one earlier in the thread. It
should be applied to scm/fret-diagrams.scm. The earlier changelog still
warning: kpathsea can not find TFM file: `ecrm17'
warning: can't find font: `ecrm17'
warning: Loading default font
paper output to `fret-diagram.tex'...
Any thoughts on how to fix this?
Thanks
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL
On Thu, 2004-06-24 at 03:12, Jan Nieuwenhuizen wrote:
AFAICS your patches were not yet applied; if it's not too much
trouble could you please send a full cvs diff (ie: all patches together?)
Jan.
I'll be working on that this evening. If all goes well, I'll have it
done in an hour or so.
On Thu, 2004-06-24 at 03:12, Jan Nieuwenhuizen wrote:
AFAICS your patches were not yet applied; if it's not too much
trouble could you please send a full cvs diff (ie: all patches together?)
Jan.
Attached is a patch for all the files, including the ChangeLog (thanks
to Heikki for the tips
on the current CVS.
Carl
Index: ChangeLog
===
RCS file: /cvsroot/lilypond/lilypond/ChangeLog,v
retrieving revision 1.2291
diff -r1.2291 ChangeLog
0a1,19
2004-06-29 Carl Sorensen [EMAIL PROTECTED
On Tue, 2004-06-29 at 19:10, Heikki Johannes Junes wrote:
The fret diagrams look nicer and nicer all the time.
Thanks!
However, few suggestions:
- place also white text to the center of the circle
According to the algorithms, I am currently doing this (I use
stencil-align-to and
Pedro Kroger wrote:
* Carl Sorensen ([EMAIL PROTECTED]) wrote:
I built lilypond 2.3.5 under Fedora. I had trouble with the images
(none were found), but proceeded to make install. Lilypond apparently
installed OK, as I can process .ly files. However, every time I do, I
get the following
On Fri, 2004-07-02 at 03:40, Jan Nieuwenhuizen wrote:
I think you'll see that the fonts are in a whole new direcory
./usr/share/texmf/... from where you ran rpm2cpio
Sure enough, they were there.
You'd better do something like rpm --install --force ec-fonts...
I tried this, got the same
as complex as lilypond).
Thanks,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Mon, 2004-07-05 at 04:14, Mats Bengtsson wrote:
In addition to Jan's hints, don't forget to run the
command 'texhash' as root to update the file name database
used by TeX and friends.
/Mats
Thanks. That fixed it!
Carl
___
-r1.2300 ChangeLog
--- ChangeLog 1 Jul 2004 21:36:09 - 1.2300
+++ ChangeLog 5 Jul 2004 23:18:47 -
@@ -1,3 +1,28 @@
+2004-07-05 Carl Sorensen [EMAIL PROTECTED]
+
+ * scm/define-grob-properties.scm (all-user-grob-properties): Add descriptions
+ for all fret-diagram properties.
+
+ * scm
On Mon, 2004-07-05 at 17:18, Carl Sorensen wrote:
I've added documentation for fret diagram properties to
define-grob-properties.scm and define-grob-interfaces.scm. These
changes, along with updates to the ChangeLog are included in the
attached patch.
Note: The CVS has not yet been
input,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Tue, 2004-07-06 at 02:59, Han-Wen Nienhuys wrote:
looking through your patch, I have the impression that you have a lot
of properties. Having everything tweakable seems nice at first, but it
makes the program more difficult to understand (as it pollutes the
namespace for properties) and
On Tue, 2004-07-06 at 02:51, Han-Wen Nienhuys wrote:
in particular, the thickness for fret-diagrams should not be renamed
fret-thickness, but it should work like thickness works for other
grobs.
OK. I can easily fix that one. That's in fact how it was originally
written.
Carl
On Tue, 2004-07-06 at 05:50, Carl Sorensen wrote:
I'd be very happy to get CVS access. How do I proceed?
I believe I can now answer my own question. I went to the savannah
website (http://savannah.gnu.org), clicked on New User via SSL,
answered the questions, created a public GPG key
On Tue, 2004-07-06 at 13:16, Han-Wen Nienhuys wrote:
Our thoughts on this matter aren't entirely set in stone. Since you've
already added a lot of properties, we can't save precious development
time by not using properties :-) Maybe you could review all of them,
and prune the ones which are
On Tue, 2004-07-06 at 16:45, Han-Wen Nienhuys wrote:
(ly:add-interface
+ 'fret-diagram-interface
+ A fret diagram
+ '()
this should be a list of the properties for the fret diagram, i.e.
'(thickness dot-radius ... )
Thanks for the input. It's fixed now. I was going to ask how
-item?
Thanks,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Thu, 2004-07-22 at 16:24, Han-Wen Nienhuys wrote:
I would not base anything on the chord name itself (ie. the output
string). Systems for chord names are highly non-standard, so they're
not a good basis to interpret. I suppose that you would have to
devise some kind of lookup structure,
', needed by
`out/drum-note-engraver.o'. Stop.
make[1]: Leaving directory
`/home/carl/lilypond/current-cvs/lilypond/lily'
make: *** [all] Error 2
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo
that the current font
requests in fret-diagrams work properly again, or (b) a description of
how I should fix the font requests so that they work properly?
Thanks,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo
On Fri, 2004-08-06 at 10:08, Jan Nieuwenhuizen wrote:
Carl Sorensen writes:
(font-encoding . TeX-text). In later releases, although scm/font.scm
Why do you ask for an ecoding? I think you should ask for: family . sans
Empirically, I found that in order for it to work, I needed to give
Fixed in cvs.
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Tue, 2004-08-10 at 15:59, Heikki Johannes Junes wrote:
Currently, my favourite pending issue for publishing the next stable branch is
the Fret Diagram markup, which however seem to already be in a fairly mature
state. After that is completed as a markup (Carl may decide), I'm happy since
the current behavior to
having the execution stop as soon as an error occurs.
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Wed, 2004-08-18 at 16:28, Han-Wen Nienhuys wrote:
Carl, can you select fonts by tacking any properties you need (and
only those) onto the props variable passed via the markup system? It
will make sure you select text fonts in the appropriate encoding.
I'm not sure exactly how to do this.
On Thu, 2004-08-19 at 07:44, Carl Sorensen wrote:
On Wed, 2004-08-18 at 16:28, Han-Wen Nienhuys wrote:
Carl, can you select fonts by tacking any properties you need (and
only those) onto the props variable passed via the markup system? It
will make sure you select text fonts
On Thu, 2004-08-19 at 13:07, Han-Wen Nienhuys wrote:
That's better still, since then you're not tied to the specifics of
the text-output backend.
OK, I've fixed scm/fret-diagrams.scm so there are no more calls to
fontify-text, and the only changes to the font from props are to make
the font
On Fri, 2004-08-20 at 07:35, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
I've grep'ed the source code for fontify-text, and only
fret-diagrams.scm uses it. Can I go ahead and remove both fontify-text
and fontify-text-white?
Please do. Thanks!
Done. Can I get permissions for
-engraver
is in out/chord-name-engraver.dep. I know that out/*.dep is
automatically generated during the make process. Something must control
the process and cause out/chord-name-engraver.dep to be created, but I
have not been able to find what this thing is.
Thanks,
Carl Sorensen
addition?
Actually, LilyPond already has the syntax for identifying the string on
which a note should be played (see Tablature). All that remains is to
have an engraver process the string information and put it on the music.
Carl Sorensen
___
lilypond
, but I'm not strident enough about it to
complain if you, as the Docmeister, choose to make all
non-gender-specific pronouns female.
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
. I've been really busy with some
hardware (home remodeling) issues, so I haven't been able to do much of
anything with lilypond, but a short manual section shouldn't be too
much.
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http
On Sun, 2004-10-17 at 17:26, Juergen Reuter wrote:
Hi!
In input/test/fret-diagram.ly, we have a nice fret diagram, but I can not
find any section in the manual about it (or did I miss something?). Since
the NEWS file advertises fret diagrams for the upcoming version of lily,
it would be
On Mon, 2004-10-18 at 18:08, Carl Sorensen wrote:
Since I wrote the fret-diagram markup code, I guess I should at least
take the first stab at a manual. I've been really busy with some
hardware (home remodeling) issues, so I haven't been able to do much of
anything with lilypond, but a short
On Sun, 2004-10-24 at 04:49, Han-Wen Nienhuys wrote:
note that the real docs for fret diagrams should also be linked in
(they are in the Markup section)
Links to both the real docs in the Markup section and to the markup
properties were included in the notation manual.
Carl
On Tue, 2004-10-26 at 02:00, Mats Bengtsson wrote:
It looks as if you have built LilyPond yourself and sourced
buildscripts/lilypond-profile.sh instead of the correct one:
buildscripts/out/lilypond-profile.
/Mats
Thanks. That fixed it!
Carl
On Wed, 2004-10-27 at 08:36, Werner LEMBERG wrote:
I have a fundamental problem with the width of lilypond output, and
which should be fixed before releasing 2.4. Currently, I use
(interval-start (ly:stencil-extent page X))
but this isn't the right value. Reason: Contrary to TeX
On Sun, 2004-10-31 at 16:20, Juergen Reuter wrote:
And, whenever changing feta-schrift, don't forget to clean the font such
that all font files will be rebuilt; otherwise, you will not see any
change, or the font will be messed up (as inserting a new character
changes the numbers in the
On Mon, 2004-11-01 at 21:32, Carl Sorensen wrote:
I'm trying to get documentation to work so I can make an attempt at
including the programming concepts chapter.
When I run make web, I get the following, after a bunch of apparently
successful stuff:
Invoking `gs -sDEVICE=bbox -q
to the programming
concepts (or internals reference ) manual.
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
in the lilypond file.
How can I make this work?
Thanks,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Tue, 2004-11-09 at 13:32, Nicolas Sceaux wrote:
Since that thread, the first guile module name used in the lily file
has changed: (*anonymous-ly-0*) iso (*anonymous-ly-1*).
Thanks! That fixed it.
Carl
___
lilypond-devel mailing list
[EMAIL
I'm trying to make a FretDiagram context and a Fret_diagram_engraver to
better implement fret diagrams.
Here's what I've done:
1. Copied ChordNames context in ly/engraver-init.ly
Modified as it seemed to make sense to me.
\context {
\type Engraver_group_engraver
\name FretDiagram
On Wed, 2004-11-10 at 01:31, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Someone (probably Score) should accept the FretDiagram
engraver.
(context)
I changed the name of the context from FretDiagram to FretDiagrams, for
consistency with ChordNames.
Then I added a line to
On Wed, 2004-11-10 at 07:39, Mats Bengtsson wrote:
I hope you have checked that LilyPond really reads the copy of
the engraver-init.ly file that you edit (run lilypond --verbose
to see the full path).
/Mats
Thanks, Mats. That helped me see what was going on.
I was changing
I've (somewhat) successfully created a FretDiagrams context, with a
Fret_diagram_engraver. I can sort of make things work. Now I'd like
some clarification on Items.
As part of the engraver, I have the code
fret_diagram_ = make_item (FretDiagram,SCM_EOL); //WHAT GOES HERE?
It appears to me
On Thu, 2004-11-11 at 01:44, Jan Nieuwenhuizen wrote:
This should be a symlink:
09:42:47 [EMAIL PROTECTED]:~/lily
$ ls -l share/lilypond/ly
lrwxrwxrwx 1 janneke janneke 21 2004-10-17 14:05 share/lilypond/ly -
/home/janneke/lily/ly/
No, but you may want to find out why the
I've succeeded in getting a fret diagram out of a FretDiagrams context.
(The Fret_diagram_engraver is hard-coded to only produce a single
diagram for now, but it still lets me test out contexts).
Here's the .ly file:
\score{
\chords{d}
\new FretDiagrams {d}
\chordmode{d}
}
On Fri, 2004-11-12 at 01:42, Jan Nieuwenhuizen wrote:
The directories are symlinked, not the files.
08:37:57 [EMAIL PROTECTED]:~/lily
OK, now I understand what's going on. I have two copies of the lilypond
source on my system: one in current-cvs/ and one in cds-dev/.
I'm making my new
I've been exploring the architecture of the FretDiagrams context.
One thing I think is really important to do is to have the FretDiagrams
music expression be the same as the ChordNames music expression. That
way the user doesn't have to try to synchronize two different sets of
chord definitions.
On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
* We tack frets onto \chordmode{}, that is, we do
chordScheme = \chordmode { d }
\new FretDiagrams \chordScheme
\new ChordNames \chordScheme
The \chordmode produce d fis a. In Fret_diagram engraver (contained
in
get started by referring to the web site:
http://lilypond.org/web/devel/participating/
The code you'll need to work with is likely found in
lily/tab-note-heads-engraver.cc.
Have fun!
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED
started by implementing things in guile
(scheme), rather than starting off playing with the parser.
Hope this helps,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
* Although it is possible to make a #(set-fret-diagram-string ) , I
think we can use the mechanism now used for chord exceptions, ie.
* I suppose that this is still too difficult for normal users, and
that we should also have an option
On Sat, 2004-11-20 at 16:16, Giancarlo Niccolai wrote:
Actually, I am quite fresh on parsers (just developed a language), however, I
sense you are right in the idea of starting slow; however, although I have
some basic knowledge of scheme, I suppose I can only hack around
copyingpasting
On Sun, 2004-11-21 at 09:24, Han-Wen Nienhuys wrote:
there is nothing stopping you from entering the chord in \chordmode, i
believe,
exceptions = \chordmode
{
c:dim7-\markup { \fretdiagram sitnhsoit }
}
for ideas, check chord-modifiers-init.ly
Actually,
On Sun, 2004-11-21 at 05:15, Giancarlo Niccolai wrote:
Uhm, since you are working on the chords: is there any possibility to have
chord names also in other languages? I.e. Am in italian is LAm, Bsus4 is
SIsus4 (only the note name changes, the chord system is the same all over the
world);
On Sun, 2004-11-21 at 05:25, Han-Wen Nienhuys wrote:
I think that
a. we are storing chords in the wrong way. In retrospect, I find
root + list of (step, alteration) tuples
more logical
So rather than using the pitches as the key for the hash table, it ought
to be the chord
On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
* I suppose that this is still too difficult for normal users, and
that we should also have an option
a. to override fret diagrams for once, eg.
\chordmode { d:add9 \frets abc9312 }
b. to override a fret diagram from now on
to these two cases. Are there any other cases?
Thanks,
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
was last seen living in the hands of Carl Sorensen (I believe). Can
you try to make the info appear there?
I think it can. But I don't think we yet have the right
internationalization system. We've changed chordnames, but not easy
noteheads. I've got a plan to make that happen, but I'd still
certainly
want to be able to pass the same music expression to both contexts, and
have each context do the right thing.
Carl Sorensen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
1301 - 1400 of 1841 matches
Mail list logo
