Le mercredi 15 juillet 2009 à 18:40 -0600, Carl Sorensen a écrit :
> I'll delete all the English and just leave the corrected snippets in the
> Spanish docs.
>
> How about french and german? What would you prefer?
Let's not have different policies for different languages, or all
contributors and
Le jeudi 16 juillet 2009 à 04:46 -0700, Graham Percival a écrit :
> On Thu, Jul 16, 2009 at 01:30:56AM +0200, John Mandereau wrote:
> > I assume you mean Documentation.
>
> No; I really want to rename that dir. I've wanted to rename it
> since I first got involved in li
Hi Till,
Sorry for the delay :-/
Le dimanche 28 juin 2009 à 11:00 +0300, Till Rettig a écrit :
> first time I consulted the contributor's guide.
It's never too late :-) (it's never too late either for me to work on it
again :-P)
> in 3.7.2 Documentation translation details you have different s
Le jeudi 16 juillet 2009 à 09:12 -0600, Carl Sorensen a écrit :
> I tried running
>
> make ISOLANG=fr snippet-update
>
> from Documentation/. It ran, but most of the files were not able to be
> updated because they had a different snippet count. So at the present time,
> make snippet-update is
Le jeudi 16 juillet 2009 à 09:40 -0600, Carl Sorensen a écrit :
> However, when non-snippet text is changed, added, or removed from the
> english documentation, no corresponding changes should be made to the
> translated versions of the documentation.
All right, this is clearer.
Cheers,
John
_
I'd like to start working on the plan below real soon now so it can be
finished by the end of August; if it isn't I might have no time to
complete this within a year.
Le samedi 11 juillet 2009 à 03:21 -0700, Graham Percival a écrit :
> docs/
> docs/learning.tely
> docs/learning/*.itely
> docs/not
Le jeudi 16 juillet 2009 à 16:45 +0200, John Mandereau a écrit :
> Have you realized that it will make browsing Git history
> more difficult and require hackery in translation checking scripts to
> follow old history of files from docs/ to Documentation? We have this
> problem for in
Le samedi 18 juillet 2009 à 03:31 -0700, Graham Percival a écrit :
> Good point. I had a vague notion that having them there might
> make it easier to produce the top-level *.txt files, but I
> honestly would rather have them moved. If you're happy with that,
> then by all means let's move them.
Hi Jean-Charles,
Le lundi 20 juillet 2009 à 22:06 +0200, Jean-Charles Malahieude a
écrit :
> Hi Mr release-master and his fellow workers,
>
> Please wait a couple of days before delivering a new release, since I'm
> almost (99% plus a proof-reading) of a complete reviewing of the French
> versio
Le mardi 21 juillet 2009 à 15:56 +0200, Jan Nieuwenhuizen a écrit :
> What is so difficult here, can't this be scripted?
If you mean solving conflicts caused by moved files, this certainly can.
John
signature.asc
Description: Ceci est une partie de message numériquement signée
_
Hi guys,
I expect comments (and even maybe votes from developers) about the
directory structure, which will very soon drive an important part of the
docs and web site reorganization (especially the makefiles and
buildscripts :-P).
I have a naive question with not so naive implications about the c
Le mardi 21 juillet 2009 à 23:57 -0700, Graham Percival a écrit :
> I would personally remove the web/, and have things like
> lilypond.org/introduction.html
> lilypond.org/doc/v2.x/
> lilypond.org/download/
> lilypond.org/tiny_examples.html
> along with whatever redirects are desirable.
I
As the changes involved by the new web site are quite large and
invasive, I try to give steps so you are not too surprised by what's
going on with dozens of files suddenly moved or temporarily broken HTML
links. Please report any breakage in case I haven't explicitly mentioned
it in a commit (this
Le jeudi 23 juillet 2009 à 14:11 -0700, Mark Polesky a écrit :
> I assume that a comprehensive visual "parent-web" demonstrating
> all such relationships would be too convoluted to have any
> practical value, and too difficult to generate to even justify
> trying such a thing
It might be doable to
Le mercredi 22 juillet 2009 à 10:30 +0200, John Mandereau a écrit :
> Step 1) Move all Texinfo documentation in user/ and topdocs/ one
> directory higher (done in my working tree), in translations too.
>
> Step 2) Update all build and maintenance scripts and the CG.
> At the end of
Le samedi 25 juillet 2009 à 09:58 -0700, Mark Polesky a écrit :
> But even in such cases, as long as my tab-width matches the
> tab-widths in the source, tabs2spaces should be fine. Is it
> correct to say that git (or savannah) translates all tabs to 8
> spaces without exception?
Git doesn't trans
Hi Carl,
Le samedi 25 juillet 2009 à 18:14 -0600, Carl Sorensen a écrit :
> make runs through the creation of the .o and the executable. It finishes
> the fonts, then when it starts compiling the snippets it ends with:
This log is cumbersome to read, because "make" doesn't print
"entering/leaving
Le samedi 25 juillet 2009 à 22:37 -0600, Carl Sorensen a écrit :
> Any git gurus out there who have an idea of how I can do this without having
> to manually apply patches made between the files in the different
> directories?
If marvellous renames detection capacity of Git enabled by default when
Le dimanche 26 juillet 2009 à 02:02 -0700, Graham Percival a écrit :
> Congratulations! There seems to be a strong correlation between
> working on lilypond and getting PhDs.
Maybe, but in my case it looks more like a coincidence between my
translations meister role in LilyPond and studies, even
Le samedi 25 juillet 2009 à 19:25 -0700, Patrick McCarty a écrit :
> I can confirm. The entire "split" version of the CG is not being built
> either.
I have not checked this before cleaning up Documentation/GNUmakefile
today, but the link to the split HTML CG from devel.html was wrong. This
shou
Le samedi 25 juillet 2009 à 13:05 -0700, Patrick McCarty a écrit :
> However, I just tried `make install' after `make all', and I get the
> attached output.
Thanks for the report, fixed in Git. Gee, this made me realize OMF stuff
had been broken since 'out-www' was stripped from the docball (i.e.
Le mercredi 22 juillet 2009 à 21:46 -0700, Graham Percival a écrit :
> I disagree; @lilypond blocks have a few problems for this case:
> - this is a really "courageous" regression test. Ok, ideally we'd
> never merge any patches that break any regtests, but it happens
> from time to time -- es
Le dimanche 26 juillet 2009 à 19:50 +0100, Neil Puttock a écrit :
> I've just tried to invoke makelsr.py to update a snippet in one of my
> Rietveld patchsets, and I'm getting the following error message:
> os.environ['PYTHONPATH'] += ':python'
> KeyError: 'PYTHONPATH'
>
> Should I have a PYT
Le lundi 27 juillet 2009 à 01:31 -0700, Graham Percival a écrit :
> I'm not having any luck googling "pytt". Was that a typo? I'm
> not aware of any tool like awk or sed called anything similar to
> "pytt", but I admit that I don't know a lot about that side of
> things.
'find' is your friend.
Le dimanche 26 juillet 2009 à 16:20 -0700, Patrick McCarty a écrit :
> > When you get a chance, could you also try "make dist" again? It looks
> > like there are some more makefiles that need adjustments for the
> > NEWS.tely --> changes.tely transition.
I fixed it in an ugly way; I still don't k
Le lundi 27 juillet 2009 à 07:36 -0600, Carl Sorensen a écrit :
> When I tried make, it got through rhythms.itely (which was were all the doc
> changes I made were located). But it failed later on:
Which upstream Git revision of the sources did you try to build? There
are so much changes between
Le dimanche 26 juillet 2009 à 21:30 -0700, Patrick McCarty a écrit :
> 1) The following directories are missing copies of the stylesheets:
>
> Documentation/changes/
This directory shouldn't be present; in Documentation/GNUmakefile new
terminology, changes.tely is in UNSPLITTED_HTML_MANUALS.
Le dimanche 28 juin 2009 à 17:58 +0300, Till Paala a écrit :
> it seems I just did the same mistake and commited everything in
> input/texidoc. But I really don't understand makelsr.py and how it
> should work.
Then please read the CG.
> I called it without any argument and it updated some 4
Le lundi 27 juillet 2009 à 09:01 -0600, Carl Sorensen a écrit :
> Current master.
Did you mean 2848f13c9c7fe59b47165832348e14d771439dc7?
> I couldn't find a log.
I meant the mix of stdout and stderr, which I usually save to a file,
e.g.
make -j3 doc &> make-doc-2009-07-27.log
> Perhaps I w
Le lundi 27 juillet 2009 à 01:17 -0700, Graham Percival a écrit :
> I thought we were keeping the uploaded-website on a separate
> branch?
The uploaded website is the generated website; as it's generated, it
doesn't need nor deserve to be stored in a version control system, it
should just be uploa
Le lundi 27 juillet 2009 à 17:12 +0100, Trevor Daniels a écrit :
> This is sensible - thanks. I've made a note to
> do this once the major doc changes are done.
If by "major doc changes" you mean everything I did that has produced no
user-visible change besides broken links, missing CSS and docum
Le lundi 27 juillet 2009 à 13:04 -0700, Patrick McCarty a écrit :
> I just modified Documentation/notation/spacing.itely, and when I ran
> "make doc", the changes did not appear in my local offline-root/
> documentation.
>
> I needed to touch Documentation/notation.tely for the changes to be
> com
tart actively working on it
before the end of August.
Please make any comment, suggestion, objection or question as you wish,
either publicly or privately.
Best regards,
--
John Mandereau
LilyPond translations meister
signature.asc
Description: Ceci e
Le mardi 28 juillet 2009 à 11:42 +0200, Francisco Vila a écrit :
> 2009/7/28 Graham Percival :
> >>
> >> rm -rf * && git reset --hard
> >
>
Duh, I tracked down the problem; sorry for the delay, I would have
solved it earlier if I wasn't an idiot or with more complete make logs,
as I didn't got th
Le mercredi 29 juillet 2009 à 05:28 -0700, Graham Percival a écrit :
> Hi John,
>
> Could there be a make target for building only the English docs?
> Or is this already done with something like
> make LANG=en doc
As all manuals are built in Documentation/, which has translations as
subdirector
Le mercredi 29 juillet 2009 à 20:05 +0200, Francisco Vila a écrit :
> What makes our setup so different that makes this fail? I think John
> should in theory obtain the same result.
>
> I don't bother removing the whole directory contents despite of having
> untracked stuff inside, because I've zi
Le mercredi 29 juillet 2009 à 20:13 +0200, Werner LEMBERG a écrit :
> One of the most important constraints of Makefiles: You must not rely
> on the order of targets within a single rule. If necessary, you have
> to add more rules to enforce a certain order.
This is exactly what the CHAIN_RULE tr
Le mercredi 29 juillet 2009 à 20:26 +0200, Francisco Vila a écrit :
> Besides, Why 'make' should bother about tely files? Isn't it supposed
> to make the binary only?
It builds Info documentation without images, which is a least a useful
validation test for documentation in English, as makeinfo er
Le mercredi 29 juillet 2009 à 20:23 +0200, John Mandereau a écrit :
> This is exactly what the CHAIN_RULE trick in make/ly-*.make is supposed
> to do: it generates rules that ensure no several lilypond-book instances
> ever run simultaneously.
...and the generated rules chain must in p
Le mercredi 29 juillet 2009 à 21:15 +0200, Werner LEMBERG a écrit :
>
> > make -np &> make-db.log
>
> Attached.
Thanks, it shows the same problem as Francisco. I really hope I got it
right in the commit I just pushed to master and lilypond/translation.
Sorry for the 4-days build breaking,
John
Le mercredi 29 juillet 2009 à 23:48 +0900, Maximilian Albert a écrit :
> But frankly, even though I was actively looking for
> it when opening the new page for the first time, it took me a while to
> find the information what LilyPond actually does. The subtitle is
> really small so that all you ac
Le jeudi 30 juillet 2009 à 19:42 -0700, Graham Percival a écrit :
> The patch works for me; please push if you think it's ok.
LGTM, will push as soon as 'make doc' works again (I'm on it).
John
signature.asc
Description: Ceci est une partie de message numériquement signée
__
Le jeudi 30 juillet 2009 à 20:59 -0700, Graham Percival a écrit :
> Attached patch works for me.
LGTM, will push with the other patch.
John
signature.asc
Description: Ceci est une partie de message numériquement signée
___
lilypond-devel mailing list
Hi guys,
Could someone checks paragraphs and the snippet I @ignored today in
Notation, chapter Spacing, in order to compile docs? Maybe they should
be deleted.
Best,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
Le lundi 27 juillet 2009 à 18:13 -0700, Graham Percival a écrit :
> My apologies for being unclear in the past. (and my advanced
> apologies for being unclear in the future, although hopefully I
> won't be unclear about this specific issue)
Thanks, I've been preparing a detailed reply but have be
Hi Jan,
Le jeudi 30 juillet 2009 à 15:45 +0200, Jan Nieuwenhuizen a écrit :
> Or just two very big (scalex4) glyphs,
> clef+eight, flat/sharp + sixteenth?
This sounds better than a full bar of music: we don't want to make a
music piece so prominently, which could in particular distract the
reader
Le samedi 01 août 2009 à 13:11 +0200, Jean-Charles Malahieude a écrit :
> * The availability in the different languages we used to find in
> every footer has disappeared. It is only placed on the root page
> and every individual home page. You cannot switch anywhere else.
>
> * I don't know if it
Le mardi 28 juillet 2009 à 21:55 +0100, Neil Puttock a écrit :
> I've just done a docs compile and noticed some regression tests
> appearing in the snippet list. I've prepared a patch which fixes it,
> but I'm wary of pushing it without passing it by you first, since I
> know precisely nothing abo
Le lundi 27 juillet 2009 à 17:26 -0700, Graham Percival a écrit :
> There are *plenty* of lilypond sources available. I really think
> that adding complexity to the Introduction pages would not be
> warranted.
Just like free software source code should be reachable from a place
where you get bin
Le samedi 01 août 2009 à 20:22 -0700, Graham Percival a écrit :
> On Sat, Aug 01, 2009 at 07:32:21PM -0600, Andrew Hawryluk wrote:
> > On Sat, Aug 1, 2009 at 4:44 PM, Graham Percival
> > wrote:
> > > Great! Now that that's working, you can delete the web-gop repo
> > > and move back to main repo
Le dimanche 02 août 2009 à 19:00 +0200, Jean-Charles Malahieude a
écrit :
> For the first point: you'll notice it when you choose a language other
> than English on the root page and then navigate into one of the manuals.
I see this too, but not on my build. It looks like @translationof
commands
Le lundi 27 juillet 2009 à 03:22 -0700, Graham Percival a écrit :
> One of the biggest complaints people have with lilypond -- other
> than that silly "there's no gui" -- is the changing syntax. Now,
> inventing a language or standards is difficult. If you set it in
> stone too soon, you risk bei
Le lundi 27 juillet 2009 à 18:13 -0700, Graham Percival a écrit :
> Details are in the ADD-TO-CG.txt file, but as a brief summary:
> - nobody edits texinfo files in this repo. They are imported
> via scripts/update-imported.sh from the
> unstable/current/head/master lilypond branch.
> (curre
Le dimanche 02 août 2009 à 21:27 +0200, Michael Käppler a écrit :
> What I wasn't unable to figure out is at which time line-width is
> calculated if you don't set it explicitly. And, much more confusing, I
> don't see any procedures in C++ that actually check the line-width. A
> "grep -R line-w
Le dimanche 02 août 2009 à 00:38 -0700, Joe Neeman a écrit :
> I've added some more stretchable space and a little padding to Dynamics,
> so the pedals look better. If you think pedals and dynamics should be
> treated differently, feel free to add a new context. I haven't actually
> updated the sni
Le lundi 27 juillet 2009 à 17:12 +0200, John Mandereau a écrit :
> Le dimanche 28 juin 2009 à 17:58 +0300, Till Paala a écrit :
> > I called it without any argument and it updated some 4
> > snippets in input/lsr with convert-ly to a new lilypond-version -- but
> > it
Le dimanche 02 août 2009 à 19:55 +0200, John Mandereau a écrit :
> Le samedi 01 août 2009 à 20:22 -0700, Graham Percival a écrit :
> > so we can't
> > build the English docs without building all the docs in other
> > languages.
>
> I understand this one can b
Le lundi 03 août 2009 à 04:19 -0700, Graham Percival a écrit :
> On Sun, Aug 02, 2009 at 09:16:15PM +0200, John Mandereau wrote:
> > Le lundi 27 juillet 2009 à 18:13 -0700, Graham Percival a écrit :
> > > - nobody edits texinfo files in this repo. They are imported
> >
Le lundi 03 août 2009 à 09:01 -0600, Andrew Hawryluk a écrit :
> I may use said script to quickly check for dumb errors, but it didn't
> seem to import the images, and if I run 'make doc' twice the second
> run only takes 33 seconds, so I'll still build the full set regularly.
We all rely on this
Le lundi 03 août 2009 à 05:51 -0700, Graham Percival a écrit :
> Well, it depends how you define "tweak". In the LM, we lean
> pretty heavily on "tweak = \override and \set" (plus others).
> Some of those examples definitely *do* use tweaks!
>
> I'd rather keep the wiggle room and just say "look a
Le mardi 04 août 2009 à 01:12 -0700, Graham Percival a écrit :
> Yes, but what if somebody reads the LM, looks at the source, then
> accuses us of lying when we claimed "no tweaks were used"? I
> wouldn't blame that person at all!
Of course, I rather meant lilyond-book trickery, which we probably
Le lundi 03 août 2009 à 05:57 -0700, Graham Percival a écrit :
> ok, I'm willing to go as far as adding a single "View sources"
> link at the bottom of the page, which takes people to a
> Snippets->Examples page. Of course, that would require adding the
> Examples to LSR (or at least new/), requir
Le lundi 03 août 2009 à 05:51 -0700, Graham Percival a écrit :
> I thought the website was going to be built from the stable
> branch? If we're doing that, then let's delete the web branches.
This just made me come to mind that I'm for not including News in
generated offline docball: if we did, i
Le mardi 04 août 2009 à 05:20 -0700, Graham Percival a écrit :
> ... at the very minimum, we could omit the news on the home page
> (that would require one macro/conditional thingie in
> general.texi),
I want to restore and fix the RSS feed, so I merge news-* into a single
source file for import i
Le mardi 04 août 2009 à 14:36 +0200, Reinhold Kainhofer a écrit :
> > I see this too, but not on my build. It looks like @translationof
> > commands are ignored on kainhofer.com, as I saw French page names.
>
> Hmm, this should work. I haven't updated texi2html for some days/weeks,
> though...
Le mardi 28 juillet 2009 à 16:39 +0200, Translation Project Robot a
écrit :
> A new POT file for textual domain 'lilypond' has been made available
> to the language teams for translation. It is archived as:
>
> http://translationproject.org/POT-files/lilypond-2.13.3.pot
>
> http://downl
Le mardi 04 août 2009 à 06:58 -0700, Graham Percival a écrit :
> Hmm, I suppose this would screw up the cross-references.
Not at all, cross-references are defined in macros.itexi.
> I guess we'll just expect users
> looking at a pdf tarball to open up "general.pdf" first.
We don't care so much
Le mardi 04 août 2009 à 07:30 -0600, Carl Sorensen a écrit :
> So, I have heartburn about regressions on the stable branch as indicated by
> failure to pass the regtest. But I have no heartburn about "regressions"
> that mean a complicated example that uses tweaks doesn't look right any
> more.
I
Le mardi 04 août 2009 à 05:06 -0700, Graham Percival a écrit :
> Look, I was sole maintainer of the docs for 4 years. A few times,
> I took a look at the build process because I wanted something or
> other changed. Each time, I abandoned the idea after a few hours,
> because I was getting nowhere
The new directory Documentation/examples that was proposed to host
examples for the web site plays a duplicate role of input/ and
input/mutopia. What about cleaning up these two directories (that is,
deleting unused input files and cleaning up makefiles) and use input/
instead of creating a new di
The web site in Texinfo is on master now, except the examples (see my
other email). All of what I could think of the technical status and
to-do is in the commmit message. There are many regressions compared to
the output , but my goal is to have no regressions (and even bugfixes)
compared to the
Le lundi 03 août 2009 à 22:32 -0700, Graham Percival a écrit :
> The general steps are:
> 1) copy snippet from Documentation/snippets/ to new/
> 2) remove any non-english texidoc?? items from the \header
> 3) edit file at will
> 4) run makelsr.py without arguments
>
> I'm not certain if these step
Le mercredi 05 août 2009 à 09:09 +0100, Trevor Daniels a écrit :
> Any further thoughts?
At least one of the terms listed by Mark is introduced in the Learning
Manual: "grob" in 4.1.2 Objects and interfaces. I see this glossary
could be a quick reference that briefly defines each term and gives
c
Le mercredi 05 août 2009 à 22:13 +0100, Neil Puttock a écrit :
> Try running `collision-mesh.ly' to see what happens. :)
Indeed :-P
dots.ly before
dots.ly after
collision-mesh.ly before
collision-mesh.ly after
John
<><><><>
signature.asc
Description: Ceci est une partie de message numé
Le mercredi 05 août 2009 à 23:40 -0700, Graham Percival a écrit :
> Is it ok if Patrick Schmidt and I do a few more days' work on that
> branch? The changes would be almost all[1] in his css/alt2.css
> file.
The changes can be wherever you like, the guy that will import these
changes just has to
Le jeudi 06 août 2009 à 11:35 +0100, Trevor Daniels a écrit :
> > Not until we have @rweb or @rgeneral or whatever it gets called.
> > At least, that's what the @ref{Setup for MacOS X} are waiting for.
> > I admit that I could fix the @rprogram{LilyPond-book} link right
> > now if it was a priority
Le jeudi 06 août 2009 à 13:51 +0200, Reinhold Kainhofer a écrit :
> No, big pages should link to the other big pages. That's how the current
> .init
> file is supposed to work. If it doesn' t, then that' s a bug in the script
> and
> needs to be fixed.
But does the web site in one large page m
Le jeudi 06 août 2009 à 14:48 +0100, Trevor Daniels a écrit :
> No; I'm on Windows Vista, so building isn't an option, is it?
No, but you can still run check-xrefs and fix-xrefs, but it will
complain about missing files markup*.tely, internals.tely and so on.
> Good. In that case I'll leave the
Le jeudi 06 août 2009 à 04:18 -0700, Graham Percival a écrit :
> > make check-xrefs
> I need to spend 1-2 more days on the AU, but then I'll finally
> start my CG review. I'll definitely add this at that point.
Documentation]$ grep check-xrefs contributor/*
contributor/doc-work.itexi:for check-x
Le jeudi 06 août 2009 à 00:29 -0700, Graham Percival a écrit :
> 1) news items: would it be possible to keep the news-front vs.
> news-old? I'd like to maintain human control over what's on the
> front page.
This is achieved easily by marking news entries with ad-hoc tags, e.g. a
dummy Texinfo ma
Le jeudi 06 août 2009 à 16:14 +0100, Ian Hulin a écrit :
> At the moment it looks like we're setting the equivalent of a global
> static variable to do this - bad news for such a specific function.
Indeed.
> Is there a way of do this sort of thing sometime in the future?
>
> \afterGrace {d1 {
Le mercredi 05 août 2009 à 21:03 -0700, Patrick McCarty a écrit :
> I need this patch to run ./autogen.sh with the latest Autoconf version
> (2.64). The only earlier version I am able to test is 2.63, which
> works fine with the patch.
>
> The warnings I am seeing and workarounds are here:
>
> h
Le jeudi 06 août 2009 à 00:08 -0700, Graham Percival a écrit :
> IMO, there are two kinds of examples here.
> 1) advertizing examples: "we can do tabs, complex rhythms, lots
> of accidentals, gregorian chant, etc etc". We expect people to
> glance at the image and then move on.
> 2) educational
Le jeudi 06 août 2009 à 18:42 +0200, Francisco Vila a écrit :
> Before releasing, please check that all HTML doc pages have links to
> other languages at bottom.
>
> Just checking any page not being the first, will serve. Some of us
> have built the docs and have observed this problem; John is on
Le jeudi 06 août 2009 à 18:55 +0200, Reinhold Kainhofer a écrit :
> On kainhofer.com I'm using the latest CVS version (updated yesterday), and
> the
> language links are missing there:
> http://kainhofer.com/~lilypond/Documentation/notation/Vocal-music.html
After having read replies from you and
Le jeudi 06 août 2009 à 09:55 -0700, Mark Polesky a écrit :
> \afterGrace
> \afterGraceCustom
>
> Though I admit, I'm not particularly fond of this solution.
Neither am I. Why not just junk the form?
> This would require modifying the define-music-function defmacro
> (on line 764 of
Le jeudi 06 août 2009 à 19:52 +0200, Reinhold Kainhofer a écrit :
> Hmm, the tag is still there in the html file (both before
> postprocess_html.py and after). From a quick look at the postprocess_html.py
> script it seems that all you do is replace that tag, so I suppose the
> texi2html part i
Le vendredi 07 août 2009 à 19:45 -0700, Patrick McCarty a écrit :
> I think it would be nice to have an entire CG section devoted to
> explaining what "rebasing" means, but the "git rebase" man page
> provides a reasonably good explanation in the meantime.
>
> http://www.kernel.org/pub/software/sc
Le vendredi 07 août 2009 à 21:00 -0700, Patrick McCarty a écrit :
> Personally, I browse git history on the command line quite often when
> working with LilyPond.
So do I, or sometimes with gitk.
There are already many Git features to master for daily use, I'm not
keen on adding to the CG the sha
Le samedi 08 août 2009 à 01:46 -0700, Graham Percival a écrit :
> Despite my above paragraph, I'm not opposed to adding links to
> people's favorite git tutorial. However, I don't expect any
> contributor to read them, and I certainly won't be reading any.
FWIW I usually expect translators to rea
Le vendredi 07 août 2009 à 23:27 -0600, Andrew Hawryluk a écrit :
> I can't speak for the future content of
> http://lilypond.org/~graham/Text-input.html, but I will be working on
> the next version of the essay (once the directory structure for images
> in Documentation/ stabilizes), and it should
Le samedi 08 août 2009 à 12:37 +0200, Werner LEMBERG a écrit :
> What about changing the font name to `Bitstream Charter'? Can you
> please check, with a call to
>
> fc-match "Bitstream Charter"
>
> whether this works on other platforms too (I use fontconfig 2.7.1),
> selecting an outline vari
Le samedi 08 août 2009 à 13:55 -0600, Carl Sorensen a écrit :
> As a practical matter, -r first applies the changes that were made on origin
> (since your branch was checked out), then applies your changes on top of the
> current origin. The prevents an extra commit to merge your branch with
> or
Sorry for my initial reply to this, it was not enough to the point, I'm
trying again :-)
Le jeudi 06 août 2009 à 09:55 -0700, Mark Polesky a écrit :
> Well, now I think we're pretty much back at Han-Wen's original
> suggestion, which was to have two commands, one for temporary
> afterGraceFractio
Le dimanche 09 août 2009 à 16:21 -0600, Carl Sorensen a écrit :
> Perfect! I hope I didn't mess up the translated docs too badly with my
> recent merge.
The only risk to mess up translated docs checking is in case you change
committishes that appear as comments at the head of each file. If this
Le dimanche 09 août 2009 à 08:27 +0200, Werner LEMBERG a écrit :
> Is it OK nowadays to say
>
> git pull
> make all
>
> to *really* have a good build?
Not really. There is an issue in the tracker about fonts that are not
rebuilt after changes in the fonts sources and the build tree is not
Le dimanche 09 août 2009 à 16:48 -0700, Graham Percival a écrit :
> Mao. So that means that we don't want to add
> git config --global branch.autosetuprebase always
> to the git setup, and we still have to tell people to do
> git pull -r
> instead of
> git pull
> ?
You didn't read the end o
Le lundi 10 août 2009 à 00:56 -0700, Graham Percival a écrit :
> After spending a while reading and re-reading your addition to the
> CG git stuff, it sounds like this only applies to translated docs
> -- i.e. as long as I don't mess with anything in de/ es/ fr/ etc/,
> it's safe to "git pull -r".
Le dimanche 09 août 2009 à 16:43 -0600, Carl Sorensen a écrit :
> How about \afterGraceSpacing ?
That's OK for me; unless there is any objection on the command name,
I'll add the function with this name.
Best,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
Le lundi 10 août 2009 à 06:40 +0200, Werner LEMBERG a écrit :
> It would be sufficient for me if `make all' simply aborts with a
> message
>
> configure.in has been modified! Please rerun `autogen.sh',
> then `make all' again.
>
> or something like that.
Done. INSTALL.txt and the Contribut
201 - 300 of 1573 matches
Mail list logo
