Re: How can I avoid unicode and use Latin1? (Was: Wrong characters with jEdit)
On Sun, 4 Sep 2005, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] wrote: > > Unicode only provides a way of specifying character codes for a wide > > variety of symbols in the interior of a text file. But without font files > > containing the order of 64K symbols, the current fragmented font-file > > situation will continue to limit what can easily be output to a screen > > or a printer. It is difficult for me to share your optimism. > That's not a problem, at least, not on Linux. Pango does a wonderful job > of inspecting the coverage of each font. It substitutes whichever font > has the glyphs that are required to print the text. Well, that's impressive. For Windows users -- suppose that the right environment variable has been set to signal to LilyPond the presence of various Windows font directories. Then is Pango actually able to do that sort of font substitution if the specified font name in a .LY file is that of a TTF font located in a Windows directory? -- Tom ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: New slur/tie behaviour
Werner LEMBERG wrote: IIRC, I've sent an algorithm to the list a few years ago whether ties should go up or down, depending on the vertical structure of a chord. Maybe you can dig it out, and perhaps it helps in providing some constraints. IIRC, it was the algorithm that was present before I rewrote the thing. I thought it was rather too simplistic. Mhmm, I don't think so: The direction of slurs was always unsatisfactory :-) Cf. http://lists.gnu.org/archive/html/lilypond-devel/2004-01/msg00148.html Well, AFAIK engraving conventions are: * outer ties point outward * double directions for seconds * direction otherwise determined by vertical position. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How can I avoid unicode and use Latin1? (Was: Wrong characters with jEdit)
[EMAIL PROTECTED] wrote: Well, that's impressive. For Windows users -- suppose that the right environment variable has been set to signal to LilyPond the presence of various Windows font directories. Then is Pango actually able to do that sort of font substitution if the specified font name in a .LY file is that of a TTF font located in a Windows directory? Yes. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
How can I avoid Latin1 and use UTF-8?
Was: How can I avoid unicode and use Latin1? On 5 Sep 2005, at 08:58, [EMAIL PROTECTED] wrote: Thank you. I didn't know unicode was broader than UTF-8. Formally, one assigns to abstract characters different non-negative integers, called in Unicode lingo "code points". In order to get this stuff into a computer, one needs an integer to binary translation function. This is what UTF-8 does. Different translation functions provide different encodings of the same code points. The 3-byte value 10 (rather than FF) seems like a rather strange upper limit, When UTF-16 was designed, one did not think clearly about the above separations, so therefore one thought this upper limit was necessary. The limitation is though imposed by Unicode Inc.; the original ISO UTF-8 does not do that (so there are two differing versions of UTF-8 in play). Also, the number of available code points is for the fundamental Unicode Inc. character range so well enough that it will not fill up in hundreds of years at the current rate of character addition. Only if people are allowed to massively register private characters, might it break. but that only points up the fact that I'm going to have to learn about unicode once I get through my current arranging binge. You can read about UTF-8 at http://www.cl.cam.ac.uk/~mgk25/unicode.html Today, Windows uses Unicode exclusively -- even in North America. You won't have big success with latin1 files. I routinely switch files between Latin1 text and MS-Word docs with no problem whatsoever. ... Microsoft's unicode claims are a marketing ploy; Latin1 still rules. Editors often have a preference where the default encoding can be chosen. And the output encoding can also be chosen automatically. For example, the mailer I use, scans through the email, and chooses the encoding suitable, ASCII, ISO-Latin-1, or UTF-8, for example. Hans Aberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
syntax error
Hi folks!
I'm using 2.5.29 (and still a bit new to it I must admit). I've been
editing this .ly file and compiling it just fine when all of a sudden,
wishing to print a copy, I noticed my /paper was wrong -- I need "letter"
instead of A4. Now all along, the compile message would say:
Parsing...
warning: Must use #(set-paper-size .. ) within \paper { ... }
Interpreting music... [8][16][24][32][40][48][49]
but it would finish and be fine.
So, looking through my file I noticed I had no \paper, but my
#(set-paper-size) was withing \layout (leftover from version 2.2.6 and not
changed on convert-ly) So I moved that to the top of the file within a
\paper block. The first time I compiled that, it did just fine, but did
not change the paper size.
Then I changed something else (and I can't seem to restore it with "undo"
in xemacs) and it now gives me:
Gloria4Part.ly:20:10: error: syntax error, unexpected DIGIT
\version "
2.5.29"
error: failed files: "Gloria4Part.ly"
I don't get this -- I have several other files with the same syntax (here
is a snippet to look at -- not complete to compile):
\header {
filename = "Gloria4Part.ly"
enteredby = "Gordon Gilbert"
composer = "Gordon Gilbert 1994, 2004"
poet = "Missa Brevis"
date="2004"
title = "Gloria In Excelsis"
subtitle = "Glory to God in the highest"
metre = ""
meter = \metre
copyright = "Gordon Gilbert"
style = "Missa Brevis"
mutopiacomposer = \composer
mutopiapoet=\poet
maintainer = "Gordon Gilbert"
maintainerEmail = "[EMAIL PROTECTED]"
lastupdated = "2005/September/5
}
\version "2.5.29"
\paper{
#(set-paper-size "letter")
}
global= {
\time 4/4 \key c \major
There's something obvious here to everyone except me -- what is wrong with
my \version? Or anything else here for that matter? What am I missing?
Thanks guys,
Fr. Gordon Gilbert+
+=+
| Angels' Roost Farm |
| Rev. Fr. Gordon Gilbert & Susan Gilbert |
| 705-549-5056 |
|[EMAIL PROTECTED] |
|[EMAIL PROTECTED] |
+=+
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Note head in brackets
Note head in brackets - I do not find a solution in the documentation. Thanks for a hint! Wolfgang -- Wolfgang Mechsner Goebenstr. 3 49076 Osnabrück Telefon: 05 41 / 2 05 20 90 Mobil: 01 79 / 9 09 66 84 URL: www.wolfgang-mechsner.de Email: [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error
Gordon Gilbert angel.eicat.ca> writes:
>
> Then I changed something else (and I can't seem to restore it with "undo"
> in xemacs) and it now gives me:
>
> Gloria4Part.ly:20:10: error: syntax error, unexpected DIGIT
> \version "
>2.5.29"
> error: failed files: "Gloria4Part.ly"
>
>
> \header {
> lastupdated = "2005/September/5
> }
>
> \version "2.5.29"
Hello!
I haven't used the "lastupdated" property myself, but I believe the date would
need to be enclosed within quotes. However, it looks like you're missing one at
the end of the date.
Since this is immediately above your version statement, I suppose that's what's
causing the problem
Hope this helps :)
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Note head in brackets
see stencil-hacking.ly in the regression tests.
here's a *very* dirty trick I use for desperate cases, but which works for
me :)
(see attached png)
%
\version "2.7.6"
\layout
{
raggedright = ##t
}
\relative c''
{
r2 r4 g8
\once \override Score.SeparationItem #'padding = #1.2
\once \override TextScript #'extra-offset = #'(-2.2 . -5.1)
bes8^\markup \bold {"(" \hspace #1.8 ")"}
c4 b a g
}
%%% EOF
the given examples use perentheses, but you could use brackets too.
On Mon, 05 Sep 2005 19:03:05 +0200, Wolfgang Mechsner
<[EMAIL PROTECTED]> wrote:
Note head in brackets - I do not find a solution in the documentation.
Thanks for a hint!
Wolfgang
parentheses.png
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tie behavior (was: New slur/tie behaviour)
Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote, regarding general default tie rules or behavior: Well, AFAIK engraving conventions are: * outer ties point outward * double directions for seconds * direction otherwise determined by vertical position. --- --- Piano is my instrument, and as a polyphonic instrument it can have complex and sometimes crowded chord structures, multiple voices and chords per staff, etc. So ties are personally very important to me. A default behavior and rules for placing ties is very helpful, but there can also occur numerous specific situations in which default behavior is not optimal. So I personally hope that, in any future rewriting of the LilyPond tie code, users will remain able to override default behavior and specify at least the vertical placement and arc-direction for each individual tie, between single notes (that are not part of a chord) as well as for the notes of a chord, and perhaps also be able to stretch or compress the tie horizontally along the X-axis, either the tie as a whole or the individual beginning and ending points of a tie, if the person notating the score thinks the tie would look better a little shorter or longer in any particular circumstance. However, I have no idea whether this last feature (overriding the horizontal length of an individual tie) would be worth the time and effort to implement. Regarding the engraving conventions listed above, they seem generally sound to me and applicable in most situations, although I don't claim to be an expert in such matters. All three conventions would need to be altered in some cases, which is why I hope that users will be able to override default tie behavior. The only thing I would add, personally, to the conventions listed above is a corollary to the first one, "outer ties point outward." To me (and I wonder if others agree), although outer notes of a chord should ideally arc outward from the chord, the vertical or Y-axis placement of the beginning and ending points for those outermost ties should be different for tied notes that fall within a staff or ledger *space*, than for ties between notes that fall on a staff or ledger *line*. In the case of notes that fall within a staff space rather than on a line, and merely in my opinion, the ties would look better if the beginning and ending points of the ties were placed in the staff space *adjacent* to the space in which the notes exist, rather than in the same staff space as the notes themselves. For example, in a chord within a treble clef staff, the uppermost note of which is c'', the tie connecting that note would begin and end in the staff space that would be occupied by the note e'', which is more or less exactly the same place that such a tie would be drawn if the uppermost note of the chord were a d'' (placed on a line) instead of a c'' (placed in a space). Just my opinion. ;-) Han-Wen recently mentioned that, in rewriting the tie code a week or 10 days ago, he thought of a possibly better conceptual approach to and foundation for LilyPond's tie code. I would be very willing, in a couple months (like in November for example) to help sponsor such a re-thinking and rewriting of the tie code. Although the recent rewrite is a lot better than the older default behavior for ties, if Han-Wen thinks it can be improved, I'm personally enthusiastic about helping to sponsor an improvement in this (to me) very important aspect of music notation. I am thinking about helping to sponsor such a project by making monthly payments of perhaps 200 Euros or more each, for 4 or more consecutive months, depending on how much time and effort Han-Wen spends on this functionality, should he wish to direct his thought and attention toward it. I would hope that others might be interested in helping to sponsor such a project as well. Best wishes, Steve D New Mexico US ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Installing lilypond 2.6.3
On Friday 02 September 2005 23.32, Jobst Harders wrote: This kind of questions should go to the lilypond-user mailing list. > Hi, > > I would like to install Lilypond 2.6.3. on my system using SuSE 9.1. Is > it a good idea to use the "package" download from your site? yes. > And if so, > what are the steps needed after downloading? see autopackage.org -- Erik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: New slur/tie behaviour
> Well, AFAIK engraving conventions are:
>
>* outer ties point outward
>* double directions for seconds
>* direction otherwise determined by vertical position.
This is correct, but doesn't work in cluster-like chords.
Here are my rules again for reference:
sequentially from top to bottom:
+ The topmost tie is always `up'.
+ If there is a vertical gap to the last note above larger
than or equal to a fifth (or sixth?), the tie is `up',
otherwise it is `down'.
+ The bottommost tie is always `down'.
The current behaviour of lilypond (CVS version 2005-09-01) is
attached.
Werner
==
begin 644 ties.png
MB5!.1PT*&@[EMAIL PROTECTED]&,```"/"`,```!INN;'Q\?("`@(B(B)B8F*"@H*2DI*BHJ+"PL+2TM+BXN
M,#`P,C(R,S,S-C8V-S<[EMAIL PROTECTED]/CX^/S\_0$!`04%!1$1$2DI*2TM+
M4%!04E)24U-35SA`6%A865E97%Q<8&[EMAIL PROTECTED]:&AH;6UM;V]O<'!P
M<6IA'[EMAIL PROTECTED]&!B(B(BHJ*C8V-CX^/E)24F9F9GY^?
MI*2DIJ:FKZ^OL[.SM;6UN[N[P&!WP,#`PL+"Q\?'S,S,S<"PT[6UV=G9
MW=W=W]_?Y>[EMAIL PROTECTED]"YT15AT4V]F='=A"!O9B`R,#`U,#0Q,[EMAIL PROTECTED]
M241!5'C:[9WM<]M&DL8[D;VB14JG1%&T2D3+UBH7![M4&.E(VT%%YE*U+-Y<
MM-#ZL"G<%BI;^`!7H8K__^<#0)#$@'@[EMAIL PROTECTED]@9#]/52)9E!K-`>;'>>GNH1D$
M05!U([EMAIL PROTECTED]&[EMAIL PROTECTED],9`$`3&[EMAIL PROTECTED]
M!($Q$`2!,1`$06`,[EMAIL PROTECTED]&`-!$`3&0!`$QD`0!,9`$`2!
M,[EMAIL PROTECTED]($Q4[05!$'5,:9+7306!$%5,:9+1!C)0!!4$6.F%`BM!4%0-8P)
M$8/[EMAIL PROTECTED]"F.V<,9DL0!%7"&%H([05]BG(O786V+'6._5FAK>O_W2)CHF',
M%`,9Z-.43;;"+L<::NN7+3)F,8:[EMAIL PROTECTED]@C'K&K#:5P!@(C`%CU#.FNUR)
M02`>!,:`,=4P9KKX#L];X^69GCIC3;5E.6#,1\28U882&/,89"KL$'9C;;$Z
MFQ2,J9XQTR5CL+/[EMAIL PROTECTED];&K&9-6)`!8\`8,[EMAIL PROTECTED]@#QH`Q%3)F
M"L:`,6`,&%,#8SZ9O,CAM4);^V`,&`/&@#&\M!<*;=6]%P?&@#&/C3'=V+82
M&`/&@[EMAIL PROTECTED]&6,^73*.X`Q8`P8LP7&[EMAIL
PROTECTED](SW^+G0-,9LI4D_8L9\$&7,
M`T$0!&VLSX3',0])T6'P_Y\"*XN=*#^..<[EMAIL PROTECTED];9VYXK.18;:9KVQZ5;
M?_3_-4QU3':N=$Y[Y1D3+LATJZ@:#L:`,8^7,0X;[EMAIL PROTECTED];8(QG
M,NT\9V)SI#'3;[EMAIL PROTECTED];*JGG"\:`,8^3,9[YNC7OJQ<#QFQ?W`*RZ__`9..;
MT_GO'(^L>AGC&C]&S.N-F3]J"12\CU",C7L1"U_>[EMAIL PROTECTED];P$S`&C'F$
MC''9RZ`[7/J=MW!KRK7-<4B:@>[EMAIL PROTECTED](#.N]=)GQ&M1F$V&P53O..)RS&&
MMU4;8[K4K>98`C`&C'ETC/'N_*[P/;,VJ+CEFN,SOS>;U3!&YXX-\2:A>V)M
[EMAIL PROTECTED]>4O&Z.6/()%CS+2JXY7`&##FL3'F?8N>EZGHY[)]>F&K9XP56V/Q
M?V(=TG-K(_>L/K7>SQF3L%4_8RI((P!CP)C'Q1CG);TP2U[08_]!0T\Q8^)8
MH)DW\`&X>6N^H)[K,X:W5?=Z3$4AOF`,&/.X&#,Y,R4NZ;%36S%CN+VBF7-J
ME+)[EMAIL PROTECTED]&UQ2,Q/GI\/#P)^&X.<3@(0;OXXG!VT+M"LVU,)<:4MSI3!.PF1&^-5MWES)
MR7=K.W,[EMAIL PROTECTED]@366E]_'MVI)8CXFN*;#B&W=-##)@3*V,<7VL7&NIC]2)
M=L=L9[N,<2QVJVG),%EMPM9QLP7&Q/JB+LL82PX,>B86W(DKO#9D_%^^K?H8
M,X^,$3GJ.DXBP8LPW&.*QWGCL,?SDTG*TR
M)MX791DCMW\SHVPLN.V.8,-89_1/[EMAIL PROTECTED]@(,0)'77=C(32B?H(QM3#&OHLZ
M<"^,>\\8X8S[\\CWUNM5^$[LWCWOOC>[EMAIL PROTECTED]'CG;(TQOY)"
MQLAU9PX+?TGXY&KTW!*8B][0D9VT]97<^RO-F,[EMAIL PROTECTED]<>9)B([EMAIL
PROTECTED]/6,
ML89!#SX=FR*T<&W6#X<-4>![!8RQ^&!U:[EMAIL PROTECTED]@L(N#>RXXRQ=(DN
M+\08/;B"[EMAIL PROTECTED];%OU)BC'[EMAIL PROTECTED]"/>73?HLXX%S,..UO&]L;57[-5
M"V.62S'3HKG/=(TQ73!F^XRQM9`O[D8P8-_3//2S`L;PBYUNZ)[EMAIL PROTECTED]
M6V_)&+F%4P'&U+"V:FU,*IXQ*,?S":[EMAIL PROTECTED]>,D5V$+69,QF)%
MJ:OII(A75,[EMAIL PROTECTED];;UR^5Y3\/\),^SL^9M>:_V86'1Q/*:8
MZ#"OFF^I`&3D$GQ2N02<7FW;5D$NP3M^[WSQS;LRE^)M_:=<$\3_6C8O83'6
M>?6NUGJ^R"6`(*B>7(+N8C0WC1N:BLR51.:
M,8[-[K3C=%KN::[EMAIL PROTECTED]@@)O]BW3-MP"RG$8Q1%?BNP):>B05+?+G(F2_=
MZ`H1LPEC?O6;@6Y*<<9C'4-PG?9394S:FGA7C#$E]ZY=[EMAIL PROTECTED]
MZ/&1[WL:'_9>$V,1L45A_,:=-ZNPI[KX,[EMAIL PROTECTED]>79O8,195HC]?A;[EMAIL
PROTECTED]'J`M^E
M;[EMAIL PROTECTED]>N1J?%92L]B.BT497$X8]7XF&I4:A;U?FI4Q)@K^7KAWNS>/
M>B]PS[&"6&TZGGAQQEBX+5F%WS33L,2(T88\F.
[EMAIL PROTECTED]"%5ED0O5ZT<[EMAIL PROTECTED]'DO)[EMAIL
PROTECTED]>Y4[KBA=,RM3;MT-W.D!DY
MGS2VQ<+C3EJ#U,<%C$EES&*D$I]"I0YDNAL-8^*,F;1*+ZKMT[6KGC$Z7^Y]
M<_?,YV$X?L`872(_19`QELJH5&7A9R*;,];M8N5M$.P>&N$VXD";Q[WOW3KI
MMK9V+H%SOXB5N>BOMCL7VY]O%DN&Q[=6'5QX_(SISN*E8**Z4]VL#S0NT'>S
M.%_WA`:EMP<[EMAIL PROTECTED];ZTW/[9B0YEG-`D8HV`)[EMAIL PROTECTED]&CSE9R\S1J?J&=/(46]G^,&`T+YPU8NMQ
M[PE;[EMAIL PROTECTED]&+J&[P4:[EMAIL PROTECTED]>`&/6?O+A:B&BW=B7JZMOHF_\%OWF*E7?
M[/JO[>YFOI[4;OM*F79WU=EJ/^5ZEYRM1/FYR_PHX$#J8A<*;5TM
MQR175]_1=W)WA;/UK?1-/A>_L=*NYF_QL&^3"/L*K0560M;\(`.Y.XP9^O9D:SVQ&^&O.OQ>_6LH;9V
M)[EMAIL PROTECTED]/M&<:5%"L[OXN:)C:<.YDB4=Z3!;[BM)VM+5[H2P-QGDV"H=$+F:?SIRU
M4.\:S"FF2,2JF2E$@
M^(N7ZPL?[FB/J#,R[+39250W_\1(VB+]Q=<*ZZ2V9\F*]T$8]!0WS.AJUI!E7#J._$1G:Z>"V`,&),V6XJ/
M6<*PEZG\,&;YJ=O^8FTF814>W1"FL%PX:U.H]TX]MDX_GWSA
M&.MHXJ0M[*AX`,K4VG2,\ZAPM&EGL-$+SE4*AX?GAE,Y%\`8,"8=,EV.,5.2
M7HW)*6[J#>A4(-S-8U$R4&9\JYQ37V3E74?UWCN:-M##0/+!0%O4>[EMAIL PROTECTED]
MMGGVB;NH4.^CIA>&[EMAIL PROTECTED],[EMAIL PROTECTED]([EMAIL
PROTECTED]@#QE3.&"X]*>!+=8@)NFB'
M!#=PW!L:[EMAI
Re: How can I avoid unicode and use Latin1? (Was: Wrong characters with jEdit)
Sorry for coming in at the end of the thread. I was wondering if on linux there is a way to get jedit to support hebrew with lilypond. I have been looking for that golden editor which is good for lilypond and good for hebrew. So far I remain with gvim, although emacs and jedit seem to have many more features for lilypond, they don't have the hebrew support. Aaron --- Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Well, that's impressive. For Windows users -- > suppose that the right > > environment variable has been set to signal to > LilyPond the presence of > > various Windows font directories. Then is Pango > actually able to do that > > sort of font substitution if the specified font > name in a .LY file is that > > of a TTF font located in a Windows directory? > > Yes. > > -- > Han-Wen Nienhuys - [EMAIL PROTECTED] - > http://www.xs4all.nl/~hanwen > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Syntax Error in compiling
Hi again! Thanks to Andrew for showing me where the error was -- and SO SIMPLE!! Can someone please explain how to read the error messages when lilypond fails to compile a file? For example, the bit the program quoted was *after* the error -- is this standard? Blessings, Fr. Gordon Gilbert+ +=+ | Angels' Roost Farm | | Rev. Fr. Gordon Gilbert & Susan Gilbert | | 705-549-5056 | |[EMAIL PROTECTED] | |[EMAIL PROTECTED] | +=+ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax Error in compiling
Gordon Gilbert angel.eicat.ca> writes:
>
> Hi again!
>
> Thanks to Andrew for showing me where the error was -- and SO SIMPLE!!
> Can someone please explain how to read the error messages when lilypond
> fails to compile a file? For example, the bit the program quoted was
> *after* the error -- is this standard?
>
> Blessings,
>
> Fr. Gordon Gilbert+
>
> +=+
> | Angels' Roost Farm |
> | Rev. Fr. Gordon Gilbert & Susan Gilbert |
> | 705-549-5056 |
> |gord angel.eicat.ca |
> |susan angel.eicat.ca|
> +=+
>
Usually, if you can't find anything blatantly wrong in the program output, you
would suppose the error is somewhere further up. Sometimes it can be a *lot*
further, depending on what you're doing.
In this particular case, whatever is between two quotes is considered a string
(text). Since the closing quote is missing, the compiler is simply going to
continue through the file until it finds a matching quote (which obviously isn't
the right one). So what happens here, is that the closing brace is considered as
text by the compiler, and not a part of the program structure.
> \header {
> lastupdated = "2005/September/5
> }
>
> \version "2.5.29"
as far as the compiler is concerned, "lastupdated" is something like:
"2005/September/5 } \version"
it "thinks" that it's still in the \header section, since it hasn't found a
closing brace, and now stumbled upon a series of numbers ( 2.5.29" ) which
clearly shouldn't be there on its own. And that's why it points you to the
version number instead of the missing quote.
I hope this all makes sense,
All the best,
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Book creation
Hi all! I have composed a Missa Brevis (short Mass) setting with several distinct pieces. In the past I have simply printed each piece out on separate pages. However, I would like to put them all together in a book, with title page, contents (with one-bar snippets if that's not too difficult), a page of comments, etc. Can someone point me to where in the documentation (or elsewhere) I can find *all* the necessary information on doing that? I have looked in the docs, and found some of it, but I think I am missing something. I use 2.5.29, and run it on FreeBSD 5.3 with a reasonable amount of horsepower and ram. Thanks in advance, Blessings, Fr. Gordon Gilbert+ +=+ | Angels' Roost Farm | | Rev. Fr. Gordon Gilbert & Susan Gilbert | | 705-549-5056 | |[EMAIL PROTECTED] | |[EMAIL PROTECTED] | +=+ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: typos in manual 2.6
On 3-Sep-05, at 1:08 AM, Mehmet Okonsar wrote: section: 7.3.7 p.133 Ambitus there should be " " around Ambitus_engraver section: 8.2.2 p.175 Metronome marks there shouldn't be " " around #1 Thanks for your comments! It doesn't matter if you write Ambitus_engraver or "Ambitus_engraver" I've fixed the second example. It seemed to work as it was, but I'm not quite certain why. In any case, it's better now. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error
Fr. Gordon Gilbert wrote:
> I'm using 2.5.29 . . . I need "letter" instead of A4 . . .
> Parsing...
> warning: Must use #(set-paper-size .. ) within \paper { ... }
> . . . my #(set-paper-size) was withing \layout . . .
> So I moved that to the top of the file within a \paper block.
> The first time I compiled that, it did just fine, but did
> not change the paper size.
I use 2.6.0, and putting the following two lines at the very top of the
file works for me:
\version "2.6.0"
#(set-default-paper-size "letter")
Of course 2.5.29 might be different, but it might be worth trying to set
the default paper size at the top level just to see if it works.
-- Tom
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How can I avoid unicode and use Latin1? (Was: Wrong characters with jEdit)
On Mon, 5 Sep 2005, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] wrote: > > For Windows users . . . is Pango actually able to do that > > sort of font substitution if the specified font name in a .LY file is that > > of a TTF font located in a Windows directory? > Yes. !!! I yield. You just made a convert. -- Tom ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Staff.keySignature
Can anyone please explain to me shortly how to manage the arguments of the Staff.keySignature function.. Which args to be set to which values to get which accidental on which scale step ?:) \set Staff.keySignature = #'(((1 . 2) . 1) ((0 . 3) . -1)) thanks! Best Regards, Mehmet Okonsar, pianist-composer www.okonsar.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
