https://www.wordfast.net/w/index.php?action=history&feed=atom&title=Common_Problems_in_Wordfast_Pro_4Common Problems in Wordfast Pro 4 - Revision history2026-04-20T14:26:02ZRevision history for this page on the wikiMediaWiki 1.30.0https://www.wordfast.net/w/index.php?title=Common_Problems_in_Wordfast_Pro_4&diff=3245&oldid=prevJohn: Created page with "== Wordfast Pro 4 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 pr..."2017-01-02T12:31:54Z<p>Created page with "== Wordfast Pro 4 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 pr..."</p>
<p><b>New page</b></p><div>== Wordfast Pro 4 is slow, especially with big files ==<br />
<br />
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?<br />
<br />
A. There are several quick fixes to resolve this problem. Nonetheless, as of September 2016, developers are working on several improvements to speed up the TXLF editor overall and these improvements will be in versions 4.10 and 4.11. In the meantime, please try the following:<br />
<br />
# 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 WFP4 to the point of frequent freezing. Modify this setting by going to Wordfast 4 > Preferences > Spellchecker. <br />
# 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 4 > Preferences > Spellchecker. <br />
# Try disabling term highlighting. Go to Wordfast 4 > Preferences > Terminology and uncheck the option that says "Enable term highlighting as you type", as in this screenshot http://prntscr.com/b9qid1<br />
# 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.<br />
# 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.<br />
# 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.<br />
<br />
Thanks to [http://www.proz.com/profile/877433 Danielle Deremo Cosimo] for compiling a few of these issues. <br />
<br />
<!-- <br />
== Get matches from the TM==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
<br />
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<br />
the TM file in NotePad.<br />
<br />
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. <br />
<br />
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.<br />
<br />
<br />
Q. In [[Wordfast Pro]], I cannot get a match from a TM that was used in Wordfast Classic or aligned with PlusTools.<br />
<br />
A. Click the "Reorganize" button (of Wordfast Classic) whenever you exchange a TM between Wordfast Classic and Wordfast Pro.<br />
<br />
<br />
Q. In [[Wordfast Pro]], I cannot get a match from a TM; the colour of segments of the segments are pink.<br />
<br />
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).<br />
<br />
<br />
== Open TMX Translation Memory ==<br />
<br />
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.<br />
<br />
Otherwise, you can use Okapi Olifant to convert the TMX into a Wordfast TM. This [http://youtu.be/J8A45N40a0k video] illustrates the steps.<br />
<br />
<br />
== Open TXML Sent via Email ==<br />
<br />
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.<br />
<br />
<br />
== Change Memory Preferences ==<br />
<br />
When you have a [http://wordfast.net/wiki/Common_Error_Messages_in_Wordfast_Pro#Cannot_Open_file:_Java_heap_space Java heap space error], you have to change Wordfast Pro Memory Preferences to a higher value. However, when you open "Memory Preferences" again, if you find your change reverted back to the default (smallest) value, this might mean that your security settings prevent WFP from changing the file on the system partition. One thing to try is to adjust the Wordfast.ini manually. If you have installed [[Wordfast Pro]] onto the C: partition, it should be at: C:\Program Files\Wordfast\Wordfast.ini<br />
<br />
You should have the default value: -Xmx256m<br />
<br />
Change it to be: -Xmx1024m <br />
<br />
or -Xmx1470m<br />
<br />
Q. I tried to do so, but get an error message: "Access is denied", and the system refused to save the file.<br />
A. <br />
* You need to switch to a user with the administration rights.<br />
* Right-click the Wordfast.ini file (while it is closed!) and select "Properties" > "Security".<br />
* Click "Edit". Select "Users", and under "Allow", check "Full Control".<br />
* Click "OK" > "OK".<br />
* Now, you should be able to change it in the normal way at [[Wordfast Pro]] > Edit > Preferences > Memory Preferences.<br />
<br />
<br />
== Import Terminology with Proper Encoding ==<br />
<br />
In [[Wordfast Pro]], importing a tab-delimited glossary, special characters or non-Latin language characters are not displayed properly.<br />
<br />
'''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.<br />
<br />
<br />
== Save Translated INX File ==<br />
<br />
In [[Wordfast Pro]], "Save Translated File" generates a 0KB INX file.<br />
<br />
'''Possible reasons:'''<br />
<br />
* 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.<br />
<br />
* Missing [[placeables]] in target cells.<br />
<br />
* Shrinking segments including [[placeables]].<br />
<br />
'''Solution:''' <br />
<br />
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]].)<br />
<br />
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.<br />
<br />
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. <br />
<br />
<br />
== Change Language of the Target PPT File ==<br />
<br />
Q. Is there a way to make [[Wordfast Pro]] assign the target language to the translated PPT?<br />
<br />
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.<br />
<br />
In fact, using PPTX (instead of PPT) seems to be the quick fix for several issues in both WF Pro and WF Anywhere.<br />
<br />
<br />
<br />
== Remove PDF source from the target file ==<br />
<br />
Q. I have translated a PDF using [[Wordfast Pro]] and used {{menu|File}} > {{menu|Save Translated File}} to get the target file.<br />
However, in the target document, the text is garbled and consists of both the source and the translation.<br />
I would like to get rid of the source text.<br />
<br />
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.<br />
--></div>John