How to export mqxliff files to sdlxliff files? Initiator des Themas: Tonja Gaspersic
|
|---|
Hello,
I´m confronting with a huge problem that I can´t solve it by myself.
I got a package - SDL Trados, with 4 zip-files sent by e-mail (I extended them with 7z), I imported the SDL Trados package into memoQ without any problems, and translated them with memoQ. After the translation was done, I exported them as usually, and sent them to the client via e-mail.
But he says he can´t open them. I´ve tried all I knew: exported bilingual files, exported (... See more Hello,
I´m confronting with a huge problem that I can´t solve it by myself.
I got a package - SDL Trados, with 4 zip-files sent by e-mail (I extended them with 7z), I imported the SDL Trados package into memoQ without any problems, and translated them with memoQ. After the translation was done, I exported them as usually, and sent them to the client via e-mail.
But he says he can´t open them. I´ve tried all I knew: exported bilingual files, exported (dialog) - I don´t quite understand what that means, exported (stored path) as I usually do, but the client still can´t open the files. I think I sent the files via e-mail ten or even more times. I´ve been trying it for two days now, and I am at the end of my knowledge.
What wen´t wrong? The client can´t open the files. He need sdlxliff files or xlf files (he says, is this actually xliff?). How can I prepare mqliff files that he finally would open them? Is there any other way which I do not know? I asked some translators, and nobody had similar problems with memoQ, I visited Kilgray support pages, read some posts here, and still ... the same.
I hope I´ve explained the problem in at least approximately comprehensible way as my English isn´t so good.
Please help! Thank you in advance.
Regards
Tonja ▲ Collapse
| | | | | Was it really a SDL Studio package? | Mar 21, 2013 |
When you uncompressed the 7z files (these are simply ZIP files; the reason why you got several is perhaps because the original package was too big to be attached to a single email), what is the extention of the file you got? Was it "sdlppx"? This would be a SDL Studio package.
The sdlppx file is in fact just a ZIP file. If you change the extension of that file to ZIP and decompress that in Windows, you get several folders, one of which has the country/language codes of your target l... See more When you uncompressed the 7z files (these are simply ZIP files; the reason why you got several is perhaps because the original package was too big to be attached to a single email), what is the extention of the file you got? Was it "sdlppx"? This would be a SDL Studio package.
The sdlppx file is in fact just a ZIP file. If you change the extension of that file to ZIP and decompress that in Windows, you get several folders, one of which has the country/language codes of your target language (SL-SL perhaps if you translate into Slovenian?). What do you see inside of that folder? If you see one or more SDLXLIFF files, you can simply import that into memoQ, and when you do an Export (dialog) what you get is a file the customer should be able to open and which should have an SDLXLIFF extension.
Just to verify that everything started well, let us know whether the first statement above is true, and whether renaming to ZIP and decompressing the ZIP file of the package yields a folder with your language codes containing SDLXLIFF files. ▲ Collapse
| | | | Tonja Gaspersic
Slowenien
Local time: 09:05
Deutsch > Slowenisch
+ ...
THEMENSTARTER | How to export mqxliff files to sdlxliff files? 2. | Mar 21, 2013 |
Hello, Tomás,
Thank you for your answer. I couldn't reply right away, because of hands full of work. Unfortunately, I didn't solve the problem yet. How it was started?
I got the file via email: name_sl-SI.rar (zip). I extended it with 7z, the SDLPPX file was there, and SDLPROJ also,
- there was a main folder with other folders: de-DE, File Types, Reports, Termbases, Tms with respective files;
- folder de-DE: par ex.: name_DE.fm.mif.sdlxliff, with the file ... See more Hello, Tomás,
Thank you for your answer. I couldn't reply right away, because of hands full of work. Unfortunately, I didn't solve the problem yet. How it was started?
I got the file via email: name_sl-SI.rar (zip). I extended it with 7z, the SDLPPX file was there, and SDLPROJ also,
- there was a main folder with other folders: de-DE, File Types, Reports, Termbases, Tms with respective files;
- folder de-DE: par ex.: name_DE.fm.mif.sdlxliff, with the file extension SDLXLIFF and 3 more,
- folder sl-SI: the same files,
- saved all on the computer,
- opened memoQ,
- imported all 4 files as SDL Trados files (I think the 1st choice),
- started with translations,
- after the translations were done,
- exported them: bilingual, dialog, stored path - all 3, repeatedly,
- I can't remember anymore what I have tried to do to solve the problem (asking others, video lectures at Kilgray, answers on Proz forums, etc.
- the client couldn't/can't open the files, he has Trados Studio 2011,
- I never had problems till now with opening, translating, exporting Trados files,
- I didn't make a segmentation, is this a problem perhaps?
I have now files saved:
- name_DE.fm.mif.sdlxliff (SDLXLIFF) - obviously before translation,
- name_DE.fm.mif.slv.mqlxliff (MQXLIFF) - translated, but how to change into XLIFF or SDLLIFF,
- NAME_DE.fm.mif.slv.xliff.mqliff (MQXLIFF) - translated, I wanted to change the extension, but as you see, it didn't work,
- name_DE.fm.mif_slv - translated, RTF file, and
- name_DE.fm.mif_slv - translated, saved as doc file,
- name_DE.XLIFF - translated, but only two files of 4, and the other two don't wan't to be XLIFF,
- the file with the folder name namename_sl-SI.sdlrpx (SDLRPX) is there also, but I don't think it is complete (not enough KB).
I hope I didn't forget something.
I don't use Trados Studio 2009 anymore (to many problems from start, with the licence, etc.), since my old computer was broken, I didn't even try to get the licence back and installed it on the hard disk.
What do you think I should do now? I hope that all my work and effort wasn't for nothing.
Thank you for your help!
Tonja ▲ Collapse
| | | | | Probably the segmentation... | Mar 22, 2013 |
Indeed to me it sounds like it could be the segmentation. However, memoQ does warn when the files are not segmented, or at least it does now. What version of memoQ do you have?
I have Studio 2011. If you wish, I could try to open the package and segment the files for you, so that you could retranslate them with memoQ. After that, the only think you would need to do is do an Export (Dialog) operation and send the files again to me so that I can check that they open alright. I think I... See more Indeed to me it sounds like it could be the segmentation. However, memoQ does warn when the files are not segmented, or at least it does now. What version of memoQ do you have?
I have Studio 2011. If you wish, I could try to open the package and segment the files for you, so that you could retranslate them with memoQ. After that, the only think you would need to do is do an Export (Dialog) operation and send the files again to me so that I can check that they open alright. I think I have German among my installed languages. Feel free to email me via my profile and I will answer back.
One additional question though: do you have the latest version of memoQ installed (6.2)? Right now it is 6.2.13 actually. ▲ Collapse
| | |
|
|
|
Steven Segaert
Estland
Local time: 10:05
Mitglied (2012)
Englisch > Niederländisch
+ ...
| Wrong files? | Mar 22, 2013 |
Hi,
First of all, let's make sure you have your TM's for this job safely backed up in a tmx file .
Then, I would personally "start again" and take things in the right order. Start a new project in MemoQ to keep it simple, and unzip everything you have received in a new folder (just to start fresh).
As you report, there will be different folders as a result. One of the folders has the languag... See more Hi,
First of all, let's make sure you have your TM's for this job safely backed up in a tmx file.
Then, I would personally "start again" and take things in the right order. Start a new project in MemoQ to keep it simple, and unzip everything you have received in a new folder (just to start fresh).
As you report, there will be different folders as a result. One of the folders has the language code of the target language. You will need that one. Do not work with the files you find in the folder with the source language code. That won't work.
So, in the folder with the target language code, there are sdlxliff files. These you can simply import in MemoQ.
When you open one of these files in MemoQ, you should see the grid with the source copied to the target. If that is the case, then this should mean that the file has been segmented in Studio.
Next, connect your TM to this new project, and run a pretranslation. If all is well, MemoQ should present you with the translated result and a simple check of the result should be enough. Do run the QA to make sure no tags are lost.
When you are done with that, simply use the "Export (stored path)" option. MemoQ will save your translated file in the folder where it came from, in the format it has received.
In other words, you will end up with a sdlxliff file. I suggest sending these files to your client and check if he/she can open it. It should be ok, and it should be everything they need.
All this is written presuming you are running MemoQ 6.2. If you have another version, you'll need to let us know before we can assist further.
Let me know if this helps! ▲ Collapse
| | | | Tonja Gaspersic
Slowenien
Local time: 09:05
Deutsch > Slowenisch
+ ...
THEMENSTARTER
Thank you all from the heart for your kind help!
After two days of searching advise and right solution las night (actually this morning) I've solved the problem, finally I could export the files and save them as xlf files, so that the client could open them. The proceeding is well described on this site (warmly recommended!):
<... See more Thank you all from the heart for your kind help!
After two days of searching advise and right solution las night (actually this morning) I've solved the problem, finally I could export the files and save them as xlf files, so that the client could open them. The proceeding is well described on this site (warmly recommended!):
http://www.translationtribulations.com/2013/02/the-truth-about-memoq-6x-and-xliff.html
The client wasn't quite satisfied, and I can't blame him for that. He sent me the following message:
"Ich habe die Übersetzung gerade anhand Ihre xlf-Dateien durchgeführt. Man kann die Dateien nicht in Trados importieren, also habe ich sie geöffnet, händisch bestätigt und zum Translation Memory hinzugefügt, dann vorübersetzt und die ganze Tags neu gesetzt. Das ist ein Riesenaufwand gewesen.
Bitte sagen Sie uns wann Sie wieder angefangen haben, Trados zu benutzen. Bis dahin können wir keine Übersetzungen mehr an Ihnen verteilen. Der Aufwand ist zu groß."
I've lost the client obviously, and I caused a lot of trouble to him (not to mention my dissapointment after so much work and efforts I've made). At least I've found some comfort in the fact I've learned something new from it).
I would like to know what exactly caused this problem, since I hadn't any troubles with memoQ till now. When I opened and pretranslated even Trados files I managed them to translate and export as normally. That was for the first time I've got this kind of trouble.
I use memoQ it since december, I've bought the license (6.2) a month ago, I like it, and I find it just right CAT tool for my needs (and my customer needs). On the contrary it wasn't the same with the Trados Studio 2009.
Was it the segmentation, or something else? I would llike to know to avoid similar problems in the future. After I've read your solutions I can imagine possible steps I probably wen't wrong.
As an old wisdom says, and I repeat it (but my daughter hates it when she hears me saying it because it happens very often): "A day without learning something new is a lost day".
Thank you, thank you all! I hope some day I would return to help you.
Have a very nice day all,
Tonja ▲ Collapse
| | | | | To me it is the segmentation | Mar 22, 2013 |
Indeed, to me the matter was the fact that you had not "prepared" (i.e. presegmented) the file in Studio, and therefore the XLIFF files saved from memoQ were not structurally correct.
If you do not have a current license of Studio, it is best to say so to the customer so that they are advised. We have had some customers presegment the files for us, a step that would have saved your customer a tremendous time...
If you regularly work for customers who use Studio and don'... See more Indeed, to me the matter was the fact that you had not "prepared" (i.e. presegmented) the file in Studio, and therefore the XLIFF files saved from memoQ were not structurally correct.
If you do not have a current license of Studio, it is best to say so to the customer so that they are advised. We have had some customers presegment the files for us, a step that would have saved your customer a tremendous time...
If you regularly work for customers who use Studio and don't want to risk losing them, I would buy a license of Studio and keep it there just as a useful interface to your Studio-based customers. ▲ Collapse
| | | | Steven Segaert
Estland
Local time: 10:05
Mitglied (2012)
Englisch > Niederländisch
+ ...
I'm happy you have solved the problem, Tonja, but I still think you're on the wrong track.
With the default option (stored path), MemoQ will output your files in the same format as the input. Doc in, doc out. Sdlxliff in, sdlxliff out.
What Kevin describes in his blog is how to create an xlf file that Studio will recognise, "out of the blue". That is the situation where a clients sends you a doc file and wants an sdlxliff back - in other words, doc in, xlf out. That i... See more I'm happy you have solved the problem, Tonja, but I still think you're on the wrong track.
With the default option (stored path), MemoQ will output your files in the same format as the input. Doc in, doc out. Sdlxliff in, sdlxliff out.
What Kevin describes in his blog is how to create an xlf file that Studio will recognise, "out of the blue". That is the situation where a clients sends you a doc file and wants an sdlxliff back - in other words, doc in, xlf out. That is a different workflow than getting sent a Studio package or even a pre-segmented sdlxliff file.
What you needed was indeed the sdlxliff, sdlxliff out, and it seems to me that two things went wrong:
1) I suspect you used the wrong files - not the ones from the target folder. That way, indeed, you won't have the Studio segmentation.
2) You exported as bilingual instead of using the "stored path", which means that you didn't use the "format in = format out" approach.
I would encourage you to test this out (the trial version of Studio comes with a test package) and to make sure that you can proceed with confidence.
And if someone is reading this and thinks I'm right or wrong, please also do let me know.
While I myself do have a copy of Studio 2011 exactly because I was worried about compatibility, I haven't had to use it for this purpose. If I would have to make that decision again, I probably would decide to "team up" with a few colleagues and to agree the conditions under which one of us would check the compatibility of the files if needed. It is, after all, pretty expensive software to notice that you don't really need it after all. ▲ Collapse
| | |
|
|
|
Carl Carter
Deutschland
Local time: 09:05
Deutsch > Englisch
+ ...
| Ask Kilgray's Support team for advice | Mar 22, 2013 |
Hi Tonja,
Tomás and Steven have given you some good advice here by the look of it. If you really want to find out what went wrong and what you could have done to rectify it, why not contact the Support team at Kilgray? After all, if you now have a licence for memoQ, you're entitled to a number of hours of free technical support each year, which includes helping you with any issues you have with the program.
You may also like to consider posting a message on the memoQ u... See more Hi Tonja,
Tomás and Steven have given you some good advice here by the look of it. If you really want to find out what went wrong and what you could have done to rectify it, why not contact the Support team at Kilgray? After all, if you now have a licence for memoQ, you're entitled to a number of hours of free technical support each year, which includes helping you with any issues you have with the program.
You may also like to consider posting a message on the memoQ users' forum at Yahoo! Groups, which is similar to Proz.com's user forum, but even more active, so it complements it.
SDLXLIFF is an important file format for many translators who work for agencies, it seems, so any issues there are with this kind of file need explaining and solving ASAP. As far as I know, memoQ can usually handle this file type quite well, but you need to follow the right procedure to get there, like Steven says.
Regards
Carl ▲ Collapse
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » How to export mqxliff files to sdlxliff files? | Wordfast Pro |
|---|
Translation Memory Software for Any Platform
Exclusive discount for ProZ.com users!
Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value
Buy now! » |
| | 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! » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
