Re: LSR updates and translations

[Phil Holmes]

----- Original Message ----- 
From: <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: "Devel" <address@hidden>
Sent: Wednesday, June 20, 2012 11:38 AM
Subject: Re: LSR updates and translations


> On 20 juin 2012, at 12:29, Phil Holmes wrote:
>
> > ----- Original Message ----- From: "Francisco Vila" 
> > <address@hidden>
> > To: "Phil Holmes" <address@hidden>
> >
> > > Good, I like it in principle, but how will be changes being tracked
> > > using SHA IDs?
> > >
> > > Currently, translations have a SHA ID which is that of the snippet it
> > > is a translation of. Any change to the original snippet is done in a
> > > commit whose SHA ID is used to generate a diff against the ID of the
> > > translation. This determines what the translators have to work on.
> >
> >
> > That's a bit I'd deliberately glossed over since I didn't/don't fully 
> > understand it as yet.
> >
> > My idea would be that, using the new system, changed snippets would look 
> > exactly like changed documentation files.  If I modify, say, 
> > /Documentation/notation/ancient.itely, how do the translators pick up 
> > that this has been changed?
>
> Just a couple observations, both of which may be entirely irrelevant, as I 
> do not know this part of LilyPond at all aside from various exercises in 
> code pilfering.
>
> 1) In addition to making sure the snippets are safe, would it be worth it 
> to make sure that the snippets are didactic/practical (not too many hacks, 
> well written, etc.)? Is there a way to keep alive the cookbook (and thus 
> risk-prone) culture of the LSR while at the same time implementing your 
> plan?

Snippets have to be approved before they go live.  I used to do this, but 
the current regular approver is Harm (although hee may not be doing it right 
now, owing to an injury).  We give ones tagged as "docs" a good check, and 
the others a more cursory check before letting them go live.  This should 
also minimise the potential harm they can do, but better safe than sorry.

> 2) The lilypond used on the LSR website is sometimes out of phase with the 
> current stable release of LilyPond. Would this be of issue under the 
> proposed plan?

convert-ly and snippets/new would handle this.

--
Phil Holmes