Graham Percival | 1 Sep 02:33 2007
Picon

Re: doc value of regtests: none

Trevor Bača wrote:
> I like it; smaller (on the frontpage) is better. And the bib can
> certainly be shoved into an appendix (though it's a very interesting
> read every couple of months).
>   
Ok, updated.

> While we're on it, can I ask whether anyone else would like to see the
> program reference (NOT the frontpage) flattened out? Ie, instead of
> these five categories ...
>   
That looks sensible to me, but honestly speaking, I'm still too scared 
to try navigating the program reference from the main page.  (I only 
ever follow the "seealso" links in the manual)

Anyway, that's food for thought for you, Valentin.  :)    Dealing with 
the program reference is a job for the younger generation.

Cheers,
- Graham
Han-Wen Nienhuys | 1 Sep 05:09 2007

Re: [PATCHES]: Converting header and lyrics with musicxml2ly

Reinhold Kainhofer escreveu:
> Attached is the next set of patches for musicxml2ly, diffed against current 
> git by git-format-patch.

Hi, 

Thanks for your patches!

if you intend to work on this more, I could give you write access to the 
repository.  It would require you to sign up for savannah.gnu.org.

I am traveling the next 2 weeks, so I am won't have much time to look/
I'm applying your patches. Could you address my comments in follow up 
patches?

* In general, git commit messages should have the following form

  1-line summary

  background - typically the reason why you are doing it, or the 
  general idea behind it.

Keep the 80 column limit in mind here. Perhaps it's worthwhile to 
open the 1-line summary with 'MusicXML: '

* You have replaced almost all dict accesses with .get() ; this is only
desired if the default case makes sense. Sometime throwing a KeyError 
actually does make sense.

For example
(Continue reading)

Graham Percival | 1 Sep 05:25 2007
Picon

Program Usage RFC

I think the Program Usage manual is good now.  Anybody have any comments 
before the translators start working on it?  It's on the web now in the 
2.11.31 docs.

Cheers,
- Graham
Han-Wen Nienhuys | 1 Sep 05:32 2007

Re: Program Usage RFC

Graham Percival escreveu:
> I think the Program Usage manual is good now.  Anybody have any comments
> before the translators start working on it?  It's on the web now in the
> 2.11.31 docs.

Replace lilypondtool -> jedit in the node name.

--

-- 

Han-Wen Nienhuys - hanwen <at> lilypond.org - http://www.xs4all.nl/~hanwen
Till Rettig | 1 Sep 11:01 2007
Picon
Picon

Re: some more patches updating the German translation



John Mandereau wrote:
Le jeudi 30 août 2007 à 17:50 +0300, Till Rettig a écrit :
This is strange, what do you mean? I don't find this in my version of working.ly
Neither do I, but here's an excerpt of your patch: diff --git a/Documentation/de/user/advanced-notation.itely b/Documentation/de/user/advanced-notation.itely index 79d2b61..dd02d2c 100644 --- a/Documentation/de/user/advanced-notation.itely +++ b/Documentation/de/user/advanced-notation.itely <at> <at> -1,7 +1,7 <at> <at> <at> c -*- coding: utf-8; mode: texinfo; documentlanguage: de -*- <at> c This file is part of lilypond.tely <at> ignore - Translation of GIT committish: 9634340429eb0518432b152fe4aaf7471b67b013 + Translation of GIT committish: 3121682025660b6c85fbf3f22bb9cd8396699ad1 "documentlanguage: de" appears in a context of the patch; it's very strange, isn't it? I really don't know where this comes from.
ok, I found the mistake: I have this "documentlanguage" in all untranslated files. No idea how it came there
and why it is not in git. What can we do? Would it work that I send you the rest of the updates as a diff and
after you applied then do
git reset <head of current git>? Is that enough to get me back to a copy of git without my own changes?
Yes, you're right. The big patch applied succesufully excepted index.html.in, which I edited by hand to apply your changes, so expect to encounter a conflict for this file next time you pull; if this happens, always resolve conflicts in favor of git.sv.gnu.org branch, so you avoid future conflicts.
Yes, I merged that and send you now the output of git diff. Hope it works now this way.
index.html.in seems now clean.
Sorry for the delay for applying your updates; they will be included in 2.11.32
it's ok, I was quite lazy myself lately. ;-)

Greetings
Till
diff --git a/Documentation/de/user/instrument-notation.itely b/Documentation/de/user/instrument-notation.itely
index 4a46799..931f65b 100644
--- a/Documentation/de/user/instrument-notation.itely
+++ b/Documentation/de/user/instrument-notation.itely
 <at>  <at>  -1,7 +1,7  <at>  <at> 
  <at> c -*- coding: utf-8; mode: texinfo; documentlanguage: de -*-
  <at> c This file is part of lilypond.tely
  <at> ignore
-    Translation of GIT committish: 9634340429eb0518432b152fe4aaf7471b67b013
+    Translation of GIT committish: 3db3697bb5109201192c9cecdd2e4b7a5520421a

 
     When revising a translation, copy the HEAD committish of the
diff --git a/Documentation/de/user/macros.itexi b/Documentation/de/user/macros.itexi
index fd08e3a..218d20c 100644
--- a/Documentation/de/user/macros.itexi
+++ b/Documentation/de/user/macros.itexi
 <at>  <at>  -1,6 +1,6  <at>  <at> 
- <at> c -*- coding: utf-8; mode: texinfo; -*-
+ <at> c -*- coding: us-ascii; mode: texinfo; -*-
  <at> ignore
