Re: Chord Naming

[Tao Cumplido]

I never use fret diagrams so I don't know how this predefined exceptions work. 
If I understand it right you want to make a list of all possibillities named on 
dolmetsch.com so that everyone can pick his/her favourite way?!

Generally I think it's a good idea to improve the chord symbols in LP, or maybe 
what I propose is a complete redesign. I don't know exactly how this works 
internally since I am no programmer.
In my opinion the main problem is that chord symbols are linked to actual 
notes. This probably works well for simple folkloric structures but becomes 
problematic in complex jazz constructions. A jazz chord symbol is rather linked 
to a scale than a chord but in most cases isn't limited to a single scale, e.g. 
G7alt. can mean to play G mixolydian b13, G altered (superlocrian), HTWT or 
HTWT. Even Cmaj7 isn't limited to ionian but can also mean lydian since the 
perfect fourth is an avoid tone in maj7.

I think the best solution would be to make the suffix of a chord symbol, i.e. 
everything after the root, plain text. This would allow everyone to choose 
his/her favourite suffix by just typing standard characters.
I already do something similar. I use a tweaked font to display my chord 
symbols in a Lyrics context above the Staff. This doesn't let me transpose 
though and I always have to create transposed parts manually but I still prefer 
it to the current function of LP because it allows easy displaying of chord 
symbols to my like.
Also defining exceptions in advance would become unnecessary because all 
exceptions are stored to different characters and one has only to learn his/her 
favourite way of displaying chords once.

Whatever way you want to go, dolmetsch.com is still missing some common 
exceptions and variations and I'd be happy to help out with expanding your 
exceptions list.

Regards,

Tao

 Original-Nachricht 
> Datum: Fri, 23 Jan 2009 22:48:41 -0500
> Von: David Stocker 
> An: "Carl D. Sorensen" 
> CC: lilypond , lilypond-devel 
> Betreff: Re: Chord Naming

