The 2nd and 3rd results are caused by the PDFs not having Unicode maps (required for text conversion) built-in with the fonts. The PDF plugin contains the correct maps, it just isn't selecting the right one (it has to guess).
This has been fixed for all known font examples (there may be others we're unaware of). An appliance update will be available later this week that addresses this.
This has been fixed for all known font examples (there may be others we're unaware of). An appliance update will be available later this week that addresses this.