Re: translation of the doc into italian

[Carl D. Sorensen]

On 6/13/09 11:25 AM, "Federico Bruni" <address@hidden> wrote:

> Carl D. Sorensen wrote:
>> 
>> 
>> On 6/9/09 10:39 AM, "Federico Bruni" <address@hidden> wrote:
>> 
 
>> Great!
>> 
>> John Mandereau is the translation meister.  I've copied him on this reply.
>> 
>> The first step toward developing a translation is to read the Translation
>> section of the Contributors' Guide.  You'll find that here:
>> 
>> <http://lilypond.org/doc/v2.13/Documentation/devel/contrib-guide/Translating
>> -the-documentation>
>> 
>> It gives you the instructions necessary to start translating.  If the
>> instructions aren't clear, ask questions on the lilypond-devel list; this
>> will help us update our Contributors' Guide.
>> 
> 
> Hi Carl and all,
> 
> 
> I've read that page and started the first steps. A couple of questions:
> 
> 1) GIT
> I did the following changes: run "make ISOLANG=it new-lang" in
> Documentation and added a line in Python/langdefs.py
> 
> Is this commands sufficient to commit the changes?
> git commit -a
> git format-patch origin

In order to commit the changes when *new* files are created, you need to
first add the new files to the tracking set for the git repository

git add Documentation/it/*

Then git commit -a will update the repository with the new files.
> 
> Or maybe I've committed only the file modified (langdefs.py) and not
> the new files also (Documentation/it/)?
> 
> 2) langdefs.py
> I've just added this line below the other languages:
> 
> it = LanguageDef ('it', 'italiano')
> 
> Is it sufficient?

I think you should also modify the line

LANGUAGES = (site,....)

to add an entry for 'it'.

HTH,

Carl