Using the example in the "translate" man page: jesse@dell-gx620 ~/source/build $ echo "Le probleme est resolu." | translate -f fr -t en [ ] (translate:17348): libtranslate-WARNING **: unable to translate chunk using Babel Fish: unable to parse server data (translate:17348): libtranslate-WARNING **: unable to translate chunk using SYSTRAN: unable to parse server data Le probleme est resolu. jesse@dell-gx620 ~/source/build $ I noticed that there are some "unofficial" patches on the libtranslate project page, which apparently update the services.xml file. Probably webAPIs have changed in the various providers' services since 2005... If we're scared of "unofficial", can we at least have an "unofficial" USE flag to allow Portage to pull in these "unofficial" patches listed on the "official" upstream project page. ;) Cheers!
I have put an -r1 in the tree that applies two patches (the one from the website and another one from the Ubuntu distribution's bug tracker), but it still fails some services. As services.xml(5) suggests, you could simply use your own file defining your own translation services.
