Re: GUILE-with-rational-bugfix

[Jan Nieuwenhuizen]

Rune Zedeler <[EMAIL PROTECTED]> writes:

> Where can the famous patch be found?

In GUB, pull from http://lilypond/vc/gub.darcs, or

http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch

> (Unable to compile latest guile-cvs).

(You may want to report that too)
Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


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

Re: Singing support for LilyPond

[Milan Zamazal]

> "HN" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:

HN> I notice that there are lots of functions to inspect music data
HN> structures. It would be best if they were in a separate
HN> file. Then, over time we can migrate them to the lilypond 'core'

HN> Also, would it be possible to define it as a module?  Right now,
HN> it imports in a .ly file, which already is a too-large
HN> namespace.

I'll try to do it both.

HN> see input/simple-song.ly

OK.

HN> There is a python midi parser in lilypond itself. 

Great, this is all what I need.  Then there should be no problem in
rewriting lilymidi too.

Regards,

Milan Zamazal




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

Re: German translation help file

[Han-Wen Nienhuys]

John Mandereau escreveu:
 
> Speaking of, isn't scripts/rev-to-commit.py supposed to update the
> committishes automagically? It would need an update to work, though.

no, rev-to-commit was a   hack to transition from CVS to git.

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: GUILE-with-rational-bugfix

[Han-Wen Nienhuys]

Rune Zedeler escreveu:
> Where can the famous patch be found?
> (Unable to compile latest guile-cvs).

see install.txt

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: Singing support for LilyPond

[Milan Zamazal]

> "HN" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:

HN> also, on the larger scale, I don't fully understand the need for
HN> the patch.  Why isn't possible to have script/program that sings
HN> any MIDI file?  LilyPond already exports its lyrics to MIDI.  I
HN> imagine that the only work necessary is to glue together
HN> syllables to words.

At the time we started the project LilyPond didn't export lyrics to
MIDI.  Even now it may not be possible to synthesize songs from MIDI
without additional support from LilyPond.  For instance, AFAIK there is
no information about the track corresponding to a given piece of lyrics
or about rests in lyrics.  Gluing syllables to words without additional
information would be also difficult for languages that require that to
pronounce the lyrics correctly (such as English).

But if information in the MIDI file was complete, it should be possible
(and probably easier) to use the MIDI file for song synthesis.  It would
be nice if someone wrote support for this.

Regards,

Milan Zamazal




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

Re: more skyline ideas

[Han-Wen Nienhuys]

Joe Neeman escreveu:
> On 1/3/07, *Han-Wen Nienhuys* <[EMAIL PROTECTED]
> > wrote:
> 
> 
> Just a quick idea: how about adapting the skyline procedures to
> also put crude outlines of beams and slurs in the staff outline?
> With a bit of luck, we could use that to scrap the
> outside_slur_callback.
> 
> 
> If we did a bezier -> bunch of straight lines conversion then we could
> certainly make skylines from the results. But in order to use the staff
> outlines to scrap outside_slur_callback, we would need to assume that
> all the outside-slur grobs belong outside the staff as well as outside
> the slur. This is certainly true for things like TextScript but is it
> true for all articulations?

No, but I think there is nothing that is always inside a beam, for example.
Furthermore, depending on the value of avoid-slur, we could also set
outside-staff-priority.

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: German translation help file

[till Rettig]

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]>
An: Johannes Schindelin <[EMAIL PROTECTED]>
Betreff: Re: German translation help file


> 
> 
> > I'd rather bite the bullet and say
> > 
> > $ git clone -n git://git.sv.gnu.org/lilypond.git
> > $ git checkout -b myweb web/master
> > 
> > This does a little too much, but it is easier than
> > 
> > $ mkdir lilypond
> > $ cd lilypond
> > $ git init-db
> > $ git fetch git://git.sv.gnu.org/lilypond.git web/master:web/master
> > $ git checkout -b myweb web/master
> 
> No, I prefer the cleaner way (and kept them in the revised README), even
> if the bunch of commands may scare newbies; they just need to
> copy'n'paste the commands, so what's the problem?
> 
> 
the point was that I didn't yet know about checkout -- with clone i got a clone 
of the sources, but not of the git as I was using it before, I mean with clone 
I didn't get the web/site and web/de and so on directories. With cogito it 
worked immedeately. but guess the new commands will do their jobs.

> 
> > > Dabei werden einige Dateien erstellt, u.A. auch die Datei, die den
> Namen 
> > > hat, mit dem man git commit ausgeführt hat. Diese Datei wird dann
> per 
> > > E-Mail an lilypond-devel oder lilypond-user eingeschickt.
> > 
> > You should rather mention the commit in the email, but you don't need to
> > write down all forty characters; 8 should be sufficient.
> 
> I always copy'n'paste commit numbers with mouse, so copying 8 or 10 or
> 40 characters is almost the same effort. But in this case, the commit
> numbers are useless, as they may be not the same as those of commits
> made by the git pusher (that's me).
Yes, with "Name" I meant the message you give while commiting, that's how I 
understand now the naming principle while making patches.

> 
> Johannes, thank you very much for all Git support you provided; you
> should be credited in README ;-)
> 
Very good idea!

> Till, I think you needn't bother translating README.de; do it only if it
> seems essential to you.
> 
No, you are quite right, Han-Wen's point was also that the translator anyway 
would understand English. It was just that I didn't understand the README...

Greetings
Till
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


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

Re: GIT errors?

[John Mandereau]

