German site update

[Till Rettig]

I forward this with a new subject, since you probably didn't see it because it went to the older thread...

-------- Original Message --------

Subject:	Re: German glossary for translation
Date:	Sat, 10 Feb 2007 18:11:12 +0200
From:	Till Rettig <address@hidden>
To:	John Mandereau <address@hidden>
CC:	lilypond-devel <address@hidden>
References:	<address@hidden> <address@hidden>

Hi John,

I updated the German translation: that is the changes in site/about/automated-engraving. I didn't though touch the site/sponsor changes yet, because they have the remark of being still a draft. Then I found a typo in the README and just corrected it. Here are the two patches for those corrections. Please tell me if they do not apply cleanly, I will then try to sort it out finally.

One second thought about the essay about automated engraving: There are a lot of pictures with some kind of explanation like the one explaning the mistakes in other editions. As I looked at it these graphics are included into the files: site/automated-engraving/problem-statement.html; benchmarking.html; shubert.html; typography-features.html.
My idea was to manage them the same way as the pictures in the site/switch/howto.html file that is to draw language-specific word on the on compile time. And altogether it might be worth some thinking if we should combine the benchmarking and shubert file, because the example now given in benchmarking gives kind of poor picture about the abilities of nowaday's lilypond.

A third issue is then the generation of the big page of the essay: it is not yet generated for German. But I guess you know this anyways.

I got now translated the glossary as a starting point for the 
translation of the tutorial (using mostly the definitions from the music 
glossary), just thought that it might be interesting to put it into the 
doc sources so every possible translator for German can orientate on 
these words to make the information reliable. But how would I do this? 
Is there another git repository for the documentation? Something like 
doc/master?
    

See my related message on this list for the Git details.
  

Ok, I am not really ready with this, I mean: I didn't find all the files that will be translated then in the end. But I hope you will give some  more explanation further on. One question already here, though: how does git react when I start compiling lilypond on a git repository. Will all these files ignored or should I always compy the contents of the souces directory so some other place before I start the compilation?

There is no technical support (makefiles and buildscripts) to translate
the glossary, but if it is fully translated, this won't be hard to do.

  

I am not sure if I understand you here: I picked the file from

http://lists.gnu.org/archive/html/lilypond-user-fr/2006-12/msg00003.html

as you sent the link. It conforms quite well with the glossary, but my version now contains only english-german equivalents, so it is more straitforward for a translator. That is why I thought if it should be included into the lilypond sources as a helper file for future translators.

When you have updated the German web site, you'll be ready to start
translating the tutorial.
  

Sounds promising, though I am afraid it will take me some time... Ah yes, and how is it: is there also a script like check-translation for the docs?

Greetings
Till

From 9539f995b6ca053d3fccbd97552df2e4725f33ca Mon Sep 17 00:00:00 2001
From: Till Rettig <address@hidden>
Date: Sat, 10 Feb 2007 17:40:18 +0200
Subject: [PATCH] German site update

---
 de/about/automated-engraving/conclusion.html       |    6 +++---
 .../automated-engraving/divide-and-conquer.html    |    4 ++--
 de/about/automated-engraving/input-format.html     |    6 +++---
 .../automated-engraving/typography-features.html   |   11 ++++++-----
 4 files changed, 14 insertions(+), 13 deletions(-)

diff --git a/de/about/automated-engraving/conclusion.html 
b/de/about/automated-engraving/conclusion.html
index cb21a02..1045871 100644
--- a/de/about/automated-engraving/conclusion.html
+++ b/de/about/automated-engraving/conclusion.html
@@ -1,5 +1,5 @@
 <!--
-    Translation of GIT committish: 70dccb472f11807fd39e3194421ea1153e0b282f  
+    Translation of GIT committish: 2e1d8df9b977d454e20a3ca1c99a204de4f58bef  
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  Use
@@ -17,8 +17,8 @@ Wir konnten hier zeigen, wie guter Notensatz aussehen sollte 
und
 wie wir unser Programm gestaltet haben, damit es dieses Aussehen
 nachahmt. Wir haben uns viel M&uuml;he gegeben, um es zu programmieren.
 Dank all der Bem&uuml;hungen kann nun jeder dieses <a
-href="@address@hidden/tour.html">Programm benutzen</a>, um auch sch&ouml;nen
-Notensatz zu erhalten..
+href="@address@hidden/tour.html">Programm benutzen</a>, um selber sch&ouml;nen
+Notensatz zu erhalten.
 
 
 <p align="right">
diff --git a/de/about/automated-engraving/divide-and-conquer.html 
b/de/about/automated-engraving/divide-and-conquer.html
index ccb3f55..86fbf89 100644
--- a/de/about/automated-engraving/divide-and-conquer.html
+++ b/de/about/automated-engraving/divide-and-conquer.html
@@ -1,5 +1,5 @@
 <!--
-    Translation of GIT committish: 70dccb472f11807fd39e3194421ea1153e0b282f  
+    Translation of GIT committish: 2e1d8df9b977d454e20a3ca1c99a204de4f58bef  
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  Use
@@ -51,7 +51,7 @@ wir es in Unterprobleme teilen:
 
 Schlie&szlig;lich entsteht durch die Unterteilung ein neues Problem:
 <ol start="4">
