Re: \epsfile
On Fri, 15 Nov 2019, Martin Tarenskeen wrote: Related issue: When using frescobaldi the syntax help and autocompletion balloon gives "\eps-file" instead of "\epsfile". A little bug? Reported it on github. https://github.com/frescobaldi/frescobaldi/issues/1213
Re: lilyglyphs: Python 2 deprecation
On Tue, 12 Nov 2019, Werner LEMBERG wrote:
If you are the maintainer of any of these packages, and still are using
Python2, please try to update to Python3 as soon as possible.
...
lilyglyphs/
py2 only
lilyglyphs/lily-glyph-commands.py
lilyglyphs/lily-image-commands.py
lilyglyphs/lily-rebuild-pdfs.py
lilyglyphs/lilyglyphs_common.py
...
I ran the 2to3 command on the python scripts from
https://github.com/uliska/lilyglyphs/tree/master/scripts
Without having tested it the output ouput shows me 3 types of issues that
need fixing. The most frequent one is the print command that needs to be
replaced with print ().
1. print vs print()
2. raw_input() vs input()
3. something with iterkeys() vs keys() in sorted()
I have attached the output of "2to3 *.py" where you see what I mean.
Maybe someone who knows how to use git can take a look?
--
MT--- deploy.py (original)
+++ deploy.py (refactored)
@@ -55,9 +55,9 @@
def main():
if os.path.exists('deploy'):
-overwrite = raw_input('deploy directory exists. Overwrite? ')
+overwrite = input('deploy directory exists. Overwrite? ')
if overwrite != 'y':
-print 'Aborted'
+print('Aborted')
sys.exit(1)
shutil.rmtree('deploy')
os.mkdir('deploy')
@@ -65,7 +65,7 @@
# now we're guaranteed to have an empty 'deploy/lilyglyphs' directory
-print 'Copying files:'
+print('Copying files:')
# copy individual files from the root directory
cp_root()
# copy complete directories to their corresponding dest
@@ -140,12 +140,12 @@
global manifest
if not dest:
dest = src
-print '-', src
+print('-', src)
shutil.copytree(src, dir_deploy + '/' + dest)
append_manifest(src, dest)
def cp_root():
-print '- root'
+print('- root')
f = []
f.append('CHANGES.md')
f.append('INSTALL')
@@ -153,7 +153,7 @@
copy_files(f, '')
def cp_scripts():
-print '- scripts'
+print('- scripts')
os.mkdir(dir_deploy + '/bin')
os.mkdir(dir_deploy + '/lib')
for file in os.listdir('scripts'):
@@ -165,7 +165,7 @@
manifest.append('/lib/' + file)
def lg_private():
-print '- lilyglyphs_private'
+print('- lilyglyphs_private')
zip = zipfile.ZipFile(dir_deploy +
'/documentation/lilyglyphs_private.zip', 'w')
for root, dirs, files in os.walk('lilyglyphs_private'):
for file in files:
@@ -216,15 +216,15 @@
for part in version_parts:
int(part)
except:
-print 'Malformed version argument:', version
-print 'Use three integers separated by dots'
+print('Malformed version argument:', version)
+print('Use three integers separated by dots')
sys.exit(1)
-print 'Preparing lilyglyphs deployment', version + '.'
-print 'CWD is', os.getcwd()
-print 'This should be the root of lilyglyphs.'
-print 'This script will not work on Windows.'
-check = raw_input('Proceed (y/..)? ')
+print('Preparing lilyglyphs deployment', version + '.')
+print('CWD is', os.getcwd())
+print('This should be the root of lilyglyphs.')
+print('This script will not work on Windows.')
+check = input('Proceed (y/..)? ')
if check != 'y':
sys.exit(1)
--- lily-glyph-commands.py (original)
+++ lily-glyph-commands.py (refactored)
@@ -80,10 +80,10 @@
if not len(line):
# skip if cmd and glyph haven't been filled both
if not (entry['cmd'] and entry['element']):
-print 'Skip malformed entry \'' + entry['cmd'] + '\'. Please
check input file'
+print('Skip malformed entry \'' + entry['cmd'] + '\'. Please
check input file')
reset_entry()
else:
-print 'Read entry \'' + entry['cmd'] + '\''
+print('Read entry \'' + entry['cmd'] + '\'')
lg.in_cmds[entry['cmd']] = {}
lg.in_cmds[entry['cmd']]['element'] = entry['element']
lg.in_cmds[entry['cmd']]['type'] = entry['type']
@@ -110,13 +110,13 @@
def usage():
-print 'genGlyphCommands.py'
-print 'is part of the lilyglyphs package'
-print ''
-print 'Usage:'
-print 'Pass the name (without path) of an input definitions file'
-print '(this has to be located in the /stash_new_commands directory.'
-print 'Please refer to the manual (documentation/lilyglyphs.pdf).'
+print('genGlyphCommands.py')
+print('is part of the lilyglyphs package')
+print('')
+print('Usage:')
+print('Pass the name (without path) of an input definitions file')
+print('(this has to be located in the /stash_new_commands directory.')
+print('Please refer to the manual (documentation/lilyglyphs.pdf).')
#
# Finally launch the program
--- lilyglyphs_common.py
Re: lilyglyphs: Python 2 deprecation
On Tue, 12 Nov 2019, Werner LEMBERG wrote: If you are the maintainer of any of these packages, and still are using Python2, please try to update to Python3 as soon as possible. ... lilyglyphs/ py2 only lilyglyphs/lily-glyph-commands.py lilyglyphs/lily-image-commands.py lilyglyphs/lily-rebuild-pdfs.py lilyglyphs/lilyglyphs_common.py ... This package is written by Urs Liska , who is quite busy these days. In case you have experience with Python 2 to 3 conversion, please help produce a new version! Should it still be backwards compatible with Python 2.7 if possible or is it ok to drop Python2 backwards compatibility completely? Option one is possible, option two gives cleaner code, and is easier to maintain in future. MT
end of Python2
Hi, This has been discussed here before but https://pythonclock.org/ made me wonder in which direction LilyPond and Frescobaldi are currently going. Is there anything I have to worry about? With Lilypond Python2.4 is still bundled, without a bundled Python I have an already installed Python 2.7, and the Lilypond-related python tools (like musicxml2ly) I need all seem to work. Unlike Lilypond, Frescobaldi3 is already more prepared for Python3. Having to depend on all these different Python versions isn't an ideal situation. If we only had more manpower and active developers ... -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
pythonly musicxml export error
Hi, Anyone here who can comment on this issue? https://github.com/wbsoft/python-ly/issues/75 -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: ly musicxml export
On Tue, 29 Sep 2015, Simon Albrecht wrote: Hello Martin, there might be more right addressees for this at the frescobaldi mailing list. Forwarding. Thanks. I have reported the issue on GitHub https://github.com/wbsoft/python-ly/issues/46 -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
ly musicxml export
Hi,
It seems python-ly musicxml export does not support the
\relative {c' d e f}
syntax correctly: It is pitched one octave too high.
\relative c' { c d e f }
is converted correctly to MusicXML. Maybe this is not the correct place to
report python-ly issues. But I guess one or more python-ly contributors
are reading this list?
--
MT
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly tremolo tag on notes shorter than quarter
On Tue, 12 May 2015, pls wrote: For example what happened with the Philomenos musixcml2ly-dev fork? Yes, Philomelos is still alive and I’m about to update the musicxml2ly-dev Github repo. Over at least three years I have written almost 100 bug reports and many test cases for Philomelos and I will try to publish them as well. We have fixed quite a few of these bugs. I just implemented a solution to the tremolo bug reported here. Sound promising! Allow to me to do a drastic suggestion. Wouldn't it be much simpler to replace the current musicxml2ly from the official LilyPond development tree with the one from Philomenos entirely and allow the Philomenos guy(s) to continue the work there, if he/they wants to? I never quite understood why this fork was needed. And if the Philomenos version is the only one that has been actively developed since a few years now I don't see why not everyone who installs the official LilyPond should not have the latest and greatest musicxml2ly tool without extra effort? -- MT___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond-ftplugin.vim
Hi, in lilypond-2.18.0/vim/lilypond-ftplugin.vim I see: F6 view ps with ghostview map buffer F6 :!gv --watch %.ps Return This will not work, and hasn't for some time, because Lilypond's default output is pdf these days and the ps file is only temporary. So now it should be: F6 view ps with ghostview map buffer F6 :!gv --watch %.pdf Return -- MT___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-ftplugin.vim
On Mon, 30 Dec 2013, Martin Tarenskeen wrote: F6 view ps with ghostview map buffer F6 :!gv --watch %.pdf Return the comment should be fixed also :-) : F6 view pdf with ghostview (Personally I would choose another PDF viewer, but that's another story.) -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
OooLilypond
Hi, Usage manual, 4.4 says Inserting LilyPond output into OpenOffice.org LilyPond notation can be added to OpenOffice.org with OOoLilyPond. Maybe these days it should be OpenOffice.org or LibreOffice -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly output indentation style
On Sat, 16 Nov 2013, Peter Bjuhr wrote: On 11/14/2013 09:16 AM, Martin Tarenskeen wrote: Hi, The lilypond output that is produced from musicxml2ly uses another indentation style than I see in my own scores when using for example Vim or Frescobaldi, or in all examples in the Lilypond documentation. Hi Martin! Thanks for pointing this out! In the latest development version of Frescobaldi scores imported through internal musicXML import are now reformatted (the same way as if Tools-Format were used). I did a short try with the dev version from Github (downloaded zip there) but I see no difference. Still had to use Tools-Format manually. But even if it works, it would still be a workaround instead of a real fix. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
musicxml2ly output indentation style
Hi,
The lilypond output that is produced from musicxml2ly uses another
indentation style than I see in my own scores when using for example Vim
or Frescobaldi, or in all examples in the Lilypond documentation.
for example:
%commonly used style
music = \relative c' {
a b c d
}
%musicxml2ly style
music = \relative c' {
a b c d
}
This is not a real-life example, but it shows what I mean.
(I don't know if the indentation will survive in e-mail readers, so I have
attached the example also)
It looks like everyone prefers the closing bracket to un-indent, except
the people who developed musicxml2ly?
Is this a known issue, something that needs fixing?
--
MT%frescobaldi style
music = \relative c' {
a b c d
}
%musicxml2ly style
music = \relative c' {
a b c d
}
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
where is 2.17.95
Hi, where is 2.17.95? all download links for binaries and sources are Not Found. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: where is 2.17.95
On Mon, 4 Nov 2013, Martin Tarenskeen wrote: Hi, where is 2.17.95? all download links for binaries and sources are Not Found. Question and answer were sent simultaneously :-) MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [proposal] easy triplets and tuplets - Draft 3
On Mon, 8 Oct 2012, Keith OHara wrote:
Martin Tarenskeen m.tarenskeen at zonnet.nl writes:
I am not in favour of allowing different commands \times 2/3 and \tuplet3/2
to do the same job. My voice would go to: just keep \times x/y the wayit
is. I can't see what makes 3/2 easier than 2/3. And having the choiceof two
commands doing the same job with a slightly different syntax onlymakes
things more confusing for me.
Currently, everyone who thinks of a triplet as a 3:2 ratio, 3 notes in the
usual time for 2, suffers similar confusion when trying to remember \times
2/3. Triplets are usually written with a simple 3, but 4-note-tuplets are
often designated 4:3 for clarity, while LilyPond requires the reversed
fraction in \times 3/4 {}
The likely outcome would be to document only \tuplet 3/2 (or \tuplet3 or
\triplet depending on what we choose) and have convert-ly change \times x/y
to \tuplet y/x, but let LilyPond accept \times x/y from users who have
developed the habit. Then there is only one syntax in the documentation.
OK. You convinced me.
--
MT
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [proposal] easy triplets and tuplets - Draft 3
On Tue, 9 Oct 2012, Graham Percival wrote:
On Tue, Oct 09, 2012 at 09:45:09AM +0200, Francisco Vila wrote:
So, \tuplet y/x with the exact meaning of \times x/y is less confusing
because it's not times vs time anymore, and the straightforward
fraction is just music without the maths. So, I predict a widespread
adoption.
Do we really need to use the same fraction notation, though? I
mean, in music we see 3:2 (if people are being pedantic). I'd be
much happier with
\tuplet 3:2 { }
meaning the same thing as
\times 2/3 { }
I think I like this idea.
--
MT
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [proposal] easy triplets and tuplets - Draft 3
On Mon, 8 Oct 2012, Trevor Daniels wrote: David Kastrup wrote Monday, October 08, 2012 10:45 PM Thomas Morley thomasmorle...@googlemail.com writes: [...] So, i believe that LilyPond shouldn't always follow her users' intuition, even if they are professional musicians. In this case, i think that \tuplet 2/3 is better than \tuplet 3/2 (for 3 notes in time of 2), because it corresponds to mathematical ratio, and is similar to scaling durations. +1 -1 from me for this one. We have \times for that already and I can't count the times it took me to get the fraction right. And with the name \times there is at least the mnemonic of the name itself. I am not in favour of allowing different commands \times 2/3 and \tuplet 3/2 to do the same job. My voice would go to: just keep \times x/y the way it is. I can't see what makes 3/2 easier than 2/3. And having the choice of two commands doing the same job with a slightly different syntax only makes things more confusing for me. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
pitch spelling
Hi, I found this interesting document: http://www.titanmusic.com/papers/public/meredith-dphil-final.pdf It's about pitch spelling algorithms: how to automatically determine if a note should be called C# or Db for example. Maybe it can inspire someone to use such advanced methods as dscribed in this document to improve midi2ly's ability to correctly guess notenames and accidentals? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
contributor's guide 10.2.8 Python
Hi, 10.2.8 of the contributors guide says Python is used for XML2ly and is building the documentation and the website Sounds a bit incomplete to me. XML2ly is musicxml2ly I guess. And what about midi2ly, lilypond-book, abc2ly, convert-ly? Also I was hoping to find info about the required/recommended Python version here when I was browsing the docs. Maybe that info can be found somewhere else? BTW: Are there any thoughts about switching from Python 2.x to Python 3.x somewhere in the future? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Waltrop meeting outline
Hi guys, I wish you a lot of fun and inspiration at the Waltrop LilyPond meeting! -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
version 2.16
Hi, If I have a newer \version in my lilypond score than the LilyPond I am using I am getting a Fatal Error message, but my score compiles just fine, giving a perfect PDF or MIDI. I would expect a Warning, not a Fatal error message ? Using lilypond-2.15.95 In my testfile using: \version 2.16.0 -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stable release.
Hi, Just want to say that a thread like this shows clearly: 1. Lilypond is a very advanced and complicated project 2. Several people - even if we always can use more of them - are actively working on it and care about the quality of the project. 3. Humans make mistakes. Having said that I think you (the developers) are doing a great job, and I want to thank you for that. And I am confident that we will have a new stable LilyPond version, even if that will not happen today or tomorrow. I'm sure it's worth waiting for. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly
On Sun, 8 Apr 2012, Martin Tarenskeen wrote: The good news is that in many cases only a little editing of the .ly file is required to turn a bad conversion into a good one. For example, all lead sheets from Wikifonia that I have tried have the Chords printed below instead of above the staff. I remember this had been fixed in one of the previous lilypond 2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am still (again?) having this problem. Same with 2.15.38 Hi, I did not see a reaction to this question, so I try again. What happened with this musicxml2ly bug ? First chords were printed below the staff, then I think it was fixed, and now the chords are below the staff again. Regression? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: musicxml2ly
On Sun, 8 Apr 2012, Martin Tarenskeen wrote: The good news is that in many cases only a little editing of the .ly file is required to turn a bad conversion into a good one. For example, all lead sheets from Wikifonia that I have tried have the Chords printed below instead of above the staff. I remember this had been fixed in one of the previous lilypond 2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am still (again?) having this problem. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
musicxml2ly
Hi, There have been many requests from several people for Lilypond-to-MusicXML conversion. I am not going to repeat that question. We do have a musicxml2ly script. I have tried it with many example xml and mxl files from here: http://www.makemusic.com/musicxml/music/example-set and here: http://www.wikifonia.org/ And the lilypond results are sometimes not quite perfect - which is acceptable - but sometimes really bad or even useless. The good news is that in many cases only a little editing of the .ly file is required to turn a bad conversion into a good one. For example, all lead sheets from Wikifonia that I have tried have the Chords printed below instead of above the staff. The MakeMusic/Recordare example set reveals some more serious problems like wrong stem directions, duplicated text and dynamic markings, collisions. Is anyone currently actively working on musicxml2ly ? Does it help if I write a more detailed description of errors I encounter when I try to convert real life examples of MusicXML files? Or are many problems already known? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
tabloid papersize
Hi, In NR 4.1.2 I read: Common paper sizes are available, including a4, letter, legal, and 11x17 (also known as tabloid). It is known, but lilypond does not allow to use it! #(set-default-paper-size tabloid) It's quite easy (even for me) to add this line: (tabloid . (cons (* 11.0 in) (* 17.0 in))) to the list in paper.scm, as an alias for 11x17, which should also stay. If this is ok, can someone add this in a next Lilypond release ? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond SVG output
On Wed, 22 Feb 2012, Felix Kugel wrote: 3) The PDF output has lots of metadata, is this documented somewhere? I think this is done by ghostscript ? I have experiemced that Evince gives lots of warning/error messages about these metadata. Don't know if Evince is wrong or the PDF files. But if I use Lilypond's --ps option and then use ps2pdf13 instead of ps2pdf to convert the ps file to pdf, the number of metadata decreases and the error messages disappear. I am on Linux Fedora 16 -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
the word LilyPond
Hi, Everyone who knows a bit about TeX/LaTeX knows what the result looks like when you use \LaTeX or \TeX in your source text. Wouldn't it be nice to have something like that for the word LilyPond ? A standard way to display LilyPond in documents and for example in the default lilypond tagline ? I personally would not choose something fancy like (La)TeX uses. But we could at least always write LilyPond with L and P in uppercase, and decide about and recommend the use of a standard font, one that is available on every system, to use in documents and websites, for the word LilyPond even if the surrounding text uses a different font. Just a thought. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond pdf error/warning messages from Evince
On Thu, 15 Dec 2011, Francisco Vila wrote: 2011/12/15 Francisco Vila paconet@gmail.com: Entity: line 5: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xFF 0xFF 0xFF 0xFF rdf:Description rdf:about='52da2502-5ec5-11ec--73b663e6b6f#143;uuid:52 ^ Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 16 ??#143;uuid:52da2502-5ec5-11ec--73b663e6b6f2011-12-15T00:10:12+01:00kO#16; All the errors come from metadata sections in your PDF and yes, they are put there by GhostScript. So, no LilyPond bug here. I have found that if use Lilypond to create a .ps file, and then manually convert this to pdf using the scripts provided by the ghostscript package: - if I use ps2pdf, ps2pdf14, or ps2pdfwr I will get all these error messages - if I use ps2pdf12 or ps2pdf13 I will not get any error messages -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond pdf error/warning messages from Evince
On Wed, 14 Dec 2011, Francisco Vila wrote: 2011/12/14 Martin Tarenskeen m.tarensk...@zonnet.nl: Hi, When I load a Lilypond-created pdf file in Evince I see a lot of error/warning messages in my console. The PDF looks and prints fine though. Anything to worry about ? I am working on Linux Fedora 16, using lilypond 2.15.21 evince-3.2.1 ghostscript-9.04 Attached: the output from my console if I load a Lilypond pdf score. If a tiny lilypond example is needed let me know, but I think it happens with any score. I recall obtaining lots of messages when the document is open in evince and lilypond is modifying (creating) it at the same time. When the document is done and I newly open it in evince from console, I don't get any message at all _at_least_ with the latest lilypond version and the very latest PDF I made with lilypond. That does not seem the problem here. I still see these messages. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond pdf error/warning messages from Evince
Hi, When I load a Lilypond-created pdf file in Evince I see a lot of error/warning messages in my console. The PDF looks and prints fine though. Anything to worry about ? I am working on Linux Fedora 16, using lilypond 2.15.21 evince-3.2.1 ghostscript-9.04 Attached: the output from my console if I load a Lilypond pdf score. If a tiny lilypond example is needed let me know, but I think it happens with any score. -- MT Entity: line 5: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xFF 0xFF 0xFF 0xFF rdf:Description rdf:about='c096387c-5e4c-11ec--89182f7e1f6#143;uuid:c0 ^ Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 16 ��#143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16; ^ Entity: line 5: parser error : invalid character in attribute value #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 5: parser error : attributes construct error #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 5: parser error : Couldn't find end of Start Tag Description line 5 #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 5: parser error : PCDATA invalid Char value 8 #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 16 :c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a���HO#16; ^ Entity: line 5: parser error : PCDATA invalid Char value 8 096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a���HO#16;a� ^ Entity: line 6: parser error : xmlParseCharRef: invalid xmlChar value 16 ��#143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16; ^ Entity: line 6: parser error : invalid character in attribute value #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 6: parser error : attributes construct error #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 6: parser error : Couldn't find end of Start Tag Description line 6 #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 6: parser error : PCDATA invalid Char value 8 #143;uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a� ^ Entity: line 6: parser error : xmlParseCharRef: invalid xmlChar value 16 :c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a���HO#16; ^ Entity: line 6: parser error : PCDATA invalid Char value 8 096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00kO#16;a���HO#16;a� ^ namespace error : Namespace prefix xmp on ModifyDate is not defined 1-12-14T09:47:07+01:00' xmlns:xmp='http://ns.adobe.com/xap/1.0/'xmp:ModifyDate ^ namespace error : Namespace prefix xmp on CreateDate is not defined xmp:CreateDate2011-12-14T09:47:07+01:00/xmp:CreateDate ^ namespace error : Namespace prefix xmp on CreatorTool is not defined xmp:CreatorToolLilyPond 2.15.21/xmp:CreatorTool/rdf:Description ^ Entity: line 8: parser error : Opening and ending tag mismatch: RDF line 4 and Description xmp:CreatorToolLilyPond 2.15.21/xmp:CreatorTool/rdf:Description ^ namespace error : Namespace prefix rdf for about on Description is not defined M:DocumentID='uuid:c096387c-5e4c-11ec--89182f7e1f62011-12-14T09:47:07+01:00' ^ namespace error : Namespace prefix rdf on Description is not defined
Re: lilypond pdf error/warning messages from Evince
On Wed, 14 Dec 2011, Francisco Vila wrote:
2011/12/14 Martin Tarenskeen m.tarensk...@zonnet.nl:
That does not seem the problem here. I still see these messages.
You can produce a minimal PDF from
{ c' } %END
and try launching it into evince. If it shows messages, send it to me.
OK. done -
My console shows these messages: see attachment,
--
MTEntity: line 5: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xFF 0xFF 0xFF 0xFF
rdf:Description rdf:about='c5350f47-5e99-11ec--7e60f0613c9#143;uuid:c5
^
Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 6
9#143;uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;
^
Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 16
#143;uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;
^
Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 1
;uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;
^
Entity: line 5: parser error : invalid character in attribute value
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 5: parser error : attributes construct error
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 5: parser error : Couldn't find end of Start Tag Description line 5
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 5: parser error : PCDATA invalid Char value 8
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 5: parser error : PCDATA invalid Char value 16
c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;��~�I
^
Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 1
f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;��~�I#1;
^
Entity: line 5: parser error : PCDATA invalid Char value 8
47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;��~�I#1;�
^
Entity: line 6: parser error : xmlParseCharRef: invalid xmlChar value 6
9#143;uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;
^
Entity: line 6: parser error : xmlParseCharRef: invalid xmlChar value 16
#143;uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;
^
Entity: line 6: parser error : xmlParseCharRef: invalid xmlChar value 1
;uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;
^
Entity: line 6: parser error : invalid character in attribute value
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 6: parser error : attributes construct error
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 6: parser error : Couldn't find end of Start Tag Description line 6
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 6: parser error : PCDATA invalid Char value 8
uuid:c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;�
^
Entity: line 6: parser error : PCDATA invalid Char value 16
c5350f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;��~�I
^
Entity: line 6: parser error : xmlParseCharRef: invalid xmlChar value 1
f47-5e99-11ec--7e60f0613c92011-12-14T18:58:26+01:00#6;J#16;#1;��~�I#1;
^
Entity: line 6: parser error : PCDATA invalid Char value 8
47-5e99-11ec-
Re: MusicXML exporter (was Re: Lilypond lobbying?)
Interesting discussion. And, being primarily a user and not (really) a developer, I hardly can wait to see where this will lead to. But I will be patient. The way I see it: The ideal case would be if a lilypond score that is converted to musicXML and then imported to some other music scoring software (Finale, Sibelius) the printed result would be identical. I don't think this ideal situation will ever exist. 1. My lilypond scores even don't give the exact same printed result when processed with different versions of Lilypond (for example 2.12.x vs 2.15.x). So what will happen when converted to MusicXML ? 2. Finale's and Sibelius' MusicXML import isn't 100% perfect either. Yes, when Finale exports a MusicXML file and then imports the same MusicXML file the result will be quite good. But I would not be surprised if importing MusicXML from other programs is much less perfect. Even if MusicXML was invented exactly to make that possible. But even with shortcomings, MusicXML would make it easier to convert/import Lilypond created scores to other programs. Post-editing may still be needed, but will much less work than when using MIDI export/import. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: MusicXML exporter (was Re: Lilypond lobbying?)
On Thu, 25 Aug 2011, Martin Tarenskeen wrote: But even with shortcomings, MusicXML would make it easier to convert/import Lilypond created scores to other programs. Post-editing may still be needed, but will much less work than when using MIDI export/import. I meant: will BE much less work than when using MIDI export/import :-) -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Converting ly to musicxml
On Sun, 10 Jul 2011, cab wrote: This is something I proposed to the French users list earlier this year and it got a lukewarm response from the community (save several well-thought-out responses from Scheme and/or musicxml and/or accessibility enthusiasts). I have started some sketches for this type of code, and it is certainly possible, especially if you do not include position information. Contact me if you'd like to talk more about this and I'll dig up the sketches I've already done in Scheme. Actually, I am really interested, but I am wondering why you used scheme , is it because you are doing this recursively ? Is it because it is easier to parse ly files with scheme (I don't know this language yet ) ? I guess the idea was to make it possible to export MusicXML directly from Lilypond (just like midi, png, pdf, and postscript), re-using Lilypond parsing-code that is available anyway? And Scheme is the language that integrates perfectly with Lilypond? That would be better/easier to develop than a separate python tool? Correct me if I am wrong, I am not a scheme coder. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GOP-PROP 1: python formatting - probable decision
On Wed, 15 Jun 2011, Federico Bruni wrote: How can I change this behaviour, so that automatically 4-space indentation is used. Can/should I change something in my .vimrc file http://stackoverflow.com/questions/234564/tab-key-4-spaces-and-auto-indent -after-curly-braces-in-vim http://vim.wikia.com/wiki/Converting_tabs_to_spaces Thanks! -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GOP-PROP 1: python formatting - probable decision
On Wed, 15 Jun 2011, Graham Percival wrote: Mixing indentation styles is not a great idea, and in my experience of python code documentation and examples online, the 4-space indent rule from PEP-8 is almost universally followed. Implementation notes Not that I contribute much python code to the Lilypond project, but I have a question anyway: I use vim for my own python code, and in my .vimrc file I have set autoindent set smartindent filetype plugin indent on I now write some pythoncode automatically tabs are used for indentation. How can I change this behaviour, so that automatically 4-space indentation is used. Can/should I change something in my .vimrc file ? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GOP-PROP 1: python formatting
On Mon, 6 Jun 2011, Graham Percival wrote: * never max tabs and spaces max = mix ? -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GOP-PROP 1: python formatting
that unlike C++ or scheme, indentation in python is the way that one indicates code blocks. (this makes mixing tabs and spaces particularly horrible!) Recently I tried to convert some python 2.7 code that I wrote for a little personal project to python 3.2 using the 2to3 tool. Then I discovered that my code was suffering from mixed tabs/spaces and inconsistent indentation. With Python 2.7 it worked fine but Python 3.2 was a little more critical and produced a lot of errors. Another good reason to have consistent indentation rules for our Python code. One day in the future Lilypond tools written in Python might have to be converted to Python 3. (But please, don't hurry - it can wait) This task will be easier if we have good and clean Python 2.x to start from. -- MT ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
midi2ly error
On Mon, 14 Mar 2011, Jan Nieuwenhuizen wrote:
Martin Tarenskeen schreef op ma 14-03-2011 om 13:10 [+0100]:
Which reminds me: midi2ly still needs a lot of work. In short: it is quite
useless.
Have a look at the latest version. It's starting to work.
Great, it is already much better! I must admit I had not tried it since a
long time ago.
But please try the attached example (testmidi.mid).
If I do
midi2ly -d 16 testmidi.mid
something strange happens. The first note of the tune should be e'''16 but
16 is missing:
An excerpt from the resulting testmidi-midi.ly:
trackBchannelA = \relative c {
e''' d fis,8 gis
| % 2
cis16 b d,8 e
| % 3
I am quite sure the midi file is OK. It is read and converted perfectly by
other programs like musescore and mtm (=mup to midi). If I change e''' to
e'''16 manually, everything is fine.
--
Martin
testmidi.mid
Description: MIDI audio
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
cross-staff beams
Hi,
Please try the following example, which is rendered less than optimal
using 2.13.40. Do you agree Lilypond should be able to
do better than this ? Is it worth a bug report ?
%-8-
\version 2.13.40
upper = \relative c' {
\clef treble
\time 2/4
\set Staff.beatStructure = #'(2)
e4 e | e e |
}
lower = \relative c {
\clef bass
\time 2/4
R2 |
\change Staff = up e'8
\change Staff = down a,,
\change Staff = up e''
\change Staff = down a,, |
}
\score {
\new PianoStaff
\new Staff=up \upper
\new Staff=down \lower
\layout {}
}
%--8--
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
midiInstrument
Hi, I never quite liked the way a MIDI instrument is assigned to a staff or voice in Lilypond. You are forced to use the exact names for the midiInstrument property that are hardcoded in midi.scm Why is this a problem: 1. I can't remember the names without the manual. My brains are getting old I guess ;-) ( piano 2 ? bright piano ? upright piano ? Wrong! The correct name is bright acoustic ) 2. The names are only correct when the MIDI file is played on a General Midi (GM) compatible soundcard, soundfont, synthesizer, or soundmodule. MIDI is more than just GM. One solution that would already make me happy: It would be nice if instruments could also be selected by number (1-128, or 0-127). Would it be difficult to add some code to (I guess) midi.scm that would change the behaviour from current behaviour: if instrumentname is wrong ... then instrumentname = acoustic grand to: if instrumentname is wrong then if instrumentname is a number between 0 and 127 pick the correct name from the list else instrumentname = acoustic grand This is not real code, but I hope you get the idea. Maybe someone can translate this into scheme ? Or maybe someone has a much better idea ? Martin P.S. This still would not be THE complete midi solution. Someone in an earlier thread already mentioned the lack of support for the MIDI bank change command. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: random music
On Tue, 20 Jul 2010, Graham Percival wrote: On Tue, Jul 20, 2010 at 06:17:51PM +0200, Martin Tarenskeen wrote: But thinking about this little project I was wondering: Would it be possible to write a lilypond input file, using just pure Lilypond syntax and some Scheme magick, that would produce a different score each time you process it with Lilypond? I don't know much about scheme programming, but a short google search tells me it has some support for random numbers. There is already a snippet like this in LSR. You mean this one? : http://lsr.dsi.unimi.it/LSR/Item?id=274 Thank you for the hint. It should give me some ideas to start with! -- Martin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
random music
Hi, I'm thinking of writing a little fun application based on Mozart's Musikalisches Wuerfelspiel. The idea is to compose a 16-bar Waltz using a pair of (virtual) dice and a table of musical fragments. I already wrote such a game for Mup ( I you have Mup, go to http://linux.martintarenskeen.nl and look for mupsdice ) And long ago I had this version of the same game on my old Atari ST: http://tamw.atari-users.net/mozart.htm Now I want to try to write a Lilypond version. I'll probably use Python to do it. If I have the time. Don't wait for it, I'll let you know if I ever finish it :-) But thinking about this little project I was wondering: Would it be possible to write a lilypond input file, using just pure Lilypond syntax and some Scheme magick, that would produce a different score each time you process it with Lilypond? I don't know much about scheme programming, but a short google search tells me it has some support for random numbers. Aleatoric composition using Lilypond ... maybe a nice challenge for Lilypond/Scheme developers and power-users ? http://en.wikipedia.org/wiki/Aleatoric_music -- Martin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation size
On Sun, 25 Apr 2010, James Bailey wrote: I realize that downloading and reading the documentation offline is not for everyone, but is there a way to make a documentation for download that isn't so large? Looking at it, the size increased more than 30 MB between 2.13.1 and 2.13.2. I don't know usually work with the unstable docs, but even the stable version docs increased by more than 20MB between 2.12.2 and 2.12.3. Did something wonky happen, or is this just the way it is now? Alternatively, is there an option for the documentaiton that doesn't have absolutely everything (maybe one without regression tests and snippets) for download purposes, for someone who just likes to have the documentation offline? I have been thinking about that also. I build my own updated lilypond-doc rpm package for my Fedora 12 system, because I want a copy that doesn't take to much disk space on my EeePC. I have modified my fedora spec file to only package the English documentation. I removed all the translations. This already shrinks the size of the package. Another thing that can be removed if you want to read the documentation offline with your browser is the PDF versions of the manual. They contain exactly the same information as the html version, right ? And why should everything be available both as big-page and separate html files ? If you then also remove the regression tests and snippets ( but keep links to the online versions ) it should be possible to create a light version of the Lilypond documentation. -- Martin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond-words.vim
Hi, I noticed that ( unlike r ) R and the new q are not yet recognized as possible notes for syntax higlighting in Vim. Can someone add R and q to the file lilypond-words.vim , in the section syn Bmatch lilyNote ? -- Martin Tarenskeen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Midi: Stereo Position
On Wed, 17 Mar 2010, David Kastrup wrote: Is there any way to achieve this (besides manual editing of the midi-Output)? Midi offers panning? Yes. MIDI Control Change number 10. -- Martin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [Fwd: TP: lilypond-2.13.10.nl.po [REJECTED]: missing license line]
Hoi Jan, Is het de bedoeling dat ik nog iets verander of regel jij dat. Behalve die missing licence line wordt ook nog niet overeenstemmend versie nummer (2.13.4) gemeld dat aangepast moet worden. Martin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Dutch translation lilypond-2.13.5
Hi, I have checked again the dutch nl.po translation file from Lilypond-2.13.5 with gtranslator, and tried to fix quite some typo's. I have attached my current version and hope it will reach the devel mailinglist and the persons who can check the translation and bring the changes to the git. My previous attempts to post my corrections failed for various reasons. -- Martin Tarenskeen--- nl.po.orig 2009-10-09 10:06:51.932038256 +0200 +++ nl.po 2009-10-09 10:05:37.496033088 +0200 @@ -1,18 +1,19 @@ # nl.po -- GNU LilyPond's dutch language file # Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Jan Nieuwenhuizen jann...@gnu.org, Han-Wen Nienhuys han...@xs4all.nl. -# Jan Nieuwenhuizen jann...@gnu.org, 1998. # Han-Wen Nienhuys han...@cs.uu.nl, 1998. # # Donnot change the format of the first three lines, # the TP robot needs them to be like this. # Of course, Han-Wen han...@xs4all.nl also is FIRST AUTHOR. # +# Jan Nieuwenhuizen jann...@gnu.org, 1998, 2009. msgid msgstr Project-Id-Version: lilypond 2.13.4\n -Report-Msgid-Bugs-To: http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs\n; +Report-Msgid-Bugs-To: http://post.gmane.org/post.php?group=gmane.comp.gnu.; +lilypond.bugs\n POT-Creation-Date: 2007-04-28 12:03+0200\n -PO-Revision-Date: 2009-09-06 15:01+0200\n +PO-Revision-Date: 2009-10-09 10:05+0200\n Last-Translator: Jan Nieuwenhuizen jann...@gnu.org\n Language-Team: Dutch vertal...@vrijschrift.org\n MIME-Version: 1.0\n @@ -20,7 +21,8 @@ Content-Transfer-Encoding: 8bit\n Date: 2001-05-09 23:29+0200\n From: jann...@gnu.org\n -Xgettext-Options: --c++ --default-domain=lilypond --join --output-dir=../po --add-comments --keyword=_\n +Xgettext-Options: --c++ --default-domain=lilypond --join --output-dir=../po +--add-comments --keyword=_\n Files: bow.cc int.cc\n #: convertrules.py:12 @@ -30,7 +32,7 @@ #: convertrules.py:13 msgid Please refer to the manual for details, and update manually. -msgstr Zie de handleiding voor de details, en actualiseer handmatic. +msgstr Zie de handleiding voor de details, en actualiseer handmatig. #: convertrules.py:14 #, python-format @@ -104,7 +106,7 @@ #: abc2ly.py:1350 msgid be strict about succes -msgstr wees strict over succes +msgstr wees strikt over succes #: abc2ly.py:1352 msgid preserve ABC's notion of beams @@ -115,7 +117,8 @@ msgid Report bugs via msgstr Meld fouten in het programma via %;\n -meld onjuistheden in de vertaling aan jann...@gnu.org of han...@xs4all.nl. +meld onjuistheden in de vertaling aan jann...@gnu.org of han...@xs4all. +nl. #: convert-ly.py:32 msgid @@ -206,7 +209,8 @@ #: etf2ly.py:1182 msgid Enigma Transport Format is a format used by Coda Music Technology's\n -Finale product. etf2ly converts a subset of ETF to a ready-to-use LilyPond file. +Finale product. etf2ly converts a subset of ETF to a ready-to-use LilyPond +file. msgstr Enigma Transport Format is een format dat wordt gebruikt door Coda\n Music Technology's Finale produkt. Dit programma converteert een\n @@ -221,8 +225,11 @@ msgstr toon garantie en auteursrechten #: lilypond-book.py:57 -msgid Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook document. -msgstr Verwerk LilyPond snippers in hybride HTML, LaTeX, texinfo of DocBook dokument. +msgid +Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook document. +msgstr +Verwerk LilyPond snippers in hybride HTML, LaTeX, texinfo of DocBook +dokument. #: lilypond-book.py:64 msgid BOOK @@ -247,8 +254,11 @@ msgstr pijp snippers door FILTER [convert-ly -n -] #: lilypond-book.py:120 -msgid use output format FORMAT (texi [default], texi-html, latex, html, docbook) -msgstr gebruik uitvoerformat FORMAT (texi [standaard], texi-html, latex, html, docbook) +msgid +use output format FORMAT (texi [default], texi-html, latex, html, docbook) +msgstr +gebruik uitvoerformat FORMAT (texi [standaard], texi-html, latex, html, +docbook) #: lilypond-book.py:123 msgid add DIR to include path @@ -420,7 +430,7 @@ #: midi2ly.py:99 msgid Exiting ... -msgstr Beëidigen ... +msgstr Beëindigen ... #: midi2ly.py:846 #, python-format @@ -503,7 +513,7 @@ #: musicxml2ly.py:504 msgid set output filename to FILE -msgstr zet uitvoerbestandnaam op BESTAND +msgstr zet uitvoerbestandsnaam op BESTAND #: getopt-long.cc:140 #, c-format @@ -547,7 +557,7 @@ #: accidental-engraver.cc:290 #, c-format msgid pair or context-name expected for accidental rule, found %s -msgstr paar of context-naam verwacht voor toevallig teken regel, gevonden: %s +msgstr paar of context-naam verwacht voor voorteken regel, gevonden: %s #: accidental.cc:160 #, c-format @@ -560,7 +570,8 @@ #: align-interface.cc:322 msgid tried to get a translation for something that is no child of mine -msgstr probeerde een verplaatsing te verkrijgen voor iets wat geen kind van mij is +msgstr +probeerde een vertaling te
dutch translation error
Hi, Has someone fixed this little typo in the dutch translation yet: kan wellicht geen goede waardestreephelling kunnen vinden should be kan wellicht geen goede waardestreephelling vinden -- Martin Tarenskeen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
midi2ly continued
Hi,
I have been hacking around a little bit with the midi2ly script.
Some time ago I reported a problem with tunes that were not in
3/4 time.
But as reaction I got a sorry, midi2ly is not supported anymore
So I decided to try a little Python hacking myself.
I found the problem was in format-1 MIDI files, where track 1 often
(always ?) contains Time and Tempo information, but no notes. And the
midi2ly script only writes out tracks if they contain notes. Result:
everything will get the default 4/4 time and the default 4=60 tempo.
Bad.
Then I started hacking.
Here's my ChangeLog:
- TrackA(time and tempo events, but no notes) and TrackB are combined
in one Staff. Time signature and Tempo are correctly used now.
- I have added some commandline options
-T --time NUM/DEN manually force a global time signature
-P --partial DURspecify an upbeat duration
--skip use invisible rests (s) for rests.
I have changed the default behaviour to
use visible rests (r)
-w --warranty The warranty message was broken. Fixed.
- I use the variable program_version in more places in the script.
For example \version is no longer written as 2.7.18 but uses the
actual program_version (2.13.3) .
I have attached my version of midi2ly. Anyone who is interested may take
a look at it or just try it. There are still some serious problems (
like (long) notelengths that cross barlines ) but I think my version
already works a little better than the previous one.
I have just started learning Python, and am not very good with git.
Maybe someone more experienced can evaluate my version of the script,
maybe improve or correct it, and then take it to the git ?
--
Martin Tarenskeen
#!/usr/bin/python
#
# midi2ly.py -- LilyPond midi import script
#
# source file of the GNU LilyPond music typesetter
#
# (c) 1998--2009 Han-Wen Nienhuys han...@xs4all.nl
# Jan Nieuwenhuizen jann...@gnu.org
'''
TODO:
* test on weird and unquantised midi input (lily-devel)
* update doc and manpage and translations
* simply insert clef changes whenever too many ledger lines
[to avoid tex capacity exceeded]
* do not ever quant skips
* better lyrics handling
* [see if it is feasible to] move ly-classes to library for use in
other converters, while leaving midi specific stuff here
* split notes that cross barlines, use ties
* better handling of polyphony in one staff.
* make barcheck and barcount work even after meter changes
* split midifile format-0 files into separate tracks ??
* test and debug using more, complex example MIDI files
'''
import os
import sys
This generic code used for all python scripts.
The quotes are to ensure that the source .py file can still be
run as a python script, but does not include any sys.path handling.
Otherwise, the lilypond-book calls inside the build
might modify installed .pyc files.
program_version = '2.13.3'
program_name = sys.argv[0]
authors = ('Jan Nieuwenhuizen jann...@gnu.org',
'Han-Wen Nienhuys han...@xs4all.nl')
for d in ['/usr/share/lilypond/%s' % ( program_version ),
'/usr/lib/lilypond/%s' % ( program_version )]:
sys.path.insert (0, os.path.join (d, 'python'))
# dynamic relocation, for GUB binaries.
bindir = os.path.abspath (os.path.dirname (sys.argv[0]))
for p in ['share', 'lib']:
datadir = os.path.abspath (bindir + '/../%s/lilypond/current/python/' % p)
sys.path.insert (0, datadir)
import midi
import lilylib as ly
global _;_=ly._
## CONSTANTS
LINE_BELL = 60
scale_steps = [0, 2, 4, 5, 7, 9, 11]
global_options = None
clocks_per_1 = 1536
clocks_per_4 = 0
time = 0
reference_note = 0
start_quant_clocks = 0
duration_quant_clocks = 0
allowed_tuplet_clocks = []
errorport = sys.stderr
def identify ():
sys.stdout.write ('%s (GNU LilyPond) %s\n' % (program_name,
program_version))
def warranty ():
identify ()
ly.encoded_write (sys.stdout, '''
%s
%s
%s
%s
''' % ( _ ('Copyright (c) %s by') % '2001--2009',
'\n '.join (authors),
_ ('Distributed under terms of the GNU General Public License.'),
_ ('It comes with NO WARRANTY.')))
def progress (s):
ly.encoded_write (errorport, s + '\n')
def warning (s):
progress (_ (warning: ) + s)
def error (s):
progress (_ (error: ) + s)
raise Exception (_ (Exiting... ))
def system (cmd, ignore_error = 0):
return ly.system (cmd, ignore_error=ignore_error)
def strip_extension (f, ext):
(p, e) = os.path.splitext (f)
if e == ext:
e = ''
return p + e
class Duration:
allowed_durs = (1, 2, 4, 8, 16, 32, 64, 128)
def __init__ (self, clocks):
self.clocks = clocks
