[[TF-dev]] Re: [[TF-dev]] "fuzzy matches" option in OpenCTI - Re: ru translation for installer/nbi and "\n" in messages

Hi Petra,

Petra Stastna wrote:
> Hi Dmitry,
>
>> Let me work on the TMX conversion issue and find out if it can be fixed.
>>>>
>>>> It looks like OmegaT and OpenCTI (and old Sun`s CTI) uses different 
>>>> splitters of the messages been translated. In particular, "\n" is 
>>>> been handled inappropriately.
>>>> As the result, there are a lot of messages shown as not translated 
>>>> in OpenCTI but which are, in fact, translated (included in TMX) and 
>>>> corresponding translation is already pushed to main/l10 repository. 
>>>> So, what can we do with that? I am not eager to do manual "monkey" 
>>>> work of finding the translation using OmegaT and putting it in CTI 
>>>> for each not-translated message :
> This is just to confirm that I am communicating with our tech team on 
> a possible solution.
>
> In the meantime, I am not sure if you are aware of the "*fuzzy 
> matches*" option - let me explain:
>
> When you are in OpenCTI Editor and you are on a string, you can click 
> on the right-hand side on the *+ sign*. A *tools *window opens (if it 
> is too small, just expand it, then click on the *- sign* and then 
> again on the *+ sign*, the expanded window will open). In this *tools 
> *window, you can see "fuzzy matches" - i.e. for example 50% matches of 
> the currently opened string.
>
> Find attached screenshots with some examples.
>
> I know you do not want to do any monkey or repetitive work, but if you 
> will, this might be some kind of solution to find the appropriate 
> translated strings.
>
> All you need is to double click on the appropriate string in the 
> *tools *window and it gets copied automatically into the editor string.
Thanks for the tip! It is really the thing what I was looking for :)

Dmitry
>
> Thanks,
> Petra
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>