Dutch translation lilypond-2.13.5

2009-10-09 Thread Martin Tarenskeen

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 , Han-Wen Nienhuys 
.
-# Jan Nieuwenhuizen , 1998.
 # Han-Wen Nienhuys , 1998.
 #
 # Donnot change the format of the first three lines,
 # the TP robot needs them to be like this.
 # Of course, Han-Wen  also is FIRST AUTHOR.
 #
+# Jan Nieuwenhuizen , 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 \n"
 "Language-Team: Dutch \n"
 "MIME-Version: 1.0\n"
@@ -20,7 +21,8 @@
 "Content-Transfer-Encoding: 8bit\n"
 "Date: 2001-05-09 23:29+0200\n"
 "From:  \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  of 
."
+"meld onjuistheden in de vertaling aan  of ."
 
 #: 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 verkrijgen voor iets wat geen kind van mij is"
 
 #: all-font-metrics.cc:14

Re: Engraving essay questions and RFC

2009-10-09 Thread Jan Nieuwenhuizen
Op donderdag 08-10-2009 om 19:08 uur [tijdzone -0600], schreef Andrew
Hawryluk:

> Thanks, those are good points. Do you have copies of the scores in
> question? For the PDF version I'd love to get some scans at 300 or 600
> dpi so they could be reproduced at (nearly) full size.

I've put up some stuff at

http://lilypond.org/~janneke/essay/

> Yes, the annotations speed up the reader's job a lot. I also like
> seeing the 'unmarked' version

Yes, that's right.

> Do you mean the Schubert (Sängers Morgenlied)?

Yes.

Jan.




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Engraving essay questions and RFC

2009-10-09 Thread Trevor Daniels

Hi Andrew

Generally looking good.  A few comments, mostly minor:

a) Page 2 has the phrase "Not let down, we created a font of musical 
symbols"

"Not to be deterred," or "Undiscouraged," would be better.

b) Where you compare the shapes of the quarter rests on page 2 it 
might be better to draw attention to the three sharp points in the 
middle, as the one at the bottom seems to exhibit the point :) being 
made the least.


c) Page 3:  the last para of the text immediately below the first 
music example has the references to the two examples the wrong way 
round - the _lower_ measures contain the correction.


d) Page 5, where you compare Lily 1.4 output, I suggest you make it 
clear when 1.4 is first mentioned that this is a very old version. 
This would not be immediately obvious to someone coming to LilyPond 
for the first time.


Trevor

- Original Message - 
From: "Andrew Hawryluk" 

To: "lilypond-devel" 
Sent: Thursday, October 08, 2009 5:18 AM
Subject: Engraving essay questions and RFC


Hi everyone, I'm working on the LilyPond essay, and I'm ready to ask
you some questions.

You can read my current draft at 
http://www.musicbyandrew.ca/essay.pdf
(this is identical to a doc build with my latest patch, except that 
I
have only updated the pages containing the new essay, leaving out 
the

original, the GPL stuff, and the index.) The source file in question
is Documentation/essay/engraving.itely

Questions:

1. Multiple staff sizes and optical line weights. I have a piano +
violin excerpt on page 4 (PDF page 6). If I modify the staff-space 
and

thickness by the same number then I don't get the relatively heavier
lines that I would naturally get using "set-global-staff-size". I am
currently using this:

 \new Staff \with {
 fontSize = #-4
 \override StaffSymbol #'staff-space = #(magstep -4)
 \override StaffSymbol #'thickness = #(magstep -3)
   }

This gives me staff lines that I like, but they may not match the
carefully tunes weights of "set-global-staff-size". Also, I think I
should be thickening up the barlines and stems as well.
- Any suggestions on the tweaks I should do to match the
"set-global-staff-size" appearance?

(A previous discussion suggested magstep = 3.5 for these cases, but 
I

am trying to increase the contrast a bit.)

2. Something is wrong with my beaming on page 6 (PDF 8). Any 
guesses?

