I adhere to @13 and @14 considerations.
While I am my self a native Spanish speakers who understands and can write somewhat in English as a second language, I think your proposal is not a good idea; not at least if there are sub-forums for each language such as the Audacity official forums.
Allowing anyone to post in his/her native language would considerably difficult the knowledge, opinion and material travels that this forum, despite its many issues, allows between so many users of different cultures that share the common interests in audio games.
This is not only due to moderation being harder in that case, but especially because automatic translation, despite how much it has evolved in the last years, still has bottlenecks, especially between languages of different families. If you were a native speaker of some language other than English, you would understand in practice the fact that often machine translations are hard to understand because sometimes generate non-grammatical sentences or choose words that are not applicable at all in context.
Unfortunately, Microsoft in recent years is using machine translation to translating user interfaces of star products like Office and Windows, and especially the help/support content. Much more often than it should, I'm in need to switch the help page language back to English to understand a given topic because the automatic translation miss information, mix UI terms or even leaves examples unadapted based on descriptive information that the machine decided to translate.
A good help example of this machine translation tragedy are topics about Excel functions, or the ones that explain how to do certain things with a screen reader, where often hotkeys that are translated in the product leave untranslated in these help topics.
A couple of UI examples will make you an idea of the difficulties automatic translation could present in the forum.
In certain Windows 10 release I don't exactly remember which one, Microsoft added a setting to specify how many open Microsoft Edge tabs to show when using ALT+TAB in addition to traditional windows. In the Spanish version, options said things like "5 pestañas y abrir las ventanas", "Abrir ventanas y 3 pestañas", etc. Although I remembered to read about this new feature when they announced it in a blog post about an Insider Preview build, at first the setting in Spanish is not understandable, because without reading that blog post, for a casual user the translation gives the idea of showing something to open windows as an action. It happened because English, unlike Spanish, sometimes uses the word "open" both as an action ("I want to open the window") and as a participle ("The window is open"), and the machine chose to use for "open" the Spanish word "abrir" which is "open" as an action, rater than "abiertas" that is the plural participle that was correct in this context.
In Office 2007, Microsoft added a context menu to the status bar of programs like Word and Excel, which allows to select which items we want the status bar to have. One of these is "View shortcuts". In Spanish it was translated as "Ver accesos directos", which is "view" as an action ("accesos directos" is the Microsoft translation for "shortcuts"). As a result, I thought this option enabled or disabled the possibility of clicking the items for opening dialogs such as Find and Word Count. But it actually adds and removes the buttons for changing the document view, such as Print Layout or Draft, in which the word "view" is a noun. Therefore, it should have been translated as "Accesos directos a vistas", where "vistas" is "view" as a plural noun.
In my Nokia E5 which had Latin American Spanish, the Maps application had a setting that said "Posición inicial" (literally "Starting position" or "Initial position") and was required to use the feature for quickly traveling to our house. However, this didn't actually asked the starting position, but the position of our house itself. My confusion was because they translated as "Posición inicial" the original "Home position". While "home" is a valid English word to denote a reference or starting point for something, it also refers to a house, like it was in this case, so this should have been translated as "Posición del hogar", "Posición de casa" or in any way in which the equivalent used for the word "home" could be interpreted as a place in which someone lives.
In Nero Wave Editor, which is the program of the Nero suite used for audio editing, there was an item named "Edit History" in the Edit menu. In Spanish it reads "Editar historial", in which "edit" is interpreted as an action. Since I didn't know the English version at the time, at first I think the screen for editing the history was not accessible. Actually, there was no history to edit, because in this case "edit" is a noun and this should have been translated, as the help makes clear, as "Historial de ediciones", in which "ediciones" is a plural for "edit" as a noun referred to the various changes the user made on the opened audio file.
If these things happen for popular products in which it is expected that at least a human to review the automatic translations for post-editing if necessary, you can give yourself an idea of how this might difficult moderation and understanding in case of conflict in this forum, where posts do not follow relatively rigid patterns like technical materials largely do. But think on the following cases of non-IT words, in which you can verify the phenomenon through Word Reference dictionaries, which include use examples:
The English word "cock" as a big variety of meanings, ranging from the male genital organ to various tools for fixing things.[/*
The Spanish verb "coger" means "to take" in Spain with the sense of grabbing things, but in Latin America is instead used only referred to the sexual intercourse act.
As @14 well said, these cultural and context linguistic hints are not available to machines in the current state-of-the-art. Therefore, for solving human conflicts that sometimes take place in this forum, in case we allow everyone to express in whatever language he or she wants, we would still need to have at least basic notions of the source language which we are asking the machine to translate from.
Also, back into a more technical aspect, how stable the Unicode support of this forum is? I think it is probably outdated, since once I wanted to use an emoji character (the ones that are currently in the Unicode standard, not the old emoticons based on combining certain letters) and the forum gave a strange error whose fixing required I to remove the emoji before sending the post. While it is not a problem for languages such as most of Western European ones, Arabic, Chinese, Japanese, Thai, Turkish, Vietnamese, Icelandic, Greek and the ones with Cyrillic script, many languages are only supported in Unicode (these don't have specific extended-ASCII character sets), so if we want to support posting in multiple languages the Unicode compliance should be accurate.
And even with a stable Unicode support, many screen readers can't speak at all in different scripts (for example a Cyrillic-based language with a Latin script TTS).
Sorry for my bad English. I'm from Argentina and my level speaking this language is low.