title: Does the PhraseMatcher in Spacy still work for wrong tokenization?
body: <p><a href="https://spacy.io/usage/rule-based-matching#phrasematcher" rel="nofollow noreferrer">https://spacy.io/usage/rule-based-matching#phrasematcher</a></p>
  <p>For this example:</p>
  <pre><code>    nlp = spacy.load(&quot;en_core_web_sm&quot;)
  matcher = PhraseMatcher(nlp.vocab)
  terms = [&quot;Barack Obama&quot;, &quot;Angela Merkel&quot;, &quot;Washington, D.C.&quot;]
  # Only run nlp.make_doc to speed things up
  patterns = [nlp.make_doc(text) for text in terms]
  matcher.add(&quot;TerminologyList&quot;, patterns)
  
  doc = nlp(&quot;He lives in Washington, D.C. and Boston. &quot;)
  </code></pre>
  <p>The Doc says:</p>
  <pre><code>Since spaCy is used for processing both the patterns and the text to be matched, you won’t have to worry about specific tokenization – for example, you can simply pass in nlp(&quot;Washington, D.C.&quot;) and won’t have to write a complex token pattern covering the exact tokenization of the term.
  </code></pre>
  <p>The reason that 'Washington, D.C.' can be matched successfully against the text without worrying about the tokenization is because the tokenization of 'Washington, D.C.' is correct. Let's say if the tokenization is like this below:</p>
  <pre><code>['in', 'Washington', ',',  'D.', 'C. and', 'Boston', '.']
  </code></pre>
  <p>My question is, if 'C. and' is tokenized as one token, does the match of 'Washington, D.C.' still successfully?</p>