#1271 Add UI for checking all translation issues

[Aaron Madlon-Kay]

OmegaT can check for

• Tag problems
• Spelling mistakes
• Grammar, typography, etc. issues (via LanguageTool)

But only tags have a UI that aggregates all such issues for an entire project. Outside of scripts, there is no way to check spelling or LanguageTool issues for the entire project.

With this RFE I have implemented a new "Issues" window that aggregates all of these. It replaces the Tag Validation window, and supports all of its features except for "fix all tags".

For supported issue types, users can perform relevant actions from within the Issues window such as adding words to the spelling dictionary, applying tag fixes, etc.

Issue types can be enabled and disabled via the Issues window's Options menu. In particular, checking LanguageTool issues can be slow on large projects, so users concerned with checking speed should consider disabling it.

There is also an interface for adding custom issue types: supply an instance of IIssueProvider to IssueProviders.addIssueProvider() (omegat.ci.cloudbees.com). This can be done via a Java plugin or via a script; see issue_provider_sample.groovy (sourceforge.net) for a sample implementation. Issue scripts can be placed in scripts/application_startup to ensure availability on launch.

[Aaron Madlon-Kay]

This is available in trunk.

[Aaron Madlon-Kay]

This addresses [#717] and [#1001].

[Aaron Madlon-Kay]

With [#608], LanguageTool rules can also be disabled from within the Issues window.

[Didier Briel]

Implemented in the released version 4.0.1 of OmegaT.

Didier