AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Wordfast pro download4/5/2023 ![]() In any case, it might be a good idea that Christina opens the TM and copies the header here so that we can see what the problem is/was. However, Wordfast Classic does NOT have three letter code as a standard.Īgain, as I mentioned earlier, if it is really a Wordfast TM (not a Trados exported TM), Christina can open the TM in Wordfast Classic latest version and click "Reorganize" to fix the problem in the case the TM is created in a too old version of WFC, PlusTools, or missing %, whatever. For language codes, if you have three-letter code, this could be an invalid header. ![]() WFP gives the error about the TM Header when the "syntax" of the header is clearly invalid. Wordfast offers full-featured demo versions of Wordfast Classic and Wordfast Pro that run without a paid license for. Even if you give a completely invalid language code (like ZZ-ZZ), WFP will give a different error message saying "Locale object for specified locale-code (zz) does not exist." It is important to know what might trigger the TM Header error. So, there is no problem in this regard, and even if the second part is not a valid locale at all, you will still be able to Add, Select, and use the TM. However, as far as I know (and double-checked), Wordfast Pro ignores 01 for example, WF Pro deals with JA-01 just as JA. Discussion among translators, entitled: How do I convert a Wordfast txt glossary to a Multiterm database suitable for Trados Studio. I haven't checked lately if Pro now tolerates FI-01 for Finnish. For instance, older versions of Classic suggested FI-01 as the code for Finnish, while Pro only accepted FI-FI or FI. Thanks, Yasmin, for pointing this out! However, some language codes that used to be recommended by Wordfast (Classic) earlier on were not accepted by Pro. The other case that WFP might give an error message about the header is if the user tries to open a Trados TXT exported TM. However, in this case the TMX will NOT give an error message about the header it might give rather a message about "Non-compatible locale". So, if it is rather about a TMX, I hope she clarifies that. The post of Christina seems to be about a local Wordfast (Classic) TM. You can even "Add" any TM file while you are in a project with a completely different language pair (however, you cannot select it unless you open a project with the same language pair, of course.) Both cases are different when it is rather a TMX. So, if you even have an FR>EN TM, you can "Select" and leverage (use) it in an FR-FR>EN-US project, whatever. Wordfast Pro is strict about language codes of TMX TMs however, it is very tolerant towards local TMs. ![]() So, you can either "Reorganize" or even add the missing % in the latter case manually. With the same easy-to-use features and imagery of Google Earth and additional capabilities designed specifically for business more info. I have seen this message with local Wordfast TMs coming form PlusTools or TMs missing the very first % from the header for some reason. - 12.2MB - Shareware - Increase employee productivity, communicate visually, and share geographic information with Google Earth Pro. If it is really a Wordfast TM, please open the TM in Wordfast Classic and click "Reorganize". ![]()
0 Comments
Read More
Leave a Reply. |