UNPAIRED_BRACKETS - no rule.match for Obere Anführungszeichen

m1chael · April 10, 2017, 3:25pm

I have a problem where if I had a german sentence like

Die Bezeichnung „Representational State Transfer soll

without the Obere Anführungszeichen then it will correctly throw an error (i.e. unpaired bracket). However, at the line 664 in JLanguageTool.java

RuleMatch[] thisMatches = rule.match(analyzedSentence);

it will not add anything to this.Matches, unlike other rules.

Is there anything I can do so that it finds this rule?

dnaber · April 10, 2017, 4:55pm

I’m not sure if this is your question, but this is a text-level rule, its match is created here:

github.com

languagetool-org/languagetool/blob/master/languagetool-core/src/main/java/org/languagetool/JLanguageTool.java#L970


      
                                           @Nullable Long textSessionID, List<String> sentences, List<AnalyzedSentence> analyzedSentences) throws IOException {
          RuleSet rules = getActiveRulesForLevel(level);
          if (printStream != null) {
            printIfVerbose(rules.allRules().size() + " rules activated for language " + language);
          }
          
          
List<RuleMatch> remoteMatches = new LinkedList<>();
          List<FutureTask<RemoteRuleResult>> remoteRuleTasks = null;
          
          
List<RemoteRule> remoteRules = rules.allRules().stream()
            .filter(RemoteRule.class::isInstance).map(RemoteRule.class::cast)
            .collect(Collectors.toList());
          
          
long remoteRuleCheckStart = System.nanoTime();
          // map by sentence index, as the same sentence can be repeated multiple times in a text
          // -> need to distinguish offsets / matches
          Map<Integer, List<RuleMatch>> cachedResults = new HashMap<>();
          Map<Integer, Integer> matchOffset = new HashMap<>();
          // store actual request sizes (i.e. without cached sentences), so timeouts and metrics are calculated correctly
          List<Integer> requestSize = new ArrayList<>();
          ExecutorService remoteRulesThreadPool =

m1chael · May 4, 2017, 3:16pm

Thanks for the reply. I just updated to standalone version 3.8 and this seems to have the fixed the problem. Good work