Le mercredi 03 janvier 2007 à 00:10 -0600, Daniel Tonda Castillo a
écrit :
> After finishing the priority 3 files which already have been sent, I 
> tried to do a pull to merge everything and get the newest web site.
> 
> Locally there were no errors when committing, this seems to have 
> happened after putting a different committish after the first commit.
> 
> After a bunch of errors concerning merge, I thought to start over again 
> in a new directory, just to keep the original files I translated intact.
> 
> So i went to the savanah place listed on the wiki at: 
> http://lilypondwiki.tuxfamily.org/index.php?title=Translations_HOWTO to 
> start translating and get a fresh source. I got too many errors and gave 
> up.
> 
> Here's a recap of what went on:
> =
> Following instructions here:
> 
> http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=README;hb=web/master
> 
> $ git fetch git://git.sv.gnu.org/lilypond.git/ web/master:web/master
> 
> I do a ls -a and all I get is:
> 
> $ .
> $ ..
> $ .git
> 
> Shouldn't something live here besides .git?

No, "git checkout -b myweb web/master" is supposed to do this job.

> Now the next item:
> 
> 
> $ git checkout -b myweb web/master
> fatal: ambiguous argument 'HEAD': unknown revision or path not in the 
> working tree.
> Use '--' to separate paths from revisions
> fatal: Not a valid object name HEAD
> 
> 
> $ git log
> fatal: bad default revision 'HEAD'
> 
> So I'm stopping all git stuff because the instructions seem to be incorrect.
> 

Are you sure that you actually use Git 1.4.4.1 or newer? What does

git --version

says?


I see no other reason for saying instructions are incorrect: I have
actually tested these instructions under GNU/Linux, with Git 1.4.4.2.
Do a Git expert knows why this doesn't work?

Darn, at second thought, Cogito seems to be easier to use, despite
limited portability :-/ If there is no other clean way to get you
started, you may simply fal back to Cogito...

-- 
John Mandereau <[EMAIL PROTECTED]>



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

git pushing: do not push origin

[Han-Wen Nienhuys]

Hello, 

it seems that sometimes people push their "origin" branch 
to savannah. Can you double check that you are not doing this? 

FWIW, I use

  git push sav

with .git/config

  [remote "sav"]
url = ssh+git://[EMAIL PROTECTED]/srv/git/lilypond.git
push = master:refs/heads/master


-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: Priority 3 Translation spanish, was: Priority 2 Translation of web site to spanish

[John Mandereau]

Daniel Tonda Castillo wrote:
> I get a lot of merge errors, after the git-pull:
> 
> git-rev-parse web/master
> 745ee84ea5b583686e53dc2628e5067492997773
> [EMAIL PROTECTED]: lilypond]$ git pull 
> git://git.sv.gnu.org/lilypond.git/ web/master:web/master
> Trying really trivial in-index merge...
> es/sponsor/index.html: needs merge
> es/sponsor/options.html: needs merge
> es/switch/howto.html: needs merge
> fatal: you need to resolve your current index first
> Nope.
> Merging HEAD with 745ee84ea5b583686e53dc2628e5067492997773
> Merging:
> afcbb4ac3dc6a31f371182da9c0b47cd2ca3b68f message
> 745ee84ea5b583686e53dc2628e5067492997773 Resolving conflicts with 
> [EMAIL PROTECTED]:/srv/git/lilypond.git#web/master
> found 1 common ancestor(s):
> ac5da2c7e90f10ce8a680b275d1e33b10462c4ea Merge branch 'web/master' of 
> git://git.sv.gnu.org/lilypond into web/master
> git-read-tree: fatal: you need to resolve your current index first
>  
> No merge strategy handled the merge.
> 
> git-rev-list shows one thing, and git-rev-parse another:
> 
> git-rev-list HEAD | head -1
> afcbb4ac3dc6a31f371182da9c0b47cd2ca3b68f
> 
> 
> git-rev-parse web/master
> 745ee84ea5b583686e53dc2628e5067492997773
> 
> Which would be the best way to handle this?
> 
> Should I just start over?

Did you have any uncommitted local changes before merging? i.e. did
"git status" complained about "Changed but not updated" files?

If not, that's already a good thing. Then, for each file git-pull
reported a conflict about, open it in a text editor, go to the conflict
zones (marked with <<<, === and >>>), merge the 2 versions manually,
junk any conflict mark and save the file, then run "git update-index" on
this file. After all that, commit and the merge should be complete.

However, it seems according to git-pull output that you haven't
committed files in es/sponsor/; you should add them or run
git-update-index on them before resolving other conflicts.

Try to report the result of your experiments. It might work better than
restarting from scratch.

Cheers
-- 
John Mandereau <[EMAIL PROTECTED]>



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

\new Voice no longer automatic?

[Graham Percival]

I think I missed something... my understanding was that contexts were 
created automatically as needed.  In other words,

