Common Error Messages in Wordfast Pro - Revision history

Cheeseus: /* Error while saving the document */

2022-10-21T19:16:21Z

‎Error while saving the document

Cheeseus: /* Error while saving the document */

2022-08-12T10:17:05Z

‎Error while saving the document

Cheeseus: /* “An error occurred while saving the document” or “There was a problem creating the preview file” */

2021-08-15T07:28:28Z

‎“An error occurred while saving the document” or “There was a problem creating the preview file”

Cheeseus: /* “This archive contains unclosed entries” */

2021-06-02T16:48:08Z

‎“This archive contains unclosed entries”

Cheeseus: /* “Project file is not valid” */

2021-06-01T13:00:41Z

‎“Project file is not valid”

Cheeseus: /* Exporting project problems */

2021-06-01T13:00:22Z

‎Exporting project problems

Cheeseus: /* Exporting project problems */

2021-06-01T12:57:23Z

‎Exporting project problems

Cheeseus: /* Exporting project problems */

2021-06-01T12:55:52Z

‎Exporting project problems

Cheeseus: /* “This archive contains unclosed entries” */

2021-06-01T12:54:38Z

‎“This archive contains unclosed entries”

Cheeseus: /* “This archive contains unclosed entries” */

2021-06-01T12:51:24Z

‎“This archive contains unclosed entries”

@@ Line 42: / Line 42: @@
 # If it works, fix fuzzies or no matches caused by unmerged or unsplit segments in this copy of the source file, using '''''Concordance Search''''' if necessary, then save your file as translated again (overwriting the previous version).
-If all of this fails, please submit a tech support request via your user account at wordfast.net.
+If all of this fails, please submit a tech support request via your user account at wordfast.com.
 == Exporting project problems ==

@@ Line 34: / Line 34: @@
 Don’t panic! There are a couple of workarounds.
-This error is generally caused by not replicating tags from source to target. Run Transcheck on the file ('''''Review''''' tab in TXLF Editor) to check for tag errors first. If this does not fix the problem, the error may have been caused by merging or splitting segments. Perform the following steps:
+This error is generally caused by not replicating tags from source to target. Run Transcheck on the file ('''''Review''''' tab in TXLF Editor) to check for tag errors first. If this does not fix the problem, the error may have been caused by merging or splitting segments or, if translating an Excel file, by translated sheet names that exceed the Excel limit of 31 characters. Perform the following steps:
 # Go to '''''Quick Tools''''' and perform a pseudo-translation of the source file (click on the '''''?''''' icon at the top right and go to the '''''Quick Tools > Pseudo Translate''''' section to see how to do this). This performs a roundtrip to see if the file filter is corrupt (if this fails, you’ll have to contact tech support).
 # Go back to the TXLF Editor and commit all segments to the TM using the '''''Commit All''''' icon under the '''''Translation''''' tab.

@@ Line 34: / Line 34: @@
 Don’t panic! There are a couple of workarounds.
-This error is generally caused by not replicating tags from source to target. Run Transcheck on the file ('''''Review''''' tab in TXLF Editor) to check for tag errors first. If this does not fix the problem, the error may have been caused by merging or splitting segments or by adding underline tags to target that don’t exist in source (known bug, being fixed as of 2017-03-04). Perform the following steps:
+This error is generally caused by not replicating tags from source to target. Run Transcheck on the file ('''''Review''''' tab in TXLF Editor) to check for tag errors first. If this does not fix the problem, the error may have been caused by merging or splitting segments. Perform the following steps:
 # Go to '''''Quick Tools''''' and perform a pseudo-translation of the source file (click on the '''''?''''' icon at the top right and go to the '''''Quick Tools > Pseudo Translate''''' section to see how to do this). This performs a roundtrip to see if the file filter is corrupt (if this fails, you’ll have to contact tech support).
 # Go back to the TXLF Editor and commit all segments to the TM using the '''''Commit All''''' icon under the '''''Translation''''' tab.

@@ Line 50: / Line 50: @@
 [[File:Wfp_export_package_unclosed_entries.png]]
