This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Maija Cirule Lettonie Local time: 12:47 allemand vers anglais + ...
Oct 30, 2016
MemoQ says : "Close tags should be structural". I work with MQ for several months and have never encountered this problem before. The document can be exported as a bilingual Rich text file.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
I suspect some tag is misplaced in one or several segments. Have you used the "Run QA" function to pinpoint any tag related issues? If Run QA reports changed tag order or missing tags, I suggest that you delete all tags in the affected segment(s) and insert them again in the right order (using F9 or copying/pasting).
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Maija Cirule Lettonie Local time: 12:47 allemand vers anglais + ...
AUTEUR DU FIL
Alas
Oct 30, 2016
Tomás Cano Binder, CT wrote:
I suspect some tag is misplaced in one or several segments. Have you used the "Run QA" function to pinpoint any tag related issues? If Run QA reports changed tag order or missing tags, I suggest that you delete all tags in the affected segment(s) and insert them again in the right order (using F9 or copying/pasting).
I have run Quality Assurance and re-inserted some tags to no avail. I found this very strange
[Edited at 2016-10-30 15:15 GMT]
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Apparently, the undue appearance of the error message you mention was fixed in Build 56 (issued last year; more info here: https://www.memoq.com/en/news/memoq-2015-build-56-released). Is your memoQ up-to-date? You might want to check for updates with "Look for updates" in the memoQ tab.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Maija Cirule Lettonie Local time: 12:47 allemand vers anglais + ...
AUTEUR DU FIL
My MemoQ is up to date
Oct 31, 2016
Tomás Cano Binder, CT wrote:
Apparently, the undue appearance of the error message you mention was fixed in Build 56 (issued last year; more info here: https://www.memoq.com/en/news/memoq-2015-build-56-released). Is your memoQ up-to-date? You might want to check for updates with "Look for updates" in the memoQ tab.
and the tips about the said error message I have found the same day when the problem emerged. Nothing helps, MemoQ promises to report this error to Kilgray's support service but they do not work on weekends and are extremely slow as regards fixing their bugs. Strange but the next file I exported in docx without problems.
Thank you, Tomas, for your time and effort.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
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.
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