{ c'4 }

automatically expanded to
\score{
  \new Staff {
\new Voice {
  c'4
}
  }
}

However, in bug 176 (below), a progerror went away by replacing a \new 
Staff with \new Voice.  What's happening?


\new Staff {
  \override Score.SpacingSpanner #'strict-note-spacing = ##t
  \afterGrace c'4 {c'32 c'32 }
  c'4
}


Cheers,
- Graham


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

/index.es.html has funny titles?

[Jan Nieuwenhuizen]

Hi Daniel,

Congratulations on finishing the Spanish site, we now have 4 complete
translations!

You're probably working on this (saw your git efforts), but to a
non-spanish speaker as myself this looks a bit funny
lilypond.org/web/index.es.html (divider lines by me)

   Sumérjase en ...  de LilyPond
   ---
   la Etiqueta   de la impresión de música

Wher the English site has:

   Dive into ...   |Ms. Manners
   the LilyPond|of Music Printing
  
It seems that the titles of the two columns are printed over both
columns?

Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


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

Re: \new Voice no longer automatic?

[Han-Wen Nienhuys]

Graham Percival escreveu:
> I think I missed something... my understanding was that contexts were
> created automatically as needed.  In other words,
> { c'4 }
> 
> automatically expanded to
> \score{
>   \new Staff {
> \new Voice {
>   c'4
> }
>   }
> }

no, it doesn't work like that. The c4 cause the voice to appear.

> However, in bug 176 (below), a progerror went away by replacing a \new
> Staff with \new Voice.  What's happening?
> 
> \new Staff {
>   \override Score.SpacingSpanner #'strict-note-spacing = ##t
>   \afterGrace c'4 {c'32 c'32 }
>   c'4
> }

\override Score doesn't instantiate a new Voice, neither does << >>

\aftergrace expands to 

  << { skip 2nd-arg }
 1st-arg >> 

result: 2nd arg ends up in a different Voice as 1st-arg

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

point-and-click.itely

[John Mandereau]

Hi Graham,

I'm currently adding

"""
@ignore
Translation of GIT committish: FILL-IN-HEAD-COMMITTISH

When revising a translation, copy the HEAD committish of the
version that you are working on.  See TRANSLATION for details.
@end ignore
"""

headers to .(i)tely files of the user manual, in order to make
translation checks, and I just saw that point-and-click.itely seems to
be stalled: it isn't included in lilypond.tely, and there is already a
"Point and click" node in running.itely. What should we do with this
file?

Greetings
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: point-and-click.itely

[Graham Percival]

John Mandereau wrote:

headers to .(i)tely files of the user manual, in order to make
translation checks, and I just saw that point-and-click.itely seems to
be stalled: it isn't included in lilypond.tely, and there is already a
"Point and click" node in running.itely. What should we do with this
file?


Ah, it should be deleted.  I'll let you do that since you know git 
better than I do.  :)


Cheers,
- Graham


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

Re: point-and-click.itely

[John Mandereau]

Graham Percival wrote:
> John Mandereau wrote:
> > headers to .(i)tely files of the user manual, in order to make
> > translation checks, and I just saw that point-and-click.itely seems to
> > be stalled: it isn't included in lilypond.tely, and there is already a
> > "Point and click" node in running.itely. What should we do with this
> > file?
> 
> Ah, it should be deleted.  I'll let you do that since you know git 
> better than I do.  :)

Okay, I've deleted it in both stable/2.10 ans master.

However, I don't know git well; I always use Cogito (except for some
very advanced commands), and it works for me. I couldn't have done so
many things with Git. I try to write documentation for Git, but it's so
much harder :-(

Good luck with Git ;-)
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: GIT errors?

[Till Rettig]

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 
quite a new version of git on the newest Ubuntu distro -- you are just 
somewhat used to getting updates all the times. But it seems they 
deffinitely neglect not "core" programs -- my version is 1.4.1! So 
the first time I tried every command including all that were like 
"commented" out -- and it worked. But now I got the base with this 
cogito (that is the first time to make all the git files on your local 
web/master), now git pull funktions quite well.

Didn't you Daniel also use Ubuntu? So this might be the problem with it.

I see no other reason for saying instructions are incorrect: I have
actually tested these instructions under GNU/Linux, with Git 1.4.4.2.
Do a Git expert knows why this doesn't work?

Darn, at second thought, Cogito seems to be easier to use, despite
limited portability :-/ If there is no other clean way to get you
started, you may simply fal back to Cogito...

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

Re: /index.es.html has funny titles?

[Daniel Tonda Castillo]

Jan Nieuwenhuizen escribió:

Hi Daniel,

Congratulations on finishing the Spanish site, we now have 4 complete
translations!

You're probably working on this (saw your git efforts), but to a
non-spanish speaker as myself this looks a bit funny
lilypond.org/web/index.es.html (divider lines by me)

   Sumérjase en ...  de LilyPond
   ---
   la Etiqueta   de la impresión de música

Wher the English site has:

   Dive into ...   |Ms. Manners
   the LilyPond|of Music Printing
  
Francisco also commented on that. The way it is displayed in english 
seems that one reads the title as:


Dive into... The LilyPond Ms. Manners of Music Printing, yes?

The order of the words in Spanish, would be:

Sumérjase.. en la etiqueta de LilyPond de la impresión de música.

It also could be said:

Sumérjase... en la etiqueta de la impresión musical de LilyPond.

Ms. Manners is akin to "etiquette" (there's no such thing  as Ms. 
Manners in Spanish).


We're working on a better way of putting it.
  
It seems that the titles of the two columns are printed over both

columns?

Jan.
begin:vcard
fn:Daniel Tonda Castillo
n:Tonda Castillo;Daniel
email;internet:[EMAIL PROTECTED]
version:2.1
end:vcard

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

Re: [Fwd: German translation help file]

[Till Rettig]

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 the English README.
  
Well, no I checked it. I don't think there is anything I have in my own 
version. Just now when I commit I get always the patch about adding this 
README.de to my own git -- how do I remove this commitish ie. undo the 
whole thing?


