concordance search (F3) is not working as expected

Dear Community,

 I have a problem with concordance search for some words.

As you can see it is " DİYABETİK" in 18th segment in source side.

But an f3 concordance search is not giving any results, although the TM consist of the TUs like :

EKSTRA GELENEKSEL DİYABETİK AHUDUDU REÇELİ

EKSTRA GELENEKSEL DİYABETİK BÖĞÜRTLEN REÇELİ.

Similarly ;

The case is also the same for the words like:

It is "ALIÇ " in 18th segment in source side.

But an f3 concordance search is not giving any results, although the TM consist of the TU as "Alıç Püresi". Do you think it is because of the case sensitive? Or is there any option for case choice here?

 The Project of the Case

The setting for search is minimum for one word. But it is not giving any solution as well.

 Can you have a look to see that..

 Many thanks,

 Bahar

  • Hello Bahar,

    This looks like a bug to me.  It's not related to case specifically though.  For example if you select all the text in segment #20 then it finds it all fine.  Also if you confirm the translation for segment #18 and then try a concordance you'll see it finds it, like this (ignore the translation I just copied any text in target for the test):

    To explain the problem try another concordance with lower case and you get this:

     

    However, note that I had to fudge this because I found another bug.  Very interesting problem you have here!  If I search for pure lowercase then nothing is found at all in this case.  The reason is because if the letter "i".  Upper case "i" retains the dot, so like this "İ", but Studio won't recognise this at all if I just use a lowercase "i".  So my example above uses lowercase apart fro  the "i"'s.

    So, to summarise there are two problems here:

    1. If you try to concordance an uppercase word that is in the middle of a sentence then nothing is found, and
    2. Studio doesn't handle the special characters used in Turkish for the letter "i"

    I guess there could be more letters like this, but that's a job for a proper QA engineer to figure out ;-)  I'll log this with development as a bug.

    Thanks you reporting this.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Yes,
    Thank you so much now for your answer..
    So I am now very happy to contribute to you..
    I wait the problem to be fixed. But is there any way that I can know when it is fixed?
    Thank you,
    Best Regards ,
    Bahar
  • Hi Bahar,

    If you have a support contract then I believe you will get more personalised updates on when things are fixed. If you don't then your best bet is to check the release notes every time we get a new update.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub