Hello,
Texi2html 1.80 is out! Do you think it's all right to remove support
for "makeinfo --html" in one week?
I think we should support Texi2html 1.80 during all 2.12 series and not
require Texi2html from CVS again before we start 2.13.
Cheers,
John
_
Do we want to keep buildscripts/git-update-changelog.py?
This script was designed to update Savannah CVS with changes made in
git.or.cz Git repository during the transition between the two revision
systems. We no longer need this script for this purpose, but with a bit
of hacking we could still u
Le vendredi 02 janvier 2009 à 13:34 +, Ian Hulin a écrit :
> Grahame,
His name is Graham.
> Can you, John or Han-Wen do
> gmane.comp.gnu.lilypond.announce?
Some time has flown since 2.12.1, so I just did it.
We are a bit confused, as 2.12 stable series begin while tasks with high
responsab
Le jeudi 01 janvier 2009 à 21:26 -0800, Graham Percival a écrit :
> While I was working on the new website, I realized that the info I
> was adding would work better as a manual rather than a few web
> pages. Therefore, in Feb (after 2.13 starts), I'll be creating a
> new manual: the Contributor's
Le vendredi 02 janvier 2009 à 18:37 +, Carl Sorensen a écrit :
> I haven't heard anything back on this patch, probably because I chose a bad
> subject line. I'd appreciate if it could be reviewed.
The recommended subject is "[PATCH] subject of the patch" regardless of
the form of the patch (
Hi Jan,
Have you any plan for maintaining Scons support in LilyPond? The Python
code hasn't been updated to be compatible with Python 2.6/3.0, and it
calls scripts in stepmake/bin or buildscripts that have been removed
several years ago. If we have no interest in maintaining this, I
propose to r
Le vendredi 02 janvier 2009 à 16:11 -0600, Jonathan Kulp a écrit :
> It occurred to me today that it would be nice if Lilypond could use
> \include to include files that are hosted on a website, the way html
> pages use stylesheets. Something like this:
>
> \include "http://www.websiteaddress.c
Le vendredi 02 janvier 2009 à 23:26 +0100, Valentin Villenave a écrit :
> Gosh, John was faster than me :)
I was this time only, but I go back to studies next Tuesday.
Cheers,
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.g
sv.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=Documentation/TRANSLATION;hb=lilypond/translation
Then you can get the full changes patch by issuing
git diff release/2.11.62-1 release/2.12.1-1
Append Documentation/user to the command above to restrict the patch to
fi
Le samedi 03 janvier 2009 à 20:54 +0100, Jan Nieuwenhuizen a écrit :
> I was hoping someone would see the beauty of scons and
> junk our stepmake cruft ;-)
I'm afraid it is too late to resurrect SCons, or too early if you
prefer. I remember a number of packages used a so-called revolutionary
prog
Le vendredi 02 janvier 2009 à 18:52 -0800, Graham Percival a écrit :
> I'll have the pdf on my
> website for GOP, and after the first few weeks, this document
> shouldn't be changing much, so the normal stable release will be
> fine.
IMHO a few weeks won't be enough for stabilizing the Guide, but
On 2009/01/04 14:08 +, Sawada, Yoshiki wrote:
> Yes, it is my hope to provide LilyPond community with my translation.
> I am not a professional for music or translation, so my Japanese
> document is not so good. But I hope someone will brush it up.
You may want to contact Yoshinobu Ishizaki
w
Le dimanche 04 janvier 2009 à 20:54 -0200, Han-Wen Nienhuys a écrit :
> Please junk
Done, and did the same for metapost-*.make.
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Han-Wen,
Sorry for the quite unreasonable delay, but I hope I've sorted out GCC
warnings mentioned in this thread.
Le samedi 08 novembre 2008 à 16:59 -0200, Han-Wen Nienhuys a écrit :
> +#define EPSNULL 1e-12
> this looks fishy. Why another EPS value? Joe?
I apologize for this obviously wr
Le dimanche 04 janvier 2009 à 00:39 +0100, John Mandereau a écrit :
> I will include this removal in the patch that splits stuff in
> buildscripts.
I actually made two commits, because these two issues only intersect at
builder.py and these commits are large enough.
Cheers
ot;"
commit 591dcd1740655062b541f2ca273147882bea3f9d
Author: John Mandereau
Date: Sat May 24 09:48:38 2008 +0200
Update TRANSLATION
"""
> I copyed
> http://lilypond.sourcearchive.com/documentation/2.10.33-2ubuntu1/langdefs_8py-source.html
> to buildscripts. Th
Le lundi 05 janvier 2009 à 15:32 +, Trevor Daniels a écrit :
> I have a git problem with your recent commit
> c553fc2251b508befebd1dc297c4baa898463f34 to clean up the build scripts.
> The reason is that aux is a reserved word in Windows, along with a few
> others like com, lpt1, nul, prn, Lp
Hi Till!
Till Rettig a écrit :
Was there already discussion on translating also the NEWS part of the
documentation? It might not be really used by many people when 2.12 has
become normality but for the moment it might be interesting since it
also has a direct link from the news entry on lilypon
Graham Percival a écrit :
Could I get this dir created and added to the build scripts? I'd
like to move the stuff from web-gop/texinfo/contributing into
there, so that Carl can see what's there and add to it.
Done.
BTW I'll look at integrating Texinfo docs in web-gop after Jan. 19th, as I'm
Frédéric Bron a écrit :
Hi, is there a chance that we have a 2.12.1 release for cygwin?
Using 2.10.33 on cygwin was great, I'd love to switch to 2.12.1.
Have you already tried MinGW binary available on lilypond.org?
You can run it from Cygwin if you set the PATH accordingly, and it is
probably
Hi Graham,
Graham Percival wrote:
If anybody doesn't like it (and doesn't know/feel like fixing it),
just revert that commit.
Reverting commits is not good for the moral. It's best not to break
compilation on master though, so I suggest you create a branch dev/gpercival
if you like. That sa
Graham Percival a écrit :
On Sat, Jan 10, 2009 at 08:12:49AM +0100, Frédéric Bron wrote:
- I have mainly copied documentation from the Notation Manual. Would be
better to enter the documentation only once because if the function
changes, we have to change the doc. at two locations.
De
Carl D. Sorensen a écrit :
I propose something different. I think the current NR documentation is
right, with a usage description in the section of the NR, and a short
description from the docstring in the appendix that lists all music
functions. The reason I use the Identifiers page is that it
Frédéric Bron a écrit :
That's what I did before 2.10.33. But then, cygwin came with the right
lilypond version and I preferred switching to cygwin.
I have now installed mingw version of lilypond. However, who/how was
lilypond added to cygwin?
Bertalan Fodor used to do it when MinGW binaries di
Neil Puttock a écrit :
Hi Carl,
2009/1/10 Carl D. Sorensen :
Any thoughts on what is wrong or how I can get this patch to apply?
It applies OK using `git am'.
BTW git-apply should be used for patches without authoring information, i.e.
patches not made with git-format-patch.
Cheers,
Joh
Carl D. Sorensen a écrit :
fatal: git apply: bad git-diff - expected /dev/null on line 46
Patch failed at 0001.
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "g
Hi Reinhold,
Reinhold Kainhofer a écrit :
So, apparently, ./conftest can't find the libltdl.so.3 any more (which it was
linked against), since the tools directory is no longer in LD_LIBRARY_PATH...
It seems that while building (and of course also when running) all the tools,
we still need the to
Carl D. Sorensen a écrit :
fatal: git apply: bad git-diff - expected /dev/null on line 46
Patch failed at 0001.
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "g
Carl D. Sorensen a écrit :
Are "diff --git a/... b/..." lines broken in the patch you actually tried to
apply? They should not be broken, I guess.
No, they're not broken. It's one line.
Ugh, I'm almost short of ideas; which OS do you use to work with Git? Could
a non-Linux system be confu
Reinhold Kainhofer a écrit :
Am Samstag, 10. Januar 2009 18:49:40 schrieb John Mandereau:
Have you tried installing libtool-ltdl-devel (or whatever this Fedora
package is called on Ubuntu) system-wide?
Yes, it is installed:
lilyp...@server:~$ locate libltdl.so
/usr/lib/libltdl.so
/usr/lib
Patrick McCarty a écrit :
`make all' fails on current master. Is this because the new
directory, Documentation/es/topdocs/, doesn't have a makefile yet?
It had the makefile on my working tree, but I forgot adding it to Git :-/
make[3]: Entering directory
`/home/pnorcks/git/lilypond/Document
Ian Hulin a écrit :
(Apolgoes to the list for this coming late, I'm sorting out my subscription via
gmane)
Hi Carl,
Here's a patch for ny bit of the first Frogs Task, but I've got some questions.
Hi Ian,
I wouldn't have applied your patch as this is up to Carl, but could you
resend it eit
Carl D. Sorensen a écrit :
I've only used @code{} because I saw it in the docs before I started.
I think @var{} makes more sense.
Anybody on -devel have a definitive answer to this question?
The purpose of @var is marking variables (but not names of predefined
variables), so let's use it as
Hello Yoshiki,
Thanks for your quick work on the Learning Manual.
Sawada, Yoshiki wrote:
My patches look dirty because I changed something on scripts directries to do
"make web" completely.
It looks like you reverted some changes to get the documentation to compile.
I've certainly left the
Carl D. Sorensen a écrit :
Graham and Trevor,
This mail below, from -user, shows why I think NR 5 and NR 6 should be
combined into one chapter, something like Extending LilyPond.
I rather agree with Trevor that these chapters should remain separate (in
thread Learning Manual TOC missing subsu
Carl D. Sorensen a écrit :
When I make changes to ly/music-functions-init.ly (which will affect
Appendix B.14 of the Notation Reference), then run
the documentation is not updated to reflect the changes in
ly/music-functions-init.ly.
Should I post this to bug?
No, issues with makefiles shou
Carl D. Sorensen a écrit :
This sounds good to me. I'd much rather trigger recompilation more often
than miss a change.
Done: lilypond-book will be called if at least one file in ly/*.ly or
scm/*.scm is newer than .texi output, which is enough to regenerate the
Internals Reference and other
Hi Matthieu,
Matthieu Jacquot a écrit :
File "../../scripts/lilypond-book.py", line 43, in
import lilylib as ly
ImportError: No module named lilylib
make: *** [web-1] Error 2
ma...@gentoo ~/site/lilydoc $
Maybe I missed something, here's what I've done :
I only pulled the tran
Hi Jan,
Jan Nieuwenhuizen a écrit :
After 2.12 I decided to do my small round checking of distributions
again
Super; I think it's a good idea to go on mentioning distros that provide
latest stable on the download page, so I've added links for Fedora and
Slackware.
(should we add something
Hi Han-Wen,
Han-Wen Nienhuys a écrit :
someone added a japanese translation of the docs, but after enabling
it (so it is distributed), I get error (see below). Can someone fix
this, or disable the translation? This is a blocking issue for
releasing 2.12.2.
I suggest not to enable it or revert
ns available
earliest makes proofreading them by other people easier and speeds it up
(except I couldn't reply as quickly as I'd like lately).
Best,
John Mandereau
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Sawada a écrit :
I'm sure. Perhaps, we should not include Japanese translation in the source
codes until Texinfo supports Japanese. However, I want to make my translation
available in the web.
As it's possible to distribute Japanese translation at least in one compiled
format, namely Texi2HTML
Han-Wen Nienhuys a écrit :
Can you make it so doc and web take a different set of languages? For
the tarball distribution, I still want to build the PDFs.
I'm not sure I understand what you mean with 'doc' and 'web', I assume PDF
and HTML, respectively. Japanese docs compilation will remain
Han-Wen Nienhuys a écrit :
I can't remember the status of this change, but LGTM
Thanks, applied.
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Sawada a écrit :
It is good that Texi2HTML can handle Japanese even if Texi2DVI cannot handle it.
I think we should turn off texi2dvi for Japanese Documentation.
Yes, this is what I did in the makefiles.
I provided all files which were created by "make ISOLANG=ja new-lang".
The command produ
Yoshiki Sawada wrote:
The second patch in it is the new patch. Try it, please.
If there are something to fix or do more, tell me.
I should have replied earlier to other messages... I applied all changes
that didn't add files related to the Notation Reference or Application
Usage, and made a s
Hi Graham,
Graham Percival a écrit :
How hard would it be to compile the CG with
--split=sections
instead of the current setting?
I have the following in my compilation log on Jan 24th:
make[3]: Entering directory `/home/lilydev/git/lily/master/Documentation/devel'
cp -f contrib-guide.texi o
Graham Percival a écrit :
Has anything urgent happened since 2.12.2 was released? I can't
think of anything.
Unless anybody complains within the next 48 hours, we'll switch to
2.13 and get started with all the major changes.
What major changes are expected? Are there already significant chan
Sorry for double posting, I hit the key for sending too early.
Graham Percival a écrit :
Has anything urgent happened since 2.12.2 was released?
Yes, the Japanese translation. I think it deserves a 2.12.3.
I can't
think of anything.
What about posting an announcement on info-lilypond an
Yes, the Japanese translation. I think it deserves a 2.12.3.
Good point. OK, we'll wait a week or so.
That's perfect.
Yes, that's totally my job. Umm... do you mean about 2.12.2, or
about 2.13 when that happens?
Talking from my little experience in announcing releases, it may be too la
Hi Reinhold,
Reinhold Kainhofer a écrit :
Do I understand it correctly, that for the CG, you want e.g. all subsections
of "1.1 Gettin the source code" in the same html file, all subsections of "1.2
Updating the source code" in another html file, etc.?
Yes.
The quick and dirty fix would be to
Graham Percival a écrit :
IIRC there were already two patches that are waiting to be applied
that were put off until 2.13. Trevor was talking about
reshuffling the text crescendo commands.
OK, this is probably enough to start 2.13 in one week.
I just finished
unpacking today (yeah, 3.5 wee
Jonathan Kulp a écrit :
Francisco Vila wrote:
Cross fingers, today is the premiere of Valentin's "the LilyPond
Opera" in Montpellier. Success!
The name is "Affaire étrangère"; how would you translate it, Valentin? :-)
All right! Can't wait to hear how it goes. Good luck!
IIRC it should
Hi Werner,
Werner LEMBERG a écrit :
Compiling the documentation in current git with `make web', texi2html
(CVS version from 2009-01-09) produces zillion warnings like this:
*** Duplicate node found:
Adding beams
(in out-www/expressive-marks.texi l. 13 in @lydoctitle)
*** Duplicate
Hi Jan,
Jan Nieuwenhuizen a écrit :
So, apart from not updating libtool here, I've now also fixed the target
architecture, platform etc when building tools; makes much more sense.
Oh, I've push a whole slew of fixes that will trigger a grand rebuild...
I tried building GUB again yesterday.
Hello Yoshiki,
Sawada wrote:
Please use "0001-ja-doc.patch.org.gz" instead of "0001-ja-doc.patch.gz" in:
http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html
And change access modes from 755 to 644 following the instruction written in the
page.
How did you set the execution bit?
Jan Nieuwenhuizen a écrit :
I finally cooked-up a patch for that, it took a bit more work than
I imagined. With latest GUB3 you can do
LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond
This will disallow libtool to read from or stat in /, so this should
(from target/mingw/log
Sawada wrote:
1. Release of the new patch for ja doc
I put it in the following page:
http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html
Please do not remove *.itely files for AU and Japanese messages catalog
(i.e. Documentation/ja/user/i18n/ja).
OK, I applied your patch, but ma
Jan Nieuwenhuizen a écrit :
Tried a couple of things but could not reproduce this.
What's the command you issued? Can you try removing the
root and any librestrict/make packages:
I get the error I reported when running
rm -rf target
make -f lilypond.make bootstrap
Best,
John
___
Jan Nieuwenhuizen a écrit :
Interesting, that works for me. What's your python version?
2.5.1. I hope it's easy to install a newer Python in $HOME if it's
needed to build GUB.
Best,
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
h
Jan Nieuwenhuizen a écrit :
Does the attached patch help?
It doesn't, I get exactly the same error :-(
I hope the attached full output from the terminal may give a hint. What
I don't get is that during first GUB invocation
("python bin/gub --platform=tools git"), a lot of packages in tools ar
Sawada a écrit :
It does not work. But I fixed Lilypond-book.py as following:
(line 939)
if not langdefs.LANGDICT[document_language].enable_ly_identifier_l10n:
^^^
I guess the property name "enable_ly_identifier_l10n" should be changed to
"disable_ly_identifier_l10n".
I prefer to av
John
>From ad674166ea290a28a6865d576088fcdcc44ae47f Mon Sep 17 00:00:00 2001
From: John Mandereau
Date: Wed, 18 Feb 2009 10:54:10 +0100
Subject: [PATCH] Remove more duplicate libiberty.a files generated by binutils and gcc
This fix completes a previous similar fix in commit
fdfe393e51f670b97afe945bb920bd5b525e129d
---
gu
After a successful bootstraping stage, I tried "make -f lilypond.make"
and "make -f lilypond.make installers"; both failed with the attached log.
In bootstraping, Flex and Guile are built for target "tools", which I
find strange, whereas they are not built for each target platform. I
also mis
Hi guys,
Trevor Daniels a écrit :
I'd go along with going straight to 2.13 too. AFAIK there are
no serious outstanding issues with 2.12.2 that must be fixed,
and I feel a little uncomfortable with some of the doc changes
which will appear in the next release. I'd rather they went into 2.13.
The
Hi Francisco,
Francisco Vila a écrit :
I forward this to -devel, if there is no inconvenient and nobody does
it before, I could apply it next Tue or Wed.
Right. The attached patch removes the debug print command.
Could you remove the "print" command completely by pushing to Git directly?
If
Trevor Daniels a écrit :
No, it's OK. Just a mild preference. Not worth any trouble.
I'd added a new section or two which caused a renumbering.
It's not really a problem.
Agreed; FWIW I backported a lot of doc changes in early 2.12 versions
and IIRC nobody complained about renumbering. Oh yes
Reinhold Kainhofer a écrit :
Okay, but I think the snippets in input/lsr/ need to be updated to include
this new file from input/new/, too. Otherwise lilypond-book will not be able
to find it. Unfortunately, I have no idea how to re-generate input/lsr/ from
input/new/, though...
Use makelsr
Han-Wen Nienhuys a écrit :
[+John who has been working on the japanese translation]
On Thu, Feb 26, 2009 at 10:35 PM, Han-Wen Nienhuys wrote:
Dist error:
file from VC not distributed: lilypond-2.13.0/Documentation/ja/user/i18n/ja
Oops, this file should be added to Texi2html; I removed
Graham Percival a écrit :
On Wed, Feb 25, 2009 at 11:18:32AM -, Trevor Daniels wrote:
I think I've muddled through this and updated
input/lsr with my new snippet. As this was
the first time I've used makelsr.py there were
lots of mysterious warnings, but it seems to
have converted and co
Hi Carl,
Carl D. Sorensen a écrit :
So, just for the record, I guess that the appropriate way to handle this
would be to:
1. Search through input/lsr for relevant files.
2. Fix the snippet to make sure it compiles properly.
3. Copy the snippet to input/new
4. Delete the snippet from input/ls
Hi guys,
Valentin Villenave a écrit :
2009/3/3 Han-Wen Nienhuys :
We have received some complaints about bandwidth usage at
lilypond.org; in particular, the lilypond.pdf with its 13mb is causing
a lot of bandwidth use. Could the doc frogs/meisters/gdpers look into
a solution for this?
Reinhold Kainhofer a écrit :
A few days ago, I decided it's finally time to learn what all that
hype about AJAX is about. What would be a better guinea pig than
trying to implement a seach box in our docs??? Well -- it turned out
incredibly easy. Here it is:
http://kainhofer.com/~lilypond/ajax
Dear Yoshiki,
Sawada a écrit :
Request
1. NR 1.1.3 Displaying pitches -> Clef
In "See also", the reference to Internals Reference: "Clef" is translated to
"音部記号" by ja.po file. But it should not be translated because it is a object
name.
There is no way to fix it right now, but
Sawada a écrit :
NR is very long to translate, especially 1.1 Pitches and 1.2 Rhythms.
Therefore, my translation does not look like progressing so much.
It will take a while to release the next patch.
Quoting the Contribuors' Guide, section "3.6.2 Documentation translation
details":
"Files m
Reinhold Kainhofer a écrit :
Ah, so all I have to do is to add '*.idx' to the arguments of find and mass-
link them, too.
Sure.
Hehe, I was hoping that someone would jump up enthusiastically and say "Sure,
I'll take on the polishing" ;)
Lol! I already have a bunch of work for the docu
Hi Jan,
Jan Nieuwenhuizen a écrit :
On wo, 2009-02-18 at 14:55 +0100, Jan Nieuwenhuizen wrote:
Hi John,
How hard is it for you to install another python and try that?
I compiled Python 2.6.1 and installed it in my home, setting
LD_LIBRARY_PATH to /home/lilydev.
Does fedora carry py
Hello Yoshiki,
Sawada a écrit :
Do you mean that you will make node names and section titles translated only by
manual
(that is, they are translated in the source files, but not by the po file)?
Yes, that's it.
If it is correct, I want new commands as following rather than it:
@rinternalsn
2009/3/9 David Kastrup :
make prefix=/usr/local/lilypond install-info-WWW
make --no-builtin-rules -C Documentation/user install-info
make[1]: Entering directory `/lisa/lilypond/Documentation/user'
export LILYPOND_DATADIR=
export
PYTHONPATH=/lisa/lilypond/python/out:../../python/auxiliar:/lisa/li
Jan Nieuwenhuizen a écrit :
Good points, everything should be fixed. Improvements could be
* add toplevel info and install-info targets that redirect to
Documentation/user
..and input/lsr too. I added toplevel info and intall-info target.
* make info with images automagically (
John Mandereau a écrit :
*WWW* targets must be called with out=www;
these targets are purposely undocumented and not listed in
"make help" because they are reserved for internal use or hacking.
BTW we probably should enclose all WWW targets in ifeq($(out),www) blocks.
Any though
Trevor Daniels a écrit :
Re your recent commits:
shouldn't compile.itely and introduction.itely be in /devel rather
than /user?
I don't understand why you suggest to place introduction.itely in devel/.
As for compile.itely, it's easier to put it in user/, because
compilation of Texinfo docs i
David Kastrup a écrit :
John Mandereau writes:
..and input/lsr too. I added toplevel info and intall-info target.
No, you didn't.
Oops, I meant info-install.
At least a freshly fetched lilypond copy has only
(according to bash programmable completion) the targets
in
Graham Percival a écrit :
I'm not clear about this, either. Actually, if anything
introduction.itely is going to die entirely (as part of the
web-gop stuff).
All right. I can't work on GOP in the 4 coming weeks: I must work on
translaed documentation compilation by translating
node names in
Jan Nieuwenhuizen a écrit :
Op donderdag 12-03-2009 om 10:43 uur [tijdzone +0100], schreef John
Mandereau:
I compiled Python 2.6.1 and installed it in my home, setting
LD_LIBRARY_PATH to /home/lilydev.
So, does that help?
Not at all: I set PLATFORMS=linux-64 to avoid choking on
David Kastrup a écrit :
I don't think that is standard usage. install-info would be the norm
when available.
Will fix this, but see below my request.
make install bombs out, anyway:
Traceback (most recent call last):
File "/home/tmp/lilypond/stepmake/bin/install.py", line 78, in
s
David Kastrup a écrit :
John Mandereau writes:
What does "grep NCSB config.make" (at top of the build tree) does say?
NCSB_SOURCE_FILES = /usr/share/fonts/type1/gsfonts/c059036l.pfb /usr/share/fonts/type1/gsfonts/c059013l.pfb
Your system probably misses two of the N
[forgot to CC to list]
- Forwarded message --
From: John Mandereau
Date: 2009/3/16
Subject: Re: Why is it _still_ so freaking hard to get info with images?
To: Jan Nieuwenhuizen
Hi Jan,
2009/3/16 Jan Nieuwenhuizen :
> Your point about README/INSTALL is more difficult to tac
David Kastrup wrote:
So it would appear to be a problem that fc-match first finds the true
type fonts installed by Canorus, and then this first match is
subsequently thrown away by grep -v.
So I think you need to figure out how to tell fc-match to prefer Type1
over TrueType, or how to make it li
David Kastrup a écrit :
Ok, so the bad news: canorus was not in the package repository. So
reinstallation is not trivial: I have to dig it up and then install it.
And then it is likely that the version I'll be able to find will be
quite different from what I had installed previously (and which w
2009/3/18 David Kastrup :
> Werner LEMBERG writes:
>> I don't think so. AFAIK, we want *exactly* the URW versions, so this
>> looks like a good alternative.
>
> When I wrote the above, my rationale was that the URW fonts are Century
> Schoolbook font clones with identical font metrics. If someon
Hi Valentin,
Valentin Villenave a écrit :
Josh is right, this sentence doesn't really make sense. We recently
had a discussion about this very subject with John, who 's in the same
situation as you are, and is merely forced to contribute to
proprietary music software :-)
If I'd like to develop
Hi Graham,
Graham Percival a écrit :
I've been offered a scholarship to do my PhD at the University of
Glasgow, which I'm of course eagerly accepting. I'll be starting
in Sep or Oct.
Congatulations!
2) I might organize European vacations around other lilypond
contributors, starting with a
Werner LEMBERG a écrit :
Sorry, I don't understand the problem. Why will this lilypond fix
break something in Canorus or vice versa?
Canorus installs Truetype versions of some of those fonts,
system-wide. The Lilypond configure command finds some of those
truetype fonts via fc-match in
Werner LEMBERG a écrit :
Looks good to me (if you use proper indentation :-).
Applied.
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Graham,
Graham Percival a écrit :
I just realized that I probably should have modified the download
page, but I can't see any install-2.11.html or the like. What do
we normally do for development versions?
Patrick gave you the hint: just create a new download included page
install-2.13.
James E. Bailey a écrit :
Incidentally, although the instructions in the Contributor's Guide are
generally simple enough for even me to follow, apparently they're
missing something because the git-format-patch HEAD doesn't work.
If you have a recent Git, it should probably be
git format-patch
Hi James,
James E. Bailey a écrit :
Leave it to me to take something easy and make it difficult. So, I had
a conflict. I thought I resolved it, but now tutorial.itely looks
funny. I don't know how to get back to just having the normal files
without any changes that I've made, and I don't know i
James E. Bailey a écrit :
I'm having a configure error, and I don't know how to solve it. I get
this:
ERROR: Please install required programs: /Users/lilydev/bin/fontforge
>= 20050624 (installed: .fontforge 20080927)
What does 'which fontforge' and '`which fontforge` --version' say?
Could yo
Graham Percival a écrit :
Ick. Do we really need to ask casual contributors to spend 30
minutes reading how to use git?
I think so, see below.
Isn't there any faster way to
give the instructions? Like
- copy the conflicted file to a backup name
- delete the file
- do "git reset --hard"
-
1 - 100 of 1573 matches
Mail list logo
