Han-Wen Nienhuys wrote:
> John Mandereau escreveu:
> >>> I hope this plan shouldn't involve ugly/clever hacks. How does it sound?
> >> Sounds ok to me.
> >
> > So, if you and Jan are not in a hurry to release 2.10.1 or to merge
> > fr-doc after 2.10.
stood git
concepts of course). I can easily do all common operations (including
push), except that I don't know what should be the best way to merge
branches in order to push them to git.sv.gnu.org (but Erik will
certainly tell us in his tutorial ;-)
Greetings,
--
John M
ations. Of course, the latter
point is discutable, but IMO stuff like tutorials for LilyPond
contributors is more welcome on a wiki than in LilyPond documentation or
on lilypond.org.
Cheers,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Johannes Schindelin wrote:
> On Tue, 5 Dec 2006, John Mandereau wrote:
>
> > I can easily do all common operations (including push), except that I
> > don't know what should be the best way to merge branches in order to
> > push them to git.sv.gnu.org (but Erik
Jan Nieuwenhuizen wrote:
> John Mandereau <[EMAIL PROTECTED]> writes:
>
> > I expect to be able to send a patch within a week or so. I'm slow
> > because I'm a bit busy and I have very little programming experience.
>
> In that case, do you have something
Jan Nieuwenhuizen wrote:
> John Mandereau <[EMAIL PROTECTED]> writes:
>
> > I expect to be able to send a patch within a week or so. I'm slow
> > because I'm a bit busy and I have very little programming experience.
>
> In that case, do you have something
LANG.html, and then replacing *.html hrefs
with *.LANG.html in all (i.e. real translations and copies of the
English docs) *.LANG.html files?
Cheers,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
ing/lilypond/out-www/web-root/Documentation/user/lilypond/index.html
Just issue
make CONTENT_NEGOTIATION= web
to keep the .html extensions in links.
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
ot;offline online" web
builds both.
If this can be applied and a possible link to the French tutorial in
index.html.in is added, Jan and Han-Wen may want to release 2.10.3 or
2.10.2-2, as the current docball is broken because of .html stripping
(maybe the 2.11 docball is broken too).
Cheers,
-
'
>
>
> Don't use exec. If you must, try
>
>
> locals()[s + "_re"] = ..
I only used that to avoid typing six times the same line of code.
> what's _f and _d? Write _dir or _file if you mean that.
Yes, I mean that.
> usually, list comprehensions are shorter and clearer,
>
> [p % s for p in targets]
Oh, yes , I didn't remember that possibility in Python.
I'm sending another patch according to your comments asap.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
out-www/' path components in the file name
before writing it, which is of course doable.
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
John Mandereau wrote:
> Han-Wen Nienhuys wrote:
> > > diff --git a/stepmake/bin/add-html-footer.py
> > > b/stepmake/bin/add-html-footer.py
> > > index 08ff5ff..9a28237 100644
> > > --- a/stepmake/bin/add-html-footer.py
> > > +++ b/stepmake/bin/a
Han-Wen Nienhuys wrote:
> John Mandereau escreveu:
> > Before the next release including this patch, may I also add a link to
> > the French tutorial in index.html.in?
>
> Sure.
>
> Here are some final remarks, and Jan will have a look too. If Jan is
> ok, please
Jan Nieuwenhuizen wrote:
> John Mandereau <[EMAIL PROTECTED]> writes:
>
> > Should I send a patch again, or work according to your remarks and push
> > to stable/2.10 (and possibly master) if Jan agrees?
>
> Please push to stable/2.10.
Just done. I've spent
Jan Nieuwenhuizen wrote:
> John Mandereau <[EMAIL PROTECTED]> writes:
> > If I really wanted to rewrite it, I'd split it into:
> > - a function that walks the input directories and returns directories
> > and files lists
> > - filtering these lists
> >
als (backend)
make[2]: *** [out/lilypond-internals.texi] Error 1
make[2]: Leaving directory `/home/lilycvs/git/lily/Documentation/user'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/lilycvs/git/lily/Documentation'
make: *** [all] Erreur 2
--
John Mandereau <[EMAIL PR
to move docs about \version from "Commenting input files" to
"First steps" just after the first example. May I push directly or send
a patch first?
Regards,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
;myweb", but also stores the remote "web/master" in
> your local repository, so you can always get a diff between the tips of
> "myweb" and "web/master" by
>
> $ git diff web/master..myweb
These instructons seem to be clear. With your pe
Btw, isn't
scripts/rev-to-commit.py intended to automate this work?
What's the Spanish for 'Spanish'? It could be used in the 'Other
languages' menu preferably to the English 'Spanish' ;-)
Another nitpick: are you the only translator or are you in a team?
Le vendredi 29 décembre 2006 à 18:28 +0100, John Mandereau a écrit :
> Le vendredi 29 décembre 2006 à 04:51 -0600, Daniel Tonda a écrit :
> > Hello:
> >
> > I'm attaching a bzipped tarball containing the priority 1 items in the
> > TRANSLATION document, follow
the devel branch docs for the
stable, that's why I made this proposition.
Greetings
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
with cogito and only use git commands when they have
no cogito equivalent.
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Le vendredi 29 décembre 2006 à 20:37 +0100, Han-Wen Nienhuys a écrit :
> John Mandereau escreveu:
> > By the way, do you mind if I explain this with cogito commands instead
> > of git?
>
> I think you should use git , to minimize confusion, and minimize software
> that c
Daniel Tonda Castillo wrote:
> John Mandereau wrote:
[...]
> From what I gather, so far if no write acces is provided, the most
> important git commands would seem to be clone and patch, but patch is
> still not clear for me yet.
No, you only use clone to initially clone the repo
Daniel Tonda Castillo wrote:
> John Mandereau wrote:
> > Daniel Tonda Castillo wrote:
> >> From what I gather, so far if no write acces is provided, the most
> >> important git commands would seem to be clone and patch, but patch is
> >> still not clear f
an important number
of contributors?
Happy 2007
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
ou have
already contributed in some way, and if you really prefer, it could read
"Daniel Tonda Castillo, Spanish translation, with help from Fransisco
Vila."
Happy new year and good luck for the translation,
--
John Mandereau <[EMAIL PROTECTED]>
_
ides this, deep-ln was unused, so I've junked it too and I've pushed
all changes to both master and stable/2.10.
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
nd.pot file for translation,
> which means hooking-up music-functions.ly?
I don't think so. The lilypond domain is used by LilyPond at run time,
and AFAIK doc strings are not used at run time, but are rather extracted
to build the documentation, so Documentation/po/lilypond-doc.pot s
HTML docs with links
between the same page in different languages and same file names
prefixes for all languages regardless of the node names.
(I'm not sure my explanation makes sense, and of course that's more easy
to say than to do...)
--
John Mandereau <[EMAIL PROTECTED]>
Till Rettig wrote:
> Jan Nieuwenhuizen wrote:
> > This imported cleanly. Thanks. John Mandereau, our new Translation
> > Meister will be taking over from me.
> >
> >
> Ok, will remember this. In fact I sent another patch a couple of hours
> la
f
> commands to issue in a row so in the end you would get clean apllyable
> patches.
Yes, but in the README I added some blurbs to the "straightforward chain
of commands" to help newbies gradually understand git concepts. IMHO
concepts are more important than the actual commands.
entation.html
> es/install/cygwin.html
>
> I didn't touch the big-file, though, as per some comments I've been
> reading about the possibility of removing it?
The big-page file is generated by make from the sections of the essay
(one
s copy'n'paste commit numbers with mouse, so copying 8 or 10 or
40 characters is almost the same effort. But in this case, the commit
numbers are useless, as they may be not the same as those of commits
made by the git pusher (that's me).
Johannes, thank you very much for all Git support you provided; you
should be credited in README ;-)
Till, I think you needn't bother translating README.de; do it only if it
seems essential to you.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
ause you took the committish of a local commit (i.e. a
commit you made but which is missing in git.sv.gnu.org). Please fix this
by using the committish given by
git-rev-parse web/master
By the way, could you please follow instructions in README to update the
translation? Thanks
Han-Wen Nienhuys wrote:
> John Mandereau escreveu:
> >>> git-rev-list HEAD | head -1
> >> It is way easier to say
> >>
> >> $ git rev-parse HEAD
> >
> > That's what README tells now.
>
> Actually, I think it's better to use
hat you actually use Git 1.4.4.1 or newer? What does
git --version
says?
I see no other reason for saying instructions are incorrect: I have
actually tested these instructions under GNU/Linux, with Git 1.4.4.2.
Do a Git expert knows why this doesn't work?
Darn, at second thought,
rk and save the file, then run "git update-index" on
this file. After all that, commit and the merge should be complete.
However, it seems according to git-pull output that you haven't
committed files in es/sponsor/; you should add them or run
git-update-index on them
aders to .(i)tely files of the user manual, in order to make
translation checks, and I just saw that point-and-click.itely seems to
be stalled: it isn't included in lilypond.tely, and there is already a
"Point and click" node in running.itely. What should we do with this
fil
Graham Percival wrote:
> John Mandereau wrote:
> > headers to .(i)tely files of the user manual, in order to make
> > translation checks, and I just saw that point-and-click.itely seems to
> > be stalled: it isn't included in lilypond.tely, and there is already a
>
.. The LilyPond Ms. Manners of Music Printing, yes?
No, you're mistaken. Have a more careful look at the layout of
lilypond.org front page. There are two distinct columns, with two
distincts titles: "Dive into... The LilyPond" for the 1st column, and
"Ms. Manners of Music Print
GNUmakefile
> #README
> #TRANSLATION
> #colors.css
> #de/
> #es/
> #fr/
> #newweb.css
> #nl/
> #po/
> #scripts/
> #site/
Argh, this looks bad. Try to resolve conflicts if any, then do "git add"
on every file
Till Rettig wrote:
> John Mandereau wrote:
> > Please read the revised README and translate the parts of README.de that
> > brings something interesting in addition to the English README.
> >
> Well, no I checked it. I don't think there is anything I have in my ow
today. So I think you should
> only apply the last patch (0003-replace-of-testimonials-txt). I will
> send you all of them though.
Third patch applied and pushed to git.sv.gnu.org.
Thanks
--
John Mandereau <[EMAIL PROTECTED]>
___
lil
racter set UTF-8, not Latin1. This will really become a problem for
the PDF (outputted by Texinfo/TeX) when we decide to make PDF of Lily
docs translation.
Well, you can safely ignore these warnings.
See also
http://lists.gnu.org/archive/html/lilypond-d
translation in both branches. Is this a good plan?
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
l
is clearly outdated, but cygwin.html is still valuable (Cygwin provides
2.10.7), so it should't be renamed to windows.html. You're right it
should be clearly mentioned there are 2 LilyPond flavours on Windows
(native and Cygwin).
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
, I'll try to sync doc improvements as they are committed.
Greetings
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
rite some blurb like where and what to
click for installing and getting started for the Windows version (to be
put in install/windows.html?), like what already exists about Cygwin.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
h as a gzipped file so as
> not to mangle the coding.
>
> Should I do the pull after the modifications?
Yes, and it might tell you that you have to merge.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
li
ond scores, one for each notation domain:
vocal music, orchestral full score, piano music, contemporary music...
For this, we would need more than one features page.
If I do something (not before February anyway), may I take inspiration
from typography-demo.svg?
--
John Mandereau <[EMAIL PROTECT
s that, big-pages.html is generated by a script from all pages of
the essay, so it should be ignored (not committed, not translated, and
not updated). I've enabled the big page generation for German and
Spanish in GNUmakefile.
I've also removed the dirty page
es/about/automated-engravi
m there you should continue to the tutorial.
Agreed. On the other hand, the route designed by Jan & Han-Wen is
clearly Home -> Diving into the LilyPond -> pages in switch/, ending
with howto -> download page -> getting-started. Adding a link doesn't
hurt, though.
Cheers
--
Jo
Le samedi 06 janvier 2007 à 20:01 +0200, Till Rettig a écrit :
>
>
> John Mandereau wrote:
> >
> > > >
> > > > http://lilypond.org/web/about/features
> > > >
> > > yes, well, actually, I also want that page to have a
&
linked from a place where it is written LilyPond is an
automated engraving system: why not about/features, as pages in switch/
already have enough contents and links, and about/features should be
shorter when revised?
--
John Mandereau <[
_lilypond.org_'s one. You
can check out Git LilyPond sources to get it.
> I attach the diffs, for the bad committish and es.po.
Thanks, applied.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
itely vote for adding such a clarification: the very beginning of
the tutorial already explains you can copy'n'paste the snippets, but
omits that it is the only way to get ready-to-compile snippets.
I'm going ahead on this.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
John Mandereau wrote:
> Graham Percival wrote:
> > For the backporting of docs, I'd just start by copying everything and
> > trying to build it with stable. The skyline spacing docs obviously
> > won't work (so remove them from the backported docs), but AFAIK
Le dimanche 07 janvier 2007 à 03:40 -0600, Daniel Tonda Castillo a
écrit :
> Daniel Tonda Castillo escribió:
> > John Mandereau escribió:
> >> Daniel Tonda wrote:
> >>
> >>> I changed the committish ids for files showing a bad committish when
>
t when I removed in git the `:' I had
added.
I wonder whether the style rule you explain should apply to the whole
user manual, as music snippets often continue sentences; I (erroneously)
added colons where I felt the snippets continue the esntence.
Sorry, I don't know good English
od French style somewhere; Jean-Charles, what
do you know about this?
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
uldn't have changed anything, so unless you complain I'm
going to undo all period replacements I've made in introduction.itely.
Greetings
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
exit"
> -msgstr "affiche le numéro de version"
> +msgstr "Afficher le numéro de version et quitter."
Idem. All option descriptions should have the same capitalization at
beginning (lower case) and shouldn't end with a period. It's generally
better to apply the same typography as the msgids.
>
>
> #: relocate.cc:354
> -#, fuzzy, c-format
> +#, c-format
> msgid "Relocation file: %s"
> -msgstr "Fichier de relocation %s\n"
> +msgstr "Réaffectation au fichier : %s\n"
Est-tu sûr de vouloir changer ceci ?
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
that's much work!
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
28e83c9af8d9dc16baab
diff --git a/site/about/thanks.html b/site/about/thanks.html
index 2af2fa5..e0a1990 100644
--- a/site/about/thanks.html
+++ b/site/about/thanks.html
@@ -55,7 +55,7 @@
lilypond.org was brought to you
by
- Tineke de Munnik, Dutch translation
+ Tineke de Munnik, D
Hi Daniel,
sorry for the late reply!
Le dimanche 07 janvier 2007 à 15:50 -0600, Daniel Tonda Castillo a
écrit :
> John Mandereau escribió:
> > Haven't you read the whole README? You have finished the web site
> > translation, this is very cool. Recently, the English pages ha
Le vendredi 12 janvier 2007 à 17:20 +0100, Jan Nieuwenhuizen a écrit :
> John Mandereau <[EMAIL PROTECTED]> writes:
>
> > What do the LilyPond hackers think of this?
>
> Indeed, use utf-8. I'd try with gnome-terminal, xterm does not
> show utf-8 by default, he
[Moving from the -user list]
Jan Nieuwenhuizen a écrit :
> John Mandereau <[EMAIL PROTECTED]> writes:
>
> > We translated all testimonials excepted the ones from Chris Cannam (too
> > difficult to translate) and Vaylor Trucks (easy to understand). Till,
> > you'
e notice in testimonials), so you needn't
worry about this. It will be different for documentation translation,
though.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
or to
> help her incorporating the changes made in the mean time?
After a quick test, I say "yes", but only if you do things right from
the beginning with Git, which is seldom true. Current check-translation
system is slightly more tolerant and reliable IMHO.
--
John Mandereau <
being already in translated pages.
After that, you will be able to safely follow README instructions for
future translation updates.
Good luck!
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
and pushed to Git. The site I build myself in out/site
with 'make' looks good, but it looks like it hasn't changed on
lilypond.org (it still shows only French and English big pages). Jan,
do you know what's wrong?
Greetings
--
John Mandereau <[EMAIL PROTECTED]>
_
encoding.
That's all right. If you email client supports utf-8, you even needn't
(g/b)zip the patch.
> > You learn something every day.
:-)
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
arranty' para más
> información.
It looks good. I've committed the new es.po. Thanks!
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
ession (in this case, a half note).
>
> Probably should read:
>
> The above is another expression, and therefore, it may be combined
> again with a simultaneous expression (in this case, a half note).
Thanks, fixed.
Greeting
Le dimanche 14 janvier 2007 à 13:18 +0100, Johannes Schindelin a écrit :
> On Sat, 13 Jan 2007, John Mandereau wrote:
> > See also Jean-Charles's gitrux, that he recently sent on this list.
>
> I missed that. I also cannot find it in the archives. What does it do?
See the &
Le dimanche 14 janvier 2007 à 15:31 +0200, Till Rettig a écrit :
> John Mandereau wrote:
> >
> > What command exactly do you use to generate patches? The following
> > should make clean patches, as long as you committed all your changes and
> > pulled:
> >
&g
except the committish: changing it is
useless as the English corresponding page hasn't changed.
check-translation checks and warns about changes in the English pages,
not in the translated ones.
Greetings
--
John Mandereau <[EMAIL PROTECTED]>
___
ry and
engraving terms, like one of the French translators Frédéric Chiasson
did:
http://lists.gnu.org/archive/html/lilypond-user-fr/2006-12/msg3.html
This kind of glossary is useful to make sure you always translate a
technical word the same way.
Cheers
--
John Mande
avoid
check-translation false warnings).
Cheers,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
.6.7, or upgrade to latest 1.8 with the rational bugfix patch
available in http://lilypond.org/vc/gub.darcs/patches/
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Le samedi 20 janvier 2007 à 12:22 +0100, Francisco Vila a écrit :
> El vie, 19 de ene de 2007, a las 11:22:57 +0100, John Mandereau dijo:
> > Thanks, applied. Your patch was clean, excepted for es/index.html. It
> > looks like you haven't pull since you send the last patch to
end of each page, so we could hack it in add_html_footer.py. As
I'm cleaning it up along with www_post and mirrortree, I offer to work
on this too.
Greetings
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
is if it looks OK? I'd like to push French doc updates
along with this, too.
I'm a bit sorry I am slower than usual for pushing and replying to
emails; I'll have more free time in end of March.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
diff --git a/buildscripts/add_htm
argets=offline|onlineset page processing depending on the target
> >offline is for reading HTML pages locally
> >online is for hosting the HTML pages on a website with content
> > negotiation
> > - mail_address set \&q
Hi Francisco,
please keep future such traffic on the list.
Le lundi 05 février 2007 à 18:41 +0100, Francisco Vila a écrit :
> El lun, 05 de feb de 2007, a las 01:29:53 +0100, John Mandereau dijo:
> > This one doesn't work...
>
> So, does the other one work? You haven't
is list for the Git details.
There is no technical support (makefiles and buildscripts) to translate
the glossary, but if it is fully translated, this won't be hard to do.
When you have updated the German web site, you'll be ready to start
translating the tutorial.
Cheers
--
John M
> >
> Sounds promising, though I am afraid it will take me some time...
The tutorial is 1400 lines long.
> Ah yes, and how is it: is there also a script like check-translation
> for the docs?
Yes, there is. I'll have time to write a full README next week, when I
have a vacation.
Cheers,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
gt;
> @c to get decent French quotes in ``foo''
> @macro qq{TEXT}
> @html
> « \TEXT\ »
> @end html
> @end macro
>
> ?
Thanks Werner, this is fixed in Git.
I had already looked for the thin space HTML code, without success. I'd
like to put thin spa
Le dimanche 11 février 2007 à 21:52 +0100, Francisco Vila a écrit :
> This refers once again to sponsor/options.html file
Thanks, all the typos you mentioned are fixed.
Cheers,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mai
Le lundi 12 février 2007 à 22:12 +0200, Till Rettig a écrit :
> John Mandereau wrote:
> > There was a nitpick with the committish in
> > about/engraving/input-format.html: it looks like you had made the patch
> > with a revision different from the web/master upstream.
> &
sn't
> apply cleanly...
Applying one or a hundred patches is equally trivial as long as the
patches succesion was made against the latest upstream branch.
I've applied your patches, thanks.
--
John Mandereau <[EMAIL PROTECTED]>
__
Le mercredi 14 février 2007 à 11:01 +0100, Francisco Vila a écrit :
> Attached are latest spanish web updates.
Thanks, I've applied patch #7; why did you send the 6 other?
Could you please fix the bad committish in es/index.html too?
Cheers,
--
John Mandereau <[EMAI
Le vendredi 16 février 2007 à 01:49 +0100, Francisco Vila a écrit :
> El jue, 15 de feb de 2007, a las 01:03:47 +0100, John Mandereau dijo:
> > Thanks, I've applied patch #7; why did you send the 6 other?
>
> because you had asked me to do so, at least in one ocassion. You s
will be more active and
will be able to reply within a reasonable time again on mid-March, when
I have *only* 20 hours math per week.
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://l
Le samedi 17 février 2007 à 18:43 +0100, Jean-Charles a écrit :
> Hi all!
>
> Here is an update for the po/fr.po
Thanks, applied.
- John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
ntil Friday evening, as I want to have a deeper
look at the French updates and would like to update the fr/*.itely
skeletons with an ad-hoc script, so the French docs deserve an
announcement on lilypond.org: the whole learning manual excepted
tweaks.itely is translated, and the Basic notation
ion? or rather translation/master and
translation/stable-2.10?
Thanks in advance for your feedbask
Cheers
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
in a directory and all
other branches in another directory. To create a repository with only
the web/master branch, see README from web/master:
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=README;hb=web/master
Cheers
--
John Mandereau
This might be insteresting for other translators, so I CC this to
-devel.
Le samedi 03 mars 2007 à 17:40 +0100, Francisco Vila a écrit :
> El sáb, 03 de mar de 2007, a las 12:30:42 +0100, John Mandereau dijo:
> > Le vendredi 02 mars 2007 à 21:30 +0100, Francisco Vila a écrit :
> &
901 - 1000 of 1573 matches
Mail list logo
