Re: 2.16.1

[David Kastrup]

Francisco Vila <address@hidden> writes:

> 2012/10/22 David Kastrup <address@hidden>:
>>
>> Here is another problem with translations that is rather curious:
>> commit bf1900d44f4937fe8e69e0e04e188a0c3daf5172
>> Author: Francisco Vila <address@hidden>
>> Date:   Thu May 31 11:18:26 2012 +0200
>>
>> has some bit of English content in here that is totally out of place:
>> and that causes documentation compilation of issue 2883 to fail after
>> syntax changes.
>
> I have pushed the missing translation.
>
> But the @lilypond snippet matches the one from original English in
> Documentation/changes.tely , all snippets do match, so how can the
> Spanish version break anything?

Well, the problem more or less is that changes.tely (in English or in
Spanish) does not have a \version header.  I don't really know whether
this is intentional.  It is possible that it is, in order to be able to
show before/after pairs of LilyPond syntax without having the before
version clobbered by convert-ly.

Yes, this is rather speculative.  Whether this is intentional or not, it
means that if changes.tely contains stuff that needs a convert-ly run
before working again, stuff will go southward.

The problem now is not actually that Documentation/es/changes.tely
contained unconverted material.  The problem rather is that
Documentation/es is the _only_ translation containing a changes.tely
file at all!

If you take a look at
<URL:http://lilypond.org/doc/v2.16/Documentation/changes/index.html>,
you'll see that the _only_ "other language" offered at the bottom of the
page is "español".

Now the changes have not been reset to empty in master yet as
translations are generally still in 2.16 state.

I have no idea why Spanish is the only translation caring about
"Changes".  But while that is the case, it would be helpful if you
already committed a change to staging resetting the Spanish "Changes"
section to the state in the international Changes document.  Once we
change the translation branch over to master rather than stable/2.16,
this change will get merged into translation with the initial
master->translation merge.

-- 
David Kastrup