The source is
\relative c {
 \clef "bass"
 \key d \minor
 \time 3/4
 \mergeDifferentlyDottedOn
 << {\slurDashed d8.-\flageolet( e16) e4.-\trill( d16 e)}
\\ {d4_2 a2}
 >>
 \slurDashed
 4. e8( d c)
 \slurSolid
 bes g' f e16( f g_1 a_2 bes_3 d,_2)
 \slurDashed
 cis4.-\trill b8_3( a g)
 << {\slurDashed d'8.( e16) e4.-\trill( d16 e)}
\\ {4 a2}
 >>
}

3. As you can see, I have started a comparison of Finale / LilyPond 
/

real engravings. The scores are on the last 3 pages. (Note that the
Finale example has been clipped just a bit to close on the right 
hand

side. I will fix this.) My preliminary observations are

- Finale rests are always at the same heights (in v1/v2 situations).
- Finale doesn’t interlock notes nicely (mm. 28–29).
- Finale misses the B-flat in mm. 33!
- Finale’s beamed stems are almost always too long when they extend
off the staff.
- LilyPond 2.13.5 currently has a vertical spacing problem (no 
padding

between staves).
- LilyPond could use a little more space before the first note of 
mm. 30, 33–34.

- LilyPond’s ties to beat 1 of mm. 31 are shorter than any of the
reference scores, and Finale’s are even worse.
- LilyPond’s stems are often shorter than any of the references,
especially RH mm. 31.

Have I missed anything?
Please discuss?
Maybe a couple of those items should be bug reports? Although I want
to be fair in this essay, I also don't want to

4. I believe that I have now incorporated the most valuable elements
of the original essay into the nicer structure that Trevor began. Do
you agree or did I miss something? (There are probably still things 
to

add, but I don't think they will come from the old essay.)

5. Any other thoughts? The essay has been a prominent piece of
LilyPond 'marketing' and I want to know that community is getting 
the

upgraded essay that they want.

Thanks,
Andrew


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Dutch translation lilypond-2.13.5

2009-10-09 Thread Ian Hulin

Hi Martin, Jan, Han-Wen,
Does this message about etf format feel like it's been translated by a 
machine to native Dutch speakers?


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."

msgstr ""
"Enigma Transport Format is een format dat wordt gebruikt door Coda\n"
"Music Technology's Finale produkt.  Dit programma converteert een\n"
"subset van ETF naar een gebruiksklaar lilypondbestand."

is this more reasonable?

msgstr ""
"Enigma Transport Format is een format dat wordt gebruikt door de\n"
" Finale produkt van Coda Music Technology.\n"
" Dit programma converteert een subset van ETF naar\n"
" een gebruiksklaar lilypondbestand."

Cheers,
Ian

Martin Tarenskeen wrote:

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.




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


testing 2.13.6 darwin, mingw

2009-10-09 Thread Graham Percival
http://lilypond.org/~graham/

If somebody confirms darwin-x86 and mingw, I'll release it
tomorrow.

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread Mats Bengtsson
I just tried to install the mingw version on Window 7 and it seems to 
run well, both from command prompt, with drag/drop and double-clicking a 
file.


However, double-clicking the LilyPond icon on the desktop does not start 
the LilyPad editor (is it even included in the distro?) and similarly if 
you try right-click -> edit on a .ly file.


Another problem I noticed is that Lilypond cannot handle UNC directory 
paths.


  /Mats

Graham Percival wrote:

http://lilypond.org/~graham/

If somebody confirms darwin-x86 and mingw, I'll release it
tomorrow.

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
  


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: mats.bengts...@ee.kth.se
WWW: http://www.s3.kth.se/~mabe
=



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread James E. Bailey
2.13.6 runs fine on osx 10.4 from command line and the lilypad.  
Convert-ly too.


On 09.10.2009, at 16:58, Graham Percival wrote:


http://lilypond.org/~graham/

If somebody confirms darwin-x86 and mingw, I'll release it
tomorrow.

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


James E. Bailey



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread Graham Percival
On Fri, Oct 09, 2009 at 05:33:19PM +0200, Mats Bengtsson wrote:
> However, double-clicking the LilyPond icon on the desktop does not start  
> the LilyPad editor (is it even included in the distro?) and similarly if  
> you try right-click -> edit on a .ly file.

Hmm.  I'll try a complete rebuild of mingw tomorrow; some of the
fixes that Jan and I did for generating the exe at all might fix
this.

> Another problem I noticed is that Lilypond cannot handle UNC directory  
> paths.

If that's not a new item, could you add it to the google tracker?
At the moment I'm only trying to solve the "no worse than previous
releases" problem.  :)

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: quick question: web manuals presentation

2009-10-09 Thread John Mandereau
Le dimanche 04 octobre 2009 à 14:06 +0100, Graham Percival a écrit :
> Sorry, that would involve too much suckage and conditionals in the
> source file, or macros calling other macros.  I agree it's not
> ideal, but it's better than the alternative.

What about naming the frame "All formats" instead of "Other formats"
then?

Best,
John



signature.asc
Description: Ceci est une partie de message numériquement signée
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread Patrick McCarty
On Fri, Oct 9, 2009 at 7:58 AM, Graham Percival
 wrote:
> http://lilypond.org/~graham/
>
> If somebody confirms darwin-x86 and mingw, I'll release it
> tomorrow.

Both darwin installers work fine for me on OSX 10.5.

Thanks,
Patrick


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: quick question: web manuals presentation

2009-10-09 Thread Graham Percival
On Fri, Oct 09, 2009 at 06:29:03PM +0200, John Mandereau wrote:
> Le dimanche 04 octobre 2009 à 14:06 +0100, Graham Percival a écrit :
> > Sorry, that would involve too much suckage and conditionals in the
> > source file, or macros calling other macros.  I agree it's not
> > ideal, but it's better than the alternative.
> 
> What about naming the frame "All formats" instead of "Other formats"
> then?

Great idea!  Done.

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread Christian Hitz


Am 09.10.2009 um 16:58 schrieb Graham Percival:

If somebody confirms darwin-x86 and mingw, I'll release it
tomorrow.


darwin-x86 on 10.6.1 (Snow Leopard):

2.13.6 (like the whole 2.13 series) hangs on creating the fonts cache.

If the cache is already present (crated by 2.12.2) it works ok.

/Christian


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread Valentin Villenave
On Fri, Oct 9, 2009 at 5:33 PM, Mats Bengtsson  wrote:
> However, double-clicking the LilyPond icon on the desktop does not start the
> LilyPad editor (is it even included in the distro?) and similarly if you try
> right-click -> edit on a .ly file.

Could this be http://code.google.com/p/lilypond/issues/detail?id=793
all over again ?

(please ignore the issue's title, but look at the initial report instead)

Regards,
Valentin


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread Graham Percival
On Fri, Oct 09, 2009 at 09:10:20PM +0200, Christian Hitz wrote:
>
> Am 09.10.2009 um 16:58 schrieb Graham Percival:
>> If somebody confirms darwin-x86 and mingw, I'll release it
>> tomorrow.
>
> darwin-x86 on 10.6.1 (Snow Leopard):
>
> 2.13.6 (like the whole 2.13 series) hangs on creating the fonts cache.
>
> If the cache is already present (crated by 2.12.2) it works ok.

Interesting.  What happens if you try 2.12.3 ?  That was created
with current GUB, but (obviously) 2.12 code.

If that succeeds, then we know[1] that the problem is in the main
source code; if that fails, then we know[1] that the problem is in
GUB.

Cheers,
- Graham

[1] by "know", I mean "have reasonable grounds to suspect"


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread Christian Hitz

Am 09.10.2009 um 21:37 schrieb Graham Percival:

On Fri, Oct 09, 2009 at 09:10:20PM +0200, Christian Hitz wrote:


Am 09.10.2009 um 16:58 schrieb Graham Percival:

If somebody confirms darwin-x86 and mingw, I'll release it
tomorrow.


darwin-x86 on 10.6.1 (Snow Leopard):

2.13.6 (like the whole 2.13 series) hangs on creating the fonts  
cache.


If the cache is already present (crated by 2.12.2) it works ok.


Interesting.  What happens if you try 2.12.3 ?  That was created
with current GUB, but (obviously) 2.12 code.

If that succeeds, then we know[1] that the problem is in the main
source code; if that fails, then we know[1] that the problem is in
GUB.


I tested both 2.12.2 and 2.12.3 on darwin-x86 10.5 and 10.6.

2.12.2 works on both platforms, 2.12.3 hangs on creating the fonts cache
on both systems. It works if 2.12.2 has created the cache before.

@James: Could you try 2.13.6 or 2.12.3 on your 10.4 box but clear the  
font

cache before? (delete ~/.lilypond-fonts.cache-2)

/Christian


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: testing 2.13.6 darwin, mingw

2009-10-09 Thread James E. Bailey


On 10.10.2009, at 01:20, Christian Hitz wrote:


Am 09.10.2009 um 21:37 schrieb Graham Percival:

On Fri, Oct 09, 2009 at 09:10:20PM +0200, Christian Hitz wrote:


Am 09.10.2009 um 16:58 schrieb Graham Percival:

If somebody confirms darwin-x86 and mingw, I'll release it
tomorrow.


darwin-x86 on 10.6.1 (Snow Leopard):

2.13.6 (like the whole 2.13 series) hangs on creating the fonts  
cache.


If the cache is already present (crated by 2.12.2) it works ok.


Interesting.  What happens if you try 2.12.3 ?  That was created
with current GUB, but (obviously) 2.12 code.

If that succeeds, then we know[1] that the problem is in the main
source code; if that fails, then we know[1] that the problem is in
GUB.


I tested both 2.12.2 and 2.12.3 on darwin-x86 10.5 and 10.6.

2.12.2 works on both platforms, 2.12.3 hangs on creating the fonts  
cache

on both systems. It works if 2.12.2 has created the cache before.

@James: Could you try 2.13.6 or 2.12.3 on your 10.4 box but clear  
the font

cache before? (delete ~/.lilypond-fonts.cache-2)

/Christian



2.13.6 worked fine here. Took about 20 extra seconds to create the  
font database, but other than that, no problems. Sorry.

James E. Bailey



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel