If you use Type3 for your Internet presence, and you require your website to be translated, then you have two options:
1) You give one or more translators access to the back-end, by assigning them an appropriate username and password. In the back-end, the translator then opens the individual blocks of text, and translates them directly.
2) You use the Localization Manager in Typo3 and export the texts which you require into an XML file which can be translated by the language service provider, and then reloaded.
In most cases, I would advise you to take the second option. This has a number of advantages. In processing the XML files, the translator can use a translation memory system, and you thus benefit from increased consistency and efficiency, and the translations can also be used for future localisation projects. In addition, the translator does not have to familiarise himself with the Typo3 back-end; this can be difficult for people who are unused to it. Even if there are some elements which you do not require to be translated, this is easy to manage using the XML option. Thanks to modern CAT tools, skilled translators who know how to use their applications are in the position to exclude specific elements from being translated, by means of parser settings. This can significantly reduce the costs and also the time taken.
Regardless of whether you decide on the first or the second option, you should consider proofreading of the front end. The person who carried out the translation, or even another language service provider, should review the translation in its intended layout. Often the length of the texts must be adapted, or it results from the overall context that a phrase or sentence needs to be expressed differently. In any case, such a proofreading will benefit the quality of your text. Quality is decisive, especially for website texts, as these are generally intended directly for the customer or client. Here too, you should therefore rely on the services of professionals.