Forum: Wordfast support
Topic: Wordfast Pro from 3 to 4
Poster: John Di Rico
Post title: TM exporting, project organization
Hi John,
I just noticed that there is no export to TXT format which is strange. I will submit a ticket ASAP. In any event, you can import a TMX file with Wordfast Classic or Wordfast Pro 3.
We are discussing a way to make it easy to sync TMs so users can switch between Wordfast Pro 3 or Classic and Pro 4.
As far as importing a TXML file into Wordfast Pro 4, there is a TXML filter. Unfortunately, there is no way of importing a project with its settings (TM, glossary/blacklists, and links to recent files). When you decide to migrate, this is what I have done (still thinking about the best way to name/organize project folders, feel free to comment):
1. Create client-specific projects with timestamp at the beginning: YYMMDD client-endclient_FIELD One or two word description
2. Primary TM/glossary names: client-endclient_FIELD_ssss_tttt
3. Secondary TM/glossary: FTM_INTLDEV_frfr_enus and FG_INTLDEV_frfr_enus
For example, a project related to elephant trafficking for a direct client called IFW in the international development field would be:
YYMMDD ifw_INTLDEV Elephant trafficking blog post
Primary TM and glossary would have the same names and are saved in a TM and glossary folder respectively:
ifw_INTLDEV_frfr_enus
Secondary TM and glossary would be field based. By writing to two TMs, I can leverage translations done for one client in INTLDEV with another client in the same field.
There is a simpler way of doing things, namely—like in wfp4—just create one project per client and drop files into it as you get them. When finished translating the file, click on save translated file from the TXLF editor and that's it. However, you won't be able to leverage some advanced project management features in the future, such as exporting a package and sending it to a colleague for revision. You can also create a big momma TM/glossary that stores everything (i.e. not distinguish between different fields). This might work if you are very specialized and don't do a legal translation, then finance, then something marketing related to IT or cosmetics! Doesn't make sense in the latter case to store everything in a massive TM.
With my system, I can use the advanced project creation wizard to create a new project based on a project from the list of projects. I can see the previous project I did for the client, select it and run the wizard. It will automatically use the TMs, glossaries, and blacklist from the previous project, I just need to add the files.
If I have a brand new client that is in the INTLDEV field with no TM or glossary, I would chose another client in the INTLDEV field as a project template. When I get to the TM selection, I would remove the other client's TM and create a new one for the new client. Idem for the glossary.
Note: I use an Excel spreadsheet that lists standardized field acronyms. This is important so you don't create a TM using SWRE for software, then forget later and create a new one with IT… Keep it consistent!
As I said, when migrating to wfp4 from 3, I am basically moving a similar structure over to wfp4 on a case by case basis. When an INTLDEV project comes up for IFW, I will migrate the appropriate linguistic assets over to wfp4. When and INTLDEV project comes up for Client XYZ, I will move their TM over, etc.
Gradually, my TMs and glossaries will migrate over.
When you do decide to migrate from 3 to 4, it is a good opportunity to take stock of your current organization and think if you could improve it in light of the new features available in 4.
There is one problem with the glossaries in Wordfast Pro right now that really annoys me: I can't add a term to two glossaries at the same time. I am pestering development to implement this improvement.
Of course, you could go the simple route: one project, one TM, one glossary :-)
I hope this helps and would love to hear how others organize things…
Best,
John
Topic: Wordfast Pro from 3 to 4
Poster: John Di Rico
Post title: TM exporting, project organization
Hi John,
I just noticed that there is no export to TXT format which is strange. I will submit a ticket ASAP. In any event, you can import a TMX file with Wordfast Classic or Wordfast Pro 3.
We are discussing a way to make it easy to sync TMs so users can switch between Wordfast Pro 3 or Classic and Pro 4.
As far as importing a TXML file into Wordfast Pro 4, there is a TXML filter. Unfortunately, there is no way of importing a project with its settings (TM, glossary/blacklists, and links to recent files). When you decide to migrate, this is what I have done (still thinking about the best way to name/organize project folders, feel free to comment):
1. Create client-specific projects with timestamp at the beginning: YYMMDD client-endclient_FIELD One or two word description
2. Primary TM/glossary names: client-endclient_FIELD_ssss_tttt
3. Secondary TM/glossary: FTM_INTLDEV_frfr_enus and FG_INTLDEV_frfr_enus
For example, a project related to elephant trafficking for a direct client called IFW in the international development field would be:
YYMMDD ifw_INTLDEV Elephant trafficking blog post
Primary TM and glossary would have the same names and are saved in a TM and glossary folder respectively:
ifw_INTLDEV_frfr_enus
Secondary TM and glossary would be field based. By writing to two TMs, I can leverage translations done for one client in INTLDEV with another client in the same field.
There is a simpler way of doing things, namely—like in wfp4—just create one project per client and drop files into it as you get them. When finished translating the file, click on save translated file from the TXLF editor and that's it. However, you won't be able to leverage some advanced project management features in the future, such as exporting a package and sending it to a colleague for revision. You can also create a big momma TM/glossary that stores everything (i.e. not distinguish between different fields). This might work if you are very specialized and don't do a legal translation, then finance, then something marketing related to IT or cosmetics! Doesn't make sense in the latter case to store everything in a massive TM.
With my system, I can use the advanced project creation wizard to create a new project based on a project from the list of projects. I can see the previous project I did for the client, select it and run the wizard. It will automatically use the TMs, glossaries, and blacklist from the previous project, I just need to add the files.
If I have a brand new client that is in the INTLDEV field with no TM or glossary, I would chose another client in the INTLDEV field as a project template. When I get to the TM selection, I would remove the other client's TM and create a new one for the new client. Idem for the glossary.
Note: I use an Excel spreadsheet that lists standardized field acronyms. This is important so you don't create a TM using SWRE for software, then forget later and create a new one with IT… Keep it consistent!
As I said, when migrating to wfp4 from 3, I am basically moving a similar structure over to wfp4 on a case by case basis. When an INTLDEV project comes up for IFW, I will migrate the appropriate linguistic assets over to wfp4. When and INTLDEV project comes up for Client XYZ, I will move their TM over, etc.
Gradually, my TMs and glossaries will migrate over.
When you do decide to migrate from 3 to 4, it is a good opportunity to take stock of your current organization and think if you could improve it in light of the new features available in 4.
There is one problem with the glossaries in Wordfast Pro right now that really annoys me: I can't add a term to two glossaries at the same time. I am pestering development to implement this improvement.
Of course, you could go the simple route: one project, one TM, one glossary :-)
I hope this helps and would love to hear how others organize things…
Best,
John