About changes document

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

About changes document

Francisco Vila
Hello, this is going to be a confusing message from a confused translator.

Something looks a bit strange regarding to the changes document. I hope
somebody clarifies it.

http://lilypond.org/doc/v2.19/Documentation/changes-big-page.es.html

This is my (untranslated) changes page. I am glad other languages have
it translated.

If I change 2.19 --> 2.20 in the URL, more or less the same page shows,
except deutsch appears as a new language in the list.

Now, latest changes in changes.tely in master branch are from 2018 (!).
No changes since then? Well, it is possible.

But changes.tely in master says "New features in 2.22 since 2.20" which
is somewhat surprising. That edit in the file is from 2017 (!),  see
60298172eaa

So what I don't understand is how building the web does not reflect that
edit made 3 years ago.

If I hypotetically translated the "2.18 to 2.20" changes document, how
long would it be available? A few days I imagine, just until "2.20 to
2.22" comes into effect. Does it worth the effort?


--
Francisco Vila - Badajoz (Spain)
paconet.org , lilypond.es


Reply | Threaded
Open this post in threaded view
|

Re: About changes document

David Kastrup
Francisco Vila <[hidden email]> writes:

> Hello, this is going to be a confusing message from a confused translator.
>
> Something looks a bit strange regarding to the changes document. I
> hope somebody clarifies it.
>
> http://lilypond.org/doc/v2.19/Documentation/changes-big-page.es.html
>
> This is my (untranslated) changes page. I am glad other languages have
> it translated.
>
> If I change 2.19 --> 2.20 in the URL, more or less the same page
> shows, except deutsch appears as a new language in the list.
>
> Now, latest changes in changes.tely in master branch are from 2018
> (!). No changes since then? Well, it is possible.

No idea how you get there.

git log origin --oneline Documentation/changes.tely

gives me (first page)
7b52921bb7 Issue 5773: Quarter Tones for all Languages incl. MusicXML import
1edb8b3c85 Update web content
28e08cc4c2 Issue 5610/2: add Changes entry
2b52bc2bf1 Issue 5520/2: add \ambitusAfter to Changes
ff348fa75a Issue 5486/1: add very short/Henze fermata commands
200658ca20 Issue 5511/4: doc: NR and Changes
464cf0d811 Fix #687: Include MIDI swing script in default distribution
77b98cbbc6 Issue 5487/2: add new fermatas to Changes doc
0f5c046811 Functions to invert chords or drop/rise chord notes
a27178e49f Add news item for ukulele changes by Davide Bonetti
78225bc1b3 Chord names clean-up; no more Banter, exceptionsPartial or \powerChords.

[...]

and the last one of those is

commit 78225bc1b386e12dc1d03a5d2c7a017c0a52a22d
Author: Valentin Villenave <[hidden email]>
Date:   Mon Jan 14 19:02:13 2019 +0100

    Chord names clean-up; no more Banter, exceptionsPartial or \powerChords.

> But changes.tely in master says "New features in 2.22 since 2.20"
> which is somewhat surprising. That edit in the file is from 2017 (!),
> see 60298172eaa

It would be when we split off the stable release branch for 2.20.  After
that point of time, changes from 2.18..2.20 would be collected in the
stable branch, and changes from 2.20 to 2.22 in the master branch.

> So what I don't understand is how building the web does not reflect
> that edit made 3 years ago.
>
> If I hypotetically translated the "2.18 to 2.20" changes document, how
> long would it be available? A few days I imagine, just until "2.20 to
> 2.22" comes into effect. Does it worth the effort?

It would remain _permanently_ available in the 2.20 documentation and
not at all in the 2.21 documentation.  You would add your translation of
the 2.18 to 2.20 changes document to the stable/2.20 branch, as a
translation of the English version in
origin/stable/2.20:Documentation/changes.tely

--
David Kastrup


Reply | Threaded
Open this post in threaded view
|

Re: About changes document

Francisco Vila
El 2/3/20 a las 0:34, David Kastrup escribió:
> It would remain_permanently_  available in the 2.20 documentation and
> not at all in the 2.21 documentation.  You would add your translation of
> the 2.18 to 2.20 changes document to the stable/2.20 branch, as a
> translation of the English version in
> origin/stable/2.20:Documentation/changes.tely

Thank you. I think I was looking at the wrong branch.

We can not push to stable directly, I think.

--
Francisco Vila, Ph.D. - Badajoz (Spain)
paconet.org , lilypond.es


Reply | Threaded
Open this post in threaded view
|

Re: About changes document

David Kastrup
Francisco Vila <[hidden email]> writes:

> El 2/3/20 a las 0:34, David Kastrup escribió:
>> It would remain_permanently_  available in the 2.20 documentation and
>> not at all in the 2.21 documentation.  You would add your translation of
>> the 2.18 to 2.20 changes document to the stable/2.20 branch, as a
>> translation of the English version in
>> origin/stable/2.20:Documentation/changes.tely
>
> Thank you. I think I was looking at the wrong branch.
>
> We can not push to stable directly, I think.

We have no individual rights in the repository.  According to the
repository, if you have permission to push anything, you have permission
to push everything.

Which does not mean that it is a good idea if you don't know what you
are doing...

--
David Kastrup