-    Translation of GIT committish: 8a19cc25524338cdd99863ccd954bbcb8f8b2afa
+    Translation of GIT committish: 3db3697bb5109201192c9cecdd2e4b7a5520421a

     When revising a translation, copy the HEAD committish of the
     version that you are working on.  See TRANSLATION for details.
 <at>  <at>  -68,7 +68,7  <at>  <at> 

  <at> macro lsrdir{DIR}
  <at> ifhtml
-   <at> uref{source/input/lsr/\DIR\/collated-files.html, <at> file{\DIR\}}
+   <at> uref{source/input/lsr/\DIR\/collated-files.html, <at> file{\DIR\}/}
  <at> end ifhtml
  <at> ifnothtml
    <at> file{\DIR\}
 <at>  <at>  -136,13 +136,11  <at>  <at> 

  <at> ifclear bigpage

- <at> c annoying parentheses stripped by add-html-footer.py
  <at> macro internalsref{NAME}
  <at> vindex \NAME\
  <at> ref{\NAME\,,,lilypond-internals}
  <at> end macro

- <at> c annoying parentheses stripped by add-html-footer.py
  <at> macro rglos{NAME}
  <at> vindex \NAME\
  <at> ref{\NAME\,,,music-glossary}
 <at>  <at>  -191,9 +189,7  <at>  <at> 
  <at> ref{\NAME\,,,lilypond-internals}
  <at> end macro

- <at> macro inputfileref{DIR,NAME}
- <at> uref{source/\DIR\/collated-files.html#\NAME\, <at> file{\DIR\/\NAME\}}
- <at> end macro
+

  <at> macro rglos{NAME}
  <at> vindex \NAME\
 <at>  <at>  -235,11 +231,7  <at>  <at> 
  <at> inforef{\NAME\,,lilypond-internals}
  <at> end macro

- <at> macro inputfileref{DIR,NAME}
- <at> file{\DIR\/\NAME\}
- <at> end macro
-
- <at> macro rglos{NAME} <at> c
+ <at> macro rglos{NAME}
  <at> vindex \NAME\
  <at> inforef{\NAME\,,,music-glossary}
  <at> end macro
 <at>  <at>  -279,10 +271,6  <at>  <at> 
  <at> code{\NAME\}
  <at> end macro

- <at> macro inputfileref{DIR,NAME}
- <at> file{\DIR\/ <at> /\NAME\}
- <at> end macro
-
  <at> macro rglos {NAME}
  <at> vindex \NAME\
  <at> code{\NAME\}
diff --git a/Documentation/de/user/programming-interface.itely b/Documentation/de/user/programming-interface.itely
index 37c8784..c31f9a0 100644
--- a/Documentation/de/user/programming-interface.itely
+++ b/Documentation/de/user/programming-interface.itely
 <at>  <at>  -1,7 +1,7  <at>  <at> 
  <at> c -*- coding: utf-8; mode: texinfo; documentlanguage: de -*-
  <at> c This file is part of lilypond.tely
  <at> ignore
-    Translation of GIT committish: 9634340429eb0518432b152fe4aaf7471b67b013
+    Translation of GIT committish: 3db3697bb5109201192c9cecdd2e4b7a5520421a

 
     When revising a translation, copy the HEAD committish of the
diff --git a/Documentation/de/user/putting.itely b/Documentation/de/user/putting.itely
index a87ae2d..ff00db7 100644
--- a/Documentation/de/user/putting.itely
+++ b/Documentation/de/user/putting.itely
 <at>  <at>  -1,7 +1,7  <at>  <at> 
  <at> c -*- coding: utf-8; mode: texinfo; -*-
  <at> c This file is part of lilypond.tely
  <at> ignore
-    Translation of GIT committish: b8d54460424b040bbc3d273048707ed2fcfd118d
+    Translation of GIT committish: 3db3697bb5109201192c9cecdd2e4b7a5520421a

     When revising a translation, copy the HEAD committish of the
     version that you are working on.  See TRANSLATION for details.
 <at>  <at>  -36,7 +36,7  <at>  <at>  Cello notieren. In diesem Fall beginnen Sie mit
   <at> qq{Noten und Text} (für die Sopranstimme).

  <at> example
-\version "2.11.15"
+\version "2.11.23"
 melodie = \relative c'  <at> {
   \clef treble
   \key c \major
 <at>  <at>  -66,7 +66,7  <at>  <at>  Jetzt wollen wir die Cellostimme hinzufügen. Schauen wir uns das
  <at> qq{Nur Noten}-Beispiel an:

  <at> example
-\version "2.11.15"
+\version "2.11.23"
 melodie = \relative c'  <at> {
   \clef treble
   \key c \major
 <at>  <at>  -106,7 +106,7  <at>  <at>  Wir setzen hier auch ein paar andere Noten für das Cello.

 
  <at> example
-\version "2.11.15"
+\version "2.11.23"
 sopranNoten = \relative c'  <at> {
   \clef treble
   \key c \major
 <at>  <at>  -181,7 +181,7  <at>  <at>  Unordnung geraden. Aber das ist einfach wieder hergestellt. Hier die
 vollständige Vorlage für Sopran und Cello:

  <at> lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 sopranoMusic = \relative c' {
   \clef treble
   \key c \major
diff --git a/Documentation/de/user/spacing.itely b/Documentation/de/user/spacing.itely
index 714804e..a693c71 100644
--- a/Documentation/de/user/spacing.itely
+++ b/Documentation/de/user/spacing.itely
 <at>  <at>  -1,7 +1,7  <at>  <at> 
  <at> c -*- coding: utf-8; mode: texinfo; documentlanguage: de -*-
  <at> c This file is part of lilypond.tely
  <at> ignore
-    Translation of GIT committish: 9634340429eb0518432b152fe4aaf7471b67b013
+    Translation of GIT committish: 3db3697bb5109201192c9cecdd2e4b7a5520421a

 
     When revising a translation, copy the HEAD committish of the
diff --git a/Documentation/de/user/tutorial.itely b/Documentation/de/user/tutorial.itely
index 4580edc..5676524 100644
--- a/Documentation/de/user/tutorial.itely
+++ b/Documentation/de/user/tutorial.itely
 <at>  <at>  -1,7 +1,7  <at>  <at> 
  <at> c -*- coding: utf-8; mode: texinfo; -*-
  <at> c This file is part of lilypond.tely
  <at> ignore
-    Translation of GIT committish: b8d54460424b040bbc3d273048707ed2fcfd118d
+    Translation of GIT committish: 3db3697bb5109201192c9cecdd2e4b7a5520421a

     When revising a translation, copy the HEAD committish of the
     version that you are working on.  See TRANSLATION for details.
 <at>  <at>  -338,7 +338,7  <at>  <at>  werden automatisch hinzugefügt.
 Wenn keine Dauer bezeichnet wird, wird die der vorhergehenden Note
 verwendet. Für die erste Note ist eine Viertel als Standard definiert.

-Um  <at> rglos{dotted notes} zu erzeugen, wird einfach ein Punkt  <at> q{.}
+Um  <at> rglos{dotted note}s zu erzeugen, wird einfach ein Punkt  <at> q{.}
 hinter die Notendauer geschrieben.

  <at> lilypond[quote,ragged-right,verbatim]
 <at>  <at>  -427,10 +427,11  <at>  <at>  siehe  <at> ref{Clef}.
  <at> node Working on text files
  <at> subsection Working on text files

-LilyPonds Quelldateien werden wie Dateien in den meisten
-Programmiersprachen behandelt: Es ist auf Groß- und Kleinschreibung
-zu achten, Ausdrücke werden mit geschweiften Klammern  <at> {  <at> }
-eingeklammert und Kommentare mit dem Prozentzeichen  <at> code{%} auskommentiert
+LilyPonds Quelldateien ähneln Dateien in den meisten
+Programmiersprachen: Es ist auf Groß- und Kleinschreibung
+zu achten und Leerzeichen sind gleichwertig. Ausdrücke werden 
+mit geschweiften Klammern  <at> {  <at> } eingeklammert und Kommentare 
+mit dem Prozentzeichen  <at> code{%} auskommentiert
 oder mit  <at> code{% <at> { ... % <at> }} umgeben.

 Wenn das jetzt unverständlich erscheint, sind hier die  Erklärungen:
 <at>  <at>  -490,7 +491,8  <at>  <at>  Noten hat. Es gibt zwei verschiedene Typen von Kommentaren. Das
 Prozentzeichen  <at> q{%} geht einem Zeilen-Kommentar voraus: Alles
 nach diesem Zeichen wird in dieser Zeile ignoriert. Ein Block-Kommentar
 ist ein ganzer Abschnitt mit einem Kommentar. Alles, was von  <at> code{% <at> {}
- und  <at> code{% <at> }} umgeben ist, wird ignoriert. Das folgende Beispiel zeigt
+ und  <at> code{% <at> }} umgeben ist, wird ignoriert. (Kommentare könne nicht 
+geschachtelt werden.) Das folgende Beispiel zeigt
 mögliche Anwendung von Kommentaren:

  <at> example
 <at>  <at>  -727,10 +729,9  <at>  <at>  d4( c16) cis( d e c cis d) e( d4)

  <at> cindex Phrasierungsbögen
  <at> cindex Legatobögen, Phrasierung
