Ayaka Ito 様

投稿いただき、ありがとうございます。
QA Checker 3.0の正規表現を用いて、検知することが可能かと存じます。

たとえば、[UI Word] という表現が原文にあったとして、こちらが全角の［］で訳文側に入力されていた場合、検証時にこのように警告が上がります。

Kiyotaka Tsuchida 様

ご回答いただきありがとうございます。
チェックしたいのは記号だけではなく、原文と訳文がともに記号をその中の文言が[UI Word]となっているか、なのですがそれも正規表現で指定、検知可能なのでしょうか。

Hi Paul Filkin,

Thank you for your advice. I have tried to write the regular expression using the Grouped search expression but it seems it didn't work. I know my RegEx source and target description doesn't match to the situation that I want to check.

I described as below but could you check it works or not?

Hi Ayaka Ito 

It would be helpful to have some example text you need to find, but in general I think your problem is that you are not using the Grouped Search expression correctly.  The idea is that you create your search pattern in the source as a backreference, so bracket it, and then call it in the target using the standard back reference mechanism.  For example this seems to be what you are trying to achieve:

I did that with this rule:

Hope that makes sense for you?

Hi Paul Filkin

Your suggestion perfectly works for my supposed situation. Thank you so much.

I created another rule for different symbol to check. However, it didn't work. The situation is below:

When you access <UI>Settings</UI>
Beim ersten Zugriff auf die <UI>Einstellungen</UI>

I made the following rule:

These rules will be used to the XML files and "<UI>" is a tag used in the XML files, which is added to my original XML file type settings as a parser. Does the QA Checker regular expression work for the tags of XML files or HTML files?

interesting

at the very first time, I saw you do not understand RegExp at all, so wrote correct one.
"(<UI>.+?</UI>)"

but, it never works.
because,
this "Verification > QA Checker > RegExp" has its own strange playground which I have never known,
just like you explained at the last comment, some of its part changed into Tags.

good luck to you.

[Edit]

I've tried some workarounds. It sucks. Because,
it never works with standard "Boundary" nor "sdlxliff Tag definitions".
There should be provided some other Tag rules. Or, it Really sucks.

I'm using my own QA tool (it's different from Verification/QA Checker, mine is much better)
And, In there, "(<UI>.+?</UI>)" works perfectly.

If, and only If, you are interested in that and if you use version 2017, I can make a tiny tool for you "QA Filter".
Sounds good, right ?

Price ?
There is no free lunch.
How much is the Big Mac combo in your country ? 

like this

RegExp check works only with translatable text, it won't catch anything what is a part of a tag itself.

However, for your purpose - checking that a tags present in source segment are also present in target segment - you don't need RegExp checker at all.
For this you simply use Tag Verifier and it will tell you if these is anything wrong with the tags:

Nice try
Unfortunately, your suggestion is one-eyed.

In my suggestion, the seg number 2
Be --> Bee
Is this Right or Wrong ? You never know.

Oh, and just in case you are looking for slightly different case - that the text in <UI> tags should not be translated - then you should have used a different approach and set up the file type so that the content of <UI> element is not translatable.
That way the entire content of the tag will be automatically carried over from source to target and you don't need to care about extra QA checks.