Reinhold Kainhofer wrote Monday, August 11, 2008 9:43 PM
As a solution I propose to remove the backslash from the node names and
the
xrefs, so links will work. They can/should stay in the section titles,
which
are not used for the links anyway. There they don't cause any errors
anyway.
Rein
Hi again Carl
Another major addition! The new fretboard additions are
very impressive! All very clearly and concisely
written except for one paragraph, which just confused
me:
2.4.1.4 Custom tablatures
I found the first paragraph less than clear, maybe
because I'm not familiar with tablature.
Thanks, Trevor.
Custom Tablatures was a section that I didn't edit; my contributions
were limited to the Fret Diagrams section.
Jonathan, as I worked on the FretBoards material, I came to understand
the fret assignment algorithm a bit. Would you like me to take on
this section, or would you pref
2008/8/9 Valentin Villenave <[EMAIL PROTECTED]>:
> when I include my usual definition files it complains as soon as it
> parses them (and yet when I copy/paste the content of these file into
> one single file it compiles OK!???)
Greetings Neil, Joe, everybody;
I have managed to isolate one bug w
2008/8/9 Valentin Villenave <[EMAIL PROTECTED]>:
> when I include my usual definition files it complains as soon as it
> parses them (and yet when I copy/paste the content of these file into
> one single file it compiles OK!???)
Greetings Neil, Joe, everybody;
I have managed to isolate one bug w
2008/8/11 Jean-Charles Malahieude <[EMAIL PROTECTED]>:
> Le 11.08.2008 18:56, John Mandereau disait :
>> Till, Francisco, Jean-Charles, would you be willing to get involved
>> (again) in this job for 2.12 release? I just did a part of it, but I
>> must also spend time on proofreading docs and fixi
On Sun, Aug 10, 2008 at 1:46 AM, Joe Neeman <[EMAIL PROTECTED]> wrote:
> Hmm, my mail bounced from Rune's address. Does anyone know how to
> contact him?
[EMAIL PROTECTED] is the one which is publically available.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
2008/8/12 Valentin Villenave <[EMAIL PROTECTED]>:
> I have managed to isolate one bug with Rune's code: in one of my
> definition files I have a piece of code that was taken from the
> "Changing flageolet mark size" on
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=input/lsr/changin
2008/8/12 Trevor Daniels <[EMAIL PROTECTED]>:
> John, there are lots of refs to this section. I
> can find and change all the ones in the English
> docs, but I'm not sure what to do about the
> translations. Advice please.
You can do exactly the same in translations, as node names and
sections t
2008/8/12 Neil Puttock <[EMAIL PROTECTED]>:
> That appears to be a line separator problem; I get the same error if I
> save the included \flageolet file as dos/windows (\r\n).
Gee, it seems that my text editor has accidentally saved one of my
definition files with \r\n EOLs; that actually explain
John, you wrote, Tuesday, August 12, 2008 5:21 PM
2008/8/12 Trevor Daniels <[EMAIL PROTECTED]>:
John, there are lots of refs to this section. I
can find and change all the ones in the English
docs, but I'm not sure what to do about the
translations. Advice please.
You can do exactly the sam
> > That appears to be a line separator problem; I get the same error
> > if I save the included \flageolet file as dos/windows (\r\n).
>
> Gee, it seems that my text editor has accidentally saved one of my
> definition files with \r\n EOLs; that actually explains my problem!
Why do we still hav
2008/8/12 Werner LEMBERG <[EMAIL PROTECTED]>:
> Why do we still have EOL problems? Shouldn't lilypond convert them
> just to spaces?
Yes, this is weird (what's even weirder is that I didn't have such
problems before applying Rune's patch). I suspect the problem was in
fact that I had \n EOLs in
2008/8/12 Graham Percival <[EMAIL PROTECTED]>:
>> Although the texinfo manual does not explicitly forbid it, using
>> backslashes in node names causes problems with both texi2pdf and
>> texi2html:
> That's a pity, but if that's the technical limitation, that's the
> technical limitation.
Is ther
> >> Although the texinfo manual does not explicitly forbid it, using
> >> backslashes in node names causes problems with both texi2pdf and
> >> texi2html:
>
> > That's a pity, but if that's the technical limitation, that's the
> > technical limitation.
>
> Is there a way to print this character
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 12. August 2008 schrieb Werner LEMBERG:
> > >> Although the texinfo manual does not explicitly forbid it, using
> > >> backslashes in node names causes problems with both texi2pdf and
> > >> texi2html:
> > >
> > > That's a pity, but if tha
Graham,
In commit f83930a3e1a3fc9ad0198379275bd101b4fd29a4, for the file
simultaneous.itely, at about line 185, you changed
@code{<<@[EMAIL PROTECTED] [EMAIL PROTECTED]@}>>}
to
@code{<<{...} \\ {...}>>}
This change led make web on my machine to fail with the messages
Documentation/user/out-ww
Reinhold Kainhofer wrote
Unfortunately, with our current way of using @rlearning etc, I don't know
any
way to get the links to show backslashes...
The @ref command has a third argument, which controls the displayed text,
but
our definitions in macros.texi don't use this third argument.
Unfor
Neil already fixed this. Do a git update.
Go ahead and fix the "note heads", though. :)
Cheers,
- Graham
On Tue, 12 Aug 2008 16:34:33 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> Graham,
>
> In commit f83930a3e1a3fc9ad0198379275bd101b4fd29a4, for the file
> simultaneous.itely, at a
On Tue, Aug 12, 2008 at 3:34 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> Graham,
>
> In commit f83930a3e1a3fc9ad0198379275bd101b4fd29a4, for the file
> simultaneous.itely, at about line 185, you changed
>
> @code{<<@[EMAIL PROTECTED] [EMAIL PROTECTED]@}>>}
>
> to
>
> @code{<<{...} \\ {...}>>}
On Tue, 2008-08-12 at 13:11 -0300, Han-Wen Nienhuys wrote:
> On Sun, Aug 10, 2008 at 1:46 AM, Joe Neeman <[EMAIL PROTECTED]> wrote:
> > Hmm, my mail bounced from Rune's address. Does anyone know how to
> > contact him?
>
>
> [EMAIL PROTECTED] is the one which is publically available.
That seems
2008/8/7 Trevor Daniels <[EMAIL PROTECTED]>:
> You're right. The value of 'layer is held as a real, but converted to an
> integer before use. It seems all +ve and -ve integers are effective,
> though, so we still have quite a few discrete layers. I'll incorporate
> the essentials of this in the
Hi list,
I have a couple of questions regarding my section (NR 1.6):
*NR 1.6.2.1 Staff symbol
This section is describing every single way to modify the properties
of StaffSymbol. The only content that doesn't involve \override
commands is the explanation of \stopStaff and \startStaff. Should I
On Tue, 12 Aug 2008 20:21:19 -0700
"Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> *NR 1.6.2.1 Staff symbol
>
> This section is describing every single way to modify the properties
> of StaffSymbol. The only content that doesn't involve \override
> commands is the explanation of \stopStaff and \s
On Sat, Aug 9, 2008 at 7:51 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> We are pleased to announce the second review of NR 2.7 Chords.
>
> Thank you to those who reviewed this section in its previous draft. All of
> the recommended changes have been made, and we believe that this section is
On Sat, Aug 9, 2008 at 4:49 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> Dear Lilypond Users and Developers,
>
> We're pleased to announce a revised second draft of NR 2.4 Fretted strings.
>
> This draft includes the new predefined-fretboards functionality that enables
> transposable guitar fr
On 8/12/08 10:08 PM, "Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 9, 2008 at 7:51 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
>> We are pleased to announce the second review of NR 2.7 Chords.
>>
>> Thank you to those who reviewed this section in its previous draft. All of
>>
27 matches
Mail list logo
