Re: [Audacity-translation] New to the list

[Richard A. <ri...@au...>]

On Sat, 2009-01-31 at 12:34 +0100, Susanna Björverud wrote:
> Furthermore, I am a bit curious about the smartmsgmerge.py-script in
> cvs, is this intended as a replacement for msgmerge for translators as
> well? Or are translators perhaps never expected to run either msgmerge
> nor the python script?
It was created by one of the Audacity developers because they didn't
like the way standard msgmerge handled fuzzy translations, in particular
ones that had numbers in them (it quite liked making the translation of
"Audacity 1.3.1 released" a fuzzy of "Audacity 1.3.0 released" which was
less than helpful). It's supposed to be more linguistic about the way it
decides on fuzzy matches, and so produce better results when the
translations are lagging behind the changes to the strings.

> Browsing the archives for this mailing list, I stumbled across the
> http://audacityteam.org/wiki/index.php?title=Translating_Audacity-page, I was a bit surprised on not finding a link to that page on the translation page I first found by browsing (http://audacity.sourceforge.net/community/translation)

Good point, although that page was written almost entirely for the
benefit of developers it probably should be made available to a wider
audience by linking to it. 

> but at least the statements about context prefixes and translations of
> short cuts imo needs to be made available to the average translator as
> well,
Agreed - possibly we need a separate page which keeps track of
translation notes and guidelines like these which are fairly
project-specific.

>  I would much appreciate pointers to what is the proper procedure to
> update the contents on the website (rather than just translating it).
http://audacityteam.org/wiki/index.php?title=Editing_audacity.sourceforge.net

is the nearest currently available. It requires audacity developer CVS
access.

Richard