Hello everyone, Thank you for your emails, and apologies for not communicating clearly enough on our side this time. Below is the full context: how we normally prepare releases, what was different with 4.0, and how much time you still have to submit translations.
How our release process normally works - We prepare a release candidate (RC) build containing all the features and bug fixes planned for the release. - The RC is treated as final for localization purposes: once regression testing begins, strings are frozen. - We email you the planned release date, which is your signal that we are ready to accept translations. - If we find critical bugs, we fix them and prepare a new RC for continued testing. These fixes do not normally add new strings. What was different with 4.0 Two things caused new strings to appear after the freeze: 1. We discovered that a number of strings in Audacity 4 were not translatable at all. We only noticed once several languages had reached 100% in Transifex while parts of the interface still displayed in English. Making those strings translatable is why new entries appeared after the freeze. 2. Late in the cycle we implemented a few remaining features that needed interface text. We only took them on at that stage because their text could be reused from Audacity 3, so the existing translations carry over and nothing new is required from you. The entries still show up in Transifex, which is why the total string count can increase even though no translation work should be required. We should have told you when this happened. If we ever need to add strings after a freeze again, we will send a separate email to let you know. Current status and deadlines - Regression testing is still ongoing and the release target has moved to next week, September 3. We are continuing to accept translations. - As with every major version, 4.0 will be followed by patch releases. Translations submitted after the 4.0 cutoff will be included in those. - We expect the first patch release to follow within a few weeks of 4.0 and will confirm the date once it is set. You can keep translating in the meantime, and we will make sure your work is included. Why this happened, and what we expect going forward Audacity 4.0 is not only a new major version, it is a new application that uses a different localization system from Audacity 3. The untranslatable strings were a side effect of that transition. Over the past month we identified and fixed the cases we found, and today, we've added translator comments where context was missing. Because this class of issue comes from the initial move to the new system rather than from our regular workflow, we expect it to be specific to 4.0. >From 4.1 onwards the localization process should return to the normal cycle described above. Thank you for your patience and for the work you have put into this release. If you see any issues specific to your native language, don't hesitate to raise them on our GitHub. Best regards, Yana On Thu, Aug 27, 2026 at 8:44 AM Tadahisa Sugisaki < [email protected]> wrote: > Hello dear Dmitry and all, > > Since Transifix has translation assistance features, using them is one > option. > > Please note that Transifix strings have been added twice since August 11. > > The menu command in Audacity 4 has changed from “Title Case” to > “Sentence Case.” This is an inconvenient change for localizers working > with languages like Japanese. I’ve submitted a suggestion for > improvement regarding this on the Audacity GitHub issue, though I > don’t expect it to be adopted. > https://github.com/audacity/audacity/issues/11627 > > 2026年8月11日(火) 0:15 Dmitry <[email protected]>: > > > > Hello dear translators, > > > > We are getting closer to Audacity 4 release date and the string freeze > date is set to August 24. > > > > For Audacity 4 we will be accepting translations only via Transifex. All > existing matching strings > > from Audacity 3 were reused in Audacity 4, as well as translators' > attributions, but if anything is missing, please let us know. > > > > Transifex could be used in two ways: > > - You can translate strings directly from the web ui. It is convenient > for small fixes or if you don't want to use any external software > > - You can download and upload translation files locally and use your > software of choice. > > > > With Audacity 4, we moved to the Qt translation system, it uses .ts > files instead of .po files of Audacity 3. This means that some applications > used for translating Audacity 3 will not be compatible. In such a case, you > can use Poedit, QtTranslator, or Transifex Web UI. > > > > To register a transifex account with your personal email and join the > project, please use this link: > https://explore.transifex.com/audacity/audacity/ > > > > Thank you very much! > > _______________________________________________ > > Audacity-translation mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/audacity-translation > > > > -- > 杉崎 忠久 > Tadahisa Sugisaki > <[email protected]> > > > _______________________________________________ > Audacity-translation mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/audacity-translation >
_______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