> Carl,
> 
> I think this would greatly improve the chords feature of LilyPond. I 
> don't think I've ever seen a Cmaj7/9/add13 chord in actual printed 
> music, but I know how to play a Cmaj13, Cm13b5, or a Cm9#11.
> 
> I'd be happy to help with this in any way I can, even if it's only 
> testing. I can commit to a few hours a week on this, once you get it 
> going (if you'd like).
> 
> Let me know if you need that kind of assistance, since I'm not a
> programmer.
> 
> Dave
> 
> Carl D. Sorensen wrote:
> > We currently have issues with the chord naming functions of LilyPond. 
> If we
> > pass a \chordmode chord to the the ChordNames construct, we very seldom
> get
> > out what we put in (i.e. c:maj13 will give Cmaj7/9/add13).  This is
> because
> > we currently try to do the chord naming algorithmically.
> >
> > I'd like to add a feature similar to the predefinedFretDiagrams feature.
>  It
> > would be a simple means of modifying the chodNameExceptions data
> structure
> > (or perhaps a replacement of that structure) so that you could define a
> > chord name by giving a \chordmode chord specifier.  Then, I'd have an
> init
> > file that would initialize all the chords specified in Dolmetsch online
> >  and
> > .  This combination should
> cover
> > virtually all the chords people use.  Of course, if the chord somebody
> wrote
> > wasn't covered, we'd still fall back to the current algorithm, which is
> > correct, but not compact.
> >
> > I think the exceptions for the chords could be defined so that the chord
> > display properties are included in the exception.
> >
> > Does this seem like something that would be useful to add to LilyPond? 
> And
> > would this kind of architecture be acceptable, in principle?
> >
> > Thanks,
> >
> > Carl
> >
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-u...@gnu.org
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
> >
> >
> >   
> 
> 
> ___
> lilypond-user mailing list
> lilypond-u...@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL 
für nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: automatic setting of `currentBarNumber'

[Nicolas Sceaux]

Le 23 janv. 09 à 07:19, Werner LEMBERG a écrit :


#(define lastBarNumber 10)

 \score {
   \relative {
 c1 | d1 | e1 | f1 |
   \applyContext
 #(lambda (x)
   (set! lastBarNumber (ly:context-property x 'currentBarNumber)))
 }


The procedure argument of \applyContext is applied when the music is
interpreted. However, you want to use lastBarNumber when the following
score is parsed, which happens before the first score is interpreted:

\score {
  \relative {
\set Score . currentBarNumber = #lastBarNumber
...
  }
}

currentBarNumber must be an integer, so the value is computed at parsing
time. If it could be a procedure, which evaluation would be delayed at
music interpretation time, then it would be possible. That requires
modifying LilyPond code (unless I'm missing something).

For a possible solution, see the attached patch.


bar-number-proc.patch
Description: Binary data




\version "2.12.1"

#(define bar-number-proc #f)
#(define set-previous-bar-number! #f)

#(let ((previous-bar-number 0))
  (set! bar-number-proc
(lambda (num) (+ num previous-bar-number -1)))
  (set! set-previous-bar-number!
(lambda (num) (set! previous-bar-number num

\score {
  \relative {
\bar "" c1 |\break d1 |\break e1 |\break f1 |
\applyContext
#(lambda (x)
  (set-previous-bar-number! (ly:context-property x  
'currentBarNumber)))

  }
}

\score {
  \relative {
\set Score . currentBarNumberProc = #bar-number-proc
\bar "" c1 |\break d1 |\break e1 |\break f1 |
  }
}

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: why is Instrument_name_engraver not universal?

[Reinhold Kainhofer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Samstag, 24. Januar 2009 08:11:46 schrieb Mark Polesky:
> I know we've been through this before*, but
> does anyone have a good reason NOT to add
> Instrument_name_engraver to ALL the staff
> contexts? 

I've wondered about that too, some time ago. In particular, if one does not 
set instrumentName or shortInstrumentName, it will not have any effect on the 
staff or group. On the other hand, if one sets one of these properties, then 
definitely wants these names to appear. So, intuitively, I would also say that 
the engraver should be added to all staves and groups. I don't know if there 
are some technical reasons against it, though. (FWIW, In my OrchestralLily 
package I already add the engraver to all staves, so I have not been bothered 
by this problem for quite a while now, but it would still be better if the 
plain vanilla LilyPond would already have that setting).

Cheers,
Reinhold
- -- 
- --
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJew8uTqjEwhXvPN0RAjGSAKCur2uF7tTVLCYF39KSIRDcLB1F4QCeKTyk
48jXPn1OsQWLqIZU4Zn3rNg=
=utlT
-END PGP SIGNATURE-


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: References in Contributor's Guide

[Graham Percival]

On Thu, Jan 22, 2009 at 05:54:38PM -0700, Carl D. Sorensen wrote:
> 1) I included an @ref{} reference to the CG, and it wasn't valid.  Does
> @ref{} work for the CG?

@ref{} to a node within the CG, done from within the CG, works.
Maybe you had the wrong capitalization?  Maybe the @node you were
trying to refer to had the wrong capitalization?

> 2) I didn't find out that I'd made the mistake, because I did make web from
> Documentation/user, which doesn't rebuild the CG.  Is there a way to rebuild
> the CG and check cross references without rebuilding the entire
> (multi-language) documentation tree?

Try it from Documentation/devel/

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: References in Contributor's Guide

[Carl D. Sorensen]

On 1/24/09 6:03 AM, "Graham Percival"  wrote:

> 
>> 2) I didn't find out that I'd made the mistake, because I did make web from
>> Documentation/user, which doesn't rebuild the CG.  Is there a way to rebuild
>> the CG and check cross references without rebuilding the entire
>> (multi-language) documentation tree?
> 
> Try it from Documentation/devel/

When I do that, I get lots of errors that I've never seen before in working
with docs:

/Users/Carl/lilypond-working/Documentation/devel/git-starting.itexi:155:
Undefined control sequence.
l.1 @quotedblleft
 {...@xeatspaces {pu...@quotedblright{}@endinput
@scanmacro ...ceisspace @scantokens {...@endinput }
  @endgroup
@macnamexxx .@xeatspaces {...@quotedblright{}}
  @egroup
l.155 ...e with the most recent changes (@qq{pull}
  ing),
/Users/Carl/lilypond-working/Documentation/devel/git-starting.itexi:155:
Undefined control sequence.
l.1 ...tedbllef...@xeatspaces {pu...@quotedblright
  {...@endinput
@scanmacro ...ceisspace @scantokens {...@endinput }
  @endgroup
@macnamexxx .@xeatspaces {...@quotedblright{}}
  @egroup
l.155 ...e with the most recent changes (@qq{pull}
  ing),



And so on.  So I assumed that this was a problem in how make web worked.

Is this just a problem in the file?

Carl



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Chord Naming

[Carl D. Sorensen]

On 1/24/09 4:02 AM, "Tao Cumplido"  wrote:

> I never use fret diagrams so I don't know how this predefined exceptions work.

You can get a description of how the predefined fretboards work, including
the addition of new diagrams, by looking in the Notation Reference, Section
2.4.1 Common notation for fretted strings under Automatic fret diagrams.

> If I understand it right you want to make a list of all possibillities named
> on dolmetsch.com so that everyone can pick his/her favourite way?!

Not quite.  I want to make a facility that makes it easy for everyone to
create their favorite way, if one of the defaults isn't what is wanted.  And
dolmetsch.com just provides a list of the predefined chords.  Any extra
chords would have to be defined by the user.

> In my opinion the main problem is that chord symbols are linked to actual
> notes. This probably works well for simple folkloric structures but becomes
> problematic in complex jazz constructions. A jazz chord symbol is rather
> linked to a scale than a chord but in most cases isn't limited to a single
> scale, e.g. G7alt. can mean to play G mixolydian b13, G altered
> (superlocrian), HTWT or HTWT. Even Cmaj7 isn't limited to ionian but can also
> mean lydian since the perfect fourth is an avoid tone in maj7.

This is hard for me to understand.  Do you mean that in a jazz leadsheet, if
the chord symbol says G7alt. the musician is free to choose any of the
options you present?

Even if this is true, as long as you only want the ChordNames output, there
is no harm in defining a particular set of notes that will give you Cmaj7 as
a symbol.  The ChordNames output won't have any notes, just text.  And as
long as the input is as simple as c:maj7 to get Cmaj7 as an output, I think
the system works.

> 
> I think the best solution would be to make the suffix of a chord symbol, i.e.
> everything after the root, plain text. This would allow everyone to choose
> his/her favourite suffix by just typing standard characters.

If one only cares about the ChordNames context, then what you propose works.
If, on the other hand, one wants to be able to use the same music expression
for notes, FretBoards, and ChordNames (which at least I do), then picking a
root plus a freely chosen suffix doesn't work anymore.

> I already do something similar. I use a tweaked font to display my chord
> symbols in a Lyrics context above the Staff. This doesn't let me transpose
> though and I always have to create transposed parts manually but I still
> prefer it to the current function of LP because it allows easy displaying of
> chord symbols to my like.

Since all you want is text, the Lyrics method works.  And you would be able
to continue to use it under my proposal.

> Also defining exceptions in advance would become unnecessary because all
> exceptions are stored to different characters and one has only to learn
> his/her favourite way of displaying chords once.

The same is true under my proposal.  Exceptions (I don't really like the
term; I'd prefer to just call them chord names) are stored as different
characters, and one only had to learn to display them once.  And if one has
additional chord names that are not

> 
> Whatever way you want to go, dolmetsch.com is still missing some common
> exceptions and variations and I'd be happy to help out with expanding your
> exceptions list.
> 
Thanks for the feedback, and for the offer of help,

Carl



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: References in Contributor's Guide

[Graham Percival]

On Sat, Jan 24, 2009 at 07:28:40AM -0700, Carl D. Sorensen wrote:
> 
> On 1/24/09 6:03 AM, "Graham Percival"  wrote:
> 
> > Try it from Documentation/devel/
> 
> When I do that, I get lots of errors that I've never seen before in working
> with docs:
> 
> /Users/Carl/lilypond-working/Documentation/devel/git-starting.itexi:155:
> Undefined control sequence.
> l.1 @quotedblleft
>  {...@xeatspaces {pu...@quotedblright{}@endinput

Hmm... you're using texinfo 4.11 or less?  That's what I would
take away from that message; the nice @quote commands were IIRC
added in 4.12.

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: References in Contributor's Guide

[Carl D. Sorensen]

On 1/24/09 8:57 AM, "Graham Percival"  wrote:

> On Sat, Jan 24, 2009 at 07:28:40AM -0700, Carl D. Sorensen wrote:
>> 
>> On 1/24/09 6:03 AM, "Graham Percival"  wrote:
>> 
>>> Try it from Documentation/devel/
>> 
>> When I do that, I get lots of errors that I've never seen before in working
>> with docs:
>> 
>> /Users/Carl/lilypond-working/Documentation/devel/git-starting.itexi:155:
>> Undefined control sequence.
>> l.1 @quotedblleft
>>  {...@xeatspaces {pu...@quotedblright{}@endinput
> 
> Hmm... you're using texinfo 4.11 or less?  That's what I would
> take away from that message; the nice @quote commands were IIRC
> added in 4.12.

AHA -- it seems I have multiple texinfo versions on my machine.  The one I
installed with macports is version 4.13:

sorensen2:lilypond-working Carl$ port info texinfo
texinfo @4.13 (textproc)

But the one that I have as part of Pdftexk is older, and is apparently used
when I run make web in Documentation/devel :

This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=pdfetex
2007.5.18)  24 JAN 2009 09:12
entering extended mode
 file:line:error style messages enabled.
 %&-line parsing enabled.
**\nonstopmode \input ./contrib-guide.texi
(./contrib-guide.texi
(/usr/local/texlive/2007/texmf-dist/tex/texinfo/texinfo.tex
Loading texinfo [version 2007-01-02.19]:

Any idea how I can get the right version called from  make web in
Documentation/devel ?

Thanks,

Carl




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Please fix: japanese doc compilation

[Reinhold Kainhofer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Samstag, 24. Januar 2009 07:48:01 schrieb Sawada, Yoshiki:
> Now, I face one problem.
> Text strings which appear in navigation sections of my HTML files (such as
> "[ Introduction >> ]") look strange. 

These translations are done directly in texi2html. I'm attaching the current 
i18n/ja file from the texi2html distribution. You might want to update the 
translation directly in that file and send it to Patrice Dumas (the main 
developer or texi2html) or even better to the texi2html mailing list:  
texi2html-...@nongnu.org

What exactly looks strange and how should it look? Can you give us a simple 
example / screenshot?

> I guess a character code of a script
> file which handles navigation sections is wrong. Can you tell me which
> script file handles navigation?

That's texi2html itself, we are not changing anything in the navigation bars 
afterwards.

> But, it is not a big problem, so I will resolve it some time.

BTW, I just noticed that in addition to the texinfo files for the 
documentation and the .po file for the extracted strings, we have one more 
spot where we need a Japanese translation: the [Back to Documentation index] 
link in the left upper corner of the docs (above the TOC) is translated in our 
texi2html configuration script (lilypond-texi2html.init). 


> I really thank you for helping me to produce Japanese LilyPond
> Documenation.

Sure, after all, we are all working together on making the best application 
for music scores.

Cheers,
Reinhold
- -- 
- --
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJe29XTqjEwhXvPN0RAjA7AKCK/nm6P382PuXFcQdC0z6GRFehMACfdjXu
IdEsC8rilmH6qo5emYIUv1E=
=EQMD
-END PGP SIGNATURE-
$LANGUAGES->{'ja'} = {
   '  The buttons in the navigation panels have the 
following meaning:' => 
'ナビゲーションパネル中のボタンには以下の意味があります。',
   '  where the @strong{ Example } assumes that the current 
position is at @strong{ Subsubsection One-Two-Three } of a document of the 
following structure:' => 
'@strong{例}では、以下に示す構造を持つ文書ã�...@strong{1.2.3項}を現在位置に仮定しています。',
   ' Up ' => '上',
   '%{acronym_like} (%{explanation})' => '',
   '%{month} %{day}, %{year}' => 
'%{year}年%{month}月%{day}日',
   '%{name} of %{class}' => '',
   '%{name} on %{class}' => '',
   '%{node_file_href}' => '',
   '%{node_file_href} @cite{%{book}}' => '',
   '%{node_file_href} section `%{section}\' in 
@cite{%{book}}' => '',
   '%{reference_name}' => '',
   '%{style} %{number}' => '',
   '%{style}: %{caption_first_line}' => '',
   '%{style}: %{shortcaption_first_line}' => '',
   '@b{%{quotation_arg}:} ' => '',
   '@cite{%{book}}' => '',
   'About' => '',
   'About (help)' => '',
   'About This Document' => 'この文書について',
   'April' => '4月',
   'August' => '8月',
   'Back' => '',
   'Back section in previous file' => '',
   'Beginning of this chapter or previous chapter' => '',
   'Button' => 'ボタン',
   'Contents' => '目次',
   'Cover (top) of document' => '',
   'Current Position' => '現在位置',
   'Current section' => '',
   'December' => '12月',
   'FastBack' => '',
   'FastForward' => '',
   'February' => '2月',
   'First' => '',
   'First section in reading order' => '',
   'Following' => '',
   'Following node' => '',
   'Footnotes' => '脚注',
   'Forward' => '',
   'Forward section in next file' => '',
   'From 1.2.3 go to' => '1.2.3項からの移動先',
   'Go to' => '移動先',
   'Index' => '見出し',
   'Index Entry' => '見出し一覧',
   'January' => '1月',
   'July' => '7月',
   'Jump to' => '移動',
   'June' => '6月',

Problems with texi2html and Japanese navigation bars

[Reinhold Kainhofer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Patrice,
Recently, a Japanese guy decided to start translating the LilyPond 
documentation to Japanese. It basically works with texi2html (texi2pdf doesn't 
even handle Japanese glyphs at all!), however, we are running into a problem 
with the navigation bars: 

The strings are translated, but unfortunately they are not written out in 
UTF-8 to the html file, but in some other encoding (I couldn't find out which, 
none of the three major Japanese non-utf-8 encodings seems to fit!). For 
example, the [Top] link in the navbars is displayed as [å†’é ­] (that's an a 
with a ring diacritic above, a dagger, an apostrophe and an e with an acute 
accent) instead of the correct two-glyph [冒頭].

An example (.texi file to be run as "texi2html japanese.texi" and the 
resulting .html file) is attached.

Cheers,
Reinhold
- -- 
- --
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJe3ObTqjEwhXvPN0RAvQwAJ4ks0l67acMwb1yCEAFoqfxTlLqhACgn5Qk
7kyGWpiLNu2wldJzjnU+J+0=
=ylmy
-END PGP SIGNATURE-
\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
@documentencoding UTF-8
@setfilename lilypond-learning.info
@settitle GNU LilyPond -- Manuel d'initiation

@documentlanguage ja

@node Top
@top GNU LilyPond --- 学習マニュアル

@copying
Copyright @copyright{} 1999--2008 著作者一同

@emph{The translation of the following copyright notice is provided
for courtesy to non-English speakers, but only the notice in English
legally counts.}

@emph{以下は英語を話さない人々のための著作権についての注意書きです。しかしながら、
英語で書かれた注意書きだけが法的に有効です。}
@end copying


これは GNU LilyPond バージョン 

@menu
* Preface::
* Introduction::   LilyPond とは何なのか、なぜ LilyPond を使うのか、どうやって 
LilyPond を使うのか
@end menu

@node Preface
@chapter Preface

それは 1995 年のある日の EJE (Eindhoven Youth Orchestra) のリハーサル中のできごとでした − 
ある変わり者のバイオリン奏者であるジャンは同じく変わり者のフレンチホルン奏者のハン-ウェンに彼がかかわっている新しい大きなプロジェクトのことを話しました。それは音楽を出版するための自動化されたシステムです
 (正確には、それは MPP − MusiXTeX 
のプリプロセッサです)。それを聞いてハン-ウェンはすぐに楽譜からいくつかの部分をプリントアウトしたいと思い、彼はそのためのソフトウェアを探し始め、すぐにその虜になってしまいました。それが
 MPP の終わりを決定付けました。多くの哲学的考察を含み白熱した email の交換の後、ハン-ウェンは 1996 年に LilyPond 
の製作を開始しました。この時、ジャンはハン-ウェンの新しいプロジェクトに引きずり込まれました。


@node Introduction
@chapter Introduction

この章では読者に LilyPond とこのドキュメントについての紹介を行います。

@bye
http://www.w3.org/TR/html401/loose.dtd";>




GNU LilyPond – Manuel d'initiation


















[冒頭]
[目次]
[見出し]
[ ? 
]


GNU LilyPond — 学習マニュアル



これは GNU LilyPond バージョン 


1. 
Preface  

2. 
Introduction  
   LilyPond とは何なのか、なぜ LilyPond を使うのか、どうやって LilyPond を使うのか






[ < ]
[ > ]
   
[ << ]
[上]
[ 
>> ]
   
   
   
   
[冒頭]
[目次]
[見出し]
[ ? 
]


1. Preface

それは 1995 年のある日の EJE (Eindhoven Youth Orchestra) のリハーサル中のできごとでした − 
ある変わり者のバイオリン奏者であるジャンは同じく変わり者のフレンチホルン奏者のハン-ウェンに彼がかかわっている新しい大きなプロジェクトのことを話しました。それは音楽を出版するための自動化されたシステムです
 (正確には、それは MPP − MusiXTeX 
のプリプロセッサです)。それを聞いてハン-ウェンはすぐに楽譜からいくつかの部分をプリントアウトしたいと思い、彼はそのためのソフトウェアを探し始め、すぐにその虜になってしまいました。それが
 MPP の終わりを決定付けました。多くの哲学的考察を含み白熱した email の交換の後、ハン-ウェンは 1996 年に LilyPond 
の製作を開始しました。この時、ジャンはハン-ウェンの新しいプロジェクトに引きずり込まれました。





[ < ]
[ > ]
   
[ << ]
[上]
[ >> ]
   
   
   
   
[冒頭]
[目次]
[見出し]
[ ? 
]


2. Introduction

この章では読者に LilyPond とこのドキュメントについての紹介を行います。




[冒頭]
[目次]
[見出し]
[ ? 
]

この文書について

  この文書はReinhold 
Kainhoferによって2009年1月月24日にhttp://www.nongnu.org/texi2html/";>texi2html 
1.83を用いて生成されました。


ナビゲーションパネル中のボタンには以下の意味があります。


  
 ボタン 
 名称 
 移動先 
 1.2.3項からの移動先
  
  
 [ < ] 
Back
Previous section in reading order
1.2.2
  
  
 [ > ] 
Forward
Next section in reading order
1.2.4
  
  
 [ << ] 
FastBack
Beginning of this chapter or previous chapter
1
  
  
 [上] 
Up
Up section
1.2
  
  
 [ >> ] 
FastForward
Next chapter
2
  
  
 [冒頭] 
冒頭
Cover (top) of document
   
  
  
 [目次] 
目次
Table of contents
   
  
  
 [見出

garbled characters in gmane archive (devel)

[Mark Polesky]

Is this a known issue with gmane? Do we care?

characters were formatted correctly in the gnu archive...
  http://lists.gnu.org/archive/html/lilypond-user/2009-01/msg00896.html
...but were "struck-out" in the gmane one:
  http://article.gmane.org/gmane.comp.gnu.lilypond.general/44760

- Mark



  


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: automatic setting of `currentBarNumber'

[Werner LEMBERG]

> currentBarNumber must be an integer, so the value is computed at
> parsing time.  If it could be a procedure, which evaluation would be
> delayed at music interpretation time, then it would be possible.
> That requires modifying LilyPond code (unless I'm missing
> something).
> 
> For a possible solution, see the attached patch.

Thanks!  However, I believe that this ad-hoc solution is too specific;
I can imagine that there are other useful applications which need
evaluation at music interpretation time.  Any suggestion how to make
this more generic?


Werner


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Lilypond on Macports

[David Baumgold]

I'm a big fan of Macports, and since lilypond seems to be so difficult 
to compile, I figured I would try to write a portfile for it, to make
compiling easier for everyone. After about a week's work of research and
many, many failed attempts, I finally have a portfile that seems to
work. Can people test this portfile to verify that lilypond builds
correctly? And if it reliably does so, can this information be put on
the lilypond download page?

To compile lilypond using Macports, first make sure you have XCode 
installed. Then just download Macports from http://www.macports.org/ and
install it, add /opt/local to your PATH, and then run "sudo port install
lilypond". That's it. Macports will download, compile, and install
lilypond and its dependencies.

Also, I have not yet tested the GUI option in lilypond. To try building 
it, run "sudo port install lilypond +gui" instead of just "sudo port
install lilypond". If it works, great -- if it doesn't, can people post
their error messages?



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

instrument-specific-markup interface

[Carl D. Sorensen]

Both markup fret diagrams and harp pedal markups share the
instrument-specific-markup interface.  The instrument-specific-markup
interface contains fret-diagram-details, harp-pedal-details, size, and
thickness.

Do we need to combine the two interfaces into one
instrument-specific-markup-interface?  This seems strained to me.  I would
prefer to have a

fret-diagram-markup-interface
with
fret-diagram-details, size, thickness

and a

harp-pedal-interface
with
harp-pedal-details, size, thickness

so that the two aren't combined.  I think that will be more clear.

Is there any reason not to do that?

Carl



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: instrument-specific-markup interface

[Patrick McCarty]

On Sat, Jan 24, 2009 at 2:38 PM, Carl D. Sorensen  wrote:
> Both markup fret diagrams and harp pedal markups share the
> instrument-specific-markup interface.  The instrument-specific-markup
> interface contains fret-diagram-details, harp-pedal-details, size, and
> thickness.
>
> Do we need to combine the two interfaces into one
> instrument-specific-markup-interface?  This seems strained to me.  I would
> prefer to have a
>
> fret-diagram-markup-interface
> with
> fret-diagram-details, size, thickness
>
> and a
>
> harp-pedal-interface
> with
> harp-pedal-details, size, thickness
>
> so that the two aren't combined.  I think that will be more clear.
>
> Is there any reason not to do that?

I'm okay with it.

If more specialized markup environments are added to LilyPond in the
future, I could see the instrument-specific-markup interface page
getting very lengthy, so I think it would be best to split it up.

-Patrick


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Lilypond on Macports

[Jonathan Kulp]

David Baumgold wrote:
I'm a big fan of Macports, and since lilypond seems to be so difficult 
to compile, I figured I would try to write a portfile for it, to make

compiling easier for everyone. After about a week's work of research and
many, many failed attempts, I finally have a portfile that seems to
work. Can people test this portfile to verify that lilypond builds
correctly? And if it reliably does so, can this information be put on
the lilypond download page?

To compile lilypond using Macports, first make sure you have XCode 
installed. Then just download Macports from http://www.macports.org/ and

install it, add /opt/local to your PATH, and then run "sudo port install
lilypond". That's it. Macports will download, compile, and install
lilypond and its dependencies.

Also, I have not yet tested the GUI option in lilypond. To try building 
it, run "sudo port install lilypond +gui" instead of just "sudo port

install lilypond". If it works, great -- if it doesn't, can people post
their error messages?



David,

Thanks for doing this.  It's a very good idea!

I just tried it and it failed when building pango.  It said my Xcode is 
too old (2.0) and that I need to update to at least 2.4.1.  This is an 
eMac G4 that's about 4 years old.  I have an Intel iMac on my desk at 
work, though, so I'll try it there, too.  It's a much newer machine and 
the Xcode tools are probably up-to-date.


Jon
--
Jonathan Kulp
http://www.jonathankulp.com


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Lilypond on Macports

[Josh Parmenter]

Hi David,

I'm running it right now on a newer mac intel, and am noticing tons of  
xorg stuff... is this for the GUI? Does the regular X11 not cover  
these dependencies?


Thanks for doing this!

Josh

On Jan 24, 2009, at 3:27 PM, Jonathan Kulp wrote:


David Baumgold wrote:
I'm a big fan of Macports, and since lilypond seems to be so  
difficult to compile, I figured I would try to write a portfile for  
it, to make
compiling easier for everyone. After about a week's work of  
research and

many, many failed attempts, I finally have a portfile that seems to
work. Can people test this portfile to verify that lilypond builds
correctly? And if it reliably does so, can this information be put on
the lilypond download page?
To compile lilypond using Macports, first make sure you have XCode  
installed. Then just download Macports from http:// 
www.macports.org/ and
install it, add /opt/local to your PATH, and then run "sudo port  
install

lilypond". That's it. Macports will download, compile, and install
lilypond and its dependencies.
Also, I have not yet tested the GUI option in lilypond. To try  
building it, run "sudo port install lilypond +gui" instead of just  
"sudo port
install lilypond". If it works, great -- if it doesn't, can people  
post

their error messages?

David,

Thanks for doing this.  It's a very good idea!

I just tried it and it failed when building pango.  It said my Xcode  
is too old (2.0) and that I need to update to at least 2.4.1.  This  
is an eMac G4 that's about 4 years old.  I have an Intel iMac on my  
desk at work, though, so I'll try it there, too.  It's a much newer  
machine and the Xcode tools are probably up-to-date.


Jon
--
Jonathan Kulp
http://www.jonathankulp.com


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


**
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own  
interpretation of how modern society is structured: whether actively  
or passively, consciously or unconsciously, he makes choices in this  
regard. He may be conservative or he may subject himself to continual  
renewal; or he may strive for a revolutionary, historical or social  
palingenesis." - Luigi Nono

*/



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Lilypond on Macports

[James E. Bailey]

Am 25.01.2009 um 00:53 schrieb Josh Parmenter:


Hi David,

I'm running it right now on a newer mac intel, and am noticing tons  
of xorg stuff... is this for the GUI? Does the regular X11 not  
cover these dependencies?


It's for fontforge. If you look at the depencies (and the  
dependencies of depencies) all of the Xorg libraries are dependencies  
for fontforge. It's one of the downsides of macports. If you compile  
it yourself, you actually don't need all of those. At least, I didn't  
when I did.



Thanks for doing this!

Josh

On Jan 24, 2009, at 3:27 PM, Jonathan Kulp wrote:


David Baumgold wrote:
I'm a big fan of Macports, and since lilypond seems to be so  
difficult to compile, I figured I would try to write a portfile  
for it, to make
compiling easier for everyone. After about a week's work of  
research and

many, many failed attempts, I finally have a portfile that seems to
work. Can people test this portfile to verify that lilypond builds
correctly? And if it reliably does so, can this information be  
put on

the lilypond download page?
To compile lilypond using Macports, first make sure you have  
XCode installed. Then just download Macports from http:// 
www.macports.org/ and
install it, add /opt/local to your PATH, and then run "sudo port  
install

lilypond". That's it. Macports will download, compile, and install
lilypond and its dependencies.
Also, I have not yet tested the GUI option in lilypond. To try  
building it, run "sudo port install lilypond +gui" instead of  
just "sudo port
install lilypond". If it works, great -- if it doesn't, can  
people post

their error messages?

David,

Thanks for doing this.  It's a very good idea!

I just tried it and it failed when building pango.  It said my  
Xcode is too old (2.0) and that I need to update to at least  
2.4.1.  This is an eMac G4 that's about 4 years old.  I have an  
Intel iMac on my desk at work, though, so I'll try it there, too.   
It's a much newer machine and the Xcode tools are probably up-to- 
date.


Jon
--
Jonathan Kulp
http://www.jonathankulp.com


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


**
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own  
interpretation of how modern society is structured: whether  
actively or passively, consciously or unconsciously, he makes  
choices in this regard. He may be conservative or he may subject  
himself to continual renewal; or he may strive for a revolutionary,  
historical or social palingenesis." - Luigi Nono

*/



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: instrument-specific-markup interface

[Reinhold Kainhofer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am Samstag, 24. Januar 2009 23:38:53 schrieb Carl D. Sorensen:
> Both markup fret diagrams and harp pedal markups share the
> instrument-specific-markup interface.  The instrument-specific-markup
> interface contains fret-diagram-details, harp-pedal-details, size, and
> thickness.
>
> Do we need to combine the two interfaces into one
> instrument-specific-markup-interface?  This seems strained to me.  I would
> prefer to have a
[...]
> so that the two aren't combined.  I think that will be more clear.
>
> Is there any reason not to do that?

Funny thing is, you suggested to create one instrument-specific-markup-
interface:
http://lists.gnu.org/archive/html/lilypond-devel/2008-08/msg00325.html

I'm fine with either.

Cheers,
Reinhold

- -- 
- --
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJe68NTqjEwhXvPN0RAix7AJ9wwGt/Ni/yPNwkpErERJ7k9oMi7QCggYjd
c/8WIGKDrrmq1WNty4GJHow=
=z4ZL
-END PGP SIGNATURE-


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: instrument-specific-markup interface

[Carl D. Sorensen]

On 1/24/09 5:15 PM, "Reinhold Kainhofer"  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Am Samstag, 24. Januar 2009 23:38:53 schrieb Carl D. Sorensen:
>> Both markup fret diagrams and harp pedal markups share the
>> instrument-specific-markup interface.  The instrument-specific-markup
>> interface contains fret-diagram-details, harp-pedal-details, size, and
>> thickness.
>> 
>> Do we need to combine the two interfaces into one
>> instrument-specific-markup-interface?  This seems strained to me.  I would
>> prefer to have a
> [...]
>> so that the two aren't combined.  I think that will be more clear.
>> 
>> Is there any reason not to do that?
> 
> Funny thing is, you suggested to create one instrument-specific-markup-
> interface:
> http://lists.gnu.org/archive/html/lilypond-devel/2008-08/msg00325.html
> 


Yes, but I always reserve the right to change my mind.  I guess that means
I'm in touch with my feminine side. ;)

Having seen how it shakes out in the documentation, it seems wrong to have
an instrument-specific-markup-interface.  I thought it would be nice to have
one additional interface to add to TextScript objects.   Now I think it
would be better to have separate interfaces for each of the
instrument-specific markups.  It makes it more clear which properties apply
to which markups.

Thanks,

Carl



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Lilypond on Macports

[Josh Parmenter]

yes - that explains it! I have compiled it once on my own, and was  
surprised to see so much more that needed to be built!


Josh

On Jan 24, 2009, at 4:08 PM, James E. Bailey wrote:



Am 25.01.2009 um 00:53 schrieb Josh Parmenter:


Hi David,

I'm running it right now on a newer mac intel, and am noticing tons  
of xorg stuff... is this for the GUI? Does the regular X11 not  
cover these dependencies?


It's for fontforge. If you look at the depencies (and the  
dependencies of depencies) all of the Xorg libraries are  
dependencies for fontforge. It's one of the downsides of macports.  
If you compile it yourself, you actually don't need all of those. At  
least, I didn't when I did.



Thanks for doing this!

Josh

On Jan 24, 2009, at 3:27 PM, Jonathan Kulp wrote:


David Baumgold wrote:
I'm a big fan of Macports, and since lilypond seems to be so  
difficult to compile, I figured I would try to write a portfile  
for it, to make
compiling easier for everyone. After about a week's work of  
research and

many, many failed attempts, I finally have a portfile that seems to
work. Can people test this portfile to verify that lilypond builds
correctly? And if it reliably does so, can this information be  
put on

the lilypond download page?
To compile lilypond using Macports, first make sure you have  
XCode installed. Then just download Macports from http://www.macports.org/ 
 and
install it, add /opt/local to your PATH, and then run "sudo port  
install

lilypond". That's it. Macports will download, compile, and install
lilypond and its dependencies.
Also, I have not yet tested the GUI option in lilypond. To try  
building it, run "sudo port install lilypond +gui" instead of  
just "sudo port
install lilypond". If it works, great -- if it doesn't, can  
people post

their error messages?

David,

Thanks for doing this.  It's a very good idea!

I just tried it and it failed when building pango.  It said my  
Xcode is too old (2.0) and that I need to update to at least  
2.4.1.  This is an eMac G4 that's about 4 years old.  I have an  
Intel iMac on my desk at work, though, so I'll try it there, too.   
It's a much newer machine and the Xcode tools are probably up-to- 
date.


Jon
--
Jonathan Kulp
http://www.jonathankulp.com


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


**
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own  
interpretation of how modern society is structured: whether  
actively or passively, consciously or unconsciously, he makes  
choices in this regard. He may be conservative or he may subject  
himself to continual renewal; or he may strive for a revolutionary,  
historical or social palingenesis." - Luigi Nono

*/



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel




**
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own  
interpretation of how modern society is structured: whether actively  
or passively, consciously or unconsciously, he makes choices in this  
regard. He may be conservative or he may subject himself to continual  
renewal; or he may strive for a revolutionary, historical or social  
palingenesis." - Luigi Nono

*/



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Please fix: japanese doc compilation

[Sawada , Yoshiki]

Hello Reinhold,

Reinhold Kainhofer  kainhofer.com> wrote:

> These translations are done directly in texi2html. I'm attaching the current 
> i18n/ja file from the texi2html distribution. You might want to update the 
> translation directly in that file and send it to Patrice Dumas (the main 
> developer or texi2html) or even better to the texi2html mailing list:  
> texi2html-bug  nongnu.org

This advice really helped me.
I found an article about Texinfo (but it is a Japanese page). It says:

 start of English translation of the page 
texi2html uses utf-8 for HTML documents but it uses us-ascii for navigation 
bars.
Therefore, navigation bars look strange. To solve this, we need to disable
the Unicode support of texi2html as following steps:

*Step 1: Make an init file as following:
 start of "ja-init.pl" 
# -*- mode: perl -*-

$USE_UNICODE = 0;
# $ENCODING = "euc-jp";

1;
 end of "ja-init.pl" 

*Step 2: Add a following line to texinfo documents:
@documentencoding utf-8

*Step 3: Run texi2html as following:
$ texi2html --init-file=ja-init.pl lilypond-learning.texi
 end of English translation of the page 

This solution uses English messages catalog instead of Japanese messages catalog
(like as "Top" instead of "冒頭"). But, I do not know how to pass the option
"-init-file=ja-init.pl" to texi2html via "make web". So, I use "i18n/ja"
(which Reinhold gave me :)) to make messages catalog revert as following:
'Top' => 'Top',

If I need to translate a message in the catalog, I can use .po file.
I know this solution is not a fundamental solution, but this works well now.

> What exactly looks strange and how should it look? Can you give us a simple 
> example / screenshot?

I guess you found my translation page (http://irjb.s346.xrea.com/lilypond/).

> BTW, I just noticed that in addition to the texinfo files for the 
> documentation and the .po file for the extracted strings, we have one more 
> spot where we need a Japanese translation: the [Back to Documentation index] 
> link in the left upper corner of the docs (above the TOC) is translated in 
> our 
> texi2html configuration script (lilypond-texi2html.init). 

I have translated [Back to Documentation index] in "lilypond-texi2html.init".
But I did not send the patch for that. I am preparing for Japanese documents
with John. I hope I can show them soon.

> Sure, after all, we are all working together on making the best application 
> for music scores.

01234567890123456789012345678901234567890123456789012345678901234567890123456789
It is true. There are many LilyPond users in Japan and they need information
about LilyPond in Japanese. I want them to join to LilyPond community without
hesitating. They are solving their problems individually. For example, there are
many Japanese tutorials in Web, and some of them show the way to use Japanese
characters (multi-byte characters) within LilyPond scores. They may be useful
for non-Japanese speakers.

Thanks,
Yoshiki




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Lilypond on Macports

[Scott Amort]

Josh Parmenter wrote:
I'm running it right now on a newer mac intel, and am noticing tons of 
xorg stuff... is this for the GUI? Does the regular X11 not cover these 
dependencies?


FYI, you can avoid this by installing the X11 SDK headers (part of the 
Xcode developer tools). This will satisfy fontforge's dependencies and 
prevent macports from unnecessarily compiling xorg.


Scott


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Lilypond on Macports

[Josh Parmenter]

I have definitely installed that SDK, but MacPorts still installed all  
those ports... strange then!


Josh

On Jan 24, 2009, at 8:29 PM, Scott Amort wrote:


Josh Parmenter wrote:
I'm running it right now on a newer mac intel, and am noticing tons  
of xorg stuff... is this for the GUI? Does the regular X11 not  
cover these dependencies?


FYI, you can avoid this by installing the X11 SDK headers (part of  
the Xcode developer tools). This will satisfy fontforge's  
dependencies and prevent macports from unnecessarily compiling xorg.


Scott


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


**
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own  
interpretation of how modern society is structured: whether actively  
or passively, consciously or unconsciously, he makes choices in this  
regard. He may be conservative or he may subject himself to continual  
renewal; or he may strive for a revolutionary, historical or social  
palingenesis." - Luigi Nono

*/



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Directory name of aux is invalid

[Paul Scott]

dem...@suffolk.lib.ny.us wrote:

On Tue, Jan 6, 2009, Trevor Daniels  said:


  

The names are case-insensitive, and they cannot be
used as directory names or the first part of a 
filename (the bit before the dot).



please note, in DOS (and many of its contemporary file systems), what
users think of as the filename is not actually a ten character field but
in fact two seperate entitys, the name (6 characters), and a 3 character
extension.
  
It's actually (at least in DOS) an 8 character name and a 3 character 
extension and I'm not sure I can agree about the two separate entities part.


Paul Scott






___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel