Adds snippet showing transcription of mensural music to modern (issue 235660043 by philehol...@googlemail.com)
Reviewers: Trevor Daniels, J_lowe, Message: Please review. Description: I've now taken the snippet I added to the LSR concerning using the same underlying music to create both mensural and modern music, and added it to the NR where previously there was a ToDo. It's probably not perfect, but seems an improvement to me. Please ignore the headword snippets: this seems a feature of LSR import and the final push doesn't normally show them. Please review this at https://codereview.appspot.com/235660043/ Affected files (+569, -478 lines): M Documentation/notation/ancient.itely M Documentation/snippets/ancient-notation.snippet-list M Documentation/snippets/repeats-headword.ly M Documentation/snippets/simultaneous-headword.ly M Documentation/snippets/text-headword.ly A Documentation/snippets/using-tags-to-produce-mensural-and-modern-music-from-the-same-source.ly M Documentation/snippets/vocal-music.snippet-list ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add French-specific note names (issue 239930043 byv.villen...@gmail.com)
Valentin Villenave v.villen...@gmail.com writes: On Tue, May 19, 2015 at 11:12 PM, Trevor Daniels t.dani...@treda.co.uk wrote: on my laptop I have to hold down the Alt key and the Fn key, and type JOU, which is actually 164 with the Fn key pressed. That’s because, for some unexplainable reason, you’re still a proud Windows user :-) On a standard GNU Linux english keyboard, you’d just have to press Alt-Gr+], then n. Anyway, this is all fine and dandy but: what do we do with my patch? Is \include espanol.ly - \language espanol - \language español an acceptable automated conversion? In my book, no. We don't turn an ASCII-only file into UTF-8 without asking. That's just rude. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
Another thought, how about the name \regular? It works in two senses:
1. Instead of contrasting relative and absolute the contrast is between
relative and plain {…} entry, which is LilyPond's default, standard, or
“regular” mode of note entry. So \regular makes it explicit that the notes are
entered in the regular entry mode rather than the relative one.
2. “regular” also refers to the consistency or regularity of the octave
indications in this entry mode, as contrasted with relative mode — the
regularity where ,,, ,, , ’ ’’ ’’’ each refers to the same octave within
the {…}. As in this dictionary definition of “regular”: arranged in or
constituting a constant or definite pattern, especially with the same space
between individual instances”.
(3. A mostly-trivial poetic bonus: regular and relative are easy to remember as
a pair because the alliteration of them both starting with “re.)
Since \regular doesn’t have the “absolute pitch connotations of \absolute it
doesn’t present the same cognitive dissonance when its notes are shifted in
relation to a reference octave (with an optional argument). And I’d say its
descriptiveness or intuitiveness is at least as good as \fixed, maybe better.
Worth considering.
\relative { c'' g' e c }
\regular { c'' g'' e'' c'' }
\regular c'' { c g e c }
-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
(3. A mostly-trivial poetic bonus: regular and relative are easy to remember as a pair because the alliteration of them both starting with “re.) Bonus? Only native English speakers think along such lines, I reckon :-) I strongly vote against \regular in this context. It's far too easy to confuse it with \relative. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On 20/05/15 18:05, James wrote: /slaʊ/ the town of Slough in the Thames Valley of England Come friendly bombs ... :) Also reminds me of this: https://en.wikipedia.org/wiki/Ghoti I always show this to my non-native English speaking colleagues to show them how ridiculous English can be sometimes. However it is a very forgiving language, you can really mangle our sentence structure and we'll still know what you mean ;) James Thing is, English is not a pure language, it's a mongrel mess of anglo-saxon, norman french, latin, norse, and heaven knows what else. If you want a coop o' char, that's indian! I gather someone has created a text to speech engine and, if you exclude all the exceptions to handle foreign immigrant words, you only need about 30 rules to cope with a 50,000 word vocabulary (in comparison, a normal person has a regular vocabulary of about 6,000 words and typical total vocabulary of about 20,000 iirc). Cheers, Wol ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
James p...@gnu.org writes: However [English] is a very forgiving language, you can really mangle our sentence structure and we'll still know what you mean ;) Uh no? The dog bites the man has a different meaning from The man bites the dog whereas in German Der Hund beißt den Mann and Den Mann beißt der Hund have the same unambiguous meaning. Star War's Yoda's speech patterns would not be particularly distinctive in German. Den Mann zu beißen der Hund sich nicht entbrechen konnte is still almost pristine even though Den Mann zu beißen konnte der Hund sich nicht entbrechen would be slightly less archaic though not staggeringly so. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
Paul Morris p...@paulwmorris.com writes:
Another thought, how about the name \regular?
I don't find that any better than any previous proposal. \relative is
not irregular.
2. “regular” also refers to the consistency or regularity of the
octave indications in this entry mode, as contrasted with relative
mode — the regularity where ,,, ,, , ’ ’’ ’’’ each refers to the same
octave within the {…}. As in this dictionary definition of “regular”:
arranged in or constituting a constant or definite pattern,
especially with the same space between individual instances”.
That definition is the same as equidistant, not as with fixed
meaning or not depending on the previous note.
And I’d say its descriptiveness or intuitiveness is at
least as good as \fixed, maybe better. Worth considering.
I don't like \fixed but consider \regular even more arbitrary. At any
rate, we pretty much figured out that we won't get an unanimous decision
on the details of this proposal's naming choice. Even though we seem to
have more or less reached agreement that the facility itself would be a
nice addition to LilyPond's input toolbox.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
Werner LEMBERG w...@gnu.org writes: (3. A mostly-trivial poetic bonus: regular and relative are easy to remember as a pair because the alliteration of them both starting with “re.) Bonus? Only native English speakers think along such lines, I reckon :-) The pronunciations of cough, bough, though, tough, plough are easy to remember since they are conveniently different. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On 20/05/15 18:18, David Kastrup wrote: James p...@gnu.org writes: However [English] is a very forgiving language, you can really mangle our sentence structure and we'll still know what you mean ;) Uh no? The dog bites the man has a different meaning from The man bites the dog whereas in German Der Hund beißt den Mann and Den Mann beißt der Hund have the same unambiguous meaning. Star War's Yoda's speech patterns would not be particularly distinctive in German. Den Mann zu beißen der Hund sich nicht entbrechen konnte is still almost pristine even though Den Mann zu beißen konnte der Hund sich nicht entbrechen would be slightly less archaic though not staggeringly so. Except you're doing a ghoti Bernard Shaw on our sentence structure. German declines its articles, so you can tell subject and object by article, in English we have to do it by position *relative to the verb*. Bites the man the dog is weird but unambiguous because we haven't messed up the declension rules. If you just swapped the noun in German I guess either (in this case) you *would* mess up the meaning, or because you have gender rules you'd end up with nonsense. Cheers, Wol ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On 20/05/15 17:50, David Kastrup wrote: Werner LEMBERG w...@gnu.org writes: (3. A mostly-trivial poetic bonus: regular and relative are easy to remember as a pair because the alliteration of them both starting with “re.) Bonus? Only native English speakers think along such lines, I reckon :-) The pronunciations of cough, bough, though, tough, plough are easy to remember since they are conveniently different. Off topic I know but Note that slough has three pronunciations according to meaning: /sluː/ (as in, slogging through a slough of mud)[1] /slʌf/ (as in to slough off) /slaʊ/ the town of Slough in the Thames Valley of England :) Also reminds me of this: https://en.wikipedia.org/wiki/Ghoti I always show this to my non-native English speaking colleagues to show them how ridiculous English can be sometimes. However it is a very forgiving language, you can really mangle our sentence structure and we'll still know what you mean ;) James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
Paul Morris p...@paulwmorris.com writes:
On May 20, 2015, at 12:35 PM, Werner LEMBERG w...@gnu.org wrote:
(3. A mostly-trivial poetic bonus: regular and relative are easy to
remember as a pair because the alliteration of them both starting
with “re.)
Bonus? Only native English speakers think along such lines, I
reckon :-)
I strongly vote against \regular in this context. It's far too easy
to confuse it with \relative.
:-) Fair enough, at least it did occur to me that this cuts both ways
and could be seen as a negative.
If not “regular” then maybe there's something else along the lines of
the default entry mode” as with plain {…}. \default is already
taken… I guess there's \standard but I don’t suppose it would fare
any better than \regular.
There are words like \static or \moored or \tethered which better match
the semantics. But that's mostly for native English speakers rather
than those whose familiarity with English stems predominantly from a
vocabulary of computing terms. So it's more important to get a
linguistic opposite of relative than a perfectly descriptive term.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
Wols Lists antli...@youngman.org.uk writes: On 20/05/15 18:18, David Kastrup wrote: James p...@gnu.org writes: However [English] is a very forgiving language, you can really mangle our sentence structure and we'll still know what you mean ;) Uh no? The dog bites the man has a different meaning from The man bites the dog whereas in German Der Hund beißt den Mann and Den Mann beißt der Hund have the same unambiguous meaning. Star War's Yoda's speech patterns would not be particularly distinctive in German. Den Mann zu beißen der Hund sich nicht entbrechen konnte is still almost pristine even though Den Mann zu beißen konnte der Hund sich nicht entbrechen would be slightly less archaic though not staggeringly so. Except you're doing a ghoti Bernard Shaw on our sentence structure. German declines its articles, so you can tell subject and object by article, in English we have to do it by position *relative to the verb*. Bites the man the dog is weird but unambiguous because we haven't messed up the declension rules. Beißt den Mann der Hund is _also_ possible, but it is a setup. It is proper German when followed by a consequence: Beißt den Mann der Hund, gibt es Ärger. It can be used as a standalone sentence in a story setup as well. While that is not really proper German but rather Yiddish, it is commonly employed in German jokes (probably because Germans don't have germane humour and consequently no high German joke architecture): Kommt ein Pferd in den Saloon. Sagt der Barkeeper: -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
Except you're doing a ghoti Bernard Shaw on our sentence structure. German declines its articles, so you can tell subject and object by article, in English we have to do it by position *relative to the verb*. German has other niceties, like der gefangene Flohthe prisoned flea der Gefangene flohthe prisoner escaped look at the case :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On 20/05/2015 19:19, Werner LEMBERG wrote: Except you're doing a ghoti Bernard Shaw on our sentence structure. German declines its articles, so you can tell subject and object by article, in English we have to do it by position *relative to the verb*. German has other niceties, like der gefangene Flohthe prisoned flea der Gefangene flohthe prisoner escaped look at the case :-) Werner Das Zeit fliegt wie ein Pfeil, Fruchtfliegen mocht Bananen ... I hope I've translated it right, as the original is Time flies like an arrow, fruit flies like a banana. Cheers, Wol ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On May 20, 2015, at 12:35 PM, Werner LEMBERG w...@gnu.org wrote:
(3. A mostly-trivial poetic bonus: regular and relative are easy to
remember as a pair because the alliteration of them both starting
with “re.)
Bonus? Only native English speakers think along such lines, I
reckon :-)
I strongly vote against \regular in this context. It's far too easy
to confuse it with \relative.
:-) Fair enough, at least it did occur to me that this cuts both ways and
could be seen as a negative.
If not “regular” then maybe there's something else along the lines of the
default entry mode” as with plain {…}. \default is already taken… I guess
there's \standard but I don’t suppose it would fare any better than \regular.
Anyway, we already have some good options on the table. I guess you can’t
fault us for not considering all the possibilities, and at least there’s
agreement that this is a useful feature.
-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)
On 20.05.2015, at 20:19, Werner LEMBERG w...@gnu.org wrote: Except you're doing a ghoti Bernard Shaw on our sentence structure. German declines its articles, so you can tell subject and object by article, in English we have to do it by position *relative to the verb*. Schweine fressen die Menschen! Which one’s the subject and which one’s the object? Well, it depends! ;) German has other niceties, like der gefangene Flohthe prisoned flea der Gefangene flohthe prisoner escaped look at the case :-) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Assessment of Allura at SourceForge
Trevor Daniels wrote Sunday, May 17, 2015 9:33 AM Subject: Assessment of Allura at SourceForge Hi I've now completed my assessment of Allura at SourceForge against the list of requirements supplied by Phil. There are some differences from GoogleCode, but these are relatively minor and can be accommodated by small changes in our procedures. In particular the Blocking and Duplicate facilities will be different, and the various posts in the discussion are fully threaded and so are not numbered, meaning cross-referencing is by link rather than number. The emails sent out following additions and amendments are not formatted as nicely as those from GoogleCode, but contain all the information. Support is by +ve and -ve voting rather than starring. Finally, the Owner field in the transferred tickets is not populated. The owner is identified in the text of the ticket, so the field can be manually amended after the event in the few tickets where this matters. Other than that the facilities are remarkably similar, and apart from congestion the transfer of the DB is fairly trouble-free. I'm becoming increasingly concerned about the loading of Allura at SourceForge, maybe due to other projects attempting to migrate from GoogleCode. After exporting our Issues DB on Sat evening and modifying the Post authors to GoogleImporter I attempted to re-import it. During Saturday evening, all day on Sunday, and early on Monday my attempt was rejected due to the load on the server. The import request was finally accepted on Monday afternoon, but failed after loading about a quarter of the issues. No details given. I initiated the import again late on Monday evening, and this had completed successfully by early Wed morning, after running for 33 hours. So weekends are a dead loss, and altogether it took me almost 5 days just to re-import the DB. Furthermore, I've observed today that searches are frequently rejected with Errno 111 Connection refused, another symptom of server overload. Maybe we need to pursue an alternative server to SourceForge urgently. I'm in the process of tailoring a test facility for developers and admin to play with, and as a vehicle for re-engineering git-cl and patchy. I'll post again when this is ready. In spite of the frustrations I have prepared a test bed for developers, admins, bug-squad and users to play with. It's at https://sourceforge.net/p/testlily/tickets/ . It is populated with the all the Issues from GoogleCode up to around 7 May 2015. I've added all the extra fields needed to accommodate our practices and created several useful searches. This is what it would be like after migration. *** We now need others to try all the actions they would normally do with the Issues DB to expose any further problems. *** Anyone can search and read the issues, but to try creating new issues, posting to them or editing them you'll need to get a SourceForge account and let me have the resulting user name, saying whether you want to play as Admin, Devel or Member, so I can give you the appropriate permissions. Feel free to modify individual Issues, but don't delete them all! We still, of course, need to rework the several scripts. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Part_combine_iterator: treat child iterators as a set (issue 240020043 by nine.fierce.ball...@gmail.com)
https://codereview.appspot.com/240020043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improving the Contributors Guide and LilyDev
Hello, Status update: I have extended my trip to California (I'm visiting my employer's client) until June 6th, and I'm very busy with my day job. I should be able to resume work on LilyDev by June 13th - I hope that delay is not a problem. Anyway, I think that the proof of concept that I've sent last week demonstrates that my approach is good. I already have quite a few further improvements in the works. I will send an email to -devel when I'll have a version ready for serious review (hopefully that should happen by June 15th). best, Janek 2015-05-12 21:38 GMT-07:00 Janek Warchoł janek.lilyp...@gmail.com: Hello, I have an alpha version of LilyDev built with Vagrant and Ansible ready for demonstration. To try it, you need VirtualBox (https://www.virtualbox.org/) and Vagrant ( https://www.vagrantup.com/) installed, and the LilyDev Vagrant box (which you can download here: https://www.dropbox.com/s/xzv9iog9klhexgm/lilydev4.a02.box?dl=0). Open terminal and in an empty directory run: vagrant init lilydev4 path to the box file vagrant up LilyDev should setup itself completely automatically, and you should see a login screen; the username and password is `vagrant`. Inside, you should be able to compile LilyPond according to the Compiling with LilyDev section of the CG. Of course, you can build the box yourself - there are instructions in README (the repository is on GitHub: https://github.com/janek-warchol/vagrant-powered-lilydev). I hope that the code is commented well and will be self-explanatory. How do you like it? (keep in mind that this is just a proof of concept; many things mentioned in the discussion still have to be done. I'm mainly interested in your opinion about how it works in general). best, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
