Re: draft release announcement
Juergen Reuter wrote: I am not sure about capitalization in English language, but shouldn't * all words in the headline except "than" start with a capital letter and Actually, at least in the US, headlines are commonly (though not always) set in sentence case, with the first letter and any proper names capitalized, and no final period. Two online examples are CNN.com or USAtoday.com. And, if I remember correctly, Robert Bringhurst recommends this convention in The Elements of Typographic Style. I believe studies have demonstrated that sentence case is more readable (in terms of speed and comprehension) than Title Case, which is why it is often used in advertising as well. This is also why a final period is omitted from headlines: when it is included, people tend to skip the article which follows. Book titles are a whole different story. Marcus ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Capitalization (was Re: draft release announcement)
This is getting a bit off topic, but...On 11/1/06, Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote: Actually, in German, as is well known, all nouns get capitalized. Everycountry has its own rules. There is nothing "international" about usingsentence-case for titles...FYI (from Wikipedia): "The convention followed by many British publishers [...], namely to use sentence-style capitalization in titles and headlines, where capitalization follows the same rules that apply for sentences. [...]. This convention is also used in the International Organization for Standardization and Wikipedia house styles."Regards, Erlend ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On Wed, Nov 01, 2006 at 08:44:13PM +0100, Han-Wen Nienhuys wrote: > Cameron Horsburgh escreveu: > >Hmm, I'm still not happy with the first sentence! How about: > > > >*** > > > >The initial inspiration for LilyPond came ten years ago when two > >musician friends grew disappointed with the bland and boring look of > >computer generated scores. > > > >*** > > I used formatted iso. generated. GEnerated sounds a bit nerdy. > Good > > > >Also, the comma after 'improvements' should be replaced by a semi-colon. > > rather a colon ? > Gah --- I'm always mixing those two up. You're right of course. -- = Cameron Horsburgh = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
> a draft of the 2.10 release announcement is at > >http://lilypond.org/web/announce-v2.10.html > > please comment. Some typographical issues: . `--' should be replaced with — (since you use it without a space before and after it). . The link to the NEWS file looks ugly because it uses the tag instead of a simple . If I move the mouse to it, I get underlined spaces before the text and in the next line. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On Wed, 2006-11-01 at 11:37 -0600, Trevor Bača wrote: > > The rule still taught in US classrooms for capitalizing titles is that > the "important" words all get capitals (which comes down to something > like prepositions and articles being lowercase, with everything else > in uppercase). This is obvious nonsense. But it's still what's taught > and still what's -- unfortunately -- expected (as Jan points out). How is it "obvious nonsense"? Many manuals of style have no trouble expressing this rule in clear forms. The "important words" method is hard to implement, but convenient for explaining to ten-year-olds. It so happens that the American book publishing industry is not bound by what is taught to fourth graders, and you cannot judge how book publishers work in terms of the simplified explanations given in elementary school. > HOWEVER there are a couple of important exceptions. To start with, > since this "rule" is no rule at all, the Library of Congress (no less) > refuses to use it. Pick up any English-language book you happen to > have sitting nearby, open to the first couple of pages, and look at > the in-catalog number given there. The title is given in French (or > international, or whatever you want to call it) title case: first word > and proper nouns capitalized and nothing else. The reason is that the > French / intl rule is an actual rule. And so the LOC uses it for every > book published in the US, usually in direct contradiction to what the > editor and publisher put on the cover and the spine. Actually, in German, as is well known, all nouns get capitalized. Every country has its own rules. There is nothing "international" about using sentence-case for titles; it's just the custom followed in some countries and not others. What you are running into here is that the rules for library catalogs in America are different from the rules for titles in running text or bibliographies. This is a consequence of the fact that American and British libraries agreed upon a common set of rules for cataloging, which rules happen to have the "sentence case" specification. > > So, my personal preference on this point is the same as Han-Wen's: the > practice is old, out-dated and ridiculous in the US, even if still > widely practiced, as Jan points out. For all the careful time and > attention we spend making sure LilyPond output adheres as closely as > possible to beautiful examples of notation from the past, I think we > can afford ourselves the liberty to skip this one particular out-moded > practice. Yes, because the best thing to do with standards is to declare that one is going to ignore them, in the name of inventing one's own standard. Wonderful. Thomas signature.asc Description: This is a digitally signed message part ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Cameron Horsburgh escreveu: Hmm, I'm still not happy with the first sentence! How about: *** The initial inspiration for LilyPond came ten years ago when two musician friends grew disappointed with the bland and boring look of computer generated scores. *** I used formatted iso. generated. GEnerated sounds a bit nerdy. Also, the comma after 'improvements' should be replaced by a semi-colon. rather a colon ? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On Tue, Oct 31, 2006 at 01:31:26AM +0100, Han-Wen Nienhuys wrote: > > Hi guys, > > a draft of the 2.10 release announcement is at > > http://lilypond.org/web/announce-v2.10.html > > please comment. > > thanks, > Hmm, I'm still not happy with the first sentence! How about: *** The initial inspiration for LilyPond came ten years ago when two musician friends grew disappointed with the bland and boring look of computer generated scores. *** Also, the comma after 'improvements' should be replaced by a semi-colon. -- = Cameron Horsburgh = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On 10/31/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Jan Nieuwenhuizen escreveu: > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > >> The practice is silly today. > > I think so too, but it is still what people expect? only in the US, I think. And not even all the time even here, FWIW. (See below.) I've lived in the US my entire life and had plenty of chance to think abou this issue of "title case" editing copy in American and UK English. And it's basically a mess. The rule still taught in US classrooms for capitalizing titles is that the "important" words all get capitals (which comes down to something like prepositions and articles being lowercase, with everything else in uppercase). This is obvious nonsense. But it's still what's taught and still what's -- unfortunately -- expected (as Jan points out). HOWEVER there are a couple of important exceptions. To start with, since this "rule" is no rule at all, the Library of Congress (no less) refuses to use it. Pick up any English-language book you happen to have sitting nearby, open to the first couple of pages, and look at the in-catalog number given there. The title is given in French (or international, or whatever you want to call it) title case: first word and proper nouns capitalized and nothing else. The reason is that the French / intl rule is an actual rule. And so the LOC uses it for every book published in the US, usually in direct contradiction to what the editor and publisher put on the cover and the spine. The other exceptions in the US are the titles of articles in scientific journals which always use French / international title case (first word and proper nouns only), probably because most journals are inherently international in their intended audience (even if they're English-only). So, my personal preference on this point is the same as Han-Wen's: the practice is old, out-dated and ridiculous in the US, even if still widely practiced, as Jan points out. For all the careful time and attention we spend making sure LilyPond output adheres as closely as possible to beautiful examples of notation from the past, I think we can afford ourselves the liberty to skip this one particular out-moded practice. ;-) Trevor Bača [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Cameron Horsburgh escreveu: a draft of the 2.10 release announcement is at http://lilypond.org/web/announce-v2.10.html please comment. thanks, A couple of things: Is there going to be a 2.10.0? Yes, of course, but 2.10.[123...] will mostly be bugfix releases, and hardly worth mentioning. Even if there is, it's the new series that is making the news, so I would suggest leaving the version number at 2.10. `got annoyed' is a little unprofessional. Perhaps `were disappointed' or `became disillusioned'. `computer print-out' should be `computer print-outs' or even `computer generated print outs.' `reading' should be `to read' thanks. Of course, these are just my opinions! When does the announcement look likely? Somewhere within a week or so. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On Tue, Oct 31, 2006 at 01:31:26AM +0100, Han-Wen Nienhuys wrote: > > Hi guys, > > a draft of the 2.10 release announcement is at > > http://lilypond.org/web/announce-v2.10.html > > please comment. > > thanks, > A couple of things: Is there going to be a 2.10.0? Even if there is, it's the new series that is making the news, so I would suggest leaving the version number at 2.10. `got annoyed' is a little unprofessional. Perhaps `were disappointed' or `became disillusioned'. `computer print-out' should be `computer print-outs' or even `computer generated print outs.' `reading' should be `to read' Of course, these are just my opinions! When does the announcement look likely? -- = Cameron Horsburgh = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Jan Nieuwenhuizen escreveu: Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: The practice is silly today. I think so too, but it is still what people expect? only in the US, I think. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Hi, On Tue, 31 Oct 2006, Juergen Reuter wrote: > "elegant input format" and "hard for other programs to parse" sounds > somewhat like a contradiction. Maybe "sophisticated" instead of > "elegant" would be more appropriate? I think "elegant" is too elegant a description to be scrapped ;-) Maybe clarify: "While the format is easy to write and read for humans, it is less so for programs. Therefore ..." Hmmm? Ciao, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > The practice is silly today. I think so too, but it is still what people expect? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Mats Bengtsson wrote: > The second bullet point below "New Stuff" ends with "nested", I guess > some text > has disappeared. I guess Han-Wen meant "nested tuplets", didn't he? -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Johannes Schindelin escreveu: P.S.: Congratulations on your GUB work! And sorry, I could not be of assistance with git, since I was busy writing a grant application (I just spent a week in Scotland, and was working with two other scientists). Cool. We've put up a repository at repo.or.cz , but we'll probably be one of the firsts to use git at savannah. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Juergen Reuter escreveu: "elegant input format" and "hard for other programs to parse" sounds somewhat like a contradiction. Maybe "sophisticated" instead of "elegant" would be more appropriate? I am not sure about capitalization in English language, but shouldn't * all words in the headline except "than" start with a capital letter and It depends. This is really a bad practice that was started in the time that newspaper were still set by hand. Then, there were not enough large type letters, so mixing caps spread out the usage better. The practice is silly today. * the itemized texts start with small letters (except "DocBook"), since they continue an incomplete sentence? yup. Shouldn't there be a full-stop dot after the last item? Greetings, Juergen -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Mats Bengtsson escreveu: Hi, Two minor comments: For the readers that don't know LilyPond from before, it's probably not clear that the "9 months of furious programming" refer to the time since version 2.8.0. (Why not call it a "10 year anniversary release"?) good idea, that also gives it a new ring to the release text. The second bullet point below "New Stuff" ends with "nested", I guess some text has disappeared. thanks -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Hi, On Tue, 31 Oct 2006, Han-Wen Nienhuys wrote: > a draft of the 2.10 release announcement is at > > http://lilypond.org/web/announce-v2.10.html It is a great read! You meant "nested tuplets" instead of "nested", right? Ciao, Dscho P.S.: Congratulations on your GUB work! And sorry, I could not be of assistance with git, since I was busy writing a grant application (I just spent a week in Scotland, and was working with two other scientists). ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
"elegant input format" and "hard for other programs to parse" sounds somewhat like a contradiction. Maybe "sophisticated" instead of "elegant" would be more appropriate? I am not sure about capitalization in English language, but shouldn't * all words in the headline except "than" start with a capital letter and * the itemized texts start with small letters (except "DocBook"), since they continue an incomplete sentence? Shouldn't there be a full-stop dot after the last item? Greetings, Juergen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On Tuesday 31 October 2006 05:37, Joe Neeman wrote: > On 10/31/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > > Hi guys, > > > > a draft of the 2.10 release announcement is at > > > >http://lilypond.org/web/announce-v2.10.html > > > > please comment. > > On the long term -> In the long term > and > this will enable other programss -> ... programs > > Other than that, looks good. Also, perhaps "to read LilyPond" -> "to read LilyPond music"? -- Erik ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Hi, Two minor comments: For the readers that don't know LilyPond from before, it's probably not clear that the "9 months of furious programming" refer to the time since version 2.8.0. (Why not call it a "10 year anniversary release"?) The second bullet point below "New Stuff" ends with "nested", I guess some text has disappeared. /Mats Han-Wen Nienhuys wrote: Hi guys, a draft of the 2.10 release announcement is at http://lilypond.org/web/announce-v2.10.html please comment. thanks, -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
Make sure the URL in the message: http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS.html points to the NEWS for the 2.10 release. -- Michael Welsh Duggan ([EMAIL PROTECTED]) ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: draft release announcement
On 10/31/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Hi guys,a draft of the 2.10 release announcement is at http://lilypond.org/web/announce-v2.10.htmlplease comment. On the long term -> In the long termandthis will enable other programss -> ... programsOther than that, looks good. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