- <at> cindex Bögen
+
  <at> subheading Phrasing slurs

- <at> cindex Phrasierungsbögen
 Bögen, die längere Phrasierungseinheiten markieren
 (Phrasierungsbögen), werden mit  <at> code{\(} und
  <at> code{\)} eingegeben.  Es können sowohl Legato- als auch
 <at>  <at>  -779,7 +780,7  <at>  <at>  siehe  <at> ref{Phrasing slurs}.
  <at> cindex Staccato
  <at> subheading Articulations

-Übliche  <at> rglos{articulations} können durch Anfügen von Minus
+Übliche  <at> rglos{articulation}s können durch Anfügen von Minus
 ( <at> q{-}) und einem entsprechenden Zeichen eingegeben werden:

  <at> lilypond[quote,ragged-right,verbatim,fragment,relative=2]
 <at>  <at>  -1424,10 +1425,10  <at>  <at>  dient es als Einleitung zum Rest des Handbuches.
  <at> cindex Versionsnummern
 Der  <at> code{\version}-Befehl zeigt an, für welche LilyPond-Version
 eine Quelldatei geschrieben worden ist. Um etwa eine Datei für die
-Version 2.11.20 zu markieren, wird einfach
+Version 2.11.23 zu markieren, wird einfach

  <at> example
-\version "2.11.15"
+\version "2.11.23"
  <at> end example

  <at> noindent
 <at>  <at>  -1450,7 +1451,7  <at>  <at>  außerhalb der musikalischen Ausdrücke, meistens wird die
 direkt nach der Versionsnummer eingefügt.

  <at> example
