Exporting Texts for Offline Translation 
You can use this function to export short texts and PDF forms for translation outside of the system. This is an alternative to setting up a system for translation, where short texts and PDF forms are translated directly in the system itself.
Prerequisites
You have created at least one object list in the system. Ideally, development of your project is complete and no further changes to the source texts are expected.
Procedure
Call transaction LXE_MASTER and choose
Transport 
Externalization Export 
. The Export Translation Objects screen
is displayed.In the Source Language and Target Languages fields, enter the source and target languages for the objects to be exported.
In the Object List field, select an existing object list for the export using the input help or select the icon
(Create a New Object List) to create an object list.Enter a meaningful description for the export in the Job Description field. This information is then displayed in the Export Header log in the externalization log.
Select the Export to Server option if you want to export the data to the application server of the system, and specify the relevant server directory name.
Select the Export to Frontend option if you want to export the data to the local file system (for example, c:\temp).
NoteYou must select Export to Frontend if you want to export your objects in Microsoft Excel format.
End of the note.In the Export Mode group box, select the format in which you want to export the objects for translation. If you choose XLIFF you must specify if you want to export just short texts, just PDF forms, or both. Excel format is only available for short texts.
In the Options group box you can specify if translated and/or modified objects are excluded from the export.
In the Short Text Specific Options group box, specify if translated and/or modified short text lines are excluded. Select the Export Best Proposal checkbox if the best proposal for each text line is to be determined and exported. In the Lines per File field you can enter an approximate maximum number of translation lines for each file.
Result
The objects are exported in the format that you selected:
XLIFF format: The export files are standard XLIFF 1.2 compliant.
Microsoft Excel format: All fields except the target text field are write-protected by default. If it is absolutely necessary to unprotect the sheet (for example, to adjust the column width of the translation field), then you can use Microsoft Excel's unprotect function with password SAP. We recommend that you protect the sheet again to avoid accidental changes to the static data because this would lead to inconsistencies during import.
The translated text must not exceed the maximum length displayed in the Max Length column. Longer translations are not imported and an error message is written to the log.
To check the status of your export, see the log.
Note
Each translation object belongs to a terminology domain such as BC, PA, MM, and SD. This is an important source of additional information for translators because it helps them to decide whether a source text like application, for example, means an application component, a software application, or a job application.
Your XLIFF or Excel file includes this information. However, it does not include the texts that explain what the domains stand for. To provide your translation agencies with this information:
Call transaction LXE_MASTER.
On the Overviews tab page, choose Domains. A dialog box appears listing all of the domains in the system, together with their abbreviations.
Choose Print and send this information to the translation agencies.