I liked the idea and structure of the new file. Myself also forgot the 
mention of git status which is defenitely very important. Seems I have 
to check the part with the check-translation.py myself -- there is a lot 
of mistakes about wrong commitish numbers and then it finishes with a 
mistake (so I think it doesn't do the job till the end). I will see that.


Do I now understand right that when problems emerge the git pull will 
save files under different names (or insert the problem signs, as you 
had it) and then you have to change them and make git update-index on 
the very file (this was in a message to Daniel T C. today). I think this 
is also an important remark, these kind of difficulties will probably 
appear to the beginner especially often. At least for me, if I changed I 
file that was already there and made the commit nothing happened. If I 
would git add it, then I get the mistake that the file is already added. 
Only with update-index I had success. But this might also be that my 
version of git is so old...


So this update-index was the only thing I find still somehow important, 
despite Johannes S. thinks it is not a good idea.
Well, might be that there were also some problems whith me and that add 
will work in the future.


I noted you can issue the git command anywhere, and patches will be 
always put on top. I don't know if this is so important as to mention.



Like the new README! Thanks

Till


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

Re: Priority 3 Translation spanish, was: Priority 2 Translation of web site to spanish

[Daniel Tonda Castillo]

The funny thins is that before I did any pull, everything worked out 
just fine. This might be a problem due to my using cogito in ubuntu.


I'll try to compile a newer version of git and use that instead. In the 
meantime what are your suggestions?


Daniel Tonda C.

John Mandereau escribió:

Daniel Tonda Castillo wrote:
  

I get a lot of merge errors, after the git-pull:

git-rev-parse web/master
745ee84ea5b583686e53dc2628e5067492997773
[EMAIL PROTECTED]: lilypond]$ git pull 
git://git.sv.gnu.org/lilypond.git/ web/master:web/master

Trying really trivial in-index merge...
es/sponsor/index.html: needs merge
es/sponsor/options.html: needs merge
es/switch/howto.html: needs merge
fatal: you need to resolve your current index first
Nope.
Merging HEAD with 745ee84ea5b583686e53dc2628e5067492997773
Merging:
afcbb4ac3dc6a31f371182da9c0b47cd2ca3b68f message
745ee84ea5b583686e53dc2628e5067492997773 Resolving conflicts with 
[EMAIL PROTECTED]:/srv/git/lilypond.git#web/master

found 1 common ancestor(s):
ac5da2c7e90f10ce8a680b275d1e33b10462c4ea Merge branch 'web/master' of 
git://git.sv.gnu.org/lilypond into web/master

git-read-tree: fatal: you need to resolve your current index first
 
No merge strategy handled the merge.


git-rev-list shows one thing, and git-rev-parse another:

git-rev-list HEAD | head -1
afcbb4ac3dc6a31f371182da9c0b47cd2ca3b68f


git-rev-parse web/master
745ee84ea5b583686e53dc2628e5067492997773

Which would be the best way to handle this?

Should I just start over?



  
Before the pull and as the last thing, I did the commit -m with no files 
and got the vim edition of which files would be commited, etc. So I 
commented thos to be committed (in the es/ directory) and saved the 
file. git-status didn't show any uncommitted files after that.

Did you have any uncommitted local changes before merging? i.e. did
"git status" complained about "Changed but not updated" files?

If not, that's already a good thing. Then, for each file git-pull
reported a conflict about, open it in a text editor, go to the conflict
zones (marked with <<<, === and >>>), merge the 2 versions manually,
junk any conflict mark and save the file, then run "git update-index" on
this file. After all that, commit and the merge should be complete.

However, it seems according to git-pull output that you haven't
committed files in es/sponsor/; you should add them or run
git-update-index on them before resolving other conflicts.

Try to report the result of your experiments. It might work better than
restarting from scratch.
  

Here's the output of the git-pull:

Ok, here goes a session of git:

git pull git://git.sv.gnu.org/lilypond.git/ web/master:web/master

Trying really trivial in-index merge...
fatal: Untracked working tree file '.gitignore' would be overwritten by 
merge.

Nope.
Merging HEAD with 745ee84ea5b583686e53dc2628e5067492997773
Merging:
afcbb4ac3dc6a31f371182da9c0b47cd2ca3b68f message
745ee84ea5b583686e53dc2628e5067492997773 Resolving conflicts with 
[EMAIL PROTECTED]:/srv/git/lilypond.git#web/master

found 1 common ancestor(s):
ac5da2c7e90f10ce8a680b275d1e33b10462c4ea Merge branch 'web/master' of 
git://git.sv.gnu.org/lilypond into web/master
git-read-tree: fatal: Untracked working tree file '.gitignore' would be 
overwritten by merge.


No merge strategy handled the merge.

===
Now git-status reports this:

#
# Updated but not checked in:
#   (will commit)
#
#deleted:  .gitignore
#deleted:  GNUmakefile
#deleted:  README
#deleted:  TRANSLATION
#deleted:  colors.css
#deleted:  de/about/faq.html
#deleted:  de/about/index.html
#deleted:  de/contact.ihtml
#deleted:  de/index.html
#deleted:  de/install/cygwin.html
#deleted:  de/install/getting-started.html
#deleted:  de/install/index.html
#deleted:  de/install/macos.html
#deleted:  de/install/using.html
#deleted:  de/startevim.sh
#deleted:  de/switch/advantages.html
#deleted:  de/switch/howto.html
#deleted:  de/switch/index.html
#deleted:  de/switch/testimonials.html
#deleted:  de/switch/tour.html
#deleted:  es/about/automated-engraving/applications.html
#deleted:  es/about/automated-engraving/benchmarking.html
#deleted:  es/about/automated-engraving/big-page.html
#deleted:  es/about/automated-engraving/conclusion.html
#deleted:  es/about/automated-engraving/divide-and-conquer.html
#deleted:  es/about/automated-engraving/engraving.html
#deleted:  es/about/automated-engraving/formatting-architecture.html
#deleted:  es/about/automated-engraving/implementing-notation.html
#deleted:  es/about/automated-engraving/implementing-typography.html
#deleted:  es/about/automated-engraving/index.html
#deleted:  es/about/automated-engraving/input-format.html
#deleted:  es/about/automated-engraving/introduction.html
#deleted:  es/about/automated-engraving/problem-statement.html
#deleted:  es/about/automated-engravi

