Fix syntax errors in all .po translation files for Weblate parsing

[Faisal77666]

This PR fixes syntax errors in all .po translation files in the repository. The errors included:
Missing space after #~ in obsolete entries (#msgid → # msgid, #msgstr → # msgstr)
Unescaped double quotes in msgstr lines.
Incorrectly formatted multi-line msgstr entries.

Benefits / Impact:

Resolves Weblate parsing errors that previously locked the translation component.
Ensures all translation files can now be accessed and translated without issues.
Improves maintainability of the .po files and prevents similar parsing errors in the future.

Example errors fixed:

zh_TW.po: Syntax error due to #~msgid without space.
ayc.po: Unescaped double quotes in msgstr.
es.po: Complex strings with unescaped quotes corrected.
tr.po: Header formatting issue.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[walterbender]

@ac-mmi Can you please look into this?

[ac-mmi]

@walterbender Some components in Weblate were locked because the .po files couldn’t be parsed. I wasn’t able to check the alerts directly since I signed up but never got the confirmation email. That said, the PR description makes it clear what the issue was. Fixing the .po syntax should let Weblate parse everything again, unlock the components, and allow translators to contribute.

[walterbender]

@ac-mmi thx. I guess I am wondering if you need to make changes to your code to ensure that the auto-generated files are compatible. I assume that none of these files were touched by your code. (I'm still waiting on Devin to review JA before merging your changes.)

[ac-mmi]

@walterbender Only the tr.po file was provided by me. The rest of the .po files weren’t touched by me or my code.

[walterbender]

@ac-mmi The TR file also had the issue with the missing spaces for trans notes and deprecated translations. Please double-check that your code will include the proper space when we run it across other languages. Thx.

[Faisal77666]

@walterbender I noticed that the idea “Improve synth and sample features in Music Blocks” is listed in the GitHub GSoC ideas repository, but it does not appear in the official GSoC 2025 project list on the website.
Could you kindly clarify whether this idea was considered but not selected for 2025, or if it might still be available for future consideration (for example, in GSoC 2026)? I am very interested in working on Music Blocks, especially on enhancing the synth and sample functionality, and I want to align my efforts with the current roadmap of the project.
Thank you for your guidance.

[walterbender]

We have a DMP project for this.

[Faisal77666]

@walterbender Thanks for clarifying, Could you please guide me on how contributors can get involved with the DMP project? Should we start by exploring its repository or join a specific discussion channel?

[walterbender]

@Faisal77666 please take the discussion to our Matrix channel.
You are welcome to contribute to any issue through pull request.