Re: Doorst: Issue 1503 in lilypond: Feature request: simplify jazz chord display

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

Re: Doorst: Issue 1503 in lilypond: Feature request: simplify jazz chord display

Jan Nieuwenhuizen-2
Hi Francisco,

Referring to bug

    http://code.google.com/p/lilypond/issues/detail?id=1503

posted by Maestraccio which was prompted after we met at
T-DOSE last year, there is now a translation request.

Maestraccio is willing to do the translation bit, how do
we get him going?

Greetings,
Jan

Maestraccio writes:

> Hallo Jan,
>
> Vorig jaar op T-Dose spraken we elkaar over de akkoordenweergave in Lilypond, en nu ligt er vertaalwerk klaar.
> Ik voel me geroepen om dit op me te nemen maar heb nooit eerder zoiets gedaan.
> Kun jij me de weg wijzen hoe ik (tabula rasa) hieraan begin?

[English]
Hi Jan,

Last year at T-Dose we talked about chord representation in LilyPond and
now there's translation work.  I would like to do this but never did
something like this before.  Can you show me how I (tabula rasa) get
started?

>
> Met vriendelijke groet,
>
> M+º B. Thomasse,  PCA
> +31 (0) 621 216 621
>
> Deze email is verzonden van een mobiele telefoon, waardoor deze beknopter kan zijn dan u van mij verwacht of gewend bent.
> Mijn excuses hiervoor.
>
> ----- Forwarded message -----
> Van: [hidden email]
> Datum: wo, nov. 2, 2011 18:55
> Onderwerp: Issue 1503 in lilypond: Feature request: simplify jazz chord display
> Aan: <[hidden email]>
>
> Comment #15 on issue 1503 by [hidden email]: Feature request:  
> simplify jazz chord display
> http://code.google.com/p/lilypond/issues/detail?id=1503
>
> I think I am now finished.  The new patch series is available at
>
>     https://github.com/aspiers/lilypond/commits/jazz
>
> You can fetch it via:
>
>     git remote add aspiers git://github.com/aspiers/lilypond.git
>     git fetch aspiers jazz
>
> The patches also adjust the regression tests and English documentation to  
> be consistent with changes to the code.  Translation work is required for  
> other languages.
>
> --
> You received this message because you starred the issue.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>
> Reply to this email to add a comment.
>

--
Jan Nieuwenhuizen <[hidden email]> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl 


Reply | Threaded
Open this post in threaded view
|

Re: Doorst: Issue 1503 in lilypond: Feature request: simplify jazz chord display

Francisco Vila
2011/11/9 Jan Nieuwenhuizen <[hidden email]>:

> Hi Francisco,
>
> Referring to bug
>
>    http://code.google.com/p/lilypond/issues/detail?id=1503
>
> posted by Maestraccio which was prompted after we met at
> T-DOSE last year, there is now a translation request.
>
> Maestraccio is willing to do the translation bit, how do
> we get him going?
>
> Greetings,
> Jan
>
> Maestraccio writes:
>
>> Hallo Jan,
>>
>> Vorig jaar op T-Dose spraken we elkaar over de akkoordenweergave in Lilypond, en nu ligt er vertaalwerk klaar.
>> Ik voel me geroepen om dit op me te nemen maar heb nooit eerder zoiets gedaan.
>> Kun jij me de weg wijzen hoe ik (tabula rasa) hieraan begin?
>
> [English]
> Hi Jan,
>
> Last year at T-Dose we talked about chord representation in LilyPond and
> now there's translation work.  I would like to do this but never did
> something like this before.  Can you show me how I (tabula rasa) get
> started?

Right. I should understand this contributor wants to translate
documentation parts into Dutch? We have a contributor guide,

  lilypond.org/doc/v2.15/Documentation/contributor.pdf (interesting
pages are #60 on)

and it basically says that you should download our source code, edit
texinfo files and submit them to the team.

Translations should be maintained, that means in a second stage it
would be fine if you learned git, our version control system, to be
able to grab latest sources easily and format patches that are easy to
apply for us.  If this is too much work, it is fine that you just send
us translated files and I will apply them.

The ultimate goal for an active translator is to be able to check for
himself whether his files make translated documentation compile well,
for example that every cross reference is not a dead link, and that is
only possible in a Linux environment with _lots_ of software
dependencies.

For now, I think the fastest path is to learn as soon as possible
which @-commands of texinfo you have to translate, and which you have
not to.


Thanks for your offer,
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: Doorst: Issue 1503 in lilypond: Feature request: simplify jazz chord display

Francisco Vila
2011/11/9 Maestraccio BContra <[hidden email]>:

> Hello Francisco, Jan,
>
> I read the recommended part of
> the lilypond.org/doc/v2.15/Documentation/contributor.pdf , but for me there
> is still a dazzling amout of compiling, making, building and other
> programming stuff involved that I am absolutely completely new at.
> Before, I found myself quite a guy to be able to get lilypond to output a
> beautiful pdf file from my own hand-typed-text music score code, and I never
> expected the translation job to differ much from that. I may have been a
> little ignorant to expect there to be a terminology list that could be
> translated into Dutch; I simply imagined a "term-snippet".

We usually don't translate snippets because they usually don't contain
any text.  Are you proposing to create new documentation content?

> Since I was the one to report the bug, I felt obliged to contribute in any
> way possible (which I thought was the translation part). But as this, from
> reading the documentation, requires the skills, soft- and hardware that I
> don't possess, I feel I have to reluctantly withdraw from this chore.

If you locate in the source code the texinfo files you want to
translate, it is really easy to do. Just translate everything outside
@{} commands. Then send me a copy of these files.  You don't need to
install anything and compiling is not necessary. I said this for
active translators who maintain whole localized versions of the
complete manuals.

> Please do not misunderstand. It is not about unwillingness or lack of time.
> I just don't see myself, a musician/sales manager, programming and compiling
> any source stuff shortly.
> If I am mistaken and there is in fact a "term-snippet" as described (or one
> made available) please let me be the first to know and I will be very happy
> to contribute.

I have not searched the docs but please do it and show me what do you
want to adapt.  Texinfo is a very simple markup language for
documents. I will help you on anything you need.

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com