-This error may be caused if either the local TM or glossary editor is open in the project. To find out if you have an open TM or glossary editor, click on the '''''Wordfast Pro''''' tab in the top left corner. If an editor is not greyed out, it means that it is open. Click on it to be brought to the open editor, then click on the lower of two X’s in the top righthand corner to close the editor.
+This error may be caused if either the local TM or glossary editor is open in the project. To find out if you have an open TM or glossary editor, go to the '''Project TM''' or '''Project Terminology''' tab. If the TM or glossary name is shown in '''bold''', this means it is open in the respective editor. Double click the TM or glossary name to be brought to the open editor, then click on the lower of two X’s in the top righthand corner to close the editor.
 This error could also appear if you are basing a project on a previous project that was created using an earlier version of Wordfast Pro. If this is the case, attempt to recreate the project from scratch.

@@ Line 64: / Line 64: @@
 [[File:Wfp_import_package_not_valid.png]]
-This error will occur when you try to import a corrupt GLP package into '''''Wordfast Pro'''''.
+This error will occur when you try to import a corrupt GLP package into Wordfast Pro.
 In order to solve this problem, the package needs to be re-exported. For problems during package export see above.

@@ Line 54: / Line 54: @@
 This error could also appear if you are basing a project on a previous project that was created using an earlier version of Wordfast Pro. If this is the case, attempt to recreate the project from scratch.
-This error also occurs if you have inverted (flipped) or copied (without flipping) the project's TM in the same session. In order to resolve this problem, you will have to shut down '''''Wordfast Pro''''' and then start it again.
+This error also occurs if you have inverted (flipped) or copied (without flipping) the project's TM in the same session. In order to resolve this problem, you will have to shut down Wordfast Pro and then start it again.
 == Importing project package problems ==

← Older revision		Revision as of 12:57, 1 June 2021
Line 59:		Line 59:


−	~~----~~	+
		+	== Importing project package problems ==

	===“Project file is not valid”===		===“Project file is not valid”===

← Older revision		Revision as of 12:55, 1 June 2021
Line 57:		Line 57:

	Please note that a GLP package will be created even if you see this error. ''However, the package is going to be damaged.'' Therefore, it is mandatory to export it again after you have restarted '''''Wordfast Pro'''''. Choose '''Yes''' when asked if you want to overwrite the existing file.		Please note that a GLP package will be created even if you see this error. ''However, the package is going to be damaged.'' Therefore, it is mandatory to export it again after you have restarted '''''Wordfast Pro'''''. Choose '''Yes''' when asked if you want to overwrite the existing file.
		+
		+
		+	----

	===“Project file is not valid”===		===“Project file is not valid”===

← Older revision		Revision as of 12:54, 1 June 2021
Line 57:		Line 57:

	Please note that a GLP package will be created even if you see this error. ''However, the package is going to be damaged.'' Therefore, it is mandatory to export it again after you have restarted '''''Wordfast Pro'''''. Choose '''Yes''' when asked if you want to overwrite the existing file.		Please note that a GLP package will be created even if you see this error. ''However, the package is going to be damaged.'' Therefore, it is mandatory to export it again after you have restarted '''''Wordfast Pro'''''. Choose '''Yes''' when asked if you want to overwrite the existing file.
−
−

	===“Project file is not valid”===		===“Project file is not valid”===

← Older revision		Revision as of 12:51, 1 June 2021
Line 57:		Line 57:

	Please note that a GLP package will be created even if you see this error. ''However, the package is going to be damaged.'' Therefore, it is mandatory to export it again after you have restarted '''''Wordfast Pro'''''. Choose '''Yes''' when asked if you want to overwrite the existing file.		Please note that a GLP package will be created even if you see this error. ''However, the package is going to be damaged.'' Therefore, it is mandatory to export it again after you have restarted '''''Wordfast Pro'''''. Choose '''Yes''' when asked if you want to overwrite the existing file.
		+
		+
		+
		+	===“Project file is not valid”===
		+
		+	[[File:Wfp_import_package_not_valid.png]]
		+
		+	This error will occur when you try to import a corrupt GLP package into '''''Wordfast Pro'''''.
		+
		+	In order to solve this problem, the package needs to be re-exported. For problems during package export see above.

	== Error when starting Wordfast ==		== Error when starting Wordfast ==