Translating SDL Trados packages - Revision history

Cheeseus at 16:08, 22 November 2023

2023-11-22T16:08:53Z

Cheeseus: /* Known issues */

2023-09-22T12:27:33Z

‎Known issues

Cheeseus: /* Known issues */

2023-09-22T12:27:05Z

‎Known issues

Cheeseus: /* Known issues */

2022-03-08T07:14:39Z

‎Known issues

Cheeseus at 06:41, 8 March 2022

2022-03-08T06:41:53Z

Cheeseus: /* What if my client sends me an .sdlxliff file all by itself? */

2022-01-07T07:44:01Z

‎What if my client sends me an .sdlxliff file all by itself?

Cheeseus: /* Known issues */

2021-11-14T18:05:57Z

‎Known issues

Cheeseus: /* Known issues */

2021-11-14T18:03:44Z

‎Known issues

Cheeseus at 17:57, 14 November 2021

2021-11-14T17:57:24Z

Cheeseus: /* How to send files back to my client? */

2021-11-14T17:55:48Z

‎How to send files back to my client?

← Older revision		Revision as of 16:08, 22 November 2023
Line 1:		Line 1:
		+	'''WARNING:''' ''The functionality that creates a return Trados package (.sdlrpx) does not currently work correctly. The return package created will not open in SDL Trados. Until a solution is found, please only work with SDLXLIFF files directly.''
		+
	Language service providers that use SDL Trados usually send their freelance translators a translation package containing the files to be translated, one or more translation memories (TMs), and one or more termbases. This translation package has the extension ''.SDLPPX'' and serves a similar function to [[Wordfast Pro]]'s ''.GLP'' package file.		Language service providers that use SDL Trados usually send their freelance translators a translation package containing the files to be translated, one or more translation memories (TMs), and one or more termbases. This translation package has the extension ''.SDLPPX'' and serves a similar function to [[Wordfast Pro]]'s ''.GLP'' package file.

@@ Line 41: / Line 41: @@
 The above means that the translation progress will show as 100% in SDL Trados even if some segments were left untranslated (because locked or otherwise).
-– If the SDL package that is imported into Wordfast Pro contains folders and subfolders, Wordfast Pro does not maintain the folder structure in the return package generated. This means that the return package will fail to be imported back into SDL Studio. In this case, the only recourse for the time being is to exract the ''.sdlxliff'' files from the package – or ask your client to send you only the ''.sdlxliff'' files – and translate them directly.
+– If the SDL package that is imported into Wordfast Pro contains folders and subfolders, Wordfast Pro does not maintain the folder structure in the return package generated. This means that the return package will fail to be imported back into SDL Studio. In this case, the only recourse for the time being is to extract the ''.sdlxliff'' files from the package – or ask your client to send you only the ''.sdlxliff'' files – and translate them directly.
 == Future developments ==

@@ Line 33: / Line 33: @@
 == Known issues ==
-As of Wordfast Pro 7.0, the following issues exist when working with SDL Trados packages or directly with ''.sdlxliff'' files:
+As of Wordfast Pro 8.6, the following issues exist when working with SDL Trados packages or directly with ''.sdlxliff'' files:
 – Segments that were left untranslated in Wordfast Pro will be shown as translated in SDL Trados (the green-pencil-and-tick icon will be displayed)

@@ Line 33: / Line 33: @@
 == Known issues ==
-As of Wordfast Pro 6.5, the following issues exist when working with SDL Trados packages or directly with ''.sdlxliff'' files:
+As of Wordfast Pro 7.0, the following issues exist when working with SDL Trados packages or directly with ''.sdlxliff'' files:
 – Segments that were left untranslated in Wordfast Pro will be shown as translated in SDL Trados (the green-pencil-and-tick icon will be displayed)
@@ Line 40: / Line 40: @@
 The above means that the translation progress will show as 100% in SDL Trados even if some segments were left untranslated (because locked or otherwise).
 == Future developments ==

← Older revision		Revision as of 06:41, 8 March 2022
Line 26:		Line 26:

	If you want to extract the ''.sdlxliff'' file from an SDL package to translate directly, make sure you are using the ''.sdlxliff'' file that is located in the '''target language folder''' of the SDL project.		If you want to extract the ''.sdlxliff'' file from an SDL package to translate directly, make sure you are using the ''.sdlxliff'' file that is located in the '''target language folder''' of the SDL project.
		+
		+	== Tracking changes in ''.sdlxliff'' files ==
		+
		+	This is not possible at present.

	== Known issues ==		== Known issues ==

