@MsZ
I don't think he was inferring that it was a good idea to release *one single version IN FRENCH*, but rather that it would be a good idea to start releasing packages as translations are coming in. No one's debating whether or not it's a valid idea to translate aMule in users' native languages. But the fact that most major languages are finished should be incentive to release what's already working and understandable for most people, and release more localized versions later, or through a language pack. Maybe it's not feasible with the current way the software is built, but I don't really mind that OpenOffice is up to 2.2.0 in English and the French version is stuck at 2.1.3 cause the translation is lagging... I would find it much more frustrating if it was the other way around; I.e., if I have to choose between my native language and an updated English version, it's nice to be able to compromise and use something that works. In an ideal world everyone would get the latest version the day it comes out in their native language, but it's unrealistic. If I base myself on the fact that most translators are currently communicating in English, I think it's a pretty good hint that *most* should understand it well enough that they are able to run the English version, and wait a while longer, or work harder at translations so that they can begin using a localized version ASAP.
Addendum: Now, if the software itself *isn't* ready and the translations aren't what's holding it back, that's another matter entirely. But if in fact the only thing left is waiting for localization, then it shouldn't be an issue at this point, and I don't feel (as most programmers do), that a fully working stable code release isn't a "complete, fine" version if it hasn't been translated in every variant of every language imaginable.
