Difference between revisions of "Common problems with Wordfast Pro 5"

From Wordfast Wiki
Jump to: navigation, search
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
== License fails to activate, stuck in demo mode ==
 +
 +
Q. I can’t activate my license on a PC! I’ve tried both online and manual activation and WFP remains in demo mode. What can I do?
 +
 +
A. This might be caused by changing your system clock settings. First, you should set your system clock to the right time. To do this, please see the following article: [[How to correct your Windows system clock]]. Once you have done that, you will need to search your computer for any future dated files and folders. Please see the following article on how to do that: [[To perform a search operation]].
 +
 +
 
== Wordfast Pro 5 is slow, especially with big files ==
 
== Wordfast Pro 5 is slow, especially with big files ==
  
  Q. I've started running into a slowdown problem… even copying the source takes a few seconds. It's almost as if the program is running short of memory. How can I speed things up?
+
  Q. I’ve started running into a slowdown problem… even copying the source takes a few seconds. It’s almost as if the program is running short of memory. How can I speed things up?
  
 
A. There are several quick fixes to resolve this problem:
 
A. There are several quick fixes to resolve this problem:
  
# Make sure you are using the Hunspell spell checker and not Microsoft Word (PC-only). The use of the Microsoft Word spell checker can slow down WFP5 to the point of frequent freezing. Modify this setting by going to Wordfast Pro > Preferences > Spellchecker.  
+
# Make sure you are using the Hunspell spell checker and not Microsoft Word (PC-only). The use of the Microsoft Word spell checker can slow down WFP5 to the point of frequent freezing. Modify this setting by going to '''''Wordfast Pro > Preferences > Spellchecker'''''.  
# If you have the "spell check as you type" option active, disable it. This could cause slowdown issues, especially with large files. Furthermore, best practices dictate that spell checking should be done during the revision phase and not the translation phase. You save time by using "change all" for frequently misspelled words and don't break your translation flow by constant spelling error interruptions. You can disable it by going to Wordfast Pro > Preferences > Spellchecker.  
+
# If you have the "spell check as you type" option active, disable it. This could cause slowdown issues, especially with large files. Furthermore, best practices dictate that spell checking should be done during the revision phase and not the translation phase. You save time by using "change all" for frequently misspelled words and don't break your translation flow by constant spelling error interruptions. You can disable it by going to '''''Wordfast Pro > Preferences > Spellchecker'''''.  
# Try disabling term highlighting. Go to Wordfast Pro > Preferences > Terminology and uncheck the option that says "Enable term highlighting as you type", as in this screenshot http://prntscr.com/b9qid1
+
# Try disabling term highlighting. Go to '''''Wordfast Pro > Preferences > Terminology''''' and uncheck the option that says "Enable term highlighting as you type", as in this screenshot http://prntscr.com/b9qid1
 
# If you are saving TMs, glossaries, or projects to a back-up or synchronisation folder such as Dropbox or Google Drive, this can take up a lot of computer memory because it is constantly re-syncing the files. Put the service on pause while working on your translation.
 
