ttx, tmx - what for? Thread poster: Andrzej Mierzejewski
|
Several basic questions from a newbie: An agency sent me a DOC file to translate, a TMX file and a TTX file. All files from the same project. The agency uses Trados but I do not. The PM was not able to explain me me what I need the TMX and TTX for. I have had some previous experience with OmegaT for simple texts but never before received TTX and TMX files as a basis for my work. My OmegaT version is 2.6.3. So, I saved the DOC file as ODT file to be the source file for O... See more Several basic questions from a newbie: An agency sent me a DOC file to translate, a TMX file and a TTX file. All files from the same project. The agency uses Trados but I do not. The PM was not able to explain me me what I need the TMX and TTX for. I have had some previous experience with OmegaT for simple texts but never before received TTX and TMX files as a basis for my work. My OmegaT version is 2.6.3. So, I saved the DOC file as ODT file to be the source file for OmegaT to process. I heard that OmegaT needs an Okapi plugin to be able to process TTX, so I downloaded the okapi-pluginForOmegaT_all-platforms_0.20.zip, unzipped and found four JAR files and one read-me TXT file. I copied all JAR files to the OmT 'plugins' directory. I hope that operation was correct but am not sure whether I really need all four. My OS is 32-bit Windows 7. Then, I copied the TMX file to the 'tm' directory inside the project directory. Was that operation correct or not? Now, I have the TTX file and a question: which subdirectory should I copy this file to? As far as I can see, the choice is four-fold: dictionary, glossary, omegat, target. Or else? It's possible that all my questions have been answered in this forum already but could not find clear and short explanations. Awaiting your advice, Andrzej Mierzejewski ▲ Collapse | | | Susan Welsh United States Local time: 19:17 Russian to English + ... See documentation section of the website | Mar 15, 2013 |
Sounds to me like you did everything right. If memory serves, you should put the Trados .ttx file in the /source/ folder. See the documentation on the OmegaT website for more on this: ... See more Sounds to me like you did everything right. If memory serves, you should put the Trados .ttx file in the /source/ folder. See the documentation on the OmegaT website for more on this: http://www.omegat.org/en/howtos/compatibility.html http://www.opentag.com/okapi/wiki/index.php?title=Okapi_Filters_Plugin_for_OmegaT .tmx is the industry-wide translation memory format, whereas .ttx is a Trados proprietary format, which can only be used in OmegaT with the plugin. I've done it a couple of times and it worked, but it's not fresh in my mind and it's too late to look into it more tonight. You will not be able to generate a .ttx file, so you will give your client the .tmx file. Trados can make it into a .ttx. HTH ▲ Collapse | | | Did not the customer know... | Mar 15, 2013 |
...that you do not have Trados? It seems to me that you should have made it clear from the beginning. | | | Didier Briel France Local time: 01:17 English to French + ... You can translate TTX with OmegaT | Mar 15, 2013 |
Andrzej Mierzejewski wrote: Several basic questions from a newbie: An agency sent me a DOC file to translate, a TMX file and a TTX file. All files from the same project. The agency uses Trados but I do not. The PM was not able to explain me me what I need the TMX and TTX for. I have had some previous experience with OmegaT for simple texts but never before received TTX and TMX files as a basis for my work. My OmegaT version is 2.6.3. So, I saved the DOC file as ODT file to be the source file for OmegaT to process. If you translate the TTX, you do not need the DOC file (assuming they correspond to the same document), other than as a reference. I heard that OmegaT needs an Okapi plugin to be able to process TTX, so I downloaded the okapi-pluginForOmegaT_all-platforms_0.20.zip, unzipped and found four JAR files and one read-me TXT file. I copied all JAR files to the OmT 'plugins' directory. I hope that operation was correct but am not sure whether I really need all four. My OS is 32-bit Windows 7. Yes, they are all needed. Then, I copied the TMX file to the 'tm' directory inside the project directory. Was that operation correct or not? Yes. You can also move the TMX to tm/auto, if you want exact matches to be inserted automatically. Now, I have the TTX file and a question: which subdirectory should I copy this file to? As far as I can see, the choice is four-fold: dictionary, glossary, omegat, target. Or else? Else. The TTX file is a source document, so it should go to the source subdirectory. Again assuming they correspond to the same document, either you translate the DOC file, or the TTX file, but not both. Didier | |
|
|
Samuel Murray Netherlands Local time: 01:17 Member (2006) English to Afrikaans + ...
Tomás Cano Binder, CT wrote: Did not the customer know ... that you do not have Trados? It seems to me that you should have made it clear from the beginning. It sounds to me like the customer doesn't really know how Trados works either. | | | veratek Brazil Local time: 20:17 French to English + ... TTX plugin is not working properly | Jun 27, 2013 |
Didier Briel wrote: Andrzej Mierzejewski wrote: Several basic questions from a newbie: I heard that OmegaT needs an Okapi plugin to be able to process TTX, so I downloaded the okapi-pluginForOmegaT_all-platforms_0.20.zip, unzipped and found four JAR files and one read-me TXT file. I copied all JAR files to the OmT 'plugins' directory. I hope that operation was correct but am not sure whether I really need all four. My OS is 32-bit Windows 7. Yes, they are all needed. I downloaded this: okapi-pluginForOmegaT_all-platforms_0.21.zip json-simple-1.1.1.jar okapiFiltersForOmegaT-0.21.jar slf4j-api-1.7.2.jar slf4j-jdk14-1.7.2.jar stax2-api-3.1.1.jar woodstox-core-lgpl-4.1.4.jar I copied all of the above to: D:\programs\OmegaT\plugins I open Omegat, create a new project, then I add a doc.ttx file. Omegat opens the file in the project, but it only displays a few words for translation - that is, most of the text of the document is not displayed; it's as if it didn't exist in the document. I opened the doc.ttx file in Word and I found this out: C1- Usage interne C1- Internal use Above is the only type of text that Omegat displays. Below is the type of text it won't display and it doesn't appear counted in the stats either: Contexte / pré-requis Contexte / pré-requis Any idea what the problem is? Thanks. | | | Didier Briel France Local time: 01:17 English to French + ... It might be a segmentation issue | Jun 27, 2013 |
veratek wrote: I downloaded this: okapi-pluginForOmegaT_all-platforms_0.21.zip json-simple-1.1.1.jar okapiFiltersForOmegaT-0.21.jar slf4j-api-1.7.2.jar slf4j-jdk14-1.7.2.jar stax2-api-3.1.1.jar woodstox-core-lgpl-4.1.4.jar I copied all of the above to: D:\programs\OmegaT\plugins I open Omegat, create a new project, then I add a doc.ttx file. Omegat opens the file in the project, but it only displays a few words for translation - that is, most of the text of the document is not displayed; it's as if it didn't exist in the document. I opened the doc.ttx file in Word and I found this out: C1- Usage interne C1- Internal use Above is the only type of text that Omegat displays. Below is the type of text it won't display and it doesn't appear counted in the stats either: Contexte / pré-requis Contexte / pré-requis Any idea what the problem is? It could be a segmentation issue. http://www.opentag.com/okapi/wiki/index.php?title=Okapi_Filters_Plugin_for_OmegaT "If one or more segments are detected only the existing segments are passed to OmegaT. So if a file is only half segmented you will not get the un-segmented text in OmegaT." You would have better answers asking Okapi specialists (i.e., the people involved in Okapi). There is a dedicated group: http://tech.groups.yahoo.com/group/okapitools/ but one member of the Okapi team monitors the OmegaT group as well, so you can post there: http://tech.groups.yahoo.com/group/OmegaT/ Didier | | | veratek Brazil Local time: 20:17 French to English + ... actually proz interface "erased" part of my comment | Jun 27, 2013 |
let's try again: all the text between these tags appears in Omegat: ST target createdby="system" score="100" golden="true" GT C1- Usage interne C1- Internal use ST/ target GT ........................................ The text between source and target score=0 doesn't appear: ST source GT Contexte / pré-requis ST/ source GT ST target score="0" GT Contexte / pré-requis ST... See more let's try again: all the text between these tags appears in Omegat: ST target createdby="system" score="100" golden="true" GT C1- Usage interne C1- Internal use ST/ target GT ........................................ The text between source and target score=0 doesn't appear: ST source GT Contexte / pré-requis ST/ source GT ST target score="0" GT Contexte / pré-requis ST/ target GT above, ST=smaller than sign GT= greater than sign ▲ Collapse | |
|
|
Didier Briel France Local time: 01:17 English to French + ... It's not the best place to solve this issue | Jun 28, 2013 |
veratek wrote: let's try again: all the text between these tags appears in Omegat: ST target createdby="system" score="100" golden="true" GT C1- Usage interne C1- Internal use ST/ target GT ........................................ The text between source and target score=0 doesn't appear: ST source GT Contexte / pré-requis ST/ source GT ST target score="0" GT Contexte / pré-requis ST/ target GT above, ST=smaller than sign GT= greater than sign First, as far as I know, no Okapi specialist reads this forum. Secondly, the ProZ forum limitations makes it impossible to understand your sample from an XML point of view. I recommend going to one of the two support groups I have mentioned. Didier | | | veratek Brazil Local time: 20:17 French to English + ... forum interface limitations | Jun 28, 2013 |
Didier Briel wrote: veratek wrote: let's try again: all the text between these tags appears in Omegat: ST target createdby="system" score="100" golden="true" GT C1- Usage interne C1- Internal use ST/ target GT ........................................ above, ST=smaller than sign GT= greater than sign First, as far as I know, no Okapi specialist reads this forum. Secondly, the ProZ forum limitations makes it impossible to understand your sample from an XML point of view. I recommend going to one of the two support groups I have mentioned. Didier I can't know what is important for someone to understand until I post it and they can understand it. A "smaller than" sign is the sign that begins an HTML or an XML tag - and the "greater than" sign is the sign that ends an HTML tag. If you just substitute them above, you can make out what the actual snippet is like in the original file. I don't understand what is difficult about replacing ST with the smaller than sign above. I'm not saying you or anyone else here has to know how to solve the problem, but at least it would be nice if people could actually understand what was posted. What's the purpose of asking a question if other people can't even understand the question? | | | Didier Briel France Local time: 01:17 English to French + ... Your sample is too small | Jun 28, 2013 |
veratek wrote: Didier Briel wrote: veratek wrote: let's try again: all the text between these tags appears in Omegat: ST target createdby="system" score="100" golden="true" GT C1- Usage interne C1- Internal use ST/ target GT ........................................ above, ST=smaller than sign GT= greater than sign First, as far as I know, no Okapi specialist reads this forum. Secondly, the ProZ forum limitations makes it impossible to understand your sample from an XML point of view. I recommend going to one of the two support groups I have mentioned. Didier I can't know what is important for someone to understand until I post it and they can understand it. A "smaller than" sign is the sign that begins an HTML or an XML tag - and the "greater than" sign is the sign that ends an HTML tag. If you just substitute them above, you can make out what the actual snippet is like in the original file. I don't understand what is difficult about replacing ST with the smaller than sign above. I'm not saying you or anyone else here has to know how to solve the problem, but at least it would be nice if people could actually understand what was posted. What's the purpose of asking a question if other people can't even understand the question? The TTX format is rather complex, and the sample you give is too small to have any clue of what might be going on. In another medium, you could just copy/paste a significant part of the file, or send it privately to an expert. You are mentioning "source" and "target" tags. That's not what I expect to see in a TTX file. Didier | | | There is no moderator assigned specifically to this forum. To report site rules violations or get help, please contact site staff » ttx, tmx - what for? CafeTran Espresso | You've never met a CAT tool this clever!
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Buy now! » |
| TM-Town | Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |