Thomas CORDONNIER

No progress right now, I am not working on this for the moment. And as I said about the other problem, there is always the risk that solving problem for Excel has side effect on Word or vice-versa (they share the same parser class). Maybe I will need to write two separate classes... when I have time.

@miurahr9 unless the message from 2025-02-24 is not clear, actually I could only make a diagnostic, not find a solution. For the moment my attempts to solve this had side effects on other Excel files, reason why I cannot publish anything

No. This ticket is about a bug in the StaX filter which prevents reading some Excel files correctly. We had together agreed to inactivate the filter for Excel files until I find a solution but this is another ticket, whose number I don't remember. This other ticket is probably closed, while the current one is still open. For the moment I did not find a correct solution, I had implemented something but then the correction impacted Word files. So, I could not publish it as a pull request. It seems...

No. This ticket is about a bug in the StaX filter which prevents reading some Excel files correctly. We had together agreed to inactivate the filter for Excel files until I find a solution but this is another ticket, whose number I don't remember. For the moment I did not find a correct solution, I had implemented something but then the correction impacted Word files. So, I could not publish it as a pull request. It seems that the Excel format is a little bit different from other OpenXML. And more...

There is no such feature in OmegaT that penalty-<num> reconize NUM to set penalty score.</num> This is wrong, the feature exists in FindMatches: private static final Pattern SEARCH_FOR_PENALTY = Pattern.compile("penalty-(\\d+)"); To activate it, you must create a directory with the number in the name, for example tm/penalty-10 That is a little bit strange that your search does not find SEARCH_FOR_PENALTY in FuzzyMatches, I don't know why. In any case creating a constant PENALTY_TM = "penalty-xxx"...

There is no such feature in OmegaT that penalty-<num> reconize NUM to set penalty score.</num> This is wrong, the feature exists in FindMatches: private static final Pattern SEARCH_FOR_PENALTY = Pattern.compile("penalty-(\\d+)"); To activate it, you must create a directory with the number in the name, for example tm/penalty-10 That is a little bit strange that your search does not find SEARCH_FOR_PENALTY in FuzzyMatches, I don't know why. In any case creating a constant PENALTY_TM = "penalty-xxx"...

There is no such feature in OmegaT that penalty-<num> reconize NUM to set penalty score.</num> This is wrong, the feature exists in FindMatches: private static final Pattern SEARCH_FOR_PENALTY = Pattern.compile("penalty-(\\d+)"); To activate it, you must create a directory with the number in the name, for example tm/penalty-10 That is a little bit strange that your search does not find line 97 in FuzzyMatches, I don't know why. In any case creating a constant PENALTY_TM = "penalty-xxx" and even a...

There is no such feature in OmegaT that penalty-<num> reconize NUM to set penalty score.</num> This is wrong, the feature exists in FindMatches: private static final Pattern SEARCH_FOR_PENALTY = Pattern.compile("penalty-(\d+)"); To activate it, you must create a directory with the number in the name, for example tm/penalty-10 That is a little bit strange that your search does not find line 97 in FuzzyMatches, I don't know why. In any case creating a constant PENALTY_TM = "penalty-xxx" and even a...