Highlight errors in OmegaT QA (originally, check_rules.groovy)

The free computer aided translation (CAT) tool for professionals

Brought to you by: alex73, amake, brandelune, briac_pilpre, and 9 others

#1001 Highlight errors in OmegaT QA (originally, check_rules.groovy)

Milestone: 4.0

Status: closed-fixed

Owner: Aaron Madlon-Kay

Labels: scripts (9)

Priority: 5

Updated: 2018-04-07

Created: 2014-06-13

Creator: Roman Mironov

Private: No

Suggest implementing this best practice as another step towards powerful QA within OmegaT.

Example of an error highlighted in an external QA program (Verifika):

1 Attachments

2014-06-13 12-37-32 Report.png

Related

Feature Requests: ~~#1153~~
Feature Requests: ~~#1271~~
Feature Requests: ~~#717~~

Discussion

Didier Briel - 2016-09-13

status: open --> closed-out-of-date
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2016-09-13

As this will be provided by the Issue window (https://sourceforge.net/p/omegat/mailman/attachment/CAHvKJZvycjqAx5S-%2Bwf4vw2uMsUnV5NXWaZnYYPQY6oi2MKP6w%40mail.gmail.com/2/, https://omegat.ci.cloudbees.com/job/omegat-prototype/51/), I close as "out of date".

Didier

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kos Ivantsov - 2016-09-13

May I suggest to change it to open-fixed, maybe with a minor edit in title? I think the RFE isn't about the script per se, but rather about QA functionality in OmegaT.

--
Kos

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Didier Briel - 2016-09-14
  
  OK, changed. Currently, the feature is not yet included in /trunk.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2016-09-14

status: closed-out-of-date --> open-fixed

Group: 3.1 --> 4.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kos Ivantsov - 2016-09-14

summary: Highlight errors in the check_rules.groovy output --> Highlight errors in OmegaT QA (originally, check_rules.groovy)

assigned_to: Aaron Madlon-Kay
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2016-09-26

RFE [#1271] is now in /trunk.

Didier

Related

Feature Requests: ~~#1271~~

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2016-10-03

status: open-fixed --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2016-10-03

Implemented in the released version 4.0.1 of OmegaT.

Didier

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Konstantin - 2018-04-07

I just stumbled upon this (quite old) discussion and I am quite surprised, because I never saw any highlights when using the script "QA-check rules".
Did I miss something? I mean, like special settings somewhere.
I am always using the latest version, currently the 4.1.4
I'll be gratefull for any hint, thank you.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Didier Briel - 2018-04-08
  
  The highlight is not in the script, it's in "Issues": Tools > Check issues.
  
  Didier
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.