How to catch missing punctuation signs in target language

General Discussion
1

Hello there.
Nice to virtually meet all of you. I am new to this forum.
I have a question about customized checklists.
How can I create a checklist that tracks missing punctuation signs, in particular end-of-sentence periods in the target language?
Please let me know.
Thank you so much.
All the best,
Laura

2

Hi Laura,

To find segments with missing period at the end, use the following search:

Source: \.[:space:]*$
Target: -\.[:space:]*$

Search mode: Regular Expressions
PowerSearch: On.

To track any missing punctuation signs at the end of the segment, this search should help you:

Source: ([:punct:][:space:]*)=1$
Target: -@1$

Search mode: Regular Expressions
PowerSearch: On.

Please note that the second search looks for the same punctuation sign (but missing) in target.

Regards,
Oscar.

3

Hello Oscar,

Thank you for this information. It is greatly appreciated. Do you know if we could run this search automatically for each project we work on?

Please let me know.

Thank you so much.

All the best,
Laura

Outlook-rqdpn3qa.jpg

4

Hi Laura,

Instead of adding the entries to a project checklist, create a checklist and add it as a personal checklist at the Checklist Manager tab. Then, the checklist will be available for all your projects.

When running QA, click Run Personal Checklist and select that checklist.

A different way would be to create a base Xbench project per product or customer and add the checklist as a project checklist. When checking a new project of that product, add your ongoing translation files to a copy of the base Xbench project and check ongoing translation.

Regards,
Oscar.

5

Thank you Omar,

Very useful and greatly appreciated.

All the best,
Laura

Outlook-rqdpn3qa.jpg

6

Hello Òscar,

When trying to use the second search, I get an error in source: Incomplete expression.

Thanks,
Tarik

7

Hi!
i am trying to create a rule that catches all target segment that have a different amount of punctuation marks than source, I used this expression:
Source: ([:punctuation:]+)=1
Target: -@1
Search mode: Regular Expressions
PowerSearch: On.

but it’s returning the error Source term error: Incomplete expression

can you help me?

Thanks in advance

Rita

8

When using variables as in ([:punctuation:]+)=1 together with PowerSearch, the string must be entered between quotation marks as in "([:punctuation:]+)=1". Then Xbench will perform the search.

9

Hi Martin!

thanks a lot for the quick response, that worked! but it seems to be stopping at the first instance of punctuation, I need to check them all, no matter how many are in the source I need to know if it’s the same in target.
Grateful for any further help

Rita

10

The following search should work to check the first two punctuation marks of a sentence. You can check up to nine.

Source: "([:punctuation:]+)=1[^[:punctuation:]]+([:punctuation:])=2"
Target: -@1 OR -@2
Search mode: Regular Expressions
PowerSearch: on.

11

Hello @omartin

I have a EN to JP project and I used the last regexp that you provided… However it seems to be returning all segments, including those where the JP equivalent punctuation mark has been used. I want the result to show only those segments where there is a mismatch of trailing punctuation marks… Hope to hear from you soon.

Regards,
Ruzaan

13

@ruzaanb Please note that [:punctuation:] special set matches any of the following characters ! “ # % & ‘ ( ) * , - . / : ; ? @ [ ] _ { } ¡ « - · » ¿. However, Japanese or Chinese punctuation characters are not included.

This search should be adapted to include those characters in target.