Re: i18n 2nd time

[Jan Nieuwenhuizen]

Kopecek Tomas <address@hidden> writes:

> I have to ask once more. Should I submit localization based on
> `lilypond.pot' or wait (or do) further localisation steps like updating
> source files?

Sorry to keep you waiting.  I'm sort of the localisation guy around
here, but I've not been around that much, last week.

The usual steps are:

  * update source files, adding _ ( .. ) or  _f ( .. ) whenever
    necessary.  guidelines are: translate whole sentences rather than
    snippets, but try to minimise the number of localisation strings
    (eg, use one error message for 'cant open file', not 10 variations).

    see http://lilypond.org/wiki/?LocalisationGuideLines

  * incorporate new strings into .pot, and update the available .po's
    by running:
    
       make po-update

  * edit your favourite .po, or start a new one by copying
    lilypond.pot to mylang.po
           
> P.S. Is anywhere something like TODO for 1.6.?

There's:

    http://lilypond.org/wiki/?ReleaseIssues

Jan.
    
-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org