I think instead of making a separate window, we could have _all_ the automated checks in one window. That would greatly ease navigation.
Since we have a pane based display in the main OmegaT window, we could have a similar pane based display for checks: one pane for tags, one for glossary items, one for each check category that we have.
Also we can use the log that displays information live to indicate which errors are found in the active segment, when entering the segment. That would be better than using an alert window. The log can be implemented a pane of the main window so that it can be non intrusive while move to a practical position.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've recently seen the power of the translate-toolkit. It does checking on PO files, but it has a nifty TMX2PO and PO2TMX converter that doesn't break the project_save.txm. The toolkit is written in Python.
Samuel: plus the toolkit is in python so if OmegaT is "extended" with JPython or something like this it would be possible to re-use that code I suppose. ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
--- old+++ new@@ -1,3 +1,3 @@-This was already proposed in RFE 1500809, which is being broken in smaller ones.+This was already proposed in [#190], which is being broken in smaller ones.Checks for glossary consistency in a window similar to tag validation.
This is available as "Terminology Issues" in the Issues window. The following settings from Preferences > Glossary are respected when computing matching/missing terms:
Use terms appearing separately in the source text
Use stemming for glossary entries
When stemming is enabled, the quality of term recognition depends greatly on the tokenizer used; if your language's Lucene tokenizer doesn't give good results, try HunspellTokenizer (be sure to install an appropriate spelling dictionary).
Logged In: YES
user_id=915082
Originator: NO
I think instead of making a separate window, we could have _all_ the automated checks in one window. That would greatly ease navigation.
Since we have a pane based display in the main OmegaT window, we could have a similar pane based display for checks: one pane for tags, one for glossary items, one for each check category that we have.
Also we can use the log that displays information live to indicate which errors are found in the active segment, when entering the segment. That would be better than using an alert window. The log can be implemented a pane of the main window so that it can be non intrusive while move to a practical position.
Logged In: YES
user_id=168045
Originator: NO
I've recently seen the power of the translate-toolkit. It does checking on PO files, but it has a nifty TMX2PO and PO2TMX converter that doesn't break the project_save.txm. The toolkit is written in Python.
After converting to PO, a number of tests can be run on it:
http://translate.sourceforge.net/wiki/toolkit/pofilter_tests
I'm sure these tests can be extended to include other tests.
The toolkit is here:
http://translate.sourceforge.net/wiki/toolkit/index
Logged In: YES
user_id=915082
Originator: NO
Samuel: plus the toolkit is in python so if OmegaT is "extended" with JPython or something like this it would be possible to re-use that code I suppose. ?
Diff:
Related
Feature Requests: #190
This is implemented in trunk, r9940.
This is available as "Terminology Issues" in the Issues window. The following settings from Preferences > Glossary are respected when computing matching/missing terms:
When stemming is enabled, the quality of term recognition depends greatly on the tokenizer used; if your language's Lucene tokenizer doesn't give good results, try HunspellTokenizer (be sure to install an appropriate spelling dictionary).
Related
Feature Requests:
#1271Implemented in the released version 4.1.2 of OmegaT.
Didier