On Sat, Jan 09, 2010 at 03:08:09PM -0800, Patrick McCarty wrote:
> On 2010-01-09, Graham Percival wrote:
> > typography-demo.ly is already in the regtests. Do we want to keep
> > all the below?
> > - bach sarabande
> > - schubert morgenlier
> > - mozart horn con
On Sun, Jan 10, 2010 at 03:15:10PM +0100, John Mandereau wrote:
> Le vendredi 08 janvier 2010 à 23:02 +, Trevor Daniels a écrit :
> > Why not qualify each of these generic words? Like
> > Graham did with "Summary of contributing"?
>
> I second this for node names; as for section titles, they
(sorry, re-sending to list as well)
On Mon, Jan 11, 2010 at 7:23 AM, Mark Polesky wrote:
> Hey everyone. Here's a first draft of my idea for the new
> CG chapter 2.
Don't use $ in front of examples. It makes it impossible to
cut&paste! This is an abomination that probably started in printed
On Sun, Jan 10, 2010 at 04:41:21PM +0200, Dave Plater wrote:
> Hi, lilypond-2.12.3 is now available in openSUSE. It would be very much
> appreciated if someone could update the lilypond download page with this
> link :-
> http://software.opensuse.org/search?baseproject=openSUSE%3A11.2&p=1&q=lilypon
Some of you might have bookmarked
out-www/offline-root/Documentation/index.html
as your local lilypond docs. This file no longer exists; please
do a git pull -r, (and then make doc), and then use
out-www/offline-root/index.html
I don't expect this to matter for the 2.14 website. Once 2.13.11
On Mon, Jan 11, 2010 at 11:57:45AM -0800, Mark Polesky wrote:
> Is automated-engraving.itexi being used anymore? Graham
> removed these lines from essay.tely with commit 859f9f7 on
> Dec 5 2009:
>
> IIUC, it has been entirely replaced with similar material in
> the Essay. If so, should we get ri
On Tue, Jan 12, 2010 at 4:03 AM, Mark Polesky wrote:
> Graham Percival wrote:
> Of the two, I prefer "top...".
Ok. I suggest dropping the "sometimes"; let's make sure it's *always*
referred to as the "top source directory". Even if people never
On Tue, Jan 12, 2010 at 4:03 AM, Mark Polesky wrote:
> Graham Percival wrote:
>> I think a fair chunk of it will be wasted effort, but it's
>> *your* effort to waste.
>
> Geez, Graham, sometimes I wish you *would* mince a few words
> from time to time! I do
2010/1/12 John Mandereau :
> Le mardi 12 janvier 2010 à 12:31 +0000, Graham Percival a écrit :
>> now that John's
>> updated stable, I need to drop that work and start figuring out how to
>> get GUB to make 2.12.3-2.
>
> Why not releasing a 2.12.4 instead? Revisio
On Wed, Jan 13, 2010 at 01:19:30AM +0100, Francisco Vila wrote:
> 2010/1/8 John Mandereau :
> > Le vendredi 08 janvier 2010 à 12:15 +0000, Graham Percival a écrit :
> >> grr. If you add new files in master, check that you add them properly.
> >>
> >> file fro
On Tue, Jan 12, 2010 at 11:56:17PM -0800, Patrick McCarty wrote:
> On Tue, Jan 12, 2010 at 9:53 PM, Mark Polesky wrote:
> > "git-starting.itexi" 1076L, 35094C
That's trivially small. music-glossary.tely is 8755 lines.
> I wouldn't worry about, just as long as the texinfo files are
> separated
On Wed, Jan 13, 2010 at 8:16 AM, Mark Polesky wrote:
> Okay, here's a patch. Obviously, there's more work to be done,
> but it might be good to get the re-structuring stuff out of the
> way. `make' succeeded and `make doc' is still going, but I'm off
> to bed.
Looks mostly good.
- you've rever
I don't think we should be in the habit of naming all our releases after people.
Cheers,
- Graham
On Wed, Jan 13, 2010 at 2:39 PM, Francisco Vila wrote:
> Hello,
>
> if a nickname for 2.14 is still to be found, I'd like to propose
> "Taupin" for Daniel Taupin.
>
> http://www.google.com/search?so
2d334bce0e42631f1e07aa711c872f73b8 Mon Sep 17 00:00:00 2001
From: Graham Percival
Date: Tue, 12 Jan 2010 16:10:01 +
Subject: [PATCH] Keep branch name for lilypond-installer.
---
gub.make |2 +-
lilypond.make |3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git
On Wed, Jan 13, 2010 at 02:24:58PM +0100, John Mandereau wrote:
> Le mercredi 13 janvier 2010 à 12:20 +0000, Graham Percival a écrit :
> > Also, please
> > use @q{} in the @section name.
> > ... actually, could we just sidestep the whole issue by removing the
> > quo
On Wed, Jan 13, 2010 at 08:32:28AM -0800, Mark Polesky wrote:
> Graham Percival wrote:
> > - elsewhere in the docs, we use "foo -- bar", not
> > "foo---bar". I don't pretend to be authoritative about
> > the difference, though.
>
> I'v
On Wed, Jan 13, 2010 at 02:51:47PM -0500, Boris Shingarov wrote:
> How do I tell GUB to build Lilypond from a modified source tree which I
> have locally, instead of getting it from git?
Wow, you're brave! Look at lilypond.make; I believe you'll want
something like
make -f lilypond.make LILYPON
Suggestions:
1) stop sticking everything in the same thread; it makes it very hard
to keep track of what's happening.
2) I can't reproduce with some tests on programming-work.itexi based
on your description, so further debugging would be tricky for me.
3) this is a presentation issue, not a conte
On Wed, Jan 13, 2010 at 9:36 PM, Boris Shingarov wrote:
>> Oh, and make sure you're using the latest GUB; IIRC there are 2 or
>> 3 different git repositories floating around. You want the one at
>> github.
>
> git://github.com/janneke/gub.git -- this one, right?
Yes.
>> I believe you'll want so
On Wed, Jan 13, 2010 at 03:15:06PM +0100, John Mandereau wrote:
> Another thing that we could do instead of creating another list is
> writing down as a specification (even written quite informally) the
> important changes already started i.e. the i18n of Texinfo, stuff
> specific to building the w
On Wed, Jan 13, 2010 at 03:27:59PM +0100, John Mandereau wrote:
> I second this suggestion, except for the exclamation mark; I'd like
> something more explicit, like "[BUILD]" or "[DOCS BUILD]" or whatever
> depending on the area of the proposal. I suggest also to send such
> emails by always star
On Thu, Jan 14, 2010 at 2:49 PM, Boris Shingarov wrote:
> That's the very first thing I found, but that's NOT what you were talking
> about in the first e-mail. It is LILYPOND_REPO, which is a separate
> variable.
And I said I was guessing.
> You see, I read both the head revision and 2.11.64-1,
On Thu, Jan 14, 2010 at 3:56 PM, Boris Shingarov wrote:
>> By the way, do you have a good reason to build using GUB anyway?
>
> Because I read on the maillist that it was not possible to do a native build
> of lilypond for win32.
Umm. It would be *way*, ***way*** easier to download lilybuntu and
On Thu, Jan 14, 2010 at 4:17 PM, Boris Shingarov wrote:
>> Umm. It would be *way*, ***way*** easier to download lilybuntu and do
>> a normal compile in there
>
> Then I probably had misunderstood the purpose of Lilybuntu -- I thought this
> was for people who did not have a real linux setup for d
A few more thoughts:
- you can build just the mingw installer by doing
bin/gub mingw::lilypond-installer
- you can also give it a different git repo, and presumably a file
location(?), on the command-line, but I can't remember the
syntax.
- the "release work" chapter of the CG in git (*NO
Fixed. We were missing a pair of parentheses in a long
if (...)
statement.
Cheers,
- Graham
On Fri, Jan 15, 2010 at 2:15 AM, Mark Polesky wrote:
> I pushed the main draft of my changes to the CG Git chapter.
> I mentioned a confusing TOC-pane behavior in an earlier
> email:
>
> http://lists.
On Thu, Jan 14, 2010 at 08:46:17PM -0800, Mark Polesky wrote:
> In the pdf output of my CG patch, I noticed that the hyphens
> in "@code{--rebase}" got separated from the word "rebase":
Oops, I just noticed the "pdf output" part. In this case, the
@{...@code{--foo}} would definitely help.
Of cou
On Fri, Jan 15, 2010 at 09:57:16AM -0800, Mark Polesky wrote:
> Graham Percival wrote:
> > This one is preferred, but I'm pretty certain that
> > texi2html doesn't do anything with @w{}. If you're
> > inspired, please test this with a minimal .texi file,
>
Similar to the GLISS webpage, I have the pre-planning notes online:
http://lilypond.org/~graham/gop/
If you think we need to add anything, let me know. Also similar
to GLISS, this won't be starting until after 2.14.
Cheers,
- Graham
___
lilypond-deve
On Fri, Jan 15, 2010 at 07:14:54PM +0100, Jean-Charles Malahieude wrote:
> Yes, but I thing it would be a good habit that the @w encloses what is
> to be said. If I'm not misunderstanding, it would allow us to use
>
> @w...@command{run} @var{variable}}
>
> instead of
>
> @command{r...@tie{}@var{v
On Fri, Jan 15, 2010 at 04:19:58PM -0800, Mark Polesky wrote:
> Graham Percival wrote:
> > Is there a way in HTML to prevent a line break? If so,
> > does anybody want to add it to our init file, and/or get
> > it into mainline texi2html?
>
> Shouldn't @comm
LTGM
although I'd put input/ under REGRESSION TESTING, and elisp/ +
vim/ under MISC, or something like that. But it's definitely an
improvement over the current file. Please push.
Cheers,
- Graham
On Fri, Jan 15, 2010 at 10:27:42PM -0800, Mark Polesky wrote:
> ROADMAP has always confused me.
Looks fine to me:
http://lilypond.org/doc/v2.13/Documentation/changes
(hint: since this changed something in mf/, you need to do a make
doc-clean, make clean, why not make distclean, and then rebuild
everything from scratch. Yes, this is already in the issue tracker)
Cheers,
- Graham
On Sat, Ja
On Sat, Jan 16, 2010 at 4:59 PM, Mark Polesky wrote:
> A while back I proposed the name "lilypatch" for what is now
> "lily-git". I didn't hear any response so I suppose that
> most of you prefer the current name. I thought I'd mention
> it once more though, because I like the pun on the word
>
One idea that I've been considering for over a year is making a
"social" mailing list for lilypond developers. Not for discussing
bugs or new features; just to get to know each other better.
Think of it as the electronic equivalent of office-mates going to
the pub together on a Thursday night. I
On Sat, Jan 16, 2010 at 04:15:22PM -0800, Patrick McCarty wrote:
> On 2010-01-16, Graham Percival wrote:
> > I'm thinking that an open mailing list with no archives would be
> > ok, but we could make it closed instead if we wanted to feel a bit
> > more private.
>
&
Patrick,
I'm a bit confused by some of the changes to the git commands for
release/unstable. Doesn't
git merge release/unstable
produce the ugly (and pointless) "merge remote branch" in the git
history for master? I'd rather avoid that, and I thought that
git cherry-pick release/unstable
wou
On Sat, Jan 16, 2010 at 06:19:08PM -0700, Carl Sorensen wrote:
>
> On 1/16/10 11:14 AM, "pound...@lineone.net" wrote:
>
> > When building LilyPond I was confused that the general build
> > instructions (3.1.3) were different from the instructions for building
> > on a Virtual Machine (3.3), in
If you get a build error while processing the docs (even with just
plain make), do a
make -C scripts
and then
make
again. The build system doesn't pick up my latest change automatically.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypon
On Sun, Jan 17, 2010 at 6:27 PM, Patrick McCarty wrote:
> On 2010-01-17, Graham Percival wrote:
>> I'm a bit confused by some of the changes to the git commands for
>> release/unstable.
>
> It's a trade-off.
Ah, ok. I now agree that the "merge" is the
On Mon, Jan 18, 2010 at 11:29 PM, Mark Polesky wrote:
> I've attached a patch for gub that incorporates this; let me
> know if you don't like it...
Looks ok.
> One question, though: I
> changed the text in lilypond-sharhead.sh, but do I also need
> to change it in sharhead.sh?
Dunno, but a fres
2010/1/19 John Mandereau :
> Le lundi 18 janvier 2010 à 16:13 -0800, Mark Polesky a écrit :
>> Here's a small patch to clean up the `make help' output.
>
> As for any portability issue, you can't simply remove the "-e" just
> because it works better for you.
There's two issues here: the changed te
On Tue, Jan 19, 2010 at 4:23 PM, Francisco Vila wrote:
> 2010/1/19 Francisco Vila :
>> scripts/build/create-version-itexi.py
Yesterday it was put in scripts/build/create-weblinks-itexi.py, BTW.
>> def make_download_source(name, vstring, version):
>>
>> accepts an additional argument prefix="So
On Wed, Jan 20, 2010 at 11:01:24AM -0500, Boris Shingarov wrote:
> But for me the whole thing about GUB is driven by the organizational
> side: as a developer, I am completely happy with the Linux development
> platform, and am much more interested in furthering Lilypond rather than
> trying t
On Thu, Jan 21, 2010 at 09:24:32PM +0100, Jean-Charles Malahieude wrote:
> Attending to a seminar about French typography, I've printed several
> pages of "notation.fr.pdf", and noticed something disturbing.
> -8<
> See also
>Notation Reference: Section A.8.1 [Font], page
Does anybody object to this patch? Alternately, is anybody
willing to rewrite the GNUmakefile portion to make it like a real
makefile?
Cheers,
- Graham
>From 5cee5fd0b10f4a6ed8f86de4591cda23bea1ec27 Mon Sep 17 00:00:00 2001
From: Graham Percival
Date: Fri, 22 Jan 2010 00:18:18 +
Subj
2010/1/22 John Mandereau :
> Le vendredi 22 janvier 2010 à 00:35 +0000, Graham Percival a écrit :
>> Does anybody object to this patch?
>
> I don't care too much for the makefile, but please fix the shebang of
> the Python script -- it should be the same as the ones of ot
On Fri, Jan 22, 2010 at 02:45:19PM -0800, Mark Polesky wrote:
> Documentation editor's edit/compile cycle:
> Initial:
> make
> make doc
Yes, although many people would want to do something like
make -j3
make doc -j3 CPU_COUNT=3
> Cycle:
> [edit source files]
> make<--
On Sat, Jan 23, 2010 at 02:54:16AM -0800, Patrick McCarty wrote:
> BSTINPUTS=./essay /home/pnorcks/git/lilypond/scripts/build/out/bib2html \
> -o ./out/colorado.html \
> ./essay/colorado.bib
>
> bibtex: Not writing to /tmp/tmpSnvwo5bib2html.blg (openout_any = p)
Hi Nick,
Could you add some info about grand-replace.py to the CG? I'm
thinking in the "release work" chapter, in the "administrative
policies" section.
We might split some of this chapter off into a "general
maintenance" chapter, but I'd like to get the info in the CG
_somewhere_ before we forg
Good news: we're down to 18 release-blocking items: 9 code, and 9
non-code. I can't really estimate the time required to fix the code
regressions. The other items are all 2-10 hours. So 2.14 might
happen in Feb. Granted, this doesn't include any new regressions that
we might discover when we an
Hi Francisco,
Thanks for fixing the broken link, but this still looks suspect:
-
An introduction to Guile/Scheme as used in LilyPond can be found in the
-Learning Manual, see @rlearning{Scheme tutorial}.
+Learning Manual, see @rextend{Scheme tutorial}.
--
Since it's in @rextend, surely
On Wed, Jan 27, 2010 at 06:12:14PM -, Trevor Daniels wrote:
>
> Neil Puttock wrote Wednesday, January 27, 2010 5:38 PM
>>
>> There's nothing in the documentation policy for \context block
>> formatting,
The patch is being written by James Lowe.
>> I much prefer the context name to be on the n
On Wed, Jan 27, 2010 at 10:33:45PM +0100, Harmath Dénes wrote:
> Latest revision in lilypond-translation branch gives the following build
> error when running make all:
>
> make PACKAGE=LILYPOND package=lilypond -C ly-examples all && make
> PACKAGE=LILYPOND package=lilypond -C server all && tru
On Thu, Jan 28, 2010 at 01:01:16AM -, Trevor Daniels wrote:
>
> Graham Percival wrote Wednesday, January 27, 2010 6:43 PM
>
>> I'm happy with having a newline there, but please glance over the
>> LM stuff you wrote, and confirm that you prefer it with a newline.
>
On Thu, Jan 28, 2010 at 8:27 PM, Patrick McCarty wrote:
> I believe 2.8.0 has a fix for font-cache corruption that was
> introduced in 2.7.3, so here's patch to bump the version.
Go ahead and test:
http://lilypond.org/~graham/
Cheers,
- Graham
___
li
On Thu, Jan 28, 2010 at 02:51:49PM -0800, Patrick McCarty wrote:
> On Thu, Jan 28, 2010 at 2:22 PM, Graham Percival
> wrote:
> > Go ahead and test:
> > http://lilypond.org/~graham/
>
> Is this based on latest master, or the merge commit before that?
Hmm... I just did
,
- Graham
>From b51656614f8e76da5912ffd6ce1377f7a95f1fb4 Mon Sep 17 00:00:00 2001
From: Graham Percival
Date: Sat, 30 Jan 2010 00:02:46 +
Subject: [PATCH] Doc: move divisiones.ly into Ancient.
Translations: I did the same thing here to retain compiling;
hopefully this doesn't break
On Fri, Jan 29, 2010 at 05:47:03PM -0700, Carl Sorensen wrote:
> On 1/29/10 5:15 PM, "Graham Percival" wrote:
>
> > Does anybody know if I can push this patch? It removes
> > Documentation/included/divisiones.ly and puts that info in the
> > main .itely fil
The devel-chat list is now up. It's on lilynet.net:
http://lists.lilynet.net/devel-chat/
If you're intrested, sign up. I'll start complaining about my
supervisor and the mess that is his C programming course in a few
days, and I'm sure that nobody wants to miss that. :)
I won't count devel-
When I'm staring at a directory of files, "working.itexi" doesn't give
any clue about the contents of the file, so I renamed it.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-deve
On Sat, Jan 30, 2010 at 3:55 PM, Neil Puttock wrote:
> Following your fontconfig caching improvements, my
> fetaNumber/fetaDynamic glyphs have disappeared (see attached image).
Problem confirmed with a freshly-built GUB binary from lilypond master
032a7f20fcf23ae1002809e4e63778029ba22df5. This i
On Sat, Jan 30, 2010 at 5:12 PM, Trevor Bača wrote:
> http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/Avoiding-tweaks-with-slower-processing
>
> ... the language in the LM is somewhat ambiguous as to whether
> keep-inside-line settings speed things up or slow things down.
>
> QU
Carl, why did you push the recent change to Clef?
1. no contractions, please. I'm not convinced about the new
language there, anyway -- what about "(but are not required to
be)" ?
2. we have a policy of "show, don't tell". Why did we remove
\clef G, F, C from the example?
If there's a desire
On Sun, Jan 31, 2010 at 07:51:03PM -0700, Carl Sorensen wrote:
>
> On 1/31/10 11:55 AM, "Patrick Schmidt" wrote:
>
> > OK, so how about placing them closer to the treble, alto and bass clefs to
> > show that they can be used alternatively?
>
> I'd be fine to have \treble \G \tenor \C \bass \F.
On Sun, Jan 31, 2010 at 07:38:42PM +, Neil Puttock wrote:
> On 31 January 2010 17:59, Jean-Charles Malahieude wrote:
>
> > It might help to keep in mind that the documentation is produced in 7 other
> > languages than English. There is then 1 instance missing?
>
> No, it's surely a bug (if
On Tue, Feb 02, 2010 at 02:40:28PM -0800, Patrick McCarty wrote:
> I need this patch for the latest updates to bibtex in TeX Live 2009 on
> my machine. LilyPond fails to compile the bibliographies without it.
A quick glance at the patch looks ok, but I'll test it thoroughly
tomorrow. Once you ig
I remember seeing some discussion and patches about fonts. If I'm
not hallucinating, then any font-related contributor for 2.14 who
isn't an official developer should be listed in
Documentation/included/authors.itexi
in the fontCurrent macro.
If contributors worked in multiple areas, they shoul
On Tue, Feb 02, 2010 at 02:54:18PM -0800, Patrick McCarty wrote:
> On 2010-02-02, Graham Percival wrote:
> > A quick glance at the patch looks ok, but I'll test it thoroughly
> > tomorrow. Once you ignore the superfulous tempfile -> tmpfile
> > change, there isn&#x
On Wed, Feb 03, 2010 at 10:25:44AM +0100, Francisco Vila wrote:
> Currently, notation/world.itely mixes 'maqam' / 'maqams' and 'makam' /
> 'makamlar'. Is this correct for Arabic/Turkish respectively, or should
> it be unified?
I believe that both "k" and "q" are acceptable English
representations
We officially only require python 2.4 for lilypond. Could the recent
change to ilypond-book.py be rewritten to avoid using the "any"
keyword introduced in 2.5 ?
File
"/main/src/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/scripts/lilypond-book.py",
line 2194,
Thanks, tested and applied.
Cheers,
- Graham
On Tue, Feb 2, 2010 at 10:40 PM, Patrick McCarty wrote:
> Hi,
>
> I need this patch for the latest updates to bibtex in TeX Live 2009 on
> my machine. LilyPond fails to compile the bibliographies without it.
>
> Here are the references for backgroun
On Thu, Feb 04, 2010 at 09:25:01PM +, Werner wrote:
> In the NR of version "2.11.57" I found:
Why are you look at that version? It's an UNSTABLE DEVELOPMENT
version, which normal people should not be using.
> Instrument names may be changed in the middle of a piece:
> \set Staff.instru
On Fri, Feb 5, 2010 at 9:46 AM, Patrick McCarty wrote:
> Here's the actual list of steps:
>
> - Change the current working directory to the outdir
> - Create the .aux file
> - Invoke `bibtex' on the .aux file
> - Read the .bbl file and write it contents to the .html file
That should work... altho
Definitely, thanks! James, please do this. In fact, add 2 and -2 to
the example as well, and remove the final text sentence of the main
section.
Cheers,
- Graham
On Fri, Feb 5, 2010 at 3:40 PM, Werner wrote:
> There are three examples in the doc.
>
> 8va
> 8
> text
>
> always \ottava #1
>
> P
Why did you remove tab and percussion clefs from the clef section?
The general idea is that anything that could make sense in NR 1
goes there, other than ancient notation, and NR 2 links back to NR
1 in the relevant "references for..." subsection.
I won't complain about adding a tab clef to frette
On Mon, Feb 08, 2010 at 12:29:48PM +0100, David Kastrup wrote:
>
> +Even if you are not familiar with git or are not able to compile
> +LilyPond you can still help to narrow down the cause of a regression
> +simply by downloading the binaries of different LilyPond versions
> +and testing them for
On Mon, Feb 08, 2010 at 09:46:59AM -0200, Han-Wen Nienhuys wrote:
>
> The release rate of the LilyPond has gone down from once per week to
> once per month (at most).
In the past few months, it's gone back to once per two weeks:
LilyPond 2.13.12 released! February 2, 2010
LilyPond 2.13.11 releas
On Mon, Feb 8, 2010 at 12:02 PM, David Kastrup wrote:
> Graham Percival writes:
>
>> On Mon, Feb 08, 2010 at 12:29:48PM +0100, David Kastrup wrote:
>>>
>>> +Even if you are not familiar with git or are not able to compile
>>> +LilyPond you can still help t
On Sun, Feb 7, 2010 at 10:02 AM, Patrick Schmidt wrote:
> Hi Graham,
>
> I moved the tab clef to fretted-strings and the percussion clef to percussion
> for the following reasons:
>
> 1) (in a strict sense) they don't display pitches (1.1.3 Displaying pitches)
That's a nice argument, but it does
Hi all,
Valentin and I are bringing back the LilyPond Report. The current
plan is one issue every two months. If more people get involved,
we might make it once a month.
I'm not going to bother with any of the cutesy fun stuff like
snippets, interviews, postcards, statistics... or pretty much
a
Could anybody who cares about chord names look at this file:
Documentation/included/chord-names-jazz.ly
It contains these comments:
%% This is the Banter (1987) style. It gives exceedingly
%% verbose (wide) names, making the output file take up to 4 pages.
%% (FIXME: h
t 4:15 PM, Francisco Vila wrote:
> 2010/2/11 Graham Percival :
>> If these must be fixed before 2.14, please fix them now.
>
> If this means that 2.14 is imminent, please remember that the docs
> have been a moving target until just now. There are some broken links
> in th
We're down to 13 FIXMEs in the docs. More to the point, there's 2 in
automated-engraving (which is old, not compiled, and should be removed
as soon as somebody's reviewed the new
essay), and 13 in contributor/source-code.itexi.
Mark, are you still working on CG 2?
Cheers,
- Graham
Does the new essay contain all the info we want to save from
automated-engraving ?
I don't care about the formatting, lack of sections, or whatever. I
just want to delete the old .texi files which were extracted from the
old website.
If Andrew thinks that the new essay fulfils this condition, th
I've bumped nsis to 2.4.6. Could somebody check if it still installs
+ uninstalls in a manner which is no worse than 2.13.12 ?
http://lilypond.org/~graham/
PLEASE NOTE: I haven't tried using any of the new functions in nsis
2.4.6; I don't expect this version to be *better* than 2.13.12. If
it's
I've tweaked the list of dirs to remove from
share/ghostscript/Resources. The resulting files are (on average) 5
megs smaller. linux-x86 works here for me.
Could we get a few tests for various OSes?
http://lilypond.org/~graham/
(mingw is "mingw-new.exe", to avoid a clash with the nsis 2.4.6
On Fri, Feb 12, 2010 at 7:06 PM, Kieren MacMillan
wrote:
> Hi Graham,
>
>> Could we get a few tests for various OSes?
>> http://lilypond.org/~graham/
>
> Mac OS X 10.6 is aok.
> It also seemed that "first compile" was almost instantaneous, as compared
> with earlier upgrades -- is this a chang
On Fri, Feb 12, 2010 at 08:55:10PM +0100, Francisco Vila wrote:
> Runaway argument?
> version "@w...@version{}}"^...@{^^mc' e' g' e'^...@}^^m@end example^^m...@etc.
> ./included/generating-output.texi:238: Paragraph ended before \ was complete.
I remember seeing this earlier in the week. Make sur
On Fri, Feb 12, 2010 at 08:37:00PM +0100, James Bailey wrote:
>
> One thing I find very helpful is to have a short list of things to check
> for when doing these kinds of quick version test. I haven't really worked
> very hard on it, but here's kinda the things I do so far when looking at
> chec
On Tue, Feb 09, 2010 at 11:47:14PM +0100, Francisco Vila wrote:
> Hello. The google filter for our search box in the new webpage applies
> +2.12, shouldn't it be +2.13 instead?
I don't think so, but I've added a note to issue 815 to consider
this.
Cheers,
- Graham
__
On Sat, Feb 13, 2010 at 01:39:08AM +0100, Francisco Vila wrote:
> e600412e50db9e8ee3b9e408527322b84b946f52 Doc build: make
> screenshot-tutorials shared.
>
> one tends to think that only blocks of text were moved or files
> renamed. It is impossible, (and check scripts do not help on that) to
>
On Sat, Feb 13, 2010 at 11:23:25AM -0700, Carl Sorensen wrote:
>
> On 2/13/10 10:45 AM, "Christian Hitz" wrote:
>
> > In order to verify the fix I have added a new regression test suite
> > lilypondbook_html. It tests the lilypond-book operation when processing HTML
> > files. Most of the patch
On Thu, Feb 11, 2010 at 11:39:57PM -0800, Mark Polesky wrote:
> This one might be easier for someone other than me*:
> 23: Add instructions for using @command{lily-git} here.
> *I don't remember if I said I'd write it, but I haven't done
> any work on it. If someone who's more familiar with it
> w
On Fri, Feb 12, 2010 at 01:52:01PM -0800, Patrick McCarty wrote:
>
> *** Warning: GenericResourceDir doesn't point to a valid resource directory.
>the -sGenericResourceDir=... option can be used to set this.
>
> WARNING: /Unicode /Decoding r
Anybody want to take a stab at getting the website translations to
build? With the attached patch, I can get a bunch of files in
out-website/es/ -- but most of them are index_xy.html, and half of the
filenames that have proper names are capitalized.
Since I just copied the command for the regular
On Sun, Feb 14, 2010 at 2:18 PM, Christian Hitz wrote:
> the attached patch fixes the HTML tag in lilypond-book.
Thanks, applied.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-
On Sun, Feb 14, 2010 at 1:01 AM, Graham Percival
wrote:
> Anybody want to take a stab at getting the website translations to
> build? With the attached patch, I can get a bunch of files in
> out-website/es/ -- but most of them are index_xy.html, and half of the
> filenames that have
On Tue, Feb 16, 2010 at 12:34 AM, Trevor Daniels wrote:
> While answering a user question I noticed that
> some examples in the LM which were earlier on
> a single line now spread undesirably over two lines in both html and pdf
> versions. You can
> see several examples in 4.5.3.
> I'm happy to f
On Tue, Feb 16, 2010 at 08:02:11PM +0100, John Mandereau wrote:
> Il giorno mar, 16/02/2010 alle 15.23 +, Trevor Daniels ha scritto:
> > The change seems to have started after commit
> > c258b7788db8a717b4741f02d9f5cc52862338d4
> > which was applied by John on Christmas Eve.
> > As part of his
701 - 800 of 1310 matches
Mail list logo
