Start a new topic

Alternative glossary entries trigger QA errors

If in a glossary there is more than one translation for a single source term, when running the QA's glossary terms check CTE triggers a QA error. 


Why? Is this by design, perhaps?


I can confirm it only if the target language alternatives are in separate entries in the glossary. Then, CafeTran displays the QA error with the unused alternative. However, since another target term is used the program's QA function should not flag the source language term at all. To be improved possibly in the coming update.

Here, the glossary QA error is triggered (also) by ";"-separated entries such as "xxx;yyy;www". 

>Here, the glossary QA error is triggered (also) by ";"-separated entries such as "xxx;yyy;www".  


Never observed that!

>I can confirm it only if the target language alternatives are in separate entries in the glossary. Then, CafeTran displays the QA error with the unused alternative. 


That's exactly how it should be. I use this to clean up my glossary during QA: I either add the flagged target term with a semicolon to the term pair with the correct/desired target term (and then remove the flagged term pair), or I directly remove the flagged term pair, since it is wrong.


>However, since another target term is used the program's QA function should not flag the source language term at all. To be improved possibly in the coming update.


Please don't change this. It's perfect as it is.

In my opinion, the QA tool should be used to check the ongoing translation, not to clean up glossaries, although I recognize that it might be useful for this purpose too in certain cases. For cleaning up glossaries, a different tool such as Ron's Editor or a properly-featured general-purpose text editor for other OSs would be a more practical solution.


I was mainly referring to cases when for a single source term there might be the need for multiple alternative translations such as in "xxx;yyy", although I even find that sometimes I need completely separated entries for the same source term.


I don't know in other language pairs, but in mine it makes a lot of sense to have multiple translations available for one single source term, and being presented with lots of false errors during the QA process, particularly with very long documents, is irritating, distracting and time consuming.


How are other CAT tools handling this situation?

> Here, the glossary QA error is triggered (also) by ";"-separated entries such as "xxx;yyy;www".  

> Never observed that!


Have you tried? It's happening here, and I don't think I have a special edition of CTE, or do I?

 

Demo: https://youtu.be/DPFEaOVYfYw


First I have every term pair in a separate row: alternative targets are flagged, as they should be.


Then I have all target terms merged per corresponding source term: alternative targets are not flagged, as should be.

>In my opinion, the QA tool should be used to check the ongoing translation, not to clean up glossaries, although I recognize that it might be useful for this purpose too in certain cases. 


Luckily, multiple workflows / approaches are possible with CafeTran Espresso.


>For cleaning up glossaries, a different tool such as Ron's Editor or a properly-featured general-purpose text editor for other OSs would be a more practical solution.


The USP of CafeTran Espresso for me is the ability to constantly optimize my glossaries during work, with the full context available. YMMV, of course.

> the QA tool should be used to check the ongoing translation, not to clean up glossaries.


Agreed.


> multiple workflows / approaches are possible with CafeTran Espresso.


 The QA option has been added in 12.0.3 update (see Preferences > QA tab) to flag duplicate glossary entries during the terms consistency check.

Thank you for making this an option and not simply default behavior.

The QA option has been added in 12.0.3 update (see Preferences > QA tab) to flag duplicate glossary entries during the terms consistency check.


Many thanks for fixing this so quickly. Just one question: I am about to finish a huge translation and I would like to use the new build for the glossary term QA. Would it be safe to update to the latest build after the translation is finished and before the QA?


 

There have been no changes to filters between 12 and 12.0.3 updates so the latest update should not cause any issues with the export if you use CafeTran 12. Anyway, with big projects I always recommend making (and saving) partial exports right before updating and later at some intervals during your progress, just in case.

Thank you for the confirmation. I am an export and back-up maniac!

Login to post a comment