-\version "2.11.15"
+\version "2.11.23"
 \header  <at> {
   title = "Symphony"
   composer = "Ich"
 <at>  <at>  -1658,7 +1659,7  <at>  <at>  haben wir bei vielen Beispielen in der Übung die
  <at> code{\relative c''}-Umgebung weggelassen.

 Im Rest des Handbuches wurde noch viel nachlässiger vorgegangen:
-In manchen Fällen fehlt nur das  <at> code{\relative c''}, in anderen
+In manchen Fällen fehlt nur das  <at> code{\relative c''  <at> { ...  <at> }}, in anderen
 wurde eine andere Oktave als Startpunkt benutzt (etwa  <at> code{c'} oder
   <at> code{c,,}), manchmal ist das ganze Beispiel im absoluten Modus
 geschrieben. Solche Mehrdeutigkeiten treten aber nur in Fällen auf, in
diff --git a/Documentation/po/de.po b/Documentation/po/de.po
index 9493402..2902da4 100644
--- a/Documentation/po/de.po
+++ b/Documentation/po/de.po
 <at>  <at>  -1,20 +1,21  <at>  <at> 
 # translation of LilyPond documentation
 # Copyright (C) 2006 Han-Wen Nienhuys, Jan Nieuwenhuizen
 # This file is distributed under the same license as the lilypond package.
-# FIRST AUTHOR <EMAIL <at> ADDRESS>, YEAR.
-#
-#, fuzzy
+# Till Rettig <till.rettig <at> gmx.de>, 2007.
+# , fuzzy
+# 
+# 
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2007-08-02 13:38+0200\n"
-"PO-Revision-Date: 2007-05-12 18:41+0200\n"
+"PO-Revision-Date: 2007-08-30 21:37+0300\n"
 "Last-Translator: Till Rettig <till.rettig <at> gmx.de>\n"
-"Language-Team: de <LL <at> li.org>\n"
+"Language-Team: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
+"Content-Transfer-Encoding: 8bit"

 #: add_html_footer.py:44
 #, python-format
 <at>  <at>  -33,7 +34,8  <at>  <at>  msgstr ""
 msgid ""
 "Your <a href=\"%(suggest_Docs_url)s\">suggestions for the documentation</a> "
 "are welcome."
-msgstr ""
+msgstr "Ihre <a href=\"%(suggest_Docs_url)s\">Vorschläge für die Dokumentation</a> "
+"sind willkommen."

 #: add_html_footer.py:55
 #, python-format
 <at>  <at>  -57,17 +59,16  <at>  <at>  msgstr "Entwicklungszweig"
 msgid ""
 "This section has not been translated yet; please refer to the manual in "
 "English."
-msgstr ""
+msgstr "Dieser Abschnitt wurde noch nicht übersetzt, bitte lesen Sie den Abschnitt im englischen Benutzerhandbuch."

 #.  <at> node in ../../../Documentation/user/lilypond-program.tely
 #.  <at> node in ../../../Documentation/user/lilypond.tely
 msgid "Top"
-msgstr ""
+msgstr "Top"

 #.  <at> top in ../../../Documentation/user/lilypond-program.tely
-#, fuzzy
 msgid "GNU LilyPond --- program usage"
-msgstr "GNU LilyPond -- Das Notensatzprogramm"
+msgstr "GNU LilyPond -- Die Programmbenutzung"

 #.  <at> node in ../../../Documentation/user/lilypond-program.tely
 #.  <at> appendix in ../../../Documentation/user/lilypond-program.tely
 <at>  <at>  -99,81 +100,76  <at>  <at>  msgstr "Übliche Veränderungen der Einstellungen"
 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> chapter in ../../../Documentation/user/install.itely
 msgid "Install"
-msgstr ""
+msgstr "Installieren"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> section in ../../../Documentation/user/install.itely
 msgid "Precompiled binaries"
-msgstr ""
+msgstr "Vorkompilierte Binär-Pakete"

 #.  <at> subsection in ../../../Documentation/user/install.itely
 msgid "Downloading"
-msgstr ""
+msgstr "Herunterladen"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> section in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "Compiling from source"
-msgstr "Eine Quelldatei übersetzen"
+msgstr "Aus den Quellen übersetzen"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> subsection in ../../../Documentation/user/install.itely
 msgid "Downloading source code"
-msgstr ""
+msgstr "Den Quellcode herunterladen"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> subsection in ../../../Documentation/user/install.itely
 msgid "Requirements"
-msgstr ""
+msgstr "Voraussetzungen"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "Compilation"
-msgstr "Einfache Notation"
+msgstr "Übersetzen"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
+#, fuzzy
 msgid "Running requirements"
-msgstr ""
+msgstr "Voraussetzungen erfüllen"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "Building documentation"
-msgstr "Komplizierte Funktionen erstellen"
+msgstr "Die Dokumentation übersetzen"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> subsection in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "Building LilyPond"
-msgstr "LilyPond starten"
+msgstr "LilyPond übersetzen"

 #.  <at> subsubsection in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "Compiling"
-msgstr "Eine Quelldatei übersetzen"
+msgstr "Kompilieren"

 #.  <at> subsubsection in ../../../Documentation/user/install.itely
 msgid "Compiling for multiple platforms"
-msgstr ""
+msgstr "Für mehrere Plattformen kompilieren"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> subsection in ../../../Documentation/user/install.itely
 msgid "Building documentation without compiling LilyPond"
-msgstr ""
+msgstr "Die Dokumentation übersetzen ohne LilyPond zu kompilieren"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> subsection in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "Testing LilyPond"
-msgstr "LilyPond starten"
+msgstr "LilyPond testen"

 #.  <at> node in ../../../Documentation/user/install.itely
 #.  <at> subsection in ../../../Documentation/user/install.itely
 msgid "Problems"
-msgstr ""
+msgstr "Probleme"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
 msgid "Bison 1.875"
-msgstr ""
+msgstr "Bison 1.875"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
 #.  <at> subsubheading in ../../../Documentation/user/tutorial.itely
 <at>  <at>  -181,23 +177,21  <at>  <at>  msgid "MacOS X"
 msgstr "MacOS X"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "Solaris"
-msgstr "Legatobögen"
+msgstr "Solaris"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
 msgid "FreeBSD"
-msgstr ""
+msgstr "FreeBSD"

 #.  <at> unnumberedsubsubsec in ../../../Documentation/user/install.itely
-#, fuzzy
 msgid "International fonts"
-msgstr "Interpretationsumgebungen"
+msgstr "Internationale Schriftarten"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> chapter in ../../../Documentation/user/setup.itely
 msgid "Setup"
-msgstr ""
+msgstr "Setup"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> section in ../../../Documentation/user/setup.itely
 <at>  <at>  -206,35 +200,33  <at>  <at>  msgstr "Anmerkungen für MacOS X"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> section in ../../../Documentation/user/setup.itely
-#, fuzzy
 msgid "Text editor support"
 msgstr "Unterstützung von Texteditoren"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> subsection in ../../../Documentation/user/setup.itely
 msgid "Emacs mode"
-msgstr ""
+msgstr "Emacs-Modus"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> subsection in ../../../Documentation/user/setup.itely
 msgid "Vim mode"
-msgstr ""
+msgstr "Vim-Modus"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> subsection in ../../../Documentation/user/setup.itely
-#, fuzzy
 msgid "LilyPondTool"
-msgstr "LilyPond-Index"
+msgstr "LilyPondTool"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> subsection in ../../../Documentation/user/setup.itely
 msgid "TexShop"
-msgstr ""
+msgstr "TexShop"

 #.  <at> node in ../../../Documentation/user/setup.itely
 #.  <at> section in ../../../Documentation/user/setup.itely
 msgid "Point and click"
-msgstr ""
+msgstr "Point and click"

 #.  <at> node in ../../../Documentation/user/running.itely
 #.  <at> chapter in ../../../Documentation/user/running.itely
 <at>  <at>  -274,7 +266,7  <at>  <at>  msgstr "Fehlermeldungen"

 #.  <at> node in ../../../Documentation/user/lilypond-book.itely
 msgid "LilyPond-book"
-msgstr ""
+msgstr "LilyPond-book"

 #.  <at> chapter in ../../../Documentation/user/lilypond-book.itely
 msgid " <at> command{lilypond-book}: Integrating text and music"
 <at>  <at>  -405,7 +397,7  <at>  <at>  msgstr "LilyPond-Dateien erstellen"
 #.  <at> node in ../../../Documentation/user/fdl.itexi
 #.  <at> appendix in ../../../Documentation/user/fdl.itexi
 msgid "GNU Free Documentation License"
-msgstr ""
+msgstr "GNU Free Documentation License"

 #.  <at> appendixsubsec in ../../../Documentation/user/fdl.itexi
 msgid "ADDENDUM: How to use this License for your documents"
 <at>  <at>  -462,24 +454,21  <at>  <at>  msgstr "Über das Handbuch"

 #.  <at> subsubheading in ../../../Documentation/user/introduction.itely
 msgid "Learning manual"
-msgstr ""
+msgstr "Handbuch zum Lernen"

 #.  <at> subsubheading in ../../../Documentation/user/introduction.itely
-#, fuzzy
 msgid "Notation reference"
-msgstr "Zurechtfinden in der Programmreferenz"
+msgstr "Notationsreferenz"

 #.  <at> subsubheading in ../../../Documentation/user/introduction.itely
 msgid "Program usage"
-msgstr ""
+msgstr "Programmbenutzung"

 #.  <at> subsubheading in ../../../Documentation/user/introduction.itely
-#, fuzzy
 msgid "Appendices"
 msgstr "Anhang"

 #.  <at> subsubheading in ../../../Documentation/user/introduction.itely
-#, fuzzy
 msgid "Other information"
 msgstr "Mehr Information"

 <at>  <at>  -504,11 +493,11  <at>  <at>  msgstr "Eingabe von Noten und Ansicht des Ergebnisses"

 #.  <at> subsubheading in ../../../Documentation/user/tutorial.itely
 msgid "Windows"
-msgstr ""
+msgstr "Windows"

 #.  <at> subsubheading in ../../../Documentation/user/tutorial.itely
 msgid "Unix"
-msgstr ""
+msgstr "Unix"

 #.  <at> node in ../../../Documentation/user/tutorial.itely
 #.  <at> subsection in ../../../Documentation/user/tutorial.itely
 <at>  <at>  -1068,7 +1057,7  <at>  <at>  msgstr "Auflösung von Zusammenstößen"
 #.  <at> node in ../../../Documentation/user/basic-notation.itely
 #.  <at> section in ../../../Documentation/user/basic-notation.itely
 msgid "Staff notation"
-msgstr "Notation innerhalb von Systemen"
+msgstr "Notation innerhalb eines Systems"

 #.  <at> node in ../../../Documentation/user/basic-notation.itely
 #.  <at> subsection in ../../../Documentation/user/basic-notation.itely
 <at>  <at>  -1148,12 +1137,12  <at>  <at>  msgstr "Triller"
 #.  <at> node in ../../../Documentation/user/basic-notation.itely
 #.  <at> subsection in ../../../Documentation/user/basic-notation.itely
 msgid "Glissando"
-msgstr ""
+msgstr "Glissando"

 #.  <at> node in ../../../Documentation/user/basic-notation.itely
 #.  <at> subsection in ../../../Documentation/user/basic-notation.itely
 msgid "Arpeggio"
-msgstr ""
+msgstr "Arpeggio"

 #.  <at> node in ../../../Documentation/user/basic-notation.itely
 #.  <at> subsection in ../../../Documentation/user/basic-notation.itely
 <at>  <at>  -1273,13 +1262,12  <at>  <at>  msgstr "Eingabe von Text"
 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsection in ../../../Documentation/user/instrument-notation.itely
 msgid "Aligning lyrics to a melody"
-msgstr ""
+msgstr "Text an einer Melodie ausrichten"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsubsection in ../../../Documentation/user/instrument-notation.itely
-#, fuzzy
 msgid "Automatic syllable durations"
-msgstr "Automatische Balken"
+msgstr "Automatische Silbendauer"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsubsection in ../../../Documentation/user/instrument-notation.itely
 <at>  <at>  -1289,23 +1277,22  <at>  <at>  msgstr "Eine andere Art, den Text einzugeben"
 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsubsection in ../../../Documentation/user/instrument-notation.itely
 msgid "Assigning more than one syllable to a single note"
-msgstr ""
+msgstr "Mehr als eine Strophe an einer Note ausrichten"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsubsection in ../../../Documentation/user/instrument-notation.itely
 msgid "More than one note on a single syllable"
-msgstr ""
+msgstr "Mehr als eine Note für eine einzelne Silbe"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsubsection in ../../../Documentation/user/instrument-notation.itely
 msgid "Extenders and hyphens"
-msgstr ""
+msgstr "Unterstrichen und Trennstriche"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsection in ../../../Documentation/user/instrument-notation.itely
-#, fuzzy
 msgid "Working with lyrics and identifiers"
-msgstr "Stücke durch Bezeichner organisieren"
+msgstr "Mit Gesangtexten und Bezeichnern arbeiten"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsection in ../../../Documentation/user/instrument-notation.itely
 <at>  <at>  -1495,12 +1482,12  <at>  <at>  msgstr "Vorzeichen der alten Musik"
 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsection in ../../../Documentation/user/instrument-notation.itely
 msgid "Custodes"
-msgstr ""
+msgstr "Custodes"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsection in ../../../Documentation/user/instrument-notation.itely
 msgid "Divisiones"
-msgstr ""
+msgstr "Divisiones"

 #.  <at> node in ../../../Documentation/user/instrument-notation.itely
 #.  <at> subsection in ../../../Documentation/user/instrument-notation.itely
 <at>  <at>  -1600,7 +1587,6  <at>  <at>  msgstr "Überblick über Textbeschriftungsbefehle"

 #.  <at> node in ../../../Documentation/user/advanced-notation.itely
 #.  <at> subsection in ../../../Documentation/user/advanced-notation.itely
-#, fuzzy
 msgid "Overview of text markup list commands"
 msgstr "Überblick über Textbeschriftungsbefehle"

 <at>  <at>  -1727,7 +1713,7  <at>  <at>  msgstr "Gespreizte Balken"
 #.  <at> node in ../../../Documentation/user/advanced-notation.itely
 #.  <at> subsection in ../../../Documentation/user/advanced-notation.itely
 msgid "Improvisation"
-msgstr ""
+msgstr "Improvisation"

 #.  <at> node in ../../../Documentation/user/advanced-notation.itely
 #.  <at> subsection in ../../../Documentation/user/advanced-notation.itely
 <at>  <at>  -1792,7 +1778,7  <at>  <at>  msgstr "Standardeinstellungen verändern"
 #.  <at> node in ../../../Documentation/user/changing-defaults.itely
 #.  <at> section in ../../../Documentation/user/changing-defaults.itely
 msgid "Automatic notation"
-msgstr ""
+msgstr "Automatische Notation"

 #.  <at> node in ../../../Documentation/user/changing-defaults.itely
 #.  <at> subsection in ../../../Documentation/user/changing-defaults.itely
 <at>  <at>  -1851,17 +1837,14  <at>  <at>  msgstr "Umgebungen aneinander ausrichten"

 #.  <at> node in ../../../Documentation/user/changing-defaults.itely
 #.  <at> subsection in ../../../Documentation/user/changing-defaults.itely
-#, fuzzy
 msgid "Vertical grouping of grobs"
-msgstr "Vertikale Abstände"
+msgstr "Vertikale Gruppierung der grafischen Objekte (grob)"

 #.  <at> node in ../../../Documentation/user/changing-defaults.itely
-#, fuzzy
 msgid "The \\override command"
 msgstr "Der \\override-Befehl"

 #.  <at> section in ../../../Documentation/user/changing-defaults.itely
-#, fuzzy
 msgid "The  <at> code{\\override} command"
 msgstr "Der \\override-Befehl"

 <at>  <at>  -1891,22 +1874,20  <at>  <at>  msgid "Objects connected to the input"
 msgstr "Objekte, die mit der Eingabe verbunden sind"

 #.  <at> node in ../../../Documentation/user/changing-defaults.itely
-#, fuzzy
 msgid "Using Scheme code instead of \\tweak"
 msgstr "Scheme-Code anstelle von \tweak verwenden"

 #.  <at> subsection in ../../../Documentation/user/changing-defaults.itely
-#, fuzzy
 msgid "Using Scheme code instead of  <at> code{\\tweak}"
 msgstr "Scheme-Code anstelle von  <at> code{\tweak} verwenden"

 #.  <at> node in ../../../Documentation/user/changing-defaults.itely
 msgid "\\set versus \\override"
-msgstr ""
+msgstr "\\set versus \\override"

 #.  <at> subsection in ../../../Documentation/user/changing-defaults.itely
 msgid " <at> code{\\set} vs.  <at> code{\\override}"
-msgstr ""
+msgstr " <at> code{\\set} vs.  <at> code{\\override}"

 #.  <at> node in ../../../Documentation/user/changing-defaults.itely
 #.  <at> subsection in ../../../Documentation/user/changing-defaults.itely
 <at>  <at>  -1976,11 +1957,10  <at>  <at>  msgstr "Eigene Titel"
 #.  <at> node in ../../../Documentation/user/non-music.itely
 #.  <at> subsection in ../../../Documentation/user/non-music.itely
 msgid "Reference to page numbers"
-msgstr ""
+msgstr "Verweis auf die Seitenzahlen"

 #.  <at> node in ../../../Documentation/user/non-music.itely
 #.  <at> subsection in ../../../Documentation/user/non-music.itely
-#, fuzzy
 msgid "Table of contents"
 msgstr "Inhaltsverzeichnis"

 <at>  <at>  -2081,9 +2061,8  <at>  <at>  msgstr "Optimale Umbrüche zum Blättern"

 #.  <at> node in ../../../Documentation/user/spacing.itely
 #.  <at> subsection in ../../../Documentation/user/spacing.itely
-#, fuzzy
 msgid "Minimal page breaking"
-msgstr "Optimale Seitenumbrüche"
+msgstr "Minimale Seitenumbrüche"

 #.  <at> node in ../../../Documentation/user/spacing.itely
 #.  <at> subsection in ../../../Documentation/user/spacing.itely
 <at>  <at>  -2439,7 +2418,7  <at>  <at>  msgstr "Vorlage zur Transkription von Gregorianik"
 #.  <at> node in ../../../Documentation/user/templates.itely
 #.  <at> appendixsec in ../../../Documentation/user/templates.itely
 msgid "Jazz combo"
-msgstr ""
+msgstr "Jazz combo"

 #.  <at> node in ../../../Documentation/user/templates.itely
 #.  <at> appendixsec in ../../../Documentation/user/templates.itely
 <at>  <at>  -2448,11 +2427,11  <at>  <at>  msgstr "Lilypond-book-Vorlagen"

 #.  <at> appendixsubsec in ../../../Documentation/user/templates.itely
 msgid "LaTeX"
-msgstr ""
+msgstr "LaTeX"

 #.  <at> appendixsubsec in ../../../Documentation/user/templates.itely
 msgid "Texinfo"
-msgstr ""
+msgstr "Texinfo"

 #.  <at> node in ../../../Documentation/user/cheatsheet.itely
 #.  <at> appendix in ../../../Documentation/user/cheatsheet.itely
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Shelagh Manton | 1 Sep 13:17 2007
Picon

Emacs lilypond-mode

I have been trying to put together a number of interactive skeletons for
my own use with LilyPond and I was wondering if they might be of use to
others. I've taken the templates from the recent 2.11 documentation and
used skeleton.el. I also included some smaller skeletons for inserting
LilyPond structures, such as \header{} , \transpose,  \global  and other
variables. But mainly it is to make it easy to access the example
templates from within lilypond-mode.

I am not sure of the procedure of drawing attention to work like this,
how or where to upload the file. I would appreciate if someone could
look over the file, try it out and see if it might be useful. 

I have some ideas for functions which I haven't the expertise to put
into place. 

Shelagh 

Attachment (lp-skeletons.el): text/x-emacs-lisp, 33 KiB
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
John Mandereau | 1 Sep 13:37 2007
Picon

Re: some more patches updating the German translation

Le samedi 01 septembre 2007 à 12:01 +0300, Till Rettig a écrit :
> John Mandereau wrote: 
> > "documentlanguage: de" appears in a context of the patch; it's very
> > strange, isn't it?  I really don't know where this comes from.
> >   
> ok, I found the mistake: I have this "documentlanguage" in all untranslated files. No idea how it came there
> and why it is not in git.

It's autogenerated by texi-langutils.py when skeletons are created or
updated.  It seems that some Eamcs versions/configs keep this local
variable, whereas other don't.  I don't mind whether we keep it or not
as long as it does not prevent anybody to make clean patches.

>  What can we do? Would it work that I send you the rest of the updates as a diff and 
> after you applied then do 
> git reset <head of current git>? Is that enough to get me back to a copy of git without my own changes?

Yes, approximately.  git-reset is the good command to use, use it with
- the name of lilypond/translation remote branch in your git repository as <head of current git>
- --hard option, to also apply changes to your working tree.

  
> Yes, I merged that and send you now the output of git diff. Hope it works now this way.
> index.html.in seems now clean.

However, PDF compilation fails on German manual with your patch, see
comments below.  I pushed fixes to lilypond/translation.

>  #.  <at> node in ../../../Documentation/user/instrument-notation.itely
>  #.  <at> subsection in ../../../Documentation/user/instrument-notation.itely
>  <at>  <at>  -1600,7 +1587,6  <at>  <at>  msgstr "Überblick über Textbeschriftungsbefehle"
>  
>  #.  <at> node in ../../../Documentation/user/advanced-notation.itely
>  #.  <at> subsection in ../../../Documentation/user/advanced-notation.itely
> -#, fuzzy
>  msgid "Overview of text markup list commands"
>  msgstr "Überblick über Textbeschriftungsbefehle"

Pay attention to these slightly different titles!  The identical
translation you provide for different titles makes pdfetex complain.
I fixed the second title as "Überblick über
Textbeschriftungslistenbefehle", please provide a patch if it's not
correct (it's certainly not, as I've not written in German for
ages :-p).

There were other various  <at> commands typos and oddities, fixed in
7c9ff05e82902b3357f8a2ac0354d8971539a15a and
718cc970304f6b9a3bb990259a048c06e56f4e48 (lilypond/translation).  Your
recent 2 patches and all fixes are also on master.

Cheers,
John
Reinhold Kainhofer | 1 Sep 14:42 2007

Re: [PATCHES]: Converting header and lyrics with musicxml2ly

Hi Han-Wen!

Attached are two more patches, which already address some of the points you 
mention.

-) 2007-09-01_0008-MusicXML-Conversion-of-various-types-of-spanners-o.patch  
converts some more spanners from MusicXML to lilypond. In particular, octave 
shifts, trill spanners, glissando and bends.

-) 2007-09-01_0009-MusicXML-Convert-all-clefs-escape-in-header-fiel.patch    
Convert all available clefs to lilypond. Also address the issues by Han-Wen 
mentioned below. Don't be so strict about quoting in lyrics: Only wrap the 
lyrics syllables in quotes if necessary (but then also escape " in lyrics and 
header fields!).

