Thanks, Yuri.
msgcmp tells me there are a few still not translated, but now uk.po is
above 99% complete, so we can test this too.
PRL
On Sun, Mar 4, 2018 at 7:43 AM, Yuri Chornoivan <[email protected]> wrote:
> неділя, 4 березня 2018 р. 10:11:40 EET Paul Licameli написано:
> > Hello Audacity translators!
> >
> > Audacity is in release 2.3.0 development, which will likely last four
> > months, and the lately updated audacity.pot is not final. But it would
> be
> > helpful to the team's testing to get at least one language up-to-date
> with
> > that soon.
> >
> > Here it is: https://raw.githubusercontent.com/audacity/audacity/master/
> > locale/audacity.pot
> >
> > We have done something new, which we need to test: we are
> > internationalizing the parts of Audacity written in Lisp, not C++. These
> > are the effects, generators, and analyzers that appear below the
> separator
> > lines in the menus. They have long been in Audacity but un-translated.
> > There are many of these and many related strings to translate now.
> >
> > So we would like to test this new Lisp translation system as soon as we
> can
> > with at least one fully updated .po file.
> >
> > You are familiar with strings marked as "c-format", with % slots that you
> > must preserve in the translation. Now we also have "lisp-format" strings
> > with ~ slots.
> >
> > In case you are unfamiliar: ~a can be substituted by anything (string or
> > number -- Lisp can check the run-time value types of format arguments,
> as C
> > cannot).
> >
> > No other ~ directives are substitution slots. ~~ just becomes one ~
> > character. ~% becomes a new-line. ~ followed by end-of-line in the Lisp
> > source code becomes ~\n in the audacity.pot. This tells Lisp to omit the
> > newline and following blank spaces, just to make it possible to break
> long
> > format strings in the program in a readable way.
> >
> > (This is only a subset of the complete format directives of Common Lisp.
> > It is all that our tiny Lisp implements. You don't need to learn all the
> > complications of common Lisp's format function.)
> >
> > So look for ~ directives in lisp-format strings, and make corresponding
> > ones in translation, knowing that only ~a is a blank to be filled in.
> >
> > Finally, I mention that a few strings include some HTML markup like
>
> > and <b> which you should preserve. I tried to avoid markup in
> translatable
> > strings, but sometimes there is the conflicting and more important
> > requirement that you should translate long phrases in context, not
> isolated
> > words. So sometimes you see marked-up words in their larger context.
> >
> > Thanks, and please send me a reply directly when you complete the
> updates.
> > I will watch Transifex, or take a GitHub Pull request, or take a file
> that
> > you attach to email -- whichever method you prefer.
> >
> > Paul Licameli
>
> Hi,
>
> I have tested the new translation system on self-compiled git and so far it
> works smooth, exactly as expected. Many thanks to you and all Audacity
> developers.
>
> Best regards,
> Yuri
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-translation mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/audacity-translation
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation
