Re: improving LilyPond useability

[Alex Loomis]

I can proofread the English version.



On Dec 27, 2013, at 4:08 AM, Daniel Rosen <address@hidden> wrote:

>> -----Original Message-----
>> From: Janek Warchoł [mailto:address@hidden
>> Sent: Thursday, December 05, 2013 12:58 PM
>> To: Daniel Rosen
>> Cc: LilyPond Users; Jan Nieuwenhuizen; David Kastrup; Urs Liska; Noeck;
>> Kieren MacMillan; Joseph Wakeling; Benjamin CL; Richard Shann
>> Subject: Re: improving LilyPond useability
>> 
>> Hi Daniel,
>> 
>> (sorry for delayed reply - so many emails flying around...)
>> 
>> 2013/12/2 Daniel Rosen <address@hidden>:
>>>> -----Original Message-----
>>>> From: Janek Warchoł [mailto:address@hidden I've created a
>>>> "Quick-start" tutorial some time ago - my choir colleagues used it
>>>> when crowd-typesetting "Dixit Dominus".  It's only
>>>> 6 pages long and covers nearly all basic notation elements than a
>>>> beginner would need - but it's not just a cheat-sheet: it introduces
>>>> and teaches how to use Lily.  Add to that 3 pages explaining how to
>>>> write basic structure and we'd have something that gives an easy (but
>>>> complete enough) introduction to LilyPond in half an hour (as opposed
>>>> to 2 days of reading and heavy thinking for the Learning manual).
>>> 
>>> Sounds awesome.
>>> 
>>>> I'd be more than happy to share this tutorial and translate it, but i
>>>> don't have time to lead an effort to incorporate it in our docs.  So,
>>>> if someone wants to take responsibility for this, i'll help, but
>>>> without support this will not work out!
>>> 
>>> I would definitely be willing to help with this, but I’m afraid that
>>> my skill set may be too limited to take the lead--in particular, I
>>> don't speak any languages well enough to translate them into English
>> without resorting to Google.
>> 
>> That's not a problem at all!  I would translate my materials to English; as 
>> for
>> translating them back to other languages we have people who'd take care of
>> that.  What you'd have to do is to turn my materials into proper
>> documentation: find a place for it, fix wording (my translation probably 
>> won't
>> be perfect), incorporate comments from other developers, etc.
>> 
>> In other words, i'd be glad to make the translation but i want to be sure 
>> that
>> my work will actually be used, and that someone will shepherd it through our
>> contributing process so that it ends up in the official documentation (i 
>> don't
>> have time to this management myself).
>> Of course if you run into *any* technichal difficulty (like "how do i add a 
>> new
>> section to the documentation?"), i'll try to help.  But i need someone that 
>> will
>> take responsibility for getting it done.
>> 
>> Quite frankly, i think this would be an excellent project to get started in
>> contributing to LilyPond.  It doesn't require programming expertise or any
>> particular knowledge - you just have to put some effort in.
>> 
>> best,
>> Janek
> 
> Janek,
> 
> I think I'm about ready to take a swing at this. Shall I email you about it 
> directly, or keep the discussion here on the list?
> 
> DR
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user