new German patch

[Till Rettig]

Hi,

so here comes the new German patch. As for now when making format-patch 
I get three patches. One was the last one which is already applied to 
the internet, the other is my own README.de, which I would like to 
remove, and the third is the addition I did today. So I think you should 
only 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:10:25 +0200
Subject: [PATCH] addition and update of german translation
---
 de/about/automated-engraving/index.html |4 -
 de/about/thanks.html|6 +
 de/install/cygwin.html  |  183 +++
 de/install/using.html   |4 -
 de/switch/testimonials.html |  175 ++
 5 files changed, 367 insertions(+), 5 deletions(-)

diff --git a/de/about/automated-engraving/index.html 
b/de/about/automated-engraving/index.html
index 18dee8a..6afc7ba 100644
--- a/de/about/automated-engraving/index.html
+++ b/de/about/automated-engraving/index.html
@@ -1,5 +1,5 @@
 
 
-„Besessen damit, mit Tinte auf dem Papier zu zeichnen“
+„Besessen davon, mit Tinte auf dem Papier zu zeichnen“
 
 
 Was steckt hinter LilyPond?
diff --git a/de/about/thanks.html b/de/about/thanks.html
index 1f29283..15709b2 100644
--- a/de/about/thanks.html
+++ b/de/about/thanks.html
@@ -1,5 +1,5 @@
 
+
+LilyPond - mit Cygwin
+
+LilyPond mit Cygwin
+
+
+Installieren
+
+
+
+
+  
+Laden Sie sich setup.exe auf Ihren Computer, indem Sie
+http://cygwin.com/setup.exe";>hier klicken.
+  
+  
+Wenn Sie Windows NT, 2000 and XP benutzen, müssen Sie evtl. zuerst 
Administrator werden
+  
+
+  
+Starten Sie setup.exe 
+  
+
+  
+und klicken Sie „next“, bis Sie zum
+  
+
+  
+Package View-Dialog kommen.  Wählen Sie 
+LilyPond aus, es befindet sich im Abschnitt
+Publishing.
+  
+
+  
+Jetzt wird LilyPond mit allen Unterstützungsprogrammen installiert.
+Dazu müssen 66 Mb heruntergeladen werden, die gesamte Installation
+wird 260 Mb auf Ihrer Festplatte einnehmen.
+  
+
+
+
+
+   Wenn Sie sich nicht sicher sind, was von setup.exe abgefragt wird,
+  verändern Sie nicht die ursprünglichen Einstellungen.
+Auf keinen Fall den voreingestellten Installationsordner
+  (c:/cygwin) verändern und auch die Texteinstellungen
+  bei ihrem Originalwert (UNIX muss als Typ benutzt werden) 
+  belassen.
+
+
+
+Überprüfung
+
+
+  
+Hier können Sie eine Testdatei herunterladen.
+  
+
+  
+Speichern Sie sie auf Ihrem Desktop unter dem Namen test.ly (und 
versichern
+Sie sich, dass es  nicht 
+test.ly.TXT heißt).
+  
+
+  
+Doppelklicken Sie auf die Datei.
+  
+
+
+Jetzt wird die Datei verarbeitet und das Ergibnis in einem Pdf-Betrachter 
angezeigt.
+
+Hurra, es klappt!
+
+
+  Gut! Fahren Sie fort mit der Benutzung von LilyPond.
+
+
+Hmm, ich weiß wirklich nicht, was ich machen soll. Helft mir!
+
+
+  Fragen und Bitte um Unterstützung können Sie an die Mailingliste mailto:lilypond-user@gnu.org";>lilypond-user@gnu.org schicken.
+
+
+Mist, es klappt nicht!
+
+
+  Versuchen Sie, nocheinmal  setup.exe aufzurufen; dadurch werden etwa
+  90% der Probleme gelöst. Versichern Sie sich, dass die richtige Version
+  von LilyPond installiert ist; wenn Sie zweimal auf das ausgewählte Paket
+  klicken, erhalten Sie eine ältere Version.
+  
+
+
+  Wenn es jetzt immer noch nicht funktionieren sollte, schicken Sie uns bitte
+  einen Fehlerbericht (möglichst auf englisch). Im gleichen Ordner wie
+  test.ly sollte sich auch eine Datei test.log befinden.
+  Schicken Sie diese Datei an mailto:lilypond-user@gnu.org";>lilypond-user@gnu.org 
+  mit einer Beschreibung Ihres Problems.
+
+
+Windows 98
+
+
+  Unter Windows 95, 98 und ME gibt es Probleme mit dem
+  Cygwin Python-Paket, das evtl. die ungestörte Funktion von
+  LilyPond behindern kann (siehe auch http://www.cygwin.com/ml/cygwin/2004-06/msg00956.html";>Python
+  besteht die Testsuite nicht(auf englisch)).  LilyPond selber
+  sollte benutzbar sein, aber die Funktion, auf eine .ly-Datei
+  zu klicken, damit ein pdf erstellt wird, sowie lilypond-book und midi2ly
+  funktionieren evtl. nicht. Leider sind diese Probleme ausßer Reichweite
+  des   LilyPond-Entwicklerteams.  Windows NT, 2000
+  und XP haben keine Probleme damit.
+
+
+Aber ich habe keine Datei test.log
+
+  Das LilyPond-Paket ist nicht korrekt installiert. Gehen Sie bitte
+  nocheinmal die Prozedur der 
+  Installation durch und versichern Sie sich,
+  dass alles fehlerfrei verlaufen ist. Fragen können an
+  mailto:lilypond-user@gnu.org";>lilypond-user@gnu.org per E-Mail 
geschickt werden.
+
+
+
+Deinstallieren
+
+
+  
+Entweder mit Gewalt:
+entfernen Sie den ganzen C:\CYGWIN-Ordner.
+
+Damit wird auch Ihr  Cygwin-/home/-Verz