← Older revision		Revision as of 07:44, 7 January 2022
Line 24:		Line 24:

	Another important thing to remember if working directly with an ''.sdlxliff'' file is that when you create the target file ('''''File''''' > '''''Save File As Translated'''''), Wordfast will change the file name by adding the target language code to it, e.g. if the source file name was ''text_to_translate.docx.sdlxliff'', the target file name will be ''text_to_translate.docx_en-US.sdlxliff''. Before the recipient of the translated ''.sdlxliff'' file can put it back in the target language folder of their project in SDL Trados, they will have to rename the file by removing the ''_en-US'' bit that was added to it.		Another important thing to remember if working directly with an ''.sdlxliff'' file is that when you create the target file ('''''File''''' > '''''Save File As Translated'''''), Wordfast will change the file name by adding the target language code to it, e.g. if the source file name was ''text_to_translate.docx.sdlxliff'', the target file name will be ''text_to_translate.docx_en-US.sdlxliff''. Before the recipient of the translated ''.sdlxliff'' file can put it back in the target language folder of their project in SDL Trados, they will have to rename the file by removing the ''_en-US'' bit that was added to it.
		+
		+	If you want to extract the ''.sdlxliff'' file from an SDL package to translate directly, make sure you are using the ''.sdlxliff'' file that is located in the '''target language folder''' of the SDL project.

	== Known issues ==		== Known issues ==

← Older revision		Revision as of 18:05, 14 November 2021
Line 32:		Line 32:

	– Locked segments will also be marked as as translated in SDL Trados (the green-pencil-and-tick icon will be displayed).		– Locked segments will also be marked as as translated in SDL Trados (the green-pencil-and-tick icon will be displayed).
		+
		+	The above means that the translation progress will show as 100% in SDL Trados even if some segments were left untranslated (because locked or otherwise).

	== Future developments ==		== Future developments ==

← Older revision		Revision as of 18:03, 14 November 2021
Line 26:		Line 26:

	== Known issues ==		== Known issues ==
		+
		+	As of Wordfast Pro 6.5, the following issues exist when working with SDL Trados packages or directly with ''.sdlxliff'' files:
		+
		+	– Segments that were left untranslated in Wordfast Pro will be shown as translated in SDL Trados (the green-pencil-and-tick icon will be displayed)
		+
		+	– Locked segments will also be marked as as translated in SDL Trados (the green-pencil-and-tick icon will be displayed).

	== Future developments ==		== Future developments ==

← Older revision		Revision as of 17:57, 14 November 2021
Line 24:		Line 24:

	Another important thing to remember if working directly with an ''.sdlxliff'' file is that when you create the target file ('''''File''''' > '''''Save File As Translated'''''), Wordfast will change the file name by adding the target language code to it, e.g. if the source file name was ''text_to_translate.docx.sdlxliff'', the target file name will be ''text_to_translate.docx_en-US.sdlxliff''. Before the recipient of the translated ''.sdlxliff'' file can put it back in the target language folder of their project in SDL Trados, they will have to rename the file by removing the ''_en-US'' bit that was added to it.		Another important thing to remember if working directly with an ''.sdlxliff'' file is that when you create the target file ('''''File''''' > '''''Save File As Translated'''''), Wordfast will change the file name by adding the target language code to it, e.g. if the source file name was ''text_to_translate.docx.sdlxliff'', the target file name will be ''text_to_translate.docx_en-US.sdlxliff''. Before the recipient of the translated ''.sdlxliff'' file can put it back in the target language folder of their project in SDL Trados, they will have to rename the file by removing the ''_en-US'' bit that was added to it.
		+
		+	== Known issues ==

	== Future developments ==		== Future developments ==

@@ Line 17: / Line 17: @@
 == How to send files back to my client? ==
-Once you have completed your translation, you can use the '''''Export SDL Package''''' icon from the '''''Project List''''' or the '''''Current Project''''' views to create an SDL Trados return package (''.SDLRPX'') and send translated files back to your client.
+Once you have completed your translation, you can use the '''''Export SDL Package''''' icon from the '''''Project List''''' view to create an SDL Trados return package (''.SDLRPX'') and send translated files back to your client.
 == What if my client sends me an ''.sdlxliff'' file all by itself? ==