Difference between revisions of "Common Error Messages in Wordfast Pro"

From Wordfast Wiki
Jump to: navigation, search
Line 7: Line 7:
 
Don’t panic! There are a couple of workarounds.
 
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 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:
# Go to Quick Tools and perform a pseudo-translation of the source file (click on the Help icon under the Help tab 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 to '''''Quick Tools''''' and perform a pseudo-translation of the source file (click on the Help icon under the '''''Help''''' tab 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.  
+
# Go back to the TXLF Editor and commit all segments to the TM using the '''''Commit All''''' icon under the '''''Translation''''' tab.  
 
# Add a copy of the source file (with a different name) to the project.
 
# Add a copy of the source file (with a different name) to the project.
# Open the newly added file and use the ''Translate All'' icon on the Translation tab.  
+
# Open the newly added file and use the '''''Translate All''''' icon on the '''''Translation''''' tab.  
# Try to save the translated file by clicking on the ''Save File As Translated'' icon under the File tab.  
+
# Try to save the translated file by clicking on the '''''Save File As Translated''''' icon under the '''''File''''' tab.  
# 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 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.net.
Line 20: Line 20:
 
===“This archive contains unclosed entries”===
 
===“This archive contains unclosed entries”===
  
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 5 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, click on the '''''Wordfast 5''''' 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 could also appear if you are basing a project on a previous project that was created using an earlier version of Wordfast Pro 5 (or 4). If this is the case, attempt to recreate the project from scratch.
 
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 5 (or 4). If this is the case, attempt to recreate the project from scratch.
Line 28: Line 28:
 
===“A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run WF PRO. No Java virtual machine was found after searching the following locations: jre\bin\javaw.exe.”===
 
===“A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run WF PRO. No Java virtual machine was found after searching the following locations: jre\bin\javaw.exe.”===
  
The issue is with your Antivirus Avast (or other antivirus software) moving the file javaw.exe to quarantine.
+
The issue is with your Antivirus Avast (or other antivirus software) moving the file ''javaw.exe'' to quarantine.
  
Open the antivirus software to find the file in Quarantine and restore it. Then add it to the list of exclusions so it will be skipped during the next antivirus check.
+
Open the antivirus software to find the file in '''''Quarantine''''' and restore it. Then add it to the list of exclusions so it will be skipped during the next antivirus check.
  
  
Version: Wordfast Pro 5.7   Operating System: macOS
+
Version: Wordfast Pro 5.7 <br>  Operating System: macOS
  
Updated by [[User:Star|Star]] 15 January 2019
+
Updated by [[User:Star|Star]] 20 January 2019

Revision as of 01:40, 22 January 2019

Error while saving the document

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

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:

  1. Go to Quick Tools and perform a pseudo-translation of the source file (click on the Help icon under the Help tab 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).
  2. Go back to the TXLF Editor and commit all segments to the TM using the Commit All icon under the Translation tab.
  3. Add a copy of the source file (with a different name) to the project.
  4. Open the newly added file and use the Translate All icon on the Translation tab.
  5. Try to save the translated file by clicking on the Save File As Translated icon under the File tab.
  6. 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.

Exporting project problems

“This archive contains unclosed entries”

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 5 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 could also appear if you are basing a project on a previous project that was created using an earlier version of Wordfast Pro 5 (or 4). If this is the case, attempt to recreate the project from scratch.

Error when starting Wordfast

“A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run WF PRO. No Java virtual machine was found after searching the following locations: jre\bin\javaw.exe.”

The issue is with your Antivirus Avast (or other antivirus software) moving the file javaw.exe to quarantine.

Open the antivirus software to find the file in Quarantine and restore it. Then add it to the list of exclusions so it will be skipped during the next antivirus check.


Version: Wordfast Pro 5.7
Operating System: macOS

Updated by Star 20 January 2019