For questions, answers and opinions
https://forum.audacityteam.org/
The .mo files can be read on all platforms but you can't edit the .mo files. The .mo files are produced by editing the .po file then compiling the .mo file. That will usually be done by "saving" the edited .po file in the .po editor (such as Poedit).nilolaus wrote:Can I use the same .mo-file for mac and windows-versions? Means: I edit the mac .mo to get a simplified version of the menus (there will be nothing left than "export" and "quit"). Can I then use the same file for the windows-version or do I have to do everything again on the windows system for the windows version?
but an inverse behavior would be much better.All donations are welcomed, thanks!nilolaus wrote: May be there is a possibility for a little donation as soon as the customer paid.
No. The ability to hide menus if "!" is in the .po file has remained enabled since the time it was implemented, so will work in the current 1.3.13 Beta version too. What we aren't doing is providing any "simplified" .mo files ourselves.nilolaus wrote: I understood that the only versions I can use with simplified language .mo files are the nightly builds - am I right?
The problem with the superfluous window was introduced (on Mac only) on the 17th August and is waiting for more testing to fix it. So any "nightly" build before then or indeed 1.3.13 Beta would not have that problem.nilolaus wrote: A problem I have with the latest build (8.28) is that a project I save does not read the audio-files (saved with the project) when launching again. Instead there is a window coming up, telling the alpha-version of the software.
An older nightly-build on which i worked until today, does not show this window but loads the audio without any problem. I do of course not think that there is a correlation between showing this window and not loading the audio
I copied my Audacity folder (with Audacity 1.3.13) to another computer including the "Portable Settings" folder. But when I ran audacity.exe on the other computer it doesn't recognize the settings.Gale Andrews wrote:On each launch Audacity will look first for audacity.cfg in a "Portable Settings" folder in the Audacity installation directory and use those settings. If it cannot find audacity.cfg there it will look in Audacity's data directory. If audacity.cfg is not there either (as would normally be the case with a fresh installation) then Audacity will launch with default settings. It will be simpler for you to add the "Portable Settings" folder in the installation directory (@ Peter - indeed it does work).nilolaus wrote:As far as I understand... we can include this folder into our download-package and on the computer, where Audacity is downloaded, Audacity will use the .cfg-File insider the "Portable Settings" folder instead of creating a new one. Am I right?