Am Samstag, 1. September 2007 schrieben Sie:
> if you intend to work on this more, I could give you write access to the
> repository.  It would require you to sign up for savannah.gnu.org.

Yes, I'm planning to do some more work on musicxml2ly, at least until it is in 
a state that it's easier for me to scan a score, export it to MusicXML and 
run musicxml2ly than to write it from scratch in lilypond.

My username at savannah is kainhofer.

Getting write access would be nice, but I also appreciate the feedback that I 
got here for my patches! 

> I am traveling the next 2 weeks, so I am won't have much time to look/
> I'm applying your patches. Could you address my comments in follow up
> patches?

Okay, will do.

> * In general, git commit messages should have the following form
>
>   1-line summary
>
>   background - typically the reason why you are doing it, or the
>   general idea behind it.

Okay, in KDE we don't have any such requirement

> Keep the 80 column limit in mind here. 

Okay, again, with KDE svn that limit is no issue.

> * You have replaced almost all dict accesses with .get() ; this is only
> desired if the default case makes sense. Sometime throwing a KeyError
> actually does make sense.
>
> For example
>
> -        (glyph, pos, c0) = self.clef_dict [self.type]
> +        (glyph, pos, c0) = self.clef_dict.get (self.type)
>
> doesn't really make sense, because the assignment will fail the default,
> None.

