Quotations Thread poster: Wolfgang Schoene
|
I'm working on a quotation and am currently analyzing the files. 3 IDML files. Wordfast Pro 7 counts 38.719 word / 26.107 repetitions MemoQ counts 58.597 words / 40.145 reps Trados Studio counts 59.602 word / 48.451 reps Whom shall I trust? The difference between Wordfast count and MemoQ and Studio counts seems absurd. Any explanation for that? | | | Samuel Murray Netherlands Local time: 10:07 Member (2006) English to Afrikaans + ...
Wolfgang wrote: The difference between Wordfast count and MemoQ and Studio counts seems absurd. Perhaps Wordfast doesn't extract all of the text. You can test this by exporting the files to DOC/DOCX/RTF and comparing them in Word to see what are the extra bits of text that Trados and MemoQ are getting. In WFP7, it's Ctrl+5, then add the TXLF files, then "Bilingual export". In MemoQ, you create a view, then right-click and "Export bilingual". In Trados, right-click the project and go Batch Tasks > Export Bilingual Review. Or, perhaps Wordfast quietly ignores certain tags that both Trados and MemoQ do consider, which leads to fewer 100% matches. What do the three tools say are the total word counts? | | | Wolfgang Schoene France Local time: 10:07 Member (2007) English to German + ... TOPIC STARTER Total word counts | Mar 30, 2022 |
Samuel Murray wrote: Wolfgang wrote: The difference between Wordfast count and MemoQ and Studio counts seems absurd. Perhaps Wordfast doesn't extract all of the text. You can test this by exporting the files to DOC/DOCX/RTF and comparing them in Word to see what are the extra bits of text that Trados and MemoQ are getting. In WFP7, it's Ctrl+5, then add the TXLF files, then "Bilingual export". In MemoQ, you create a view, then right-click and "Export bilingual". In Trados, right-click the project and go Batch Tasks > Export Bilingual Review. Or, perhaps Wordfast quietly ignores certain tags that both Trados and MemoQ do consider, which leads to fewer 100% matches. What do the three tools say are the total word counts? Hi Samuel total word counts are those I quoted, that is: Trados: 59.402 MemoQ: 58.597 Wordfast: 38.719 Just doing one more analysis with DVX | | | Stepan Konev Russian Federation Local time: 11:07 English to Russian Different ways of trimming spaces? | Mar 30, 2022 |
Probably, this may be caused by how different tools trim spaces for example. Below are three identical segments in MS Word, Trados and memoQ.![2022-03-30_204939](https://res.cloudinary.com/proz/image/upload/v1648663334/rzffhi5p5h7wjwkszcpc.jpg) In this situation Trados seems to be most honest. Basically you can copy the entire source column from Trados and paste it into an MS Word document to see the real scope of work net of multiple spaces and tabs, tags, pictures, etc. | |
|
|
Wolfgang Schoene France Local time: 10:07 Member (2007) English to German + ... TOPIC STARTER DVX analysis | Mar 30, 2022 |
Wolfgang wrote: Samuel Murray wrote: Wolfgang wrote: The difference between Wordfast count and MemoQ and Studio counts seems absurd. Perhaps Wordfast doesn't extract all of the text. You can test this by exporting the files to DOC/DOCX/RTF and comparing them in Word to see what are the extra bits of text that Trados and MemoQ are getting. In WFP7, it's Ctrl+5, then add the TXLF files, then "Bilingual export". In MemoQ, you create a view, then right-click and "Export bilingual". In Trados, right-click the project and go Batch Tasks > Export Bilingual Review. Or, perhaps Wordfast quietly ignores certain tags that both Trados and MemoQ do consider, which leads to fewer 100% matches. What do the three tools say are the total word counts? Hi Samuel total word counts are those I quoted, that is: Trados: 59,402 MemoQ: 58,597 Wordfast: 38,719 Just doing one more analysis with DVX The DVX analysis says Total Words 32,869 / Duplicates 18,194 (no match 14,675) So this looks more or less like the WFP analysis. | | | Wolfgang Schoene France Local time: 10:07 Member (2007) English to German + ... TOPIC STARTER Thanks Stepan | Mar 30, 2022 |
Stepan Konev wrote: Probably, this may be caused by how different tools trim spaces for example. Below are three identical segments in MS Word, Trados and memoQ. ![2022-03-30_204939](https://res.cloudinary.com/proz/image/upload/v1648663334/rzffhi5p5h7wjwkszcpc.jpg) In this situation Trados seems to be most honest. Basically you can copy the entire source column from Trados and paste it into an MS Word document to see the real scope of work net of multiple spaces and tabs, tags, pictures, etc. Will do that | | |
IDML is a "distilled" (plain-text marked-up) InDesign format (for translation) that cannot be exported to DOC. It can only be imported back to the same InDesign project to update it with translation. I guess the problem is in the CAT-tools' filters and their ability to handle the InDesign-specific XML correctly. Samuel Murray wrote: Wolfgang wrote: The difference between Wordfast count and MemoQ and Studio counts seems absurd. Perhaps Wordfast doesn't extract all of the text. You can test this by exporting the files to DOC/DOCX/RTF and comparing them in Word to see what are the extra bits of text that Trados and MemoQ are getting. In WFP7, it's Ctrl+5, then add the TXLF files, then "Bilingual export". In MemoQ, you create a view, then right-click and "Export bilingual". In Trados, right-click the project and go Batch Tasks > Export Bilingual Review. Or, perhaps Wordfast quietly ignores certain tags that both Trados and MemoQ do consider, which leads to fewer 100% matches. What do the three tools say are the total word counts? | | | Samuel Murray Netherlands Local time: 10:07 Member (2006) English to Afrikaans + ...
Sergei Leshchinsky wrote: Samuel Murray wrote: You can test this by exporting the files to DOC/DOCX/RTF and comparing them in Word to see what are the extra bits of text that Trados and MemoQ are getting. In WFP7, it's Ctrl+5, then add the TXLF files, then "Bilingual export". In MemoQ, you create a view, then right-click and "Export bilingual". In Trados, right-click the project and go Batch Tasks > Export Bilingual Review. IDML is a "distilled" (plain-text marked-up) InDesign format (for translation) that cannot be exported to DOC. It can only be imported back to the same InDesign project to update it with translation. The export formats mentioned in my post are actually possible for IDML. | |
|
|
Yes, one can export a bilingual table and compare even visually. But this is only to see the logic bug. Samuel Murray wrote: You can test this by exporting the files to DOC/DOCX/RTF and comparing them in Word to see what are the extra bits of text | | |
Any particular reason not to use CafeTran? Import the idml, replace [aeiuo] with m. Export. Use Affinity Puplisher trial to check the idml. Regarding the counting: you could verify via a bilingual export table. | | |
Used a very simple, publicly available IDML file (but from experiences I know that CafeTran Espresso's filter is good and can handle complex documents). ![Screen Shot 2022-03-31 at 08.02.18](https://res.cloudinary.com/proz/image/upload/v1648706635/kpqlklnsrcbvjdsmd1ym.png) ![Screen Shot 2022-03-31 at 08.01.00](https://res.cloudinary.com/proz/image/upload/v1648706645/xfmbdayr2brbyhwamxny.png) ![Screen Shot 2022-03-31 at 08.01.43](https://res.cloudinary.com/proz/image/upload/v1648706653/cccjtsvorkapjywk94fn.png) | | |
Without the header and the numbering: ![Screen Shot 2022-03-31 at 08.06.09](https://res.cloudinary.com/proz/image/upload/v1648706807/w4ji8jmjevepnz9nydwy.png) | |
|
|
Rolf Keller Germany Local time: 10:07 English to German Counting words vs. counting characters | Mar 31, 2022 |
Stepan Konev wrote: Probably, this may be caused by how different tools trim spaces for example. Different handling of spaces might influence the character count but not the word count - at least not to such an extent. | | | Joakim Braun Sweden Local time: 10:07 German to Swedish + ...
Sergei Leshchinsky wrote: IDML is a "distilled" (plain-text marked-up) InDesign format It's not distilled. IDML contains all data necessary for recreation of the complete Indesign document, the same as .indd files. In fact, it IS an Indesign document. Sergei Leshchinsky wrote: (for translation) IDML is intended as a backwards-compatible XML format. That it works with CAT is just a coincidence. Sergei Leshchinsky wrote: It can only be imported back to the same InDesign project to update it with translation. There's no such thing as an "Indesign project", and the IDML file is not "imported back to" anything. The CAT tool simply creates a new IDML file with updated text. | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Quotations Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
| Pastey | Your smart companion app
Pastey is an innovative desktop application that bridges the gap between human expertise and artificial intelligence. With intuitive keyboard shortcuts, Pastey transforms your source text into AI-powered draft translations.
Find out more » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |