I would also like to add (to anyone concerned) that this entire privacy
controversy is entirely down to an awfully written Privacy Policy (a large
revision of which is about to be released - along with an explanation about
why was so vague and alarming). Our team have largely been sitting around,
waiting for Muse PR/legal to clarify this issue and assure users that
Audacity 3.0.3 will have exactly the feature set we said it would back when
we dropped Telemetry in May.

I'm deeply sorry for the repeated fiascos that I'm sure have been getting
you down as much as they have us here on the Audacity team.

Thanks a lot,
Martin


On Thu, Jul 15, 2021 at 6:16 PM Paul Licameli <paul.licam...@gmail.com>
wrote:

> Dear translators,
>
> You may have heard the news about the need for clarification of Audacity's 
> privacy policy before release 3.0.3 is announced.  The updated policy will be 
> available (in English) on the web.
>
> It also required some source code changes giving further explanation to the 
> user in dialogs, and links to that page.  Some of those messages will be made 
> prominent to the user the first time the new version of Audacity runs on 
> their machines, and they should be translated if possible.
>
> So there are a small number of new strings that we would like you to 
> translate if you can, but we don't want to delay the release for long.  So 
> the tentative cutoff date for your additions is Tuesday, 20 July 2021.
>
> Please see updated .po and .pot files:
> https://github.com/audacity/audacity/tree/master/locale
>
> I thank you in advance for helping the Audacity Team on such short notice.
>
> Paul Licameli
>
>
> _______________________________________________
> Audacity-translation mailing list
> Audacity-translation@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/audacity-translation
>
_______________________________________________
Audacity-translation mailing list
Audacity-translation@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/audacity-translation

Reply via email to