# If you are saving TMs, glossaries, or projects to a back-up or synchronisation folder such as Dropbox or Google Drive, this can take up a lot of computer memory because it is constantly re-syncing the files. Put the service on pause while working on your translation.
# Try disabling Show Whitespace Characters by clicking on the icon under the Edit Tab in the TXLF Editor. This improves the speed of the TXLF Editor.
+
# Try disabling '''Show Whitespace Characters''' by clicking on the icon under the '''''Edit''''' Tab in the TXLF Editor. This improves the speed of the TXLF Editor.
# On a very large Word file with images, [https://support.office.com/en-us/article/Reduce-the-file-size-of-a-picture-8db7211c-d958-457c-babd-194109eb9535 compress all images] in the source document, save it as a copy, translate the copy, then use Analyze in Quicktools or from the Current Project view to pre-translate the original source file.
+
# On a very large Word file with images, [https://support.office.com/en-us/article/Reduce-the-file-size-of-a-picture-8db7211c-d958-457c-babd-194109eb9535 compress all images] in the source document, save it as a copy, translate the copy, then use '''Analyze in Quicktools''' or from the '''Current Project''' view to pre-translate the original source file.
  
 
Thanks to [http://www.proz.com/profile/877433 Danielle Deremo Cosimo] for compiling a few of these issues.  
 
Thanks to [http://www.proz.com/profile/877433 Danielle Deremo Cosimo] for compiling a few of these issues.  
Line 21: Line 28:
 
A. There a few workarounds to resolve this problem:
 
A. There a few workarounds to resolve this problem:
  
# Submit a feedback ticket via the Help icon as soon as possible.
+
# Submit a feedback ticket via the '''''Help''''' icon as soon as possible.
# If you use 7-zip (PC) or the Unarchiver (Mac), you can unzip<ref>Thanks to Samuel for the tip!</ref> the PowerPoint file (if it is a PPTX file), and then you can look in the "media" subfolder to see if there are any large files (e.g. images or videos). Once you have identified them, open the source file, select the images that are over 1 MB and under '''File''', use the '''Compress Pictures…''' option to make them smaller (choose the smallest value, e.g. ''Email 96 ppi''). Remove any videos. Translate in Wordfast. Once you have your target file Powerpoint file, open it and replace compressed images with original images (from the unzipped folder) and re-add embedded video.
+
# If you use 7-zip (PC) or the Unarchiver (Mac), you can unzip<ref>Thanks to Samuel for the tip!</ref> the PowerPoint file (if it is a PPTX file), and then you can look in the “media” subfolder to see if there are any large files (e.g. images or videos). Once you have identified them, open the source file, select the images that are over 1 MB and under '''''File''''', use the '''''Compress Pictures…''''' option to make them smaller (choose the smallest value, e.g. ''Email 96 ppi''). Remove any videos. Translate in Wordfast. Once you have your target file Powerpoint file, open it and replace compressed images with original images (from the unzipped folder) and re-add embedded video.
# Hack the .INI file on PC (instructions coming soon). This file allocates memory to Wordfast and you can increase it manually.
+
# Hack the ''.INI'' file on PC (instructions coming soon). This file allocates memory to Wordfast and you can increase it manually.
 
 
Notes
 
 
 
<!--
 
== Get matches from the TM==
 
  
Q. In [[Wordfast Pro]], I cannot either get matches or TM Lookup results. I can see the segment stored when I open the TM file in NotePad.
+
== Importing a TMX translation memory (TM) ==
  
A. Go to {{menu|Translation Memory}} menu > {{menu|New/Select TM}}, and make sure it is marked as "Selected". Note: Even if you need it to be "Read Only", you must check "Selected" as well.
+
Q. My  client sent me a TMX translation memory and when I try to import it into [[Wordfast Pro 5]], it either fails or 0 TUs are imported. What is wrong?
  
Open the TXT file of the TM itself; does it include the segments? If not, this might mean that you have cliched the wrong button when you tried to open the TM; for opening an existing TMs, "Add TM" is the correct button while "Create TM" would overwrite its file if the TM already exists. This [http://youtu.be/RQ-PDYwE0ZE video] should give you some tips.  
+
A. Make sure the language pairs of your project exactly match those of the TMX TM. For example, if you have a TM whose source is “fr-FR” and target is “en-US”, you cannot use a project whose source language is “fr” only and whose target language is “en” only. You should create/open a project with “French (France)” (fr-FR) as your source language and “English (United States)” (en-US) as your target language. You will then be able to import the TMX TM into an existing TM or a new TM.
  
 +
== Opening a TXFL file sent via email ==
  
  Q. In [[Wordfast Pro]], I cannot get a match although I can find it using TM Lookup. Moreover, I can see the segment stored when I open
+
  Q. I tried opening a TXLF file my client sent me and I get a message saying “Invalid document format detected”. What gives?
the TM file in NotePad.
 
 
 
A. Is this segment already translated on the TXML file? If so, you should use Alt+Space to get the match, or you can use Ctrl+Alt+M to insert the TM Lookup match.
 
 
 
If it is rather a new segment that is not translated (you see "N/A" in the "Score" column), close Wordfast Pro and delete the two files *.jtx and *.lock found in the same folder as the TM *.txt file. Open Wordfast Pro again, go to the mentioned segment and press Alt+Space.
 
 
 
 
 
Q. In [[Wordfast Pro]], I cannot get a match from a TM that was used in Wordfast Classic or aligned with PlusTools.
 
 
 
A. Click the "Reorganize" button (of Wordfast Classic) whenever you exchange a TM between Wordfast Classic and Wordfast Pro.
 
 
 
 
 
Q. In [[Wordfast Pro]], I cannot get a match from a TM; the colour of segments of the segments are pink.
 
 
 
A. Try to use Alt+Space. If those pink segments are empty, this could be due to the fact that you use an old version of WF Pro. Please download and install the latest version of [[Wordfast Pro]] (this free for current users).
 
 
 
 
 
== Open TMX Translation Memory ==
 
 
 
In [[Wordfast Pro]], please make sure you open a project with the exact language pair as those of the TMX TM. For example, if you have a translation memory whose source is "FR-FR", you cannot use a project whose source language is "FR" only; you should rather create/open a project with "French (France)" source language. Then, go to Translation Memory menu > New/Select TM and click "Open". From the drop-down menu, select Translation Memory eXchange so that you can see the TMX TM and open it.
 
 
 
Otherwise, you can use Okapi Olifant to convert the TMX into a Wordfast TM. This [http://youtu.be/J8A45N40a0k video] illustrates the steps.
 
 
 
 
 
== Open TXML Sent via Email ==
 
 
 
In [[Wordfast Pro]], if you have problems opening TXML files that were sent to you by a client, and get the message "Invalid document format detected", ask your client to resend the files after compressing them in the ZIP or RAR format. This should help you avoid spoiling TXML files through emailing them.
 
  
 +
A. Ask your client to either send the TXLF file in a GLP package or to compress it in a ZIP or RAR format, then send it to you. This will prevent the TXLF file from being corrupted by email providers.
  
 +
<!--
 
== Change Memory Preferences ==
 
== Change Memory Preferences ==
  
Line 84: Line 62:
 
  * Click "OK" > "OK".
 
  * Click "OK" > "OK".
 
  * Now, you should be able to change it in the normal way at [[Wordfast Pro]] > Edit > Preferences > Memory Preferences.
 
  * Now, you should be able to change it in the normal way at [[Wordfast Pro]] > Edit > Preferences > Memory Preferences.
 +
-->
  
 +
== Import terminology with proper encoding ==
  
== Import Terminology with Proper Encoding ==
+
Q. I just imported a glossary from a tab-delimited text file and all the accented characters, special characters, or non-Latin language characters are not displaying properly. What do I do?
 
 
In [[Wordfast Pro]], importing a tab-delimited glossary, special characters or non-Latin language characters are not displayed properly.
 
 
 
'''Solution:''' Convert the txt file of the tab-delimited glossary to Unicode before importing it into Wordfast Pro. To do so, open it in NotePad (Windows) or TextEdit (Mac) and select "Save as"; under "Encoding", select Unicode (UTF-16) or UTF-8.
 
 
 
 
 
== Save Translated INX File ==
 
 
 
In [[Wordfast Pro]], "Save Translated File" generates a 0KB INX file.
 
 
 
'''Possible reasons:'''
 
 
 
* When you create a .txml file from an .inx file, you should also have a generated .skl file. This is needed and should be in the same folder to be able to save the translated .inx file.
 
  
* Missing [[placeables]] in target cells.
+
A. You need to convert the .''txt'' file of the tab-delimited glossary to Unicode '''before''' importing it into Wordfast Pro. To do so, open it in NotePad (Windows) or TextEdit (Mac) and select "Save as"; under "Encoding", select Unicode (UTF-16) or UTF-8.
  
* Shrinking segments including [[placeables]].
 
 
'''Solution:'''
 
 
Please check the TXML file and see if there are any missing or mismatched [[placeables]]. You can run TransCheck on Placeables (Edit > Preferences > TransCheck > select Placeables (Apply)) and then use the toolbar button TransCheck; insert and correct the missing or the mismatched placeables. (This requires the latest version of [[Wordfast Pro]].)
 
 
If there is a misplaced placeable that you need to remove first, place the cursor on it and press Ctrl+Alt+Up to remove it; then insert the correct one. After that, review it using your eyes to double-check especially of ones not missing but mismatched or inserted in incorrect places.
 
 
If the problem persists, please open a fresh copy of the source file in Wordfast Pro latest version and pre-translate using the toolbar button "Translate All". Please NEVER use Expand/Shrink Segment after pre-translating.
 
  
  
Line 118: Line 76:
 
  Q. Is there a way to make [[Wordfast Pro]] assign the target language to the translated PPT?
 
  Q. Is there a way to make [[Wordfast Pro]] assign the target language to the translated PPT?
  
A. Apparently the PPT filter does not have this improvement. To work around that, save the SOURCE document as PPTX; when you "Save Translated File", you will get the target PPTX file with the correct target language.
+
A. Apparently, the PPT filter does not have this improvement. To work around that, save the SOURCE document as PPTX; when you "Save Translated File", you will get the target PPTX file with the correct target language.
  
 
In fact, using PPTX (instead of PPT) seems to be the quick fix for several issues in both WF Pro and WF Anywhere.
 
In fact, using PPTX (instead of PPT) seems to be the quick fix for several issues in both WF Pro and WF Anywhere.
Line 126: Line 84:
 
== Remove PDF source from the target file ==
 
== Remove PDF source from the target file ==
  
  Q. I have translated a PDF using [[Wordfast Pro]] and used {{menu|File}} > {{menu|Save Translated File}} to get the target file.
+
  Q. I have translated a PDF using [[Wordfast Pro 5]]. However, in the target document, the text is garbled and consists of both the source and the translation. I would like to get rid of the source text.
However, in the target document, the text is garbled and consists of both the source and the translation.
 
I would like to get rid of the source text.
 
  
 
A. Actually, the source appears on a background image. Open the target document in Word, click on a blank part of the page, and then press the 'Delete' button on your keyboard, and it gets rid of the background. Do the same for each page of the document, and "Save" it.
 
A. Actually, the source appears on a background image. Open the target document in Word, click on a blank part of the page, and then press the 'Delete' button on your keyboard, and it gets rid of the background. Do the same for each page of the document, and "Save" it.
-->
+
 
 +
 
 +
----
 +
Version: Wordfast Pro 5.7  <br> Operating System: macOS
 +
 
 +
Updated by [[User:Star|Star]] 15 January 2019

Latest revision as of 15:06, 8 April 2019

License fails to activate, stuck in demo mode

Q. I can’t activate my license on a PC! I’ve tried both online and manual activation and WFP remains in demo mode. What can I do?

A. This might be caused by changing your system clock settings. First, you should set your system clock to the right time. To do this, please see the following article: How to correct your Windows system clock. Once you have done that, you will need to search your computer for any future dated files and folders. Please see the following article on how to do that: To perform a search operation.


Wordfast Pro 5 is slow, especially with big files

Q. I’ve started running into a slowdown problem… even copying the source takes a few seconds. It’s almost as if the program is running short of memory. How can I speed things up?

A. There are several quick fixes to resolve this problem:

  1. Make sure you are using the Hunspell spell checker and not Microsoft Word (PC-only). The use of the Microsoft Word spell checker can slow down WFP5 to the point of frequent freezing. Modify this setting by going to Wordfast Pro > Preferences > Spellchecker.
  2. If you have the "spell check as you type" option active, disable it. This could cause slowdown issues, especially with large files. Furthermore, best practices dictate that spell checking should be done during the revision phase and not the translation phase. You save time by using "change all" for frequently misspelled words and don't break your translation flow by constant spelling error interruptions. You can disable it by going to Wordfast Pro > Preferences > Spellchecker.
  3. Try disabling term highlighting. Go to Wordfast Pro > Preferences > Terminology and uncheck the option that says "Enable term highlighting as you type", as in this screenshot http://prntscr.com/b9qid1
  4. If you are saving TMs, glossaries, or projects to a back-up or synchronisation folder such as Dropbox or Google Drive, this can take up a lot of computer memory because it is constantly re-syncing the files. Put the service on pause while working on your translation.
  5. Try disabling Show Whitespace Characters by clicking on the icon under the Edit Tab in the TXLF Editor. This improves the speed of the TXLF Editor.
  6. On a very large Word file with images, compress all images in the source document, save it as a copy, translate the copy, then use Analyze in Quicktools or from the Current Project view to pre-translate the original source file.

Thanks to Danielle Deremo Cosimo for compiling a few of these issues.


Wordfast Pro 5 won’t open large Powerpoint files

Q. I have a very large Powerpoint file and it is crashing Wordfast when I try to import it. What can I do?

A. There a few workarounds to resolve this problem:

  1. Submit a feedback ticket via the Help icon as soon as possible.
  2. If you use 7-zip (PC) or the Unarchiver (Mac), you can unzip[1] the PowerPoint file (if it is a PPTX file), and then you can look in the “media” subfolder to see if there are any large files (e.g. images or videos). Once you have identified them, open the source file, select the images that are over 1 MB and under File, use the Compress Pictures… option to make them smaller (choose the smallest value, e.g. Email 96 ppi). Remove any videos. Translate in Wordfast. Once you have your target file Powerpoint file, open it and replace compressed images with original images (from the unzipped folder) and re-add embedded video.
  3. Hack the .INI file on PC (instructions coming soon). This file allocates memory to Wordfast and you can increase it manually.

Importing a TMX translation memory (TM)

Q. My  client sent me a TMX translation memory and when I try to import it into Wordfast Pro 5, it either fails or 0 TUs are imported. What is wrong?

A. Make sure the language pairs of your project exactly match those of the TMX TM. For example, if you have a TM whose source is “fr-FR” and target is “en-US”, you cannot use a project whose source language is “fr” only and whose target language is “en” only. You should create/open a project with “French (France)” (fr-FR) as your source language and “English (United States)” (en-US) as your target language. You will then be able to import the TMX TM into an existing TM or a new TM.

Opening a TXFL file sent via email

Q. I tried opening a TXLF file my client sent me and I get a message saying “Invalid document format detected”. What gives?

A. Ask your client to either send the TXLF file in a GLP package or to compress it in a ZIP or RAR format, then send it to you. This will prevent the TXLF file from being corrupted by email providers.


Import terminology with proper encoding

Q. I just imported a glossary from a tab-delimited text file and all the accented characters, special characters, or non-Latin language characters are not displaying properly. What do I do?

A. You need to convert the .txt file of the tab-delimited glossary to Unicode before importing it into Wordfast Pro. To do so, open it in NotePad (Windows) or TextEdit (Mac) and select "Save as"; under "Encoding", select Unicode (UTF-16) or UTF-8.


Change Language of the Target PPT File

Q. Is there a way to make Wordfast Pro assign the target language to the translated PPT?

A. Apparently, the PPT filter does not have this improvement. To work around that, save the SOURCE document as PPTX; when you "Save Translated File", you will get the target PPTX file with the correct target language.

In fact, using PPTX (instead of PPT) seems to be the quick fix for several issues in both WF Pro and WF Anywhere.


Remove PDF source from the target file

Q. I have translated a PDF using Wordfast Pro 5. However, in the target document, the text is garbled and consists of both the source and the translation. I would like to get rid of the source text.

A. Actually, the source appears on a background image. Open the target document in Word, click on a blank part of the page, and then press the 'Delete' button on your keyboard, and it gets rid of the background. Do the same for each page of the document, and "Save" it.



Version: Wordfast Pro 5.7
Operating System: macOS

Updated by Star 15 January 2019
  1. Thanks to Samuel for the tip!