Re: /index.es.html has funny titles?

[John Mandereau]

Daniel Tonda Castillo wrote:
> Jan Nieuwenhuizen escribió:
> > Hi Daniel,
> >
> > Congratulations on finishing the Spanish site, we now have 4 complete
> > translations!
> >
> > You're probably working on this (saw your git efforts), but to a
> > non-spanish speaker as myself this looks a bit funny
> > lilypond.org/web/index.es.html (divider lines by me)
> >
> >Sumérjase en ...  de LilyPond
> >---
> >la Etiqueta   de la impresión de música
> >
> > Wher the English site has:
> >
> >Dive into ...   |Ms. Manners
> >the LilyPond|of Music Printing
> >   
> Francisco also commented on that. The way it is displayed in english 
> seems that one reads the title as:
> 
> Dive into... The LilyPond Ms. Manners of Music Printing, yes?

No, you're mistaken. Have a more careful look at the layout of
lilypond.org front page. There are two distinct columns, with two
distincts titles: "Dive into... The LilyPond" for the 1st column, and
"Ms. Manners of Music Printing" for the 2nd column.

Greetings
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: Priority 3 Translation spanish, was: Priority 2 Translation of web site to spanish

[John Mandereau]

Daniel Tonda Castillo wrote:
> The funny thins is that before I did any pull, everything worked out 
> just fine. This might be a problem due to my using cogito in ubuntu

> I'll try to compile a newer version of git and use that instead. In the 
> meantime what are your suggestions?

If you don't need 10 hours to do it, please upgrade to latest Git and
Cogito. You may also want to complain to the Ubuntu package maintainer.
If you have some time and some packaging qualifications, you could even
update Git and Cogito Ubuntu packages :-).

It'd be absurd that the translators gave up because Git is difficult to
use. So my first suggestion is to start with Cogito, which doesn't
prevent you from using git commands as you become more familiar with it.
Reading the revised README is not enough; you should spend time reading
the docs, starting from http://git.or.cz and Gitwiki. To give you an
idea, I started using Git/Cogito after having read the Crash course for
CVS users.

Then, you should exercise Cogito view commands (status, branch-ls, log,
diff) and gitk to evaluate the state of your local Git copy of
lilypond.org sources, and see whether you can go on using it, or
restarting from scratch cloning
git://git.sv.gnu.org/lilypond.git#web/master
with Cogito.



> Before the pull and as the last thing, I did the commit -m with no files 
> and got the vim edition of which files would be commited, etc. So I 
> commented thos to be committed (in the es/ directory) and saved the 
> file. git-status didn't show any uncommitted files after that.

This looks good.


> Here's the output of the git-pull:
> 
> Ok, here goes a session of git:
> 
> git pull git://git.sv.gnu.org/lilypond.git/ web/master:web/master
> 
> Trying really trivial in-index merge...
> fatal: Untracked working tree file '.gitignore' would be overwritten by 
> merge.
> Nope.
> Merging HEAD with 745ee84ea5b583686e53dc2628e5067492997773
> Merging:
> afcbb4ac3dc6a31f371182da9c0b47cd2ca3b68f message
> 745ee84ea5b583686e53dc2628e5067492997773 Resolving conflicts with 
> [EMAIL PROTECTED]:/srv/git/lilypond.git#web/master
> found 1 common ancestor(s):
> ac5da2c7e90f10ce8a680b275d1e33b10462c4ea Merge branch 'web/master' of 
> git://git.sv.gnu.org/lilypond into web/master
> git-read-tree: fatal: Untracked working tree file '.gitignore' would be 
> overwritten by merge.
>  
> No merge strategy handled the merge.
> 
> ===
> Now git-status reports this:
> 
> #
> # Updated but not checked in:
> #   (will commit)
> #
> #deleted:  .gitignore
> #deleted:  GNUmakefile
> #deleted:  README
> #deleted:  TRANSLATION
> #deleted:  colors.css
> #deleted:  de/about/faq.html

[snip/ all files deleted the same way]

> #deleted:  site/switch/menu-entries.py
> #deleted:  site/switch/new-notation.html
> #deleted:  site/switch/testimonials.html
> #deleted:  site/switch/tour.html
> #deleted:  site/template.ihtml
> #
> #
> # Untracked files:
> #   (use "git add" to add to commit)
> #
> #.gitignore
> #GNUmakefile
> #README
> #TRANSLATION
> #colors.css
> #de/
> #es/
> #fr/
> #newweb.css
> #nl/
> #po/
> #scripts/
> #site/

Argh, this looks bad. Try to resolve conflicts if any, then do "git add"
on every file, then do "git commit -a", then try to pull again to check
the same problem doesn't appear again.

