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
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
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 f
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
> dev
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 a
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-
-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-de
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 o
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 Mac
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 s
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 comb
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?
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
> 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
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
-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 navig
-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 texi2
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
>> w
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/
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 notati
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)
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
tr
-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.
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 th
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
25 matches
Mail list logo
