Hi,
adding to this old thread:
Was there already discussion on translating also the NEWS part of the
documentation? It might not be really used by many people when 2.12 has
become normality but for the moment it might be interesting since it
also has a direct link from the news entry on lilyp
John Mandereau schrieb:
Hi Till!
Till Rettig a écrit :
Was there already discussion on translating also the NEWS part of the
documentation? It might not be really used by many people when 2.12
has become normality but for the moment it might be interesting since
it also has a direct link from
Francisco Vila schrieb:
2009/2/14 Frédéric Bron :
This link has been broken for a few days:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-big-page
OK I am sorry, I did not read the message of Firefox. It says there is
an encoding problem:
In French:
"Erreur d'encodage d
Francisco Vila schrieb:
2009/5/18 John Mandereau :
Francisco Vila a écrit :
Permission to bulk fix it into the last version, in all languages.
...I'm doing my best to update the script and fix committishes
with regexp substitution before next week.
Well, I was really
Hi John,
somehow the section names don't get translated in the pdfs that are
produced by "make doc". I can see they are translated on the compiled
version on the web, but why don't I get them? :(
Another question is: can I update snippets only for one language? and
how to do a po-update (is
Hi John,
I just realized that on the web page there is now an addition for the
windos download entry about lilypond being a command line programm and
so on. This is nowhere translated. I guess it should be in the po.s. Do
we have to add it manually there?
Greetings
Till
John Mandereau schrieb:
Till Rettig a écrit :
This translation interface is getting more and more tricky it seems
(I mean technically)
Speaking of, my next task on the translation infrastructure is
simplyfing it a little, i.e. translating node names and titles in
Texinfo sources, which will
John Mandereau schrieb:
Francisco Vila a écrit :
Well, it seems that we can ignore all the diff lines that do not touch
texidoc= or doctitle= fields on files in lsr/ ; so it's not that bad.
Is this right?
It is. This will remain as much cumbersome until LSR snippets (and the
associated data
Carl D. Sorensen schrieb:
On 5/22/09 1:13 PM, "Till Rettig" wrote:
Hi John,
I just realized that on the web page there is now an addition for the
windos download entry about lilypond being a command line programm and
so on. This is nowhere translated. I guess it should be in th
Carl D. Sorensen schrieb:
On 5/22/09 2:55 PM, "John Mandereau" wrote:
Carl D. Sorensen a écrit :
I would recommend that it either be left in english, or translated manually
for now. That is a temporary hack until the great website redesign, which
will be accomplished starting in two
Hi John,
first time I consulted the contributor's guide. It's now much easier to
read than the old text file. Some things made me stumbel upon, though:
in 3.7.2 Documentation translation details you have different starting
points for the individual files: mostly you start from LL-directory, bu
Jan Nieuwenhuizen wrote:
Daniel Tonda Castillo <[EMAIL PROTECTED]> writes:
For the priority 3 files, the TRANSLATION document show these:
3 sponsor/
3 about/automated-engraving/
Then the whole directory is meant. We just found that something went
wrong with catogorisation of sponsor, a
Yes, I wrote a short message, but I don't now get the git to work out
this patch, forgot how to update an already existing file, so I will
send it this time directly. I just addes the message to the
site/news.html file, hope that was right. Here ist the message also alone:
lilypond.org auf d
Jan Nieuwenhuizen wrote:
What is it exactly that you do not understand?
git pull <...> web/master
# edit site/news.ihtml
git commit -a -m 'Add news entry'
git format-patch HEAD^
Yes, the point is: after editing some file and commiting is (actually I
never used the -a option, w
So now I have this strange case. I did all the commands I said in my
last email, that is
git pull ... web/master
for two files run
git add
and
for then changed a couple of files. Into each file I inserted the string
I get with
git-rev-parse HEAD | head -1
on top.
Then I commited them:
git commi
Ok, I checked again the wiki pages and made a new version of my local
git repository, and finally I got the right commitish and could add
changes! Here is the patch!
Till
From 86c0ec8106a4fb525c95e6c24ff173952f76e823 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
the patch form and another time the file itself so it is more easy
to read.
Thank you!
Till
From 0f876dc707a47267b40da3b9453c8f6d2ba29973 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
Date: Mon, 1 Jan 2007 19:41:57 +0200
Subject: [PATCH] README.de added
---
README.de
I am sorry, I just applied some changes and realized that I had sent a bad
version of a file. The update is now in the next patch.
Till
From 28deb2d84d43a3fc1fae16c5292d38d33cda2bb3 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
Date: Mon, 1 Jan 2007 20:28:01
Jan Nieuwenhuizen wrote:
Till Rettig <[EMAIL PROTECTED]> writes:
> Here is the patch!
This imported cleanly. Thanks. John Mandereau, our new Translation
Meister will be taking over from me.
Ok, will remember this. In fact I sent another patch a couple of hours
later on t
row so in the end you would get clean apllyable
patches.
Greetings
Till
Till Rettig escreveu:
Hello,
because it caused me some difficulties to understand how the git
conventions for commting patches worked I wrote a small helper file so
far called README.de in the web/ directory. Could
I will comment somehwo more differented later on, now just some short thoughts.
maybe the best is i would then just read the updated file (as you suggested)
and make my comments.
Original-Nachricht
Datum: Wed, 03 Jan 2007 00:35:25 +0100
Von: John Mandereau <[EMAIL PROTECTED]>
John Mandereau wrote:
No, "git checkout -b myweb web/master" is supposed to do this job.
Now the next item:
Are you sure that you actually use Git 1.4.4.1 or newer? What does
git --version
says?
Now I understand all the stuff! Of course I thought that I would use
John Mandereau wrote:
All translation hints other than support for a particular user should be
in English, so that all translators can share it.
Yes, that is totally true
Please read the revised README and translate the parts of README.de that
brings something interesting in addition to th
apply the last patch (0003-replace-of-testimonials-txt). I will
send you all of them though.
Please ignore the others if that is ok!
Greetings Till
From 86c0ec8106a4fb525c95e6c24ff173952f76e823 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED](none)>
Date: Mon, 1 Jan 2007 19
ust
stop installing this programm...
Or is there something I miss?
Greetings
Till
From dff5d173940a60b2385e8ec68d9a8742c560eddc Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Thu, 4 Jan 2007 21:02:35 +0200
Subject: [PATCH] adding correct German windows.html
---
de/install/
>
> cygwin.html and macos.html have not been updated for a while; macos.html
> is clearly outdated, but cygwin.html is still valuable (Cygwin provides
> 2.10.7), so it should't be renamed to windows.html. You're right it
> should be clearly mentioned there are 2 LilyPond flavours on Windows
> (n
John, this looks now good, there are now two versions of the same file in the
German directory, one is calles windows.html and the other cygwin.html. So you
can safely discard one of them. I was aware that the windows binary is working,
I was just really wondering what is the stuff about this c
John Mandereau wrote:
http://lilypond.org/web/about/features
yes, well, actually, I also want that page to have a
more appealing look.
Agreed. The features list is too long; IMHO it'd be better to illustrate
these features by a few LilyPond scores, one for each notation domain
Hi John,
I like the new version of the install/getting-started.html -- I hope I
will have time on the weekend to update the German translation. Actually
it seems I won't be able to do the check-translation as often as you
mentioned it, but at least once a week should be possible.
But then I di
Of course. It is certainly more consistent to translate all comments,
and we could add a small notice saying
//Original comments are in English; you can read them in the English
version of this page (scroll to the bottom to find the link).//
Do translators agree on this?
sounds like a go
A bit off-topic:
Well, I don't know anything about python, but have to say that the
current script doesnt't work for me or I didn't understand it so far.
That is, I just did the check-translation and it showed fatal error
about some git comment numbers. So I changed *all* commitishes that were
John Mandereau wrote:
The only common thing between lilypond.org sources and LilyPond sources
is the git.sv.gnu.org repository. It's better to create another local
repository for the LilyPond sources, so you can work simultaneously on
the site and on the program sources without switching branc
John Mandereau wrote:
What command exactly do you use to generate patches? The following
should make clean patches, as long as you committed all your changes and
pulled:
git-format-patch web/master..myweb
Yes, I used this without the ..myweb part.
I see there is some differences:
Hei,
I was wondering if I could start some contribution to the medieval
notation support via redesigning the fonts that in my opinion don't look
very good. Especially referring to the mensural notehead style (I think
the petrucci looks quite fine, but neomensural and mensural heads are
lot too sm
John Mandereau wrote:
Le samedi 13 janvier 2007 à 16:45 +0200, Till Rettig a écrit :
A bit off-topic:
Well, I don't know anything about python, but have to say that the
current script doesnt't work for me or I didn't understand it so far.
If you find something unclea
John Mandereau wrote:
The tutorial from the user manual, but you should wait until I've
documented documentation translation. As I'm very busy, it may take a
week. In the meantime, you could read and check lilypond.org
translation for possible typos and translation improvements with
Francisco
Werner LEMBERG wrote:
I was wondering if I could start some contribution to the medieval
notation support via redesigning the fonts that in my opinion don't
look very good. [...]
I can't give any design recommendation due to lack of knowledge.
Whatever you do, *please* follow the guidel
Karl Hammar wrote:
Great!
Is your goal, like Guthenburg, to make a few e's etc, to simulate the
variability of handwriting also?
Would that be possible within lilypond?
Well, I don't know yet -- it would definitely be userfull for the
samples taken from handwritten fonts. But what rules ap
Juergen Reuter wrote:
Agreed. I have been mainly concentrating on Vaticana style and
Petrucci style. As Werner already indicated, the ancient font was
written before Lily used fontforge et al. Therefore, the glyphs do
not follow all prerequisites that Lily glyphs are nowadays supposed to
Hei,
I am slowly evolving in my ideas and trials on the "ancient" fonts for
lilypond. So far I have a couple of good scans from which I would like
to take the shapes. But how is the best to get them into metafont? I
found something about mfpic (probably not good in this case), fig2mf
(sounds
Juergen Reuter wrote:
Hi, Till!
My personal experience is that you have to fine tune the glyphs
anyway; hence, determining just a few coordinates should suffice (this
can be easily done manually if you have a really big printout of the
scan).
Do you mean by using xfig or inkscape or by def
Han-Wen Nienhuys wrote:
I simply used pencil and paper, drawing by hand, and guessing control
points. Then, a lot of tweaking makes the glyph look OK.
Although this is harder at first, it makes a more logical to design
a true MetaFont, one whose parameters (eg. thickness) can be varied
contin
Hi John,
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 wo
there also a script like check-translation for
the docs?
Greetings
Till
From 9539f995b6ca053d3fccbd97552df2e4725f33ca Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sat, 10 Feb 2007 17:40:18 +0200
Subject: [PATCH] German site update
---
de/about/automated-engravi
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 <[EMAIL PROTECTED]>
T
John Mandereau wrote:
You needn't
send an email twice; if I don't reply quickly, just bug me with a
private email.
Ok, I know this now.
There was a nitpick with the committish in
about/engraving/input-format.html: it looks like you had made the patch
with a revision different from the w
3a16e0a83c7 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Tue, 13 Feb 2007 17:01:08 +0200
Subject: [PATCH] German Sponsor/options.html update
---
de/sponsor/options.html | 57 ++-
1 files changed, 56 insertions(+), 1 deletion
Well, I think the most promising project at the moment is canorus at
http://canorus.berlios.de/ which is not a directly what you are looking
for, but I think it shows much better the structure that a frontend to
the lilypond generator should have: not so much one big block of
software but modul
Hi John,
I will now slowly start the translation of the documentation. I got
quite most things clear from your TRANSLATION file, many thanks to you
for that! One thing is with the first file I started with:
lilypond.tely. Here is a lot of nodes that are not mentioned in the
nodenames hat shou
Hi Francisco,
I had the same problem some days ago. Was a bit confused about this
version problem, because there is no mention of the 1.8.2 version on the
web site. It might be that they have a newer version on cvs, but I don't
know to get it from there.
So I downloaded the patch from the lily
Hi John,
here a small patch for German translation.
I'm on my way with documentation translation, supposedly next week I
will send the first package...
Greetings
Till
>From c38a1e7c3e831dbd031f3625718fe915508ef26b Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Greetings
Till
>From e7acfd14ab1326ba6ed76342ad8c791b1dc77728 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sun, 11 Mar 2007 17:10:57 +0200
Subject: [PATCH] typos2 in German webpage
---
.../automated-engraving/typography-features.html |4 ++--
1 files c
Found another typo. ;-)
>From f0941e562e9b0235865e441b5038af2dd405fe56 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sun, 11 Mar 2007 22:24:37 +0200
Subject: [PATCH] third typo patch German webpage
---
.../automated-engraving/implementing-notation.html |
sorry, that they come all in seperate emails...
Till
>From 08495978402572da49bf90c9fe61e958aa54d4f1 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sun, 11 Mar 2007 22:37:05 +0200
Subject: [PATCH] fourth typo German website
---
.../automated-engraving/problem-state
still some more updates...
>From b9bae863f69ccea3544112688a45ce5b452ce65d Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Fri, 16 Mar 2007 18:05:24 +0200
Subject: [PATCH] German update and typos
---
de/about/automated-engraving/input-format.html |6 +++---
Hi John,
I think at the weekend I will deliver my first part of the translation.
Still there are some questions. Following the mailing lists I read that
you want to make a translation branch. Does this change my working? Will
I have to commit to master or to the other branch?
Another question
John Mandereau wrote:
Le jeudi 22 mars 2007 à 19:25 +0200, Till Rettig a écrit :
I suppose that by committing to master, you mean commmitting to your
local master branch, as you don't have push access to git.
yes, I meant that one
You can go
on working on master (or mymaste
with
lilypond/translation oder do I leave the refs/heads also away?
You don't write anything about pulling. So far I pulled with only
master:master, as I wrote. Do I now need this refs/heads... path or what
does this actually mean?
Greetings
John Mandereau wrote:
Le vendredi 23 mars 2007 à 19:00
#: ../../buildscripts/langdefs.py:36
msgid "Spanish"
-msgstr ""
+msgstr "Spanisch"
#: ../../buildscripts/langdefs.py:37
msgid "German"
-msgstr ""
+msgstr "Deutsch"
#. @node in ../../../Documentation/user/lilypond.
Hi John,
I just checked it again: the quotes for German are not yet adjusted like
the french ones. I thought this would happen automatically kind of with
"babel", but I don't know much about texinfo, so it doesn't seem to be
so much like latex. Anyways, I now suppose the changes are managed by
Graham Percival wrote:
I can also try to check it out myself if you have some hints: where
would I find those commands for texinfo?
The @q and @qq macros are defined in macros.itexi. I'm not certain
that I understand the question, though, so this might be the answer
you're looking for.
a
m April 1st 11 am
to April 8th.
Cheers,
Till
>From 3240d94b8c809960dac5f5b2ad00935af04f1428 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Thu, 29 Mar 2007 21:50:18 +0300
Subject: [PATCH] German updates and quotation marks
---
Documentation/de/user/macros.itexi |
-Benutzerhandbuchs
sind auf deutsch übersetzt — Version
2.10, Version
2.11.
There are also some minor changes to the webpage I would like to apply,
see the attached patch.
Thank you!
Till
>From 75ff4dac3fb1a5e73515e984b593adebeac74938 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PRO
l the work. It is fun!
Till
>From 22adc8515be6da5c3cca664b2a37988b67b504e6 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sat, 31 Mar 2007 17:53:31 +0300
Subject: [PATCH] update lilypond.tely
---
Documentation/de/user/lilypond.tely | 27 --
This example looks nice. I would just mention that for the pages which
have much text on them I would like some kind of system that would scale
the linewidth according to the resolution of the screen, assuming that
users would use mainly a know sized font in their browsers. It is
annoying to re
John Mandereau wrote:
Sorry, the patch doesn't apply. Could you please make a new one?
I tried now my luck with git... see if this patch is better.
Greetings
Till
>From 6cf63eee426ea880a09d8c7509c53b4f71f72bdf Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Hi,
just found a bug in the po/de.po on web/master, here is the fixing patch.
Till
>From c3215ba0e0a1ee0411178fb22eb2f4f9c056c967 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Fri, 13 Apr 2007 19:09:59 +0300
Subject: [PATCH] update po/de.po
---
po/de.po |
Hi John,
another correction in de/user/working.itely.
Till
>From 56f6158f30116993f4b81c4ff75ce5b05ac440ca Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Fri, 13 Apr 2007 19:14:33 +0300
Subject: [PATCH] update to de/user/working.itely
---
Documentatio
Hi,
I tried for some hours to change a picture
(site/images/naive-notation.png) from the website
(site/about/automated-engraving/...) into an svg image and then let it
be translated the same way as those pictures of the switch/howto.html. I
did the following:
creating the notes with lilypon
Graham Percival wrote:
Till Rettig wrote:
Then I removed naive-notation.png in the directory site/images and
created naive-notation.svg in the directory site/graphics
I don't recommend this; svg images at least don't work in firefox on
OSX. I'd be pleasantly surprised if t
John Mandereau wrote:
Le mardi 17 avril 2007 à 18:56 -0400, Han-Wen Nienhuys a écrit :
2007/4/17, John Mandereau <[EMAIL PROTECTED]>:
Han-Wen, do you find the (svg) sources of the files so the relevant
pngs can be replaced by svgs?
Certainly; however, we need to be careful,
I didn't have time to yet write any bug report on that but some piano
notes I wrote basing on the template have huge distances between the
stems. It seems that the additional "empty" staff for the dynamics is
just taking up much too much space. This is somehow also visible in the
template examp
Hi translators!
While translating basic-notation.itely I noticed that there are some
shortcomings of the current system: Some reference commands cannot be
translated since they refer to specific places, but they won't get
translated via LANG.po either. Especially I noticed @internalsref . I
d
Joe Neeman wrote:
There are some hacks in the template that rely on a fixed distance between
staves. I've removed those. Since it might be a while before they show up on
the web pages, the fixes are to replace
\override DynamicText #'extra-offset = #'(0 . 2.5)
\override Hairpin #'
John Mandereau wrote:
Message transféré
De: Han-Wen Nienhuys <[EMAIL PROTECTED]>
Répondre à: [EMAIL PROTECTED]
À: John Mandereau <[EMAIL PROTECTED]>
Sujet: Re: translating the pics in the engraving essay
Date: Sun, 22 Apr 2007 12:06:15 -0400
2007/4/22, John Mandereau <[EMAIL
Mats Bengtsson wrote:
Quoting Till Rettig <[EMAIL PROTECTED]>:
Joe Neeman wrote:
There are some hacks in the template that rely on a fixed distance
between staves. I've removed those. Since it might be a while before
they show up on the web pages, the fixes are
Should it be consired a bug that while compiling lilypond I get failures
if some Century Schoolbook files (which are not type1) are in the path?
I had otf files in my local .fonts directory (those ones created by
lilypond) and from canorus some ttf files in the /usr/share/fonts.
Compiling stoppe
Hi,
I investigated a bit, and got some interesting results. Compiling the
Bach didn't bring anything new, we can take the new version and it is
maybe a bit better than the old one. My actual Version is 2.11.22.
But with the Schubert I really did have some problems. I updated the
file from git
Francisco Vila wrote:
Hello. Googling does not help when searching by "windows external lilypond ..."
because these are so different subjects.
I've experienced a (bug?) problem when trying to process .ly files directly
from external USB units on Windows. Lily refuses to process them if they
a bit
uncomfortable with html. I could also try to check it out myself if you
have some idea how to make it in an easy way. Anyways, the text should
be ok, since it is from Debian.
Greetings
Till
>From 2e17eb1538ae78622baa4fc3134ea1c0153e8d1c Mon Sep 17 00:00:00 2001
From: Till Rettig
know if they apply now because you have applied the first patch
already. Git is still some kind of secret to me, so if nothing works I
will delete everything and build the git repository on my computer again.
Greetings
till
John Mandereau wrote:
Le lundi 28 mai 2007 à 21:34 +0300, Till Ret
John Mandereau wrote:
0001 doesn't apply, and I haven't tried 0002.
yes that's what I was afraid of.
If you want to see yourself what's wrong, it's a good Git exercise:
checkout a branch from current git.sv.gnu.org web/master (git-fetch the
remote branch then use git-checkout to create a n
right... I will just have to find time to really read
all the stuff in order to understand the basics of what this "stupid"
program is really doing. ;-)
Greetings
Till
>From 55fa4e73cd275fd039d1ce43dfe12d2195db6f15 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Hi John,
here a new update for the part of the German translation that is already
updated.
Thanks
Till
>From 2c3ae137033d415479bb672adfaf7efd7988d665 Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sun, 10 Jun 2007 13:08:33 +0300
Subject: [PATCH] Updates for t
Hi
I found that in the German version of the lilypond binary translation
there are some untranslated entries. How is the way here with
translating? As far as I can understand they have been initially
translated by a translation project (from sourceforge?). But version
number is 2.9 and last r
iting something or that kind of thing. After that I cannot get
the repository clean again. With the translation repository I was just
anxious not to do any mistakes, so that's why this is still clean.
Greetings
Till
John Mandereau wrote:
Le dimanche 10 juin 2007 à 12:57 +0300, Till Rett
Hello everybody,
I just tried to compile the documentation from git master branch. First
it gave an error about a missing epsf.tex file that collated-files.tely
in input/manual/out-www needed. I found that my version of texlive had
only installed xepsf.tex. So I linked it to the name epsf.tex
Hi,
another problem is that check-translation script is not working for me.
It throws following message:
[EMAIL PROTECTED]:~/Documents/Lilypond/compile/Documentation$ make ISOLANG=de
check-translation
find de/user/ -maxdepth 1 -name '*.*te??' | xargs /usr/bin/python
../buildscripts/check_tra
Greetings
Till
>From a9a9fc1bc956e22d04a3a0b655ef84f31b59989a Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sun, 19 Aug 2007 17:19:45 +0300
Subject: [PATCH] Changes to de/index.html.in updated
---
Documentation/de/index.html.in | 114 +++-
1 files changed, 1
Valentin Villenave wrote:
a few days ago, I posted a link to
http://lilypond.org/web/about/automated-engraving/benchmarking.html
which made me realize that the static pages visitors are most likely
to visit when then don't know LilyPond, are realized with very old
versions of Lily: 1.4, 1.8 --
ay on instrument-notation, hoping to get it ready
until the end of october, so it would make it into the 2.12 release.
Greetings,
Till
>From 4322e268924afb47f4932029209d3717c415739d Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Tue, 28 Aug 2007 20:35:15 +0300
Subject: [
John Mandereau wrote:
Le samedi 25 août 2007 à 20:49 -0300, Han-Wen Nienhuys a écrit :
Of course, if a translation is almost finished, it would be cool to
add the last bits, so we can announce "Manual translated in XX", but
...but we may not achieve this before some months: the user
Hi Henrik,
this sounds really good! At the moment it is only me translating and I
was quite busy with other things lately so the process is somewhat
slowed down. That to say I am on my way on chapter 7, everything
afterwards is not touched yet. I have also elaborated a glossary with
German-En
John Mandereau wrote:
Le mardi 28 août 2007 à 22:52 +0300, Till Rettig a écrit :
I don't know all the
reasons, but there is clearly one: your patches don't include all the
changes you made to German translations, for example adding
"documentlanguage: de" to working.ite
Hi,
I think we should change the version number in the tutorial text for
2.11 from 2.10.1 also to 2.11.23 as done in the example.
It is in line 1284.
After all this manual is for 2.11.x isn't it?
Greetings
Till
___
lilypond-devel mailing list
lilyp
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-notati
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
- --hard option, to also apply changes to your working tree.
Ok, did the reset, it looks p
u
anyway, but I guess we should first find out about the mistake before
applying them. :-(
Greetings
Till
>From b42c9d915e0fa1c4173f174a492bca1293c2918f Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sat, 1 Sep 2007 16:21:37 +0300
Subject: [PATCH] Updates to German tra
s the correct
way to change that ( I guess in the macros.itely file)?
So far relieved that the problems seem to be solved :-)
Greetings
Till
>From b42c9d915e0fa1c4173f174a492bca1293c2918f Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Sat, 1 Sep 2007 16:21:37 +030
John Mandereau wrote:
Of course, the POs haven't been updated. As exaplained in TRANSLATION,
all translators who don't have Git push access should not run po-update
without having pulled very recently and immediately sending me a patch
for Documentation/po, otherwise they may encounter confli
1 - 100 of 250 matches
Mail list logo
