I'm the Backblaze employee that advocated for this system we have, which is: 1) Developers must add all features fully internationalized, meaning if the locale specific file is present it will display that translation, then 2) The developer must ship a locale specific file which was machine translated, then 3) We have native speakers fix any problems. Usually the first person who complains finds out there is a static text file they can edit to fix the product. I can email you the straightforward installer French locale file if you want to help us fix it!! (Or on Windows run "install_backblaze.exe -unpackonly" and go to the folder it tells you and edit the file called InstallerConfig.xml with Notepad on Windows (
NOT Wordpad) or TextEdit on the Macintosh.
This system allowed us to do a large deal in Japan, where the Japanese company helped us improve the Japanese with very very little additional Backblaze developer time involved because everything was "ready to go". We also did a pretty good German version. The Russian is Ok because several employees at Backblaze are native Russian speakers, but the Brazilian Portuguese is probably a train wreck.
I am curious, why does the presence of the badly translated French hurt you? You can always display it in English (one menu click away), or you can help us translate it better. If it is not there, there is nowhere to "start with", why does that make you happier?
I'm USA born, so it might be a cultural thing. It might be it doesn't offend and bother Japanese people to have a bad Japanese translation available (as long as they can fall back to English), but it REALLY bothers the French that bad French is ever seen in any form, or something like that?