Eng>Jpn term correctly translated, but still reported in CheckMate

[Former user]

Original issue 265 created by polytrans2... on 2012-08-07T10:51:37.000Z:

What steps will reproduce the problem?
1. You add the ttx to a new CheckMate session, and specify the tab-delimited term files in Configuration
2. You check all, and you get the report term error.
3.

What is the expected output? What do you see instead?
That term is actually correctly translated in the file, but still reported.

What version of the product are you using? On what operating system?
Windows Vista 32 + CheckMate

Please provide any additional information below.

[Former user]

Comment [1.](https://code.google.com/p/okapi/issues/detail?id=265#c1) originally posted by @ysavourel on 2012-08-24T20:22:31.000Z:

[Former user]

Comment 2. originally posted by @ysavourel on 2012-11-08T16:39:06.000Z:

[Former user]

Comment 3. originally posted by @ysavourel on 2012-11-27T22:39:59.000Z:

Glossary entries are not being matched correctly when the source string contains "special characters." These special characters will need to be handled before doing the match. This appears to be an issue regardless of whether performing "term" or "string" based matching.

[Former user]

Comment 4. originally posted by @ysavourel on 2012-11-28T21:02:03.000Z:

Partial fix done by stripping the inline codes markers.
Needs work for multiple occurrences in source and not as many in target.

[Former user]

Comment 5. originally posted by @ysavourel on 2012-12-03T20:37:10.000Z:

Closing this issue and marking it as fixed.

Another issue (issue #295) has been opened for the cases where there are a mismatched number of source vs. target terms being matched.