Tags (and/or references) preclude glossary recognition Thread poster: Nicolas Gambardella
|
Hello caffeine addicts, I have a recurring problem in CTE. When an expression in the source segment is followed by a reference, it is not recognized and the corresponding entry is not shown in the glossaries. For instance, if I have prophylaxis11 which correspond in the source document to the word "prophylaxis" followed by a 1 in superscript (reférence to a bibliographic item) The entry "prophylaxis" of my medical glossary does not show up.... See more Hello caffeine addicts, I have a recurring problem in CTE. When an expression in the source segment is followed by a reference, it is not recognized and the corresponding entry is not shown in the glossaries. For instance, if I have prophylaxis11 which correspond in the source document to the word "prophylaxis" followed by a 1 in superscript (reférence to a bibliographic item) The entry "prophylaxis" of my medical glossary does not show up. Is there any way to tell CTE "consider tags as spaces and identify the bits in-between", or something similar? Best. ▲ Collapse | | | Longtime request | May 16, 2020 |
Nicolas Gambardella wrote: Is there any way to tell CTE "consider tags as spaces and identify the bits in-between", or something similar? This has been a longtime request from Torsten, an enthusiastic user of CafeTran Espresso, who past away too soon, last year. If you have really, really many of these superscripts (or any other combinations of terms with surrounding tags preventing term recognition), you can use a bilingual table as a workaround: Add the pipe to this field: In the bilingual table, propagate the second column and hide the first one. Select the second column and remove the red colour from the pipes (select column, assign font colour Red, then change to Automatic). Create a new project from the bilingual table. Now the term is being recognised: As you can see: a lot of steps, that are only worthwhile in large projects.
[Edited at 2020-05-16 11:11 GMT] | | | Igor Kmitowski Poland Local time: 02:44 Member (2016) English to Polish + ... Prefix matching | May 16, 2020 |
Hello Nicolas, To improve terms recognition, try to activate the prefix matching in Edit > Preferences > Glossary tab. Check if it helps after restating CTE. | | | Introducing fuzziness | May 16, 2020 |
Igor Kmitowski wrote: Hello Nicolas, To improve terms recognition, try to activate the prefix matching in Edit > Preferences > Glossary tab. Check if it helps after restating CTE. Note that this will introduce fuzziness in term recognition. Maybe you don’t want that, if you rely heavily on auto-assembling.
[Edited at 2020-05-16 13:39 GMT] | |
|
|
Nicolas Gambardella United Kingdom Local time: 01:44 Member (2019) English to French + ... TOPIC STARTER
Thank you guys. For the time being, Igor's solution works well. I will keep in mind the fuzziness going forward and be attentive to the impact on auto-assembly. | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Tags (and/or references) preclude glossary recognition 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! » |
| Trados Studio 2022 Freelance | The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |