Search misses some occurrences

Question

Dear Paul, 
 Translating into French, I very often have to run a general search and replace for apostrophes just before delivery to comply with the instructions: curly or straight. 
 Lately, I was told that in one of my projects wrong apostrophes were found, and I naturally assumed that I had made a mistake (like making edits after the apostrophe check or something else). 
 So I was a bit shocked by what I discovered by chance in a project yesterday : 
 
 After a replace of straight quotes with curly quotes, SDL reported that it found nothing. A search backwards reported the same. All looked fine and ready to be delivered with only curly quotes. 
 But then I saw a segment which still contained one straight quote. I rerun the search, it still found nothing. 
 Thinking that it might be a different character than the straight quote Alt 39 and the curly quote Alt 0146, I even copy-pasted the d' into the search field. It still did not find it! The search did not find the character(s) that I just grabbed from the text itself ! 
 
 I am wondering how this can happen, and how I can be sure to deliver a file with only curly quotes when the search cannot detect all of them. This happened in Studio 2017 SR1 14.1.10015.44945 (the latest). 
 
 To help you analyze the issue, I have three screen captures demonstrating the unsuccessful search, as well the bilingual file in which the issue occurred. Unfortunately I cannot upload them here since that would make them public to everyone, but I will gladly provide these files. I uploaded one of the 3 screen captures but hid all the content.

Jesús Prieto · Answer

Hi Philip,

I can repro your issue in Studio 2019.

It doesn't found this apostrophe:

Screenshot of Trados Studio showing text 'Dans l'aide d' with a highlighted 'component' tag.

But it does this one:

Screenshot of Trados Studio with an error highlighting a missing apostrophe in 'Dans l'aide d' before the 'component' tag.

I attach a sample XML for SDL to fix the what-I-think-is-a-bug.

Fullscreen apostrophe.xml Download

<?xml version="1.0" encoding="UTF-8"?>
<letter>
<salutation limit="40">Dear Daniel,</salutation>
<text>We especially like the Dans l’aide d'<component translate="yes">XML Parser rules</component>
options in the <component translate="no">XML</component> filter.
We especially like the Dans l’aide d' <component translate="yes">XML Parser rules</component>
options in the <component translate="no">XML</component> filter.
</text>
</letter>

PS.: In the XML I needed to declare the element component as not-translatable (with locks in the Editor), because otherwise, everything works fine.

Paul Filkin · Answer

Philippe Noth , Jesús Prieto 
 This one is already logged as CRQ-15073 for your reference. I'm not sure what priority it will receive as it's been a known issue since 2015, but we can raise the profile again and I'll let you know if it can be addressed in an update. When these things come up we try to fix them in the apps that may offer a good workaround such the SDLXLIFF Toolkit. Worth checking it out... I haven't tested it specifically yet, but I think (hope) we may have addressed this one already. If not then we will do.

Paul Filkin · Answer

Philippe Noth 
 Philippe Noth said: I am not a big fan of the interface - not only visually but also functionally : for example, I could not search the apostrophe in unlocked segments without creating an intermediate SDLXLIFF file first, the tabs seem to work independently. 
 Thank you... I'm surprised this never came up before as it seems quite an obvious omission. I'll review this with the appstore team and improve this so we have more options around which segments to search/replace in. I think the tabs should remain independent as this wouold get confusing, but there should be more options.

Trados Studio > 1. Trados Studio

Search misses some occurrences