Can you please list some examples (source and target) that should be found as errors and also counter examples that should not be found as errors?

I assume that "TODAY" is a variable text and so it will probably come down to developing a checking macro that compares, for example, the number of capitalized words in source text and translation independently of the text.

Hello Achim Herrmann ,

yes, you're right. "Today" has only been a variable text as a placeholder for a product name.

Let me try to explain a little deeper. For example, I'd like to check, if the target string contains "TODAY" instead of "Today" or "today", if "TODAY" (or even "Today") is part of the source string. The use of this shall be, to be able to check if product names are spelled correctly in the target strings. Independent how they were spelled in the source string.

In the meantime, I've added the word to a MultiTerm database, both, with the correct and the erroneous spelling. The spelling with upper and lower case has been marked as "forbidden".
Unfortunately, this check doesn't seem to recognize the misspelled word as "forbidden", too.

Are my thinkings about this wrong? Should I use "inline tags" for this purpose? And if so, how to set them up correctly to achieve this goal?
Entering a product name, written in capital letters in the inline tags configuration, leads to a lot messages that the product name has been found in the target, but not the source string.
Would it be possible, to hide these "false" positives? Maybe, this could be a solution for us.

Thank you very much for your further information.

Best regards and have a great day.
Nils

Please try the Inline Pattern function.

and insert your product names. Please be aware that this won't work performant enough, if you have 150 product names in your expression and very long segments. I'm mentioning this, because we had such a case in the past. Each string in this expression needs to be matched against your source and target segments, which might take some time.

Hello Achim Herrmann ,

thank you very much for your hint about the inline pattern function. That's, what I've ment with "inline tags" in my last post.
This seams to work. Even if it lists strings, where the spelling in the source strings is wrong, but in the target string is correct. It would be nice, if there were an option, to only check the target strings or just hide results, where the number of matches in the source is 0 but in the target is > 0.

Could you please be so kind to let me know, what the "Text of matches must be the same" option does? Unfortunaltely, I can't find any further information on that in the documentation and I don't see any difference in the results, using this option or not.

And does it make any difference, if I'm adding all product names into one single inline pattern or if every product name gets its own inline pattern, regarding the performance?

Thanks in advance for your reply and your further information.

Best regards
Nils

Usually the Inline Pattern feature is used to markup placeholders and the corresponding RegEx will be created a generic way, like markup all double curly bracketed placeholders.

The option "Text of matches must be the same" ensures that translators don’t change the inner text of a placeholder. If this was done an error will be reported.

 Regarding the performance question, I would suggest having one single pattern, assuming that you don’t have many product names.

Usually the Inline Pattern feature is used to markup placeholders and the corresponding RegEx will be created a generic way, like markup all double curly bracketed placeholders.

The option "Text of matches must be the same" ensures that translators don’t change the inner text of a placeholder. If this was done an error will be reported.

 Regarding the performance question, I would suggest having one single pattern, assuming that you don’t have many product names.

Good morning Achim Herrmann ,

thank you very much for your further clarification. As far as I have tested so far, using the Inline Patterns is a good way to go.
I think, I still have a lot to learn about Passolo...

Thank you very much for your support.

Best regards and have a nice day.
Nils