#Wordfast 3 translating ms word comments how to

These are also saved as a TXT file and this time just two columns in the tab delimited fileвЂ¦ Forbidden and Suggestion. These consist of two monolingual columns like this:

#Wordfast 3 translating ms word comments how to

Now that I watch it back perhaps this will be useful for anyone trying to learn how to use SDL MultiTerm Convert, not least because there is no sound which might remove the rambling language barrier imposed by me talking too fast! BlacklistsД«efore I move onto Translation Memories itвЂ™s probably worth mentioning that Wordfast also has the concept of blacklists. This process has always been something many users stuggled with and is just one reason why the Glossary Converter has been such a successful application. But I still wanted to make the video while I was in the mood!) soВ I annotated it insteadвЂ¦ hopefully well enough to make sure itвЂ™s clear. ThereвЂ™s no sound on this one (it was late, IвЂ™m staying at my Mothers house, and I didnвЂ™t want to wake anyone up. This is an application that is installed with MultiTerm so youвЂ™ll find this in the program group for SDL MultiTerm. The second way is the conventionalВ way using SDL MultiTerm Convert which is based on deriving a termbase definition from the file you are converting so that you can then create a MultiTerm termbase and import matching XML data intoВ it. This one is a longer video, but only because in this one I was explaining how to understand the TXT file and how best to manipulate it to get what you need. Glossary ConverterДЇirst of all, using the Glossary Converter. So I have done it two ways in order to satisfy a couple of requests I recently received. Once you know this the process of converting is pretty straightforward.

None of these fields have headers in the TXT file but they seem to be this, from left to right: The Wordfast glossary TXT seems to be a fairly simple layout with four fields I thinkвЂ¦ at least this is all I have seen. So this means that converting them to something usable in any other tool means knowing how to manipulate this data into a format you can work with. Why am I mentioning this? Well, we now have three TXT files but you can be sure the data within is different in each case. They also have Translation Memories that are in TXT format, and as you may know the old Trados had Translation Memories that were TXT format too. This means you can open them in a text editor and read the data inside. These glossaries, at least the filebased ones as opposed to server versions (no idea if they even use these?) are simple TXT based formats. This of course made me think about the old versus the newвЂ¦ I wouldnвЂ™t compare Wordfast and Studio in this way at all рџ‰ Wordfast Glossaries IвЂ™ll start with the glossaries as this is where I got the idea from, I better explain my opening statement tooвЂ¦ this is because after I did an initial conversion using the Glossary Converter from the SDLВ Openexchange I was asked to explain how this would work with MultiTerm Convert. But on a quick check it looked as though theyВ are also TXT files so I decided to take a better look.Д«efore I get into the detail IвЂ™ll just add that IвЂ™m not very familiar with Wordfast so IвЂ™m basing my suggestions on the small number of files I have received, or created, and the processВ I used to convert them to formats more useful for a Studio user.

Then itвЂ™s simple, but what if you donвЂ™t have Wordfast or donвЂ™t want to have to try and use it? WordfastВ glossaries areВ new territory for me as IвЂ™d never looked at these before. Normally, for the TXT translation memories I get I would go the traditional route and use a copy of Wordfast to export as TMX. This article is all about out with the old and in with the new in more ways than one! In the last week I have been asked three times about converting Wordfast translation memories and Wordfast glossaries into resources that could be used in Studio and MultiTerm.