Le samedi 03 mars 2007 à 17:19 +0200, Till Rettig a écrit :
> Hi John,
>
> I will now slowly start the translation of the documentation. I got
> quite most things clear from your TRANSLATION file, many thanks to you
> for that!
Well, I feel I only deserve half acknoweledgements, as this file is
Le 03.03.2007 16:19, Till Rettig disait :
Hi John,
I will now slowly start the translation of the documentation. I got
quite most things clear from your TRANSLATION file, many thanks to you
for that! One thing is with the first file I started with:
lilypond.tely. Here is a lot of nodes that a
Hi John,
I will now slowly start the translation of the documentation. I got
quite most things clear from your TRANSLATION file, many thanks to you
for that! One thing is with the first file I started with:
lilypond.tely. Here is a lot of nodes that are not mentioned in the
nodenames hat shou
John Mandereau escreveu:
> Since the translated documentation itself is ready to be released, merge
> and apply your trick as you like.
>
> So, I have a question about merging branches, since I may need to do it
> sooner or later. IIRC, Han-Wen has once told Joe Neeman on the list that
> it was be
Jan Nieuwenhuizen wrote:
> Ok, thanks. We may want to merge then and use my silly
> build-html-docs-twice solution. Or was that reverted now, Han-Wen?
Since the translated documentation itself is ready to be released, merge
and apply your trick as you like.
So, I have a question about merging b
Jan Nieuwenhuizen escreveu:
> John Mandereau <[EMAIL PROTECTED]> writes:
>
>> Btw, the tutorial node names are fully translated and the tutorial is
>> polished (I pushed that a few days ago).
>
> Ok, thanks. We may want to merge then and use my silly
> build-html-docs-twice solution. Or was tha
John Mandereau <[EMAIL PROTECTED]> writes:
> Btw, the tutorial node names are fully translated and the tutorial is
> polished (I pushed that a few days ago).
Ok, thanks. We may want to merge then and use my silly
build-html-docs-twice solution. Or was that reverted now, Han-Wen?
Jan.
--
Jan
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 done already? If you have
> translation
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 done already? If you have
> translation
Jan Nieuwenhuizen escreveu:
>> 3) roll a single docball like today, and add into the docball a Python
>> script that the end user could run to tweak the links according to his
>> language preferences. It shouldn't be too difficult, as Python is
>> shipped within GUB.
>>
>> I'd vote for 3)
>
> Me t
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 done already? If you have
translation updates, please push that (esp. the nod
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.1
>
> What's the status of this?
I expect to
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.1
What's the status of this?
It's important that this change gets pushed out soon
John Mandereau <[EMAIL PROTECTED]> writes:
> So, if you and Jan are not in a hurry to release 2.10.1 or to merge
> fr-doc after 2.10.1, I volunteer to work on GNUmakefile.in:WWW-post and
> add-html-footer.py.
Grand, please do so.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - T
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.1, I volunteer to work on GNUmakefile.in:WWW-post and
add-html
John Mandereau escreveu:
> I'm not sure what Jan means, but instead of just a CONTENT_NEGOTIATION
> switch, there could be several simultaneous docs targets, as I
> suggested in
> http://lists.gnu.org/archive/html/lilypond-devel/2006-11/msg00206.html
>
> I don't mean the html docs should be bui
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Quickest hack I can think of:
>
> enclose the menu in
Han-Wen Nienhuys wrote:
> Jan Nieuwenhuizen escreveu:
> > No idea. I also only see commits on master on my rss feed?
For branches other than master, I update my local copy, then I use gitk
to track the changes. Thanks to it I could check in 5 minutes that the
French tutorial.itely was almost up t
Jan Nieuwenhuizen escreveu:
>> this has to be done, because output distance computations need
>> information from previous versions.
>
> Hmm, then I misread lilypond.org.py. To bad, I checked-in something
> that produces a plain doc ball, and an extension-stripped
> target//build/out/web-root int
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> rsynced from web-root, and not untarred from the docball?
>
> no, it's rsynced from uploads/webdoc/v/
>
> this has to be done, because output distance computations need
> information from previous versions.
Hmm, then I misread lilypond.org.py. To b
Jan Nieuwenhuizen escreveu:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
>>> Yes, done. Local docs tarballs should now be built doing
>>>
>>>make web CONTENT_NEGOTIATION=
>> This might be a bit problematic:
>
> Yes, we need to build the .html files twice.
>
>> the -documentation tarball
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> Yes, done. Local docs tarballs should now be built doing
>>
>>make web CONTENT_NEGOTIATION=
>
> This might be a bit problematic:
Yes, we need to build the .html files twice.
> the -documentation tarball that we upload is the same one as comes
Jan Nieuwenhuizen escreveu:
> John Mandereau <[EMAIL PROTECTED]> writes:
>
>> Please wait for me to finish to check the tutorial translation, where
>> there are still spelling mistakes. I'll push into fr-doc as soon as it's
>> done.
>
> Sure. When do you estimate you will be done?
>
>> Besides
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> It works for me, see
>
> http://peder/fr/Documentation/user/lilypond/Tutorial.html
and for those not browsing from inside my home network, try
http://peder.xs4all.nl/fr/Documentation/user/lilypond/Tutorial.html
--
Jan Nieuwenhuizen <[EMA
John Mandereau <[EMAIL PROTECTED]> writes:
> Please wait for me to finish to check the tutorial translation, where
> there are still spelling mistakes. I'll push into fr-doc as soon as it's
> done.
Sure. When do you estimate you will be done?
> Besides that, .html and .png extensions in HTML li
Le samedi 25 novembre 2006 à 15:22 +0100, Han-Wen Nienhuys a écrit :
> Jan Nieuwenhuizen escreveu:
> > Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> >
> >> Yes, I understand. We'll have to see about that. I'd like to
> >> keep the snippets untranslated for now.
After thinking twice about it,
Jan Nieuwenhuizen escreveu:
> Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>
>> Yes, I understand. We'll have to see about that. I'd like to
>> keep the snippets untranslated for now.
>
> I've added a fix for the sourcefileline issue in the fr-doc branch.
> That means that we're ready to merge
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Yes, I understand. We'll have to see about that. I'd like to
> keep the snippets untranslated for now.
I've added a fix for the sourcefileline issue in the fr-doc branch.
That means that we're ready to merge the branch and release the tutorial,
as
John Mandereau <[EMAIL PROTECTED]> writes:
> Not for most snippets, but snippets with a lot of English text would be
> a bit more difficult to read, like the one which shows all avalaible
> fields in \header{}.
Yes, I understand. We'll have to see about that. I'd like to
keep the snippets untra
Jan Nieuwenhuizen wrote:
> John Mandereau <[EMAIL PROTECTED]> writes:
> > Do you mean we must not translate the snippets until that's fixed?
>
> I intended for the snippets not to be translated at all. Do we
> really want translated snippets?
Not for most snippets, but snippets with a lot of Eng
John Mandereau <[EMAIL PROTECTED]> writes:
> The mailing list allows the translation to be done in team, just like
> the French translators always have done. It's slower than working alone,
> but results in much more quality.
Ok, so I'd say: go for that.
> Do you mean we must not translate the s
John Mandereau wrote:
> Besides that, I hope I don't have to download the entire git history to
> track the `fr-doc' branch. I'm sure there is an easy way to tell git to
> push to/pull from 'fr-doc' instead of 'stable/2.10', but I'm relatively
> new to it... I'm going to investigate it.
That was j
John Mandereau <[EMAIL PROTECTED]> writes:
> Thank you for bearing with my patch. After that, what do you think the
> most efficient plan is? Should I keep working on the
> makefiles/buildscripts even if you have to polish my work, or should I
> simply restart the translation work on the lilypond-
Jan Nieuwenhuizen wrote:
> John Mandereau <[EMAIL PROTECTED]> writes:
>
> > Thank you for bearing with my patch. After that, what do you think the
> > most efficient plan is? Should I keep working on the
> > makefiles/buildscripts even if you have to polish my work, or should I
> > simply restart
John Mandereau <[EMAIL PROTECTED]> writes:
> Here's (finally) my first patch against stable/2.10 git head for the
> documentation build infrastructure.
I've included the patch verbatim and pushed it as the `fr-doc' branch,
and I'm building it right now.
> - French translation of the tutorial, wh
Hello,
Here's (finally) my first patch against stable/2.10 git head for the
documentation build infrastructure.
It includes:
- French translation of the tutorial, which is up-to-date according to
checking against the revision history of English tutorial.itely.
- Documentation/po: directory for
Francisco Vila wrote:
> I'd like to start the translation of all docs to spanish. I beg your
> advice on how to easily do this, in a manner that it keeps being
> integrated with new developments.
>
> - which files to translate and what parts of them
> - what to do with the translated files, who I
Le dimanche 05 novembre 2006 à 15:02 -0800, Graham Percival a écrit :
> John Mandereau wrote:
> > A number of French users have created a page or a section about Lily on
> > their personal sites, sometimes with briliant ideas and words explaining
> > what LilyPond is and does. That's great and bad
John Mandereau wrote:
A number of French users have created a page or a section about Lily on
their personal sites, sometimes with briliant ideas and words explaining
what LilyPond is and does. That's great and bad at the same time. It's
great because this work is independent from the LilyPond te
Han-Wen Nienhuys wrote:
> John Mandereau escreveu:
> > It's important to have the same html filenames, but the node names
> > should be translated, otherwise all that hard translation work is not
> > very worthy imho.
>
> I don't understand (bear with me , I haven't had a look at the
> infrastru
I'd like to start the translation of all docs to spanish. I beg your
advice on how to easily do this, in a manner that it keeps being
integrated with new developments.
- which files to translate and what parts of them
- what to do with the translated files, who I have to send them to,
et cetera
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> It's important to have the same html filenames, but the node names
>> should be translated, otherwise all that hard translation work is not
>> very worthy imho.
>
> I don't understand (bear with me , I haven't had a look at the
> infrastructure for
John Mandereau escreveu:
It's important to have the same html filenames, but the node names
should be translated, otherwise all that hard translation work is not
very worthy imho.
I don't understand (bear with me , I haven't had a look at the
infrastructure for translation at all), but wouldn
Graham Percival escreveu:
John Mandereau wrote:
Graham Percival wrote:
Is there anything I should be doing (or not doing) while working on
the docs?
I don't think so, except renaming input files of the user manual too
frequently.
I don't plan on doing that frequently, but we're currently
Jan Nieuwenhuizen wrote:
> Ok. If it helps the translators, we can include your patch after we
> release 2.10.
A proper build and maintenance infrastructure for translated docs would
certainly help the translators, but it would help users and developers
much more.
In fact, the translators alread
John Mandereau wrote:
Graham Percival wrote:
Is
there anything I should be doing (or not doing) while working on the docs?
I don't think so, except renaming input files of the user manual too
frequently.
I don't plan on doing that frequently, but we're currently overdue for a
few renaming
Graham Percival wrote:
> I confess that I don't know anything about translation in lilypond.
As far as I know from what I've read in the makefiles and buildscripts,
there is today almost nothing for translating the documentation. I'm
currently working on this, but I will certainly need help from J
John Mandereau wrote:
IMHO it's useful to translate the whole user manual, because:
- it is the part of the documentation where there is most explanation
blurb, and so it is the part of the documentation where translation is
most useful and (technically speaking) doable (unlike the program
refere
John Mandereau <[EMAIL PROTECTED]> writes:
> I have tested Jan's makefile (see patch from
> http://lists.gnu.org/archive/html/lilypond-devel/2005-09/msg00017.html )
> against latest tutorial French translation: it works except that I had
> to do some minor corrections, and PNG symlinks to PNGs of
John Mandereau escreveu:
Jan and I have been working very hard over the last days to give our
build infrastructuer an update. It should be possible, in the short run,
to have an almost-single-button-push method of compiling the documentation
By "build infrastructure", do you mean the git r
John Mandereau escreveu:
Regarding ly snippets, there are 2 possibilities:
1) PNGs and code snippets from the English docs are used for the
translated docs through symlinks. The main advantage is that translated
docs don't take too much time to make and don't take too much disk space
on lilypond
Han-Wen Nienhuys wrote:
> Ludovic Sardain escreveu:
> > Hello,
> >
> > As you know, we are a small team of french translators, and for some
> > months, we're not doing anything, because none of us has understood
> > how to compile the documentation. There's also some problem about
> > whereas we m
Thank you very much, so I go back to the translation.
Ludovic
Jan and I have been working very hard over the last days to give our
build infrastructuer an update. It should be possible, in the short run,
to have an almost-single-button-push method of compiling the documentation
--
Han-Wen Ni
Ludovic Sardain escreveu:
Hello,
As you know, we are a small team of french translators, and for some
months, we're not doing anything, because none of us has understood
how to compile the documentation. There's also some problem about
whereas we must translate or not the nodes titles.
Jan and
Hello,
As you know, we are a small team of french translators, and for some
months, we're not doing anything, because none of us has understood
how to compile the documentation. There's also some problem about
whereas we must translate or not the nodes titles.
Is there a way to make our job easy
55 matches
Mail list logo