-<li> Architectur: Wie setzt man alles wieder <b>zusammen</b>
+<li> Architektur: Wie setzt man alles wieder <b>zusammen</b>
 </ol>
 
 
diff --git a/de/about/automated-engraving/input-format.html 
b/de/about/automated-engraving/input-format.html
index a7ed8d5..860dc91 100644
--- a/de/about/automated-engraving/input-format.html
+++ b/de/about/automated-engraving/input-format.html
@@ -1,5 +1,5 @@
 <!--
-    Translation of GIT committish: e5fbb90ae8aa2d3ed7869f863a4c9813c8d8f0b2  
+    Translation of GIT committish: 2e1d8df9b977d454e20a3ca1c99a204de4f58bef  
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  Use
@@ -14,7 +14,7 @@
 <h2>Das Eingabeformat</h2>
 <p>
 Wie oben besprochen liegt dem Eingabeformat der Inhalt, also
-die Musik zu Grunde. Damit aber entsteht ein gro&szlig;es Problem:
+die Musik, zu Grunde. Damit aber entsteht ein gro&szlig;es Problem:
 Wie k&ouml;nnen wir denn definieren, was Musik eigentlich <em>ist</em>?
 Wir n&auml;hern uns der L&ouml;sung von hinten. Anstatt zu definieren,
 was Musik ist, lassen wir unser Programm als Definition gelten. Wir
@@ -24,7 +24,7 @@ kann, bleibt nur noch der reine Inhalt &uuml;brig.
 
 <p>
 Die Syntax ist gleichzeitig die Benutzerschnittstelle bei LilyPond, darum 
-ist es einfach zu schreiben, z.&thinsp;B. bedeutet
+soll sie einfach zu schreiben sein; z.&thinsp;B. bedeutet
 
 <pre>
   c'4 d'8
diff --git a/de/about/automated-engraving/typography-features.html 
b/de/about/automated-engraving/typography-features.html
index f6a42c7..2e07df0 100644
--- a/de/about/automated-engraving/typography-features.html
+++ b/de/about/automated-engraving/typography-features.html
@@ -1,5 +1,5 @@
 <!--
-    Translation of GIT committish: 70dccb472f11807fd39e3194421ea1153e0b282f  
+    Translation of GIT committish: 2e1d8df9b977d454e20a3ca1c99a204de4f58bef  
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  Use
@@ -32,7 +32,7 @@ viel kr&auml;ftiger. Das wird sofort deutlich in den 
folgenden Beispielen:
 </table>
 <p>
 
-Ein weiterer typischer Aspekt von handgravierten Noten ist das allgemeine
+Ein weiterer typischer Aspekt eines handgravierten Notenbildes ist das 
allgemeine
 Design der Zeichen. Sie haben fast nie scharfe Kanten. Das r&uuml;hrt 
 daher, dass scharfe Ecken an den Stempeln sehr schnell schartig 
 werden, wenn man sie in Metall schl&auml;gt. Diese rundliche Form
@@ -59,12 +59,13 @@ gleichm&auml;&szlig;igen Rhythmus gespielt werden. Die 
Abst&auml;nde
 sollten das wiederspiegeln. Leider l&auml;sst uns aber das Auge im
 Stich: es beachtet nicht nur den Abstand von aufeinanderfolgenden 
 Notenk&ouml;pfen, sondern auch den ihrer H&auml;lse. Also m&uuml;ssen
-Noten, deren H&auml;lse oben/unten gerichtet sind, weiter
+Noten, deren H&auml;lse in direkter Folge zuerst nach oben und dann nach unten 
ausgerichtet
+sind, weiter
 auseinander gezogen werden, w&auml;hrend die unten/oben-Folge engere
-Abst&auml;nde fordert, und das alles in Abh&auml;ngigkeit von der 
+Abst&auml;nde fordert; und das alles auch noch in Abh&auml;ngigkeit von der 
 vertikalen Position der Noten. Das obere Beispiel ist mit dieser 
 Korrektur gesetzt, das unter ohne. In letzterem Fall bilden sich f&uuml;r das 
Auge
-bei unten/oben-Folgen Notenhaufen.
+bei unten/oben-Folgen Notenklumpen mit schmalen Abst&auml;nden zwischen den 
Notenh&auml;lsen.
 
 <h2>Hilfslinien</h2>
 
-- 
1.5.0.rc1.gb60d

From dbe7dd72bc6fc3e71d4bcadf5732bf1950f78628 Mon Sep 17 00:00:00 2001
From: Till Rettig <address@hidden>
Date: Sat, 10 Feb 2007 17:43:18 +0200
Subject: [PATCH] typo in README

---
 README |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/README b/README
index 4b3f958..0a9eee9 100644
--- a/README
+++ b/README
@@ -191,7 +191,7 @@ revision of the translation.  To check a single page, run
 * UPDATE A TRANSLATION
 
 Check state of the translation using the method described above.  For
-each file diff shown in check-translation ouput, open the
+each file diff shown in check-translation output, open the
 corresponding translated file in a text editor and update the
 translation according to the diff.  The translation hints above still
 apply.
-- 
1.5.0.rc1.gb60d