Forum: Wordfast support
Topic: Wordfast Pro doesn't leverage from the imported TMX
Poster: jyuan_us
Post title: I second you
[quote]Heinrich Pesch wrote:
[quote]Yasmin Moslem wrote:
[quote]Heinrich Pesch wrote:
How many units were successfully loaded? I just tried this with a tmx I yesterday exported from Trados 2007, and WFP did not succeed in importing a single unit.[/quote]
This could be the problem of the original sender as well. This happens if the language codes are difference. For example, if the TMX is from EN-US to [b]FR-FR [/b] while the currently open project is EN-US to [b]FR[/b], it will not imported. TMX import in Wordfast Pro is very strict and you need to open a project with the same language pair locales/variants to be able to convert it. Later, you can use the converted (local) TM in any project with the same language pair even if the variants are different.
Otherwise, you can use Okapi Olifant:
[url removed]
Kind regards,
Yasmin [/quote]
I think WF should import all units into a new tm after I click on Add. In any case the software should do what the translator wants, not what the developer thinks is right. Many use one tm for all language pairs, because it only matters what the source is. You will not find German units in an English text, so it is not necessary to keep different tms for each source language. More flexibility please! (I have stopped using WFP because Studio 2014 is so much more useful). [/quote]
Individual TMs needed to be created for many language pairs, which makes it very confusing.
Topic: Wordfast Pro doesn't leverage from the imported TMX
Poster: jyuan_us
Post title: I second you
[quote]Heinrich Pesch wrote:
[quote]Yasmin Moslem wrote:
[quote]Heinrich Pesch wrote:
How many units were successfully loaded? I just tried this with a tmx I yesterday exported from Trados 2007, and WFP did not succeed in importing a single unit.[/quote]
This could be the problem of the original sender as well. This happens if the language codes are difference. For example, if the TMX is from EN-US to [b]FR-FR [/b] while the currently open project is EN-US to [b]FR[/b], it will not imported. TMX import in Wordfast Pro is very strict and you need to open a project with the same language pair locales/variants to be able to convert it. Later, you can use the converted (local) TM in any project with the same language pair even if the variants are different.
Otherwise, you can use Okapi Olifant:
[url removed]
Kind regards,
Yasmin [/quote]
I think WF should import all units into a new tm after I click on Add. In any case the software should do what the translator wants, not what the developer thinks is right. Many use one tm for all language pairs, because it only matters what the source is. You will not find German units in an English text, so it is not necessary to keep different tms for each source language. More flexibility please! (I have stopped using WFP because Studio 2014 is so much more useful). [/quote]
Individual TMs needed to be created for many language pairs, which makes it very confusing.