Dragomir Kovacevic

Italy

Local time: 18:13

Italian to Serbian

+ ...

"how to import a TM from wordfast (5.5) to OT" Feb 13

I am regularly using Okapi Tools, i.e the Olifant internal application for that operation: open and/or import several Wf memories into a larger one, then export them, or save them as TMX. Works very nice.

Another reserve tool of the same kind, which sometimes can provide more safety, but has less features, is a previous version of the same tool: Rainbow + Olifant.

What Marc and Esperantisto say, is also correct.

(Esperantisto, Wf2tmx does use Wf memories in UT-16LE, and exports into TMX. I do not notice the difference, besides the improvements on the latest version of the said tool: if before I had a language ID like: IT-IT, than Wf2tmx merrily kept cutting out the regional suffix: "-IT".

dragomir

Thanx in advance

esperantisto

Belarus

Local time: 19:13

This is a ProZ.com Member.>Member (2006)

English to Russian

+ ...

I did not know that Feb 13

Dragomir Kovacevic wrote:

if before I had a language ID like: IT-IT, than Wf2tmx merrily kept cutting out the regional suffix: "-IT".

But one of the things, that I like very much about OmegaT, is that OmegaT does not care about language codes

Thanks for the information!

Samuel Murray

Netherlands

Local time: 18:13

This is a ProZ.com Member.>Member (2006)

English to Afrikaans

+ ...

It is also a downside... Feb 13

esperantisto wrote:

But one of the things, that I like very much about OmegaT, is that OmegaT does not care about language codes

It does mean, however, that OmegaT TMX files may not work on tools that are more strict when it comes to language codes.

esperantisto

Belarus

Local time: 19:13

This is a ProZ.com Member.>Member (2006)

English to Russian

+ ...

Big deal! Feb 13

I don’t care. Those, who do, can simply search and replace the codes in any text editor.

Marc P

Germany

Local time: 18:13

German to English

+ ...

Clarification Feb 13

Samuel Murray wrote:

It does mean, however, that OmegaT TMX files may not work on tools that are more strict when it comes to language codes.

Is the issue here the "OmegaT TMX file", or the fact that the OmegaT user may not have specified the precise language variant expected by the other user's CAT tool? If I've understood the issue correctly, the incompatibility lies in the workflow, not the technology.

Marc

Samuel Murray

Netherlands

Local time: 18:13

This is a ProZ.com >Member (2006)

English to Afrikaans

+ ...

Assuming user's level of geekiness Feb 13

esperantisto wrote:

Samuel Murray wrote:

It does mean, however, that OmegaT TMX files may not work on tools that are more strict when it comes to language codes.

I don’t care. Those, who do, can simply search and replace the codes in any text editor.

That is, if they can figure out the reason why the other CAT tool isn't serving matches from the TM and/or giving such a weird error message. I recently encountered a tool (in beta, but still) that assumes all TMX files are 1.4, and if it finds anything 1.1-ish in the file that it doesn't understand, it tries to fix it (and usually breaks it). You hope the user has a backup copy of his beloved TMX file...

Samuel Murray

Netherlands

Local time: 18:13

This is a ProZ.com Member.Member (2006)

English to Afrikaans

+ ...

The issue is the OmegaT TMX file Feb 13

Marc P wrote:

Is the issue here the "OmegaT TMX file", or the fact that the OmegaT user may not have specified the precise language variant expected by the other user's CAT tool?

OmegaT does not complain if the user enters invalid or uncompliant language codes, but simply uses them as-is. True, if you try to add a language code like "EN-US-hillbilly" or "AF-ZA-orania", you get an error message that says "xx_XX" or "xx-XX" are the only valid codes. But the default (and hence suggested) language codes in OmegaT's project properties pane are in the form XX-XX (not xx-XX).

[Edited at 2009-02-13 12:29 GMT]