title: Different Font versions of Tahoma on Win7/10?
body: <p>I have a Win7(64bit) machine that renders a text in a Java application with squares instead of ligature-ff (Unicode FB00) and ligature-ffi (Unicode FB03) if using Tahoma as a font. The same application renders the same chars perfectly in Tahoma under Win10. </p>
  
  <p>Using charmap i discovered that there is indeed no such char in Tahoma (Win7), while it exists on Win10-Tahoma. </p>
  
  <p>BUT Word, and an older version of my app (using Java 8 instead of 11) on Win7 at least use the ligatures from other fonts instead (Word:Cambria Math, OldApp:ArialUnicodeMS), which is why it never stood out to me before.</p>
  
  <p>Windows7 has Tahoma 5.22, while Win10 has Tahoma 6.9 - i didn't know those were held at different versions (why?). </p>
  
  <p>Anybody up to explaining the different behaviours in replacing unknown chars (get them from another font vs. render them as squares)? Microsoft has a systemwide Fallback font, but as IE, Word and N++ all handle the rendering of Tahoma + ligature-ff differently, that does not seem to do much.</p>