Ah, right, I thought I had left all [..], where an exception makes sense. Will 
revert this particular change in a later patch. This code is dead,though, 
anyway. I've redone the clef conversion code in the attached patch, so now 
almost all clefs are correctly converted from Finale 2007 to lilypond (the 
only problem I still have is the "None" key, which means that no key should 
be used. Lilypond does not seems to support this :-((( ).

> If you have to check for the default value
>
>   if key in dict:
>     ..do stuff..
>
> is clearer then
>
>   foo = dict.get(key, None)
>   if foo:
>     ...

Agreed, it's clearer, but if I need to access foo later on, the second is more 
efficient (only one lookup instead of two).

> * Also fix problem that \breathe does not accept any direction modifyer
>
> modifier

got me!

>     # return the first creator tag that has type 'editor'
> +        for i in creators:
> +            if hasattr (i, 'type') and i.type == type:
> +                return i.get_text ()
> +            else:
> +                return ''
>
> I don't understand the comment, do you mean "type" iso. editor?

This happens when you write code, then restructure and outsource some parts to 
external funcitons... The comment should rather be:
        # return the first creator tag that has the particular type

> +        if ids.get_rights ():
> +            score_information['copyright'] = ids.get_rights ()
>
> you could shorten this a little,
> removing the duplicate call of ids.get_XXX()

Done.

> +        printer.dump ('%s = "%s"' % (k, score_information[k]))
>
> this probably needs some escaping. What if there is a " in the title?

Right!

> +    for k in score_information.keys ():
>
> slightly simpler:
>
>   for (k, v) in score_information.items():
>     printer.dump ('%s = "%s"' % (k, v))

Thanks!

Cheers,
Reinhold
--

-- 
------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinhold <at> kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Till Rettig | 1 Sep 15:40 2007
Picon
Picon

Re: some more patches updating the German translation

Hi John,
sorry for the problems with my patches!

John Mandereau wrote:
git-reset is the good command to use, use it with - the name of lilypond/translation remote branch in your git repository as <head of current git> - --hard option, to also apply changes to your working tree.
Ok, did the reset, it looks promising!
However, PDF compilation fails on German manual with your patch, see comments below. I pushed fixes to lilypond/translation.
#. <at> node in ../../../Documentation/user/instrument-notation.itely #. <at> subsection in ../../../Documentation/user/instrument-notation.itely <at> <at> -1600,7 +1587,6 <at> <at> msgstr "Überblick über Textbeschriftungsbefehle" #. <at> node in ../../../Documentation/user/advanced-notation.itely #. <at> subsection in ../../../Documentation/user/advanced-notation.itely -#, fuzzy msgid "Overview of text markup list commands" msgstr "Überblick über Textbeschriftungsbefehle"
Pay attention to these slightly different titles! The identical translation you provide for different titles makes pdfetex complain. I fixed the second title as "Überblick über Textbeschriftungslistenbefehle", please provide a patch if it's not correct (it's certainly not, as I've not written in German for ages :-p).
It's quote good, but I changed it a bit to meet more the meaning that I understand.
But I see the nodes for the chapters not yet translated as being not yet polished, so
they might well change.
Iin any case, your German is much better than my French (=0). ;-)
Thank you very much for fixing the mistakes I did. I am just compiling the documentation
to see if verything goes well. Then I will send you the last patches which cover the last
changes in lilypond/translation.
There were other various <at> commands typos and oddities, fixed in 7c9ff05e82902b3357f8a2ac0354d8971539a15a and 718cc970304f6b9a3bb990259a048c06e56f4e48 (lilypond/translation). Your recent 2 patches and all fixes are also on master.
Thanks for your patience!

Greetings
Till
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Werner LEMBERG | 1 Sep 17:06 2007
Picon

Re: [PATCHES]: Converting header and lyrics with musicxml2ly

> >   1-line summary
> >
> >   background - typically the reason why you are doing it, or the
> >   general idea behind it.
> 
> Okay, in KDE we don't have any such requirement

This isn't a `requirement' per se, but it makes the appearance of the
git repository within `gitk' much nicer.

The same holds for the 80-characters-per-line limit (but this is a
good thing in general).

    Werner

Gmane