(I think I'd better give up providing Git advice :-S)

Good luck
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: GUILE-with-rational-bugfix

[Karl Hammar]

[EMAIL PROTECTED]:
> Rune Zedeler escreveu:
> > Where can the famous patch be found?
> > (Unable to compile latest guile-cvs).
> 
> see install.txt

There is no install.txt, and the INSTALL.txt I found does not mention it:

  $ git-pull
  remote: Generating pack...
...
   rename input/{no-notation/parse5.ly => 
regression/warn-conflicting-key-signatures.ly} (100%)
  $ find . -name install.txt
  $ find . | grep -i install.txt
  ./Documentation/topdocs/out/INSTALL.txt
  $ grep -C2 -i guile Documentation/topdocs/out/INSTALL.txt 
   work.

 * GUILE (http://www.gnu.org/software/guile/guile.html) (version
   1.6.7 or newer).  If you are installing binary packages, you may
   need to install guile-devel or guile-dev or libguile-dev too.

 * Texinfo (ftp://ftp.gnu.org/gnu/texinfo/) (version 4.8 or newer).
  --
 * Pango (http://www.pango.org/) (version 1.12 or newer).

 * GUILE (http://www.gnu.org/software/guile/guile.html) (version
   1.8.0 or newer).

  --


  export GUILE=guile-1.6
  export GUILE_CONFIG=guile-1.6-config
  export 
PKG_CONFIG_PATH=/sw/lib/freetype219/lib/pkgconfig/:/sw/lib/fontconfig2/lib/pkgconfig/
  ./configure
  $

Regards
/Karl


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

Re: GUILE-with-rational-bugfix

[Mats Bengtsson]

Karl Hammar wrote:


[EMAIL PROTECTED]:
 


Rune Zedeler escreveu:
   


Where can the famous patch be found?
(Unable to compile latest guile-cvs).
 


see install.txt
   



There is no install.txt, and the INSTALL.txt I found does not mention it:
 



At www.lilypond.org, click on the documentation link
for version 2.11 and then on INSTALL.

  /Mats


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

Re: [Fwd: German translation help file]

[John Mandereau]

Till Rettig wrote:
> John Mandereau wrote:
> > Please read the revised README and translate the parts of README.de that
> > brings something interesting in addition to the English README.
> >   
> Well, no I checked it. I don't think there is anything I have in my own 
> version. Just now when I commit I get always the patch about adding this 
> README.de to my own git -- how do I remove this commitish ie. undo the 
> whole thing?

Assuming you have no uncommitted changes, the most simple way is to
"rm README.de" and "git commit -a".


> I liked the idea and structure of the new file. Myself also forgot the 
> mention of git status which is defenitely very important. Seems I have 
> to check the part with the check-translation.py myself -- there is a lot 
> of mistakes about wrong commitish numbers and then it finishes with a 
> mistake (so I think it doesn't do the job till the end). I will see that.

Which mistake is it? Is it related to the "fatal: bad object" issue
described in
http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00058.html
?

> Do I now understand right that when problems emerge the git pull will 
> save files under different names (or insert the problem signs, as you 
> had it) and then you have to change them and make git update-index on 
> the very file (this was in a message to Daniel T C. today). I think this 
> is also an important remark, these kind of difficulties will probably 
> appear to the beginner especially often. At least for me, if I changed I 
> file that was already there and made the commit nothing happened. If I 
> would git add it, then I get the mistake that the file is already added. 
> Only with update-index I had success. But this might also be that my 
> version of git is so old...

See my last message to Daniel Tonda C. about too old Git/Cogito
versions.

Anyway, I think I was wrong to tell you to pull with web/master as local
name of the remote branch, whereas you may not already have this name.
Johannes?


> So this update-index was the only thing I find still somehow important, 
> despite Johannes S. thinks it is not a good idea.

It's not a bad idea, it's only more complicated. When resolving
conflicts, I don't know if there are other ways than using update-index.


> I noted you can issue the git command anywhere, and patches will be 
> always put on top.

Good catch.


>  I don't know if this is so important as to mention.

It's difficult to explain everything. Documentation in README is not
meant to be a subsitute for man pages and generally Git official docs.

Cheers
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: new German patch

[John Mandereau]

Till Rettig wrote:
> so here comes the new German patch. As for now when making format-patch 
> I get three patches. One was the last one which is already applied to 
> the internet, the other is my own README.de, which I would like to 
> remove, and the third is the addition I did today. So I think you should 
> only apply the last patch (0003-replace-of-testimonials-txt). I will 
> send you all of them though.

Third patch applied and pushed to git.sv.gnu.org.

Thanks
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: GUILE-with-rational-bugfix

[Karl Hammar]

> Rune Zedeler <[EMAIL PROTECTED]> writes:
> > Where can the famous patch be found?
...
> http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch
...

Got the patch and build debian guile debs for i386.
If anybody would need them, they are available at:

  http://kalle.csb.ki.se/pub/lilypond/

You need debian unstable to use them.
To build them do:

  # apt-get install -t unstable debhelper
...
  # apt-get build-dep guile-1.8
...

  $ wget http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch
  $ apt-get source guile-1.8
  Reading package lists... Done
  Building dependency tree... Done
  Need to get 0B/2829kB of source archives.
  dpkg-source: extracting guile-1.8 in guile-1.8-1.8.1+1
  $ cd guile-1.8-1.8.1+1/libguile
  $ patch -p1  < ../../guile-1.8-rational.patch
  patching file libguile/numbers.c
  patching file libguile/numbers.h
  $ cd ..
  $ fakeroot ./debian/rules 
  #   this goes first so we clean using patched code
  rm -f debian/stamp/build
...
  dh_builddeb
  dpkg-deb: building package `guile-1.8' in `../guile-1.8_1.8.1+1-4_i386.deb'.
  dpkg-deb: building package `guile-1.8-dev' in 
`../guile-1.8-dev_1.8.1+1-4_i386.deb'.
  dpkg-deb: building package `guile-1.8-libs' in 
`../guile-1.8-libs_1.8.1+1-4_i386.deb'.
  make[1]: Leaving directory `/home/karl/most/music/lilypond/guile-1.8-1.8.1+1'
  $

./autogen.sh works for me now.

Regards
/Karl




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

Re: GUILE-with-rational-bugfix

[Karl Hammar]

> Karl Hammar wrote:
> 
> >[EMAIL PROTECTED]:
> >  
> >
> >>Rune Zedeler escreveu:
> >>
> >>
> >>>Where can the famous patch be found?
> >>>(Unable to compile latest guile-cvs).
> >>>  
> >>>
> >>see install.txt
> >>
> >>
> >
> >There is no install.txt, and the INSTALL.txt I found does not mention it:
> >  
> >
> 
> At www.lilypond.org, click on the documentation link
> for version 2.11 and then on INSTALL.
> 
>/Mats

Ohh, I see, a catch-22 situation. I could have seen it if I peeked
inside Documentation/topdocs/INSTALL.texi, but was mislead by the
configure.in text.

Regards
/Karl




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

makeinfo with utf-8 support

[Karl Hammar]

Hmm, when building I get:

 out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'.
 out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'.
 out/music-glossary.nexi:6: warning: unrecognized encoding name `utf-8'.
 out/INSTALL.texi:6: warning: unrecognized encoding name `utf-8'.
 out/README.texi:6: warning: unrecognized encoding name `utf-8'.

I've got:

 $ makeinfo --version
 makeinfo (GNU texinfo) 4.8

The latest texinfo at http://ftp.gnu.org/gnu/texinfo/ seems to be too old. 
Does anybody know where the makeinfo with utf-8 support is, a patch ?

Regards
/Karl




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

musicxml2ly bug

[Werner LEMBERG]

[lilypond 2.11.7]

I've just received the attached MusicXML file for testing purposes.
Trying musicxml2ly on this file, the script aborts with

  Traceback (most recent call last):
File "/usr/local/bin/musicxml2ly", line 656, in ?
  main()
File "/usr/local/bin/musicxml2ly", line 653, in main
  voices = convert (args[0], options)
File "/usr/local/bin/musicxml2ly", line 614, in convert
  voices = get_all_voices (parts)
File "/usr/local/bin/musicxml2ly", line 465, in get_all_voices
  part_ly_voices[n] = (musicxml_voice_to_lily_voice (v), v)
File "/usr/local/bin/musicxml2ly", line 333, in musicxml_voice_to_lily_voice
  num = int (n.get_parent ().number)
  ValueError: invalid literal for int(): 22A

And indeed, the corresponding XML snippet shows this:

  
  ...
  
  ...
  
  ...


 Werner


Seite-98 aus Cavalleria.xml.bz2
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: makeinfo with utf-8 support

[John Mandereau]

Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit :
> Hmm, when building I get:
> 
>  out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'.
>  out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'.
>  out/music-glossary.nexi:6: warning: unrecognized encoding name `utf-8'.
>  out/INSTALL.texi:6: warning: unrecognized encoding name `utf-8'.
>  out/README.texi:6: warning: unrecognized encoding name `utf-8'.
> 
> I've got:
> 
>  $ makeinfo --version
>  makeinfo (GNU texinfo) 4.8
> 
> The latest texinfo at http://ftp.gnu.org/gnu/texinfo/ seems to be too old. 
> Does anybody know where the makeinfo with utf-8 support is, a patch ?

AFAIK Texinfo does no character encoding conversion for the Info and
HTML output, so the LilyPond devels have decided to use the modern
character set UTF-8, not Latin1. This will really become a problem for
the PDF (outputted by Texinfo/TeX) when we decide to make PDF of Lily
docs translation.

Well, you can safely ignore these warnings.

See also 
http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00047.html


Greetings
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Docs check-translation

[John Mandereau]

Hello,

I've just pushed check-translation support for the user manual to
stable/2.10. I've done

cd Documentation
make ISOLANG=fr check-translation

for a testing purpose. How does it look to you?

As I'm currently the only person able to update the French user manual,
so it seems to me a urgent issue. In the coming days/weeks, I'll
actually update French translation in stable/2.10, write documentation
for translators (in Documentation/TRANSLATION), cherry-pick the
interesting documentation changes from master to stable/2.10, and
finally update French translation in both branches. Is this a good plan?

Cheers
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: Docs check-translation

[Graham Percival]

John Mandereau wrote:

As I'm currently the only person able to update the French user manual,
so it seems to me a urgent issue. In the coming days/weeks, I'll
actually update French translation in stable/2.10, write documentation
for translators (in Documentation/TRANSLATION), cherry-pick the
interesting documentation changes from master to stable/2.10, and
finally update French translation in both branches. Is this a good plan?


For the backporting of docs, I'd just start by copying everything and 
trying to build it with stable.  The skyline spacing docs obviously 
won't work (so remove them from the backported docs), but AFAIK there 
aren't any other new features in 2.11 that affect the docs.


Cheers,
- Graham


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