Le 12/03/2015 21:01, Paul Morris a écrit :
Hi Federico,
On Mar 12, 2015, at 2:57 PM, Federico Bruni fedel...@gmail.com wrote:
Yes, this is a work for translators (here in Cc).
As soon as your commit has landed from staging into master and Francisco or
Jean-Charles has merged master into
Le 12/03/2015 19:57, Federico Bruni a écrit :
Il giorno gio 12 mar 2015 alle 18:10, Paul Morris p...@paulwmorris.com
ha scritto:
After this patch the home pages for languages other than English have
the new
CSS but the old HTML, and so things are off, the side bar in particular.
(The Català
Hi,
Please find a new tarball for LilyPond at
http://download.linuxaudio.org/lilypond/source/v2.19/lilypond-2.19.16.tar.gz
Cheers,
Jean-Charles Malahieude
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
Hi all,
I've locally merged master into translation, and before merging
translation back to staging will correct bad cross-links.
notation.bigtexi.log:
WARNING: Unable to find node 'Accidentals and key signatures' in book
learning.
WARNING: Unable to find node 'Accidentals and key
Le 18/07/2014 16:58, David Kastrup disait :
Phil Holmes m...@philholmes.net writes:
OK - running makelsr on current master does not touch any files, and
they all have the wrong address. I propose to rerun my script, only
changing the address of the LSR this time...
I'll then update the LSR
Le 16/02/2014 16:18, Trevor Daniels disait :
David Kastrup wrote Sunday, February 16, 2014 2:45 PM
I find that I'm currently dead-locking in decision-making with a
somewhat tedieous task. Here is what it boils down to: basically
git checkout -b translation origin/translation
git log
Le 01/01/2014 20:45, James disait :
On 01/01/14 17:50, Jean-Charles Malahieude wrote:
I compile on native Fedora. I don't know by how would be multiplied a
90 minutes make -j3 make -j3 doc on my dual-core with 2gigs RAM
when launched in a VM.
Probably not as much as you think. Assuming you
Le 01/01/2014 18:07, Urs Liska disait :
Am 01.01.2014 18:02, schrieb Phil Holmes:
- Original Message - From: Urs Liska u...@openlilylib.org
But you're led to believe that LilyDev is the canonical environment
for working on LilyPond, and if you dare to go another route you'll be
on
Le 15/12/2013 21:49, Francisco Vila disait :
2013/12/15 Benno Schulenberg coordina...@translationproject.org
Hello Francisco and Jean-Charles,
On 2013-12-15 16:54, Francisco Vila wrote:
This is correct. Translation of PO files (which we use to
maintain translations of the binary executable
Le 08/12/2013 11:32, Phil Holmes disait :
- Original Message - From: David Kastrup d...@gnu.org
To: Jean-Charles Malahieude lily...@orange.fr
Cc: lilypond-devel lilypond-devel@gnu.org; Phil Holmes
m...@philholmes.net
Sent: Sunday, December 08, 2013 9:19 AM
Subject: Re: updates of .po
Le 07/12/2013 13:16, David Kastrup disait :
Jean-Charles Malahieude lily...@orange.fr writes:
Hi David,
I've downloaded updated files from the FTP and created a patch to be
applied on branch stable/2.18.
Wouldn't those be better applied to translation and then merged into
both stable/2.18
Le 14/11/2013 20:52, Janek Warchoł disait :
The 2nd and 3rd examples of 0.6 slurs look very bad to me. Do you
have a minimal code example?
Here it is:
\version 2.17.95
\new Staff { \relative c { \clef bass
b'4(^default b,) e2
\once \override Slur.details.max-slope = 0.8 b'4(^0.8 b,) e2
Le 25/10/2013 12:30, Janek Warchoł disait :
2013/10/22 Janek Warchoł janek.lilyp...@gmail.com:
Hi,
2013/10/22 Jean-Charles Malahieude lily...@orange.fr:
If it could by chance ameliorate this situation as well:
\relative c { \clef bass f4( f,) b2 }
in order to get what Breitkopf proposes, I
Hi David,
There are 4 po files updated to 2.17.29 available on the FTP (Spanish,
Esperanto, French and German).
Where would you prefer them to go? I can prepare and send you a patch,
but towards which branch?
It would be better to integrate them before releasing 2.17.96 which
already has a
Le 11/11/2013 12:39, David Kastrup disait :
Jean-Charles Malahieude lily...@orange.fr writes:
Hi David,
There are 4 po files updated to 2.17.29 available on the FTP (Spanish,
Esperanto, French and German).
Where would you prefer them to go? I can prepare and send you a patch,
but towards
Le 22/10/2013 20:06, David Kastrup disait :
Ok, after looking at the current situation and the current patches in
review/countdown, I've decided that I'll fork off the stable release
branch 2.18 after the current batch in countdown is in master. After
that point of time, I'll only cherry-pick
Le 25/10/2013 12:30, Janek Warchoł disait :
2013/10/22 Janek Warchoł janek.lilyp...@gmail.com:
Hi,
2013/10/22 Jean-Charles Malahieude lily...@orange.fr:
If it could by chance ameliorate this situation as well:
\relative c { \clef bass f4( f,) b2 }
in order to get what Breitkopf proposes, I
Le 26/10/2013 19:17, David Kastrup disait :
Jean-Charles Malahieude lily...@orange.fr writes:
Since nothing has changed on translation since Monday (too many
other things to deal with), I just merged _locally_ master into
it. Would you mind me pushing this before setting the freeze?
Yes
Le 21/10/2013 23:49, Janek Warchoł disait :
Hi,
i'm browsing slur formatting code and i found why slurs in these cases
{
\slurUp
d'2( f')
\slurDown
c''2( e'')
}
are soo ugly.
I facepalmed really hard :-)
Expect an awesome patch tomorrow.
If it could by chance ameliorate
Le 05/10/2013 20:03, Werner LEMBERG disait :
Is there any workaround other than locally revert Julien's commit?
That's not a workaround since your fonts would all be broken.
Maybe install TeXlive2013 to a local tree and update to the newest
version using tlmgr?
It's not necessary to
Hi all!
Since Fedora's version of mpost is 1.802, I'm now unable to build
LilyPond from scratch, and have not the resources to rebuild the Texlive
package in order to upgrade.
Is there any workaround other than locally revert Julien's commit?
TIA,
Jean-Charles
Le 05/10/2013 16:50, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
Since Fedora's version of mpost is 1.802, I'm now unable to build
LilyPond from scratch, and have not the resources to rebuild the
Texlive package in order to upgrade.
Is there any workaround
Le 05/10/2013 20:03, Werner LEMBERG disait :
Is there any workaround other than locally revert Julien's commit?
That's not a workaround since your fonts would all be broken.
Maybe install TeXlive2013 to a local tree and update to the newest
version using tlmgr?
It's not necessary to
Le 13/09/2013 09:03, Lilyfan disait :
Message du 13/09/13 00:55
De : Julien Rioux
On 12/09/2013 6:09 PM, Federico Bruni wrote:
2013/8/3 Federico Bruni
I'm getting this error if I run ./autogen.sh in git master:
ERROR: Please install required programs: International New Century
Schoolbook
Le 04/06/2013 20:19, David Kastrup disait :
lily...@orange.fr writes:
There is also
notation/rhythms.itely:2320:If a manual beam is specified with
@code{[..]} set the beam
Oh. That happens when you do search and replace on ... only.
By the way, a
git grep -n \.\.
Le 29/05/2013 10:13, Francisco Vila disait :
Dear LilyPond community,
my apologies for having disappeared these days. I have important
issues at end of every semester, along with taxes, family, and own
studies.
That's a full score with too many staves in one system!
Do your best, I'll
Le 06/04/2013 14:14, Reinhold Kainhofer disait :
Dear all,
[...]
I wish you all the best. LilyPond is an awesome project, and it was a
lot of fun to be part of if. But I simply don't have the time any more
to work on it. I will keep working with it (after all, my SO is a cello
teacher...) and
Le 10/03/2013 08:00, David Kastrup disait :
David Kastrup d...@gnu.org writes:
Removed that commit from staging. It should be fixed in the
translation branch.
I mean: it is currently broken in the translation branch and should get
fixed in the translation branch before trying the merge
Hi David,
What would be more appropriate to have
master-translation-staging ?
Before applying tracker 3229, between 3229 and 3231, or after 3231?
Cheers,
Jean-Charles
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Le 09/03/2013 18:03, David Kastrup disait :
Jean-Charles Malahieude lily...@orange.fr writes:
Hi David,
What would be more appropriate to have
master-translation-staging ?
Before applying tracker 3229, between 3229 and 3231, or after 3231?
[...]
So in short: no rush to do anything just
Le 28/02/2013 07:45, Federico Bruni disait :
I've received the texinfo_document.po file from the Translation Project.
While looking at other languages po files to understand what to
translate and what to leave untraslated, I've noticed some strange
characters. Probably because these files are
Le 28/02/2013 13:11, Federico Bruni disait :
2013/2/28 Jean-Charles Malahieude lily...@orange.fr
It is because the files are in US-ASCII and not in UTF-8.
I have to admit it has been a pain for me having to type @'a instead of
just à or @ for a non breakable space like in the old times
Le 29/01/2013 17:20, Phil Holmes disait :
- Original Message - From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Tuesday, January 29, 2013 4:13 PM
Subject: Re: Make doc; create-weblinks and translations
Phil Holmes m...@philholmes.net writes:
As for getting rid of
Le 26/01/2013 18:09, Phil Holmes disait :
- Original Message - From: Phil Holmes em...@philholmes.net
To: Devel lilypond-devel@gnu.org
Sent: Saturday, January 26, 2013 4:57 PM
Subject: Change in cs.po causes GUB to fail
The following commit:
Le 26/01/2013 19:03, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
lily...@orange.fr
To: Phil Holmes m...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Saturday, January 26, 2013 5:37 PM
Subject: Re: Change in cs.po causes GUB to fail
The problem
Le 25/12/2012 23:30, Francisco Vila disait :
El 25/12/2012 19:31, Federico Bruni escribió:
Il 25/12/2012 19:23, David Kastrup ha scritto:
What actually worries me is:
All other PO files for your package are available in:
http://translationproject.org/latest/lilypond/
And this shows:
Le 19/12/2012 12:14, David Kastrup disait :
The following message is a courtesy copy of an article
that has been posted to gmane.comp.gnu.lilypond.devel as well.
James pkx1...@gmail.com writes:
On 19 December 2012 08:11, James pkx1...@gmail.com wrote:
Hello,
author Jean-Charles Malahieude
Hi all,
In spacing.itely (paragraph beginning on line 2127) I read this sentence:
This means that the placement of a non-staff line depends
on both the surrounding staves and the surrounding non-staff lines.
Setting the @code{stretchability} of one of these types of spacing to
a small value
Hi Phil,
Since you master the LRS-update, here is a patch concerning texidocs
that have not been covered by convert-ly (resukt of a git grep #').
From 55bc3ff354a61fa7c5cec78a5b6b17cd6fefeb80 Mon Sep 17 00:00:00 2001
From: Jean-Charles Malahieude lily...@orange.fr
Date: Sun, 16 Dec 2012 20:11
Le 16/12/2012 20:54, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
To: Phil Holmes
Cc: lilypond-devel
Sent: Sunday, December 16, 2012 7:40 PM
Subject: Snippets' correction
Hi Phil,
Since you master the LRS-update, here is a patch concerning texidocs
Le 09/11/2012 18:55, Janek Warchoł disait :
Hi,
[...]
By the way, the link to gitstats is nice, but i'm pretty sure that
ordinary users, who don't know what a commit is and whether number
of changed lines of code translate to coding skills, have little idea
what all these numbers mean.
Hi John and all,
I just noticed that, because the out of tree build, lilypond.pot gets
polluted by personal path, what does not happen with an in tree build.
e.g. we get, when out of tree :
#: parser.yy:174 parser.yy:188 /home/jcharles/GIT/Mentor/lily/parser.yy:174
#:
Le 24/10/2012 17:28, David Kastrup disait :
Phil Holmes em...@philholmes.net writes:
- Original Message -
From: David Kastrup
To: Phil Holmes
Cc: Devel
Sent: Saturday, October 20, 2012 10:17 PM
Subject: Re: 2.16.1
Phil Holmes writes:
David,
I see you've done a lot of moving
Le 20/10/2012 20:33, Francisco Vila disait :
2012/10/20 David Kastrup d...@gnu.org:
If it is ok with people, I'd propose the following course in order to
get the ball rolling again:
I'll merge stable/2.16 into translation. That should be unproblematic.
Then I'll merge translation into
Le 21/10/2012 13:15, David Kastrup disait :
Jean-Charles Malahieude lily...@orange.fr writes:
That's what I feared since the freeze: having to maintain two sets of
translations.
I think that we will likely leave the stable branch behind soon with
regard to documentation maintenance. Our
Le 24/09/2012 22:18, Janek Warchoł disait :
On Monday, September 24, 2012, David Kastrup wrote:
We get about 1 request per month of the kind in
URL:http://lists.gnu.org/archive/html/lilypond-user/2012-09/msg00600.html
I can't get the automated beams to look like the manual beams in
measure 1.
Le 25/09/2012 19:11, Ian Hulin disait :
On 25/09/12 18:02, Jean-Charles Malahieude wrote:
Why not mimic the difference between phrasing slur and slur:
\beaming 4/4 { c16\[[ c c c] c[ c c c]\] c8[ c] c[ c] }
Je suis désolé, mais
\[ \] are already spoken for as delimiters for early-music
Le 20/09/2012 19:15, Marc Hohl disait :
Am 20.09.2012 18:17, schrieb lilyp...@googlecode.com:
[...]
Oh. \omit is actually even better, isn't it?
Yes, I like it!
I'll likely change that, short of protests. Still, something more
convincing for \single would be nice.
Yes, but I still have
Le 23/07/2012 19:23, David Kastrup disait :
Hi,
our issue tracker went
Google
500. That’s an error.
The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this
error message and the query
Le 13/07/2012 10:23, Phil Holmes disait :
- Original Message - From: Graham Percival
Anyway, my current understanding is that there are three realistic
options:
1)
--- linewidth --
fromsome kind of
emergency-stretch-tweak
--- linewidth --
2)
Le 03/07/2012 19:23, Janek Warchoł disait :
Hi,
until recently, 'make bin' was a very smart tool: it recompiled only
necessary .cc files, not everything. That was lifesaving: instead of
having to wait for 5 minutes, i got the results of my changes in 5
seconds. Unfortunately, this is no
Le 26/06/2012 09:24, Graham Percival disait :
Well, we had at least a week when the only release-critical bug
was the po-replace translation thing. It's a bit silly that we
couldn't have a release due to a 5-line texinfo documentation
thing, and in retrospect I should have done a hostile revert
Le 20/06/2012 11:50, Phil Holmes disait :
I'd like to propose a pretty radical change to this process. I propose
that /Documentation/snippets/ is a straight copy of a recent LSR
tarball. It's the task of the LSR meister to keep this up to date. We
have a new directory:
Le 03/06/2012 16:28, Phil Holmes disait :
I'm trying to build GUB again. This has partly been affected by my
attempt to follow the minor build process a while ago, and getting my
git stash in an inconsistent state. However, think that's now OK, but I
get this:
If I look in the lilypond.log
Le 29/05/2012 23:11, Graham Percival disait :
Friendly reminder -- since there are no Type-Critical issues
either open or in the issues to verify, 2.15.39 is aimed to
become 2.16.0 in one week.
If you do not think that this is appropriate, then take
appropriate action in the issue tracker. Do
Le 30/05/2012 18:37, Jean-Charles Malahieude disait :
Do you plan to build a last 2.15.40 for the po files to be in sync,
or should I make a new pot and upload a new tarball (2.15.39-1) anywhere
for the FTP?
Unless you plan a 2.16.1 very fast.
ps: including the work made by David on footnotes
Le 13/05/2012 15:24, James disait :
Hello,
On 13 May 2012 14:06, Jan Nieuwenhuizenjann...@gnu.org wrote:
It seems that this document is in the formatgiven name surname,
should be Pál Benkő (unless i'm heavily mistaken).
and Hungarians happen to put the given name last in the full name.
Le 11/05/2012 19:44, Graham Percival disait :
On Fri, May 11, 2012 at 09:59:49AM +0200, Janek Warchoł wrote:
On Fri, May 11, 2012 at 9:19 AM, David Kastrupd...@gnu.org wrote:
Janek Warchołjanek.lilyp...@gmail.com writes:
What about a real-life meeting? There will be a GNU conference in
Le 06/05/2012 18:34, Graham Percival disait :
On Sun, May 06, 2012 at 06:19:42PM +0200, Jean-Charles Malahieude wrote:
What you'll find in the enclosed patch is an attempt to adapt
'make po-replace' in order to have an automatically well-formed .pot
included in 'make dist'.
Please upload
Hi Jan and Graham,
Since I got a problem the last time I notified the Free Translation
Project of a new lilypond.pot, I'd like to have it updated during the
releasing process.
What you'll find in the enclosed patch is an attempt to adapt
'make po-replace' in order to have an automatically
Le 06/05/2012 18:31, Graham Percival disait :
I have a bit more information about the terminology problems.
Although the English website is relatively ok (I remember
specifically thinking about free software vs. open source while
writing it -- but Janek should still fix the little bits I
Le 04/05/2012 17:34, Francisco Vila disait :
2012/5/4 Phil Holmesm...@philholmes.net:
I think the way to do this would be to have makelsr.py extract the texidoc
and doctitle strings from the snippets and to put them into
Documentation/texidoc/. In principle it would delete them from the
Le 01/05/2012 00:55, Francisco Vila disait :
2012/4/30 Jean-Charles Malahieudelily...@orange.fr:
I've tried to understand how and when the mo files for the program are
built, in order to reproduce it for Documentation, and change
LYDOC_LOCALEDIR to point to $(top-build-dir)/Documentation/po/out
In CG 12.5 Website build, I read
create-weblinks-itexi.py creates a load of texi macros (of the order of
1000) similar to:
@macro manualStableGlossaryPdf
@uref{../doc/v2.14/Documentation/music-glossary.pdf,Music glossary.pdf}
@end macro.
It loads its languages from langdefs.py,
Le 24/04/2012 21:33, Janek Warchoł disait :
On Fri, Apr 20, 2012 at 11:54 PM, Graham Percival
I think it needs to come from people other than the main
developers, though. We're all too burnt out and overworked to get
enthusiastic about something like this.
Maybe.
As for the news, i suggest a
Le 24/04/2012 22:07, Janek Warchoł disait :
On Tue, Apr 24, 2012 at 9:54 PM, Jean-Charles Malahieude
lily...@orange.fr wrote:
Le 24/04/2012 21:33, Janek Warchoł disait :
On Fri, Apr 20, 2012 at 11:54 PM, Graham Percival
I think it needs to come from people other than the main
developers
Le 22/04/2012 19:59, David Kastrup disait :
Francisco Vilapaconet@gmail.com writes:
Hello, David and all,
I'd like the lilypond/translation branch to be renamed to just
'translation' if there are no objections. David, I recall you did
something similar for 'staging'.
A good moment would
Le 20/04/2012 23:42, Graham Percival disait :
On Fri, Apr 20, 2012 at 07:38:06PM +0200, Jean-Charles Malahieude wrote:
Le 19/04/2012 21:30, Graham Percival disait :
- nobody touches the release/unstable branch, other than
translators, who may merge with that if they want to and don't
Le 21/04/2012 10:57, Federico Bruni disait :
Il 17/04/2012 23:40, Francisco Vila ha scritto:
2012/4/17 Federico Brunifedel...@gmail.com:
Another solution could be keeping the current structure and
changing only
check-translation.py so that, when looking at the files in
Le 21/04/2012 12:33, James disait :
Hello,
On 21 April 2012 10:13, Jean-Charles Malahieudelily...@orange.fr wrote:
...
This makes me believe it would be a good opportunity to have the English
version follow the same rule as translations.
Err.. not sure what you mean by that technically but
Le 19/04/2012 21:30, Graham Percival disait :
We have a new release candidate, slower development, highlights on
development problems, and a vacation.
RELEASE CANDIDATE
As always, this means:
- activity on master goes on as normal.
- nobody touches the release/unstable branch, other than
Le 18/04/2012 16:29, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
I think that if everything goes well,
Documentation/snippets.splittexi.log should not weight that much with
all those lines like
** `Pitches' is up for `Pitches: Separating key cancellations from
Le 17/04/2012 11:46, Francisco Vila disait :
Hello all,
As you know, we translators are constantly aware of how much pendant
work we have, thanks to 'make check-translation'. For example, right
now
cd Documentation
make ISOLANG=es check-translation | wc -l
gives ten thousand lines as
Le 15/04/2012 14:56, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
lily...@orange.fr
To: Phil Holmes m...@philholmes.net
Cc: Lily Bugs bug-lilyp...@gnu.org; lilypond-devel
lilypond-devel@gnu.org
Sent: Saturday, April 14, 2012 5:46 PM
Subject: Re: issues 2266
Le 03/04/2012 23:17, Janek Warchoł disait :
On Mon, Apr 2, 2012 at 5:10 PM, m...@apollinemike.com
m...@apollinemike.com wrote:
Looks good! It's much more assertive and professional it's an easier read as
well. Good luck!
The application should now be publicly visible here:
Le 04/04/2012 13:06, Janek Warchoł disait :
Dear Team,
looks that taking a break in LilyPond work is impossible for me... ;)
How did you like the colorful Credo example posted in the LilyPond
Report #25
(http://news.lilynet.net/?The-LilyPond-Report-25lang=en#the_game_of_the_month)?
Not bad
Le 02/04/2012 00:19, Colin Hall disait :
On Sun, Apr 01, 2012 at 03:34:27PM +0200, Jean-Charles Malahieude wrote:
Unfortunately, the rewriting of NR-4.1.2 Paper size and automatic
scaling results in disappearance of the standard paper sizes which
now get only mentioned in an appendix
Le 01/04/2012 00:23, Colin Hall disait :
On Mar 31, 2012 at 07:47PM, Jean-Charles Malahieude wrote:
[...]
My questioning is: Why a same macro could behave differently when
in LM or in NR, and why, though they look identical do they work
differently according to the target manual?
Hi Jean
Hi all!
Unfortunately, the rewriting of NR-4.1.2 Paper size and automatic
scaling results in disappearance of the standard paper sizes which now
get only mentioned in an appendix.
This appendix needs a @ref (will be there in French after I have committed).
Cheers,
Jean-Charles
Hi all,
I just noticed something:
1- I overuse of @rlsrnamed{original,translated} in order to present a
translated link towards snippets, like @rlsrnamed{Pitches,Hauteurs}.
1-1 When in NR, this produces tons of lines in the logs like
WARNING: Unable to find node 'translated' in book
Le 22/03/2012 20:20, Jean-Charles Malahieude disait :
Le 22/03/2012 20:08, David Kastrup disait :
Jean-Charles Malahieudelily...@orange.fr writes:
The main problem in this case, in my opinion, is that you can't even
build a shortcut for combining melisma and autobeaming, since beaming
Le 18/03/2012 19:31, Phil Holmes disait :
http://codereview.appspot.com/5848056/diff/1/scripts/lilypond-book.py#newcode104
scripts/lilypond-book.py:104: progress(_ ('%s (GNU LilyPond) %s' %
(ly.program_name, ly.program_version)))
We don't need the _ (), we don't translate that string.
Julien
Le 09/03/2012 18:59, Janek Warchoł disait :
On Fri, Mar 9, 2012 at 6:36 PM, Jamespkx1...@gmail.com wrote:
Janek,
2012/3/9 Janek Warchołjanek.lilyp...@gmail.com:
Hi.
i'd like to give precise information on how long Lily supports
Unicode. I've searched changes on website, mailing lists and
Le 07/03/2012 15:29, David Kastrup disait :
I see rebasing commits like
commit 24f5f986998c23a1cbac15024d58ca6497093cce
Author: Julien Riouxjri...@physics.utoronto.ca
Commit: Francisco Vilafrancisco.v...@hispalinux.es
Doc-de: Compilation fix for de/notation.
commit
Le 07/03/2012 17:06, David Kastrup disait :
Jean-Charles Malahieudelily...@orange.fr writes:
Le 07/03/2012 15:29, David Kastrup disait :
which also appear in a version committed by their actual authors.
That's definitely not good. But I don't see how this would explain the
_loss_ of
Hi !
Regarding issues 2302 and 2311, which by the way are very comfortable,
I just noticed that no log file is deleted when running either
make doc-clean or make clean.
Cheers,
Jean-Charles
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Le 26/02/2012 14:30, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
Regarding issues 2302 and 2311, which by the way are very comfortable,
I just noticed that no log file is deleted when running either
make doc-clean or make clean.
Not sure if that's a good
Le 13/02/2012 14:56, julien.ri...@gmail.com disait :
Looks good, I just have a few suggestions to avoid clashing log file
names and I wonder how this part of GOP 9 might be implemented down the
road:
All other logfiles will go in the @file{build/logfiles/} directory.
Le 31/01/2012 14:21, David Kastrup disait :
David Kastrupd...@gnu.org writes:
Graham Percivalgra...@percival-music.ca writes:
The updated CG instructions for setting up git manually specify to
use clone:
http://lilypond.org/doc/v2.15/Documentation/contributor/setting-up
but the latest
Hi all!
Not only that I can no longer use -j on a first build (it is OK
on the next builds), which means 40' for a make doc LANGS='fr' and
about 2 hours for all languages, I now have to make doc-clean in
order to view a corrected typo. I've tried a touch masterfile.tely
before make doc but it
Le 22/01/2012 20:22, Julien Rioux disait :
On 22/01/2012 2:15 PM, Julien Rioux wrote:
On 22/01/2012 2:11 PM, Jean-Charles Malahieude wrote:
What I've done to check is:
open Documentation/fr/usage/running.itely
add the five X at the beginning of the first text line
XCe chapitre passe en
Le 21/01/2012 17:19, Graham Percival disait :
All release-Critical issues have patches which are either on a
current countdown, have been on a previous countdown, or don't
make sense to be on a countdown at all and will thus be pushed in
a few hours.
Unless any problem are found with the
Le 17/01/2012 21:31, Graham Percival disait :
On Tue, Jan 17, 2012 at 08:24:35PM +, janek.lilyp...@gmail.com wrote:
could we change this (and other similar) prefix so that it doesn't
contain a slash? I mean, change dev/ to dev- or something like that.
The slash confused me a lot, because
Le 27/12/2011 18:14, Phil Holmes disait :
More looking at make doc output. This set of error messages (Error:
Illegal entry in bfrange block in ToUnicode CMap) has been discussed
before, and it's not a Lilypond issue, it's to do with texi2pdf on
Ubuntu. Nevertheless, it does litter the output of
Le 24/12/2011 16:51, Janek Warchoł disait :
Merry Christmas to you all!
I brought you a present: I'm coming back!
Joyeux Noël à tous !
Jean-Charles
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hi !
Here is what I get on a fresh clone (Fedora 15 box).
Do I have to fear about it?
[jcharles@localhost Lily]$ git clone -l -s -n . ../Mentors
Cloning into '../Mentors'...
done.
[jcharles@localhost Lily]$ cd ../Mentors/
[jcharles@localhost Mentors]$ git reset --hard
HEAD is now at dd63de6
Le 27/08/2011 11:55, philehol...@googlemail.com disait :
This may be a repeat of what's in my reply, but two places is better
than none?
I'm trying to get rid of the hard-coded languages in website build,
so that making changes to the language list involves only a single
change in the source
Le 20/08/2011 16:26, Phil Holmes disait :
I think Reinhold's commit cfcb9efdbd7c6600fc89fc912ba80529010b31e7
has broken make doc. I've just done a clean build (fresh build
directory) and get this at the end of a failed make doc:
[...]
I had made a fresh build and make doc before pushing, and
Le 20/08/2011 17:26, Jean-Charles Malahieude disait :
Le 20/08/2011 16:26, Phil Holmes disait :
I think Reinhold's commit cfcb9efdbd7c6600fc89fc912ba80529010b31e7
has broken make doc. I've just done a clean build (fresh build
directory) and get this at the end of a failed make doc:
[...]
I
Le 11/08/2011 10:10, Trevor Daniels disait :
Graham
I vaguely remember commas should not be used in section headings, but
can't remember why. There is nothing about this in the CG that I can
find. Can you please remind me.
Trevor
You may not have a comma in a @node, but you can use it in its
101 - 200 of